Skip to main content
Solved

Executing a task through a HTTP POST (Indicium)


Rene Willems
Apprentice

I’m trying to execute a task through an HTTP POST request

I’m getting a HTTP 200 response, but it looks that the task has not been executed actually.

What I'm I doing wrong?

See: https://docs.thinkwisesoftware.com/docs/indicium/api

 

Best answer by Rene Willems

I worked. The problem probably was that the given task was 'TABLE task’ which normally is executed through the GUI. Thanks!

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

10 replies

Forum|alt.badge.img+17
  • Moderator
  • 761 replies
  • November 3, 2021

What does the task do and how did you conclude it did not work? 


Rene Willems
Apprentice
  • Author
  • Apprentice
  • 7 replies
  • November 4, 2021

This task is a trigger within a process flow that performs an HTTP GET and stores the results in the database of the application. The call is also registered in this application. This way I can find out that the call didn't take place.

 

 


Forum|alt.badge.img+17
  • Moderator
  • 761 replies
  • November 4, 2021

Does the first decision node log anything? If not could you add some kind of logging to this decision node to check if this is executed. And Can you execute this flow from the GUI without problems? 
Can you also check the indicum log for any additional information? 


Rene Willems
Apprentice
  • Author
  • Apprentice
  • 7 replies
  • November 4, 2021

There are two ways in which we can execute this task. First, through a ‘table task’ and second through a scheduled task (which runs at 01.00 am). In both situations this will be logged in a custom made component. See screenshot: 

By means of this screen I can conclude that the call (mentioned above) doesn't work.


Rene Willems
Apprentice
  • Author
  • Apprentice
  • 7 replies
  • November 4, 2021

There is nothing logged in the Indicium logfile about this issue

 


Forum|alt.badge.img+17
  • Moderator
  • 761 replies
  • November 4, 2021

Can you add some logging to the first decision node? Just to check if the flow get’s to that point? My first instinct would be that for some reason the red arrow is executed and the fow does not even reach the point of the http connector. Since the decision node is the first node in the green route it would be great to have some logging there. 


Rene Willems
Apprentice
  • Author
  • Apprentice
  • 7 replies
  • November 8, 2021

How can I add ‘logging’ to the first node (of type ‘descision’)? And to what source will it be logged?


Forum|alt.badge.img+17
  • Moderator
  • 761 replies
  • November 8, 2021

Looking again at your request I think you have to make some adjustments. First you need to call the process flow and not the task from postman. Second the task will not work in a system flow. Is this a placeholder task? Then just remove it from the flow. If the task actually does something then replace it with a decision node (2021.2 and lower) or a system task (2021.3). 


Rene Willems
Apprentice
  • Author
  • Apprentice
  • 7 replies
  • November 8, 2021

Ok, I will take a look at it. Thanks


Rene Willems
Apprentice
  • Author
  • Apprentice
  • 7 replies
  • Answer
  • November 8, 2021

I worked. The problem probably was that the given task was 'TABLE task’ which normally is executed through the GUI. Thanks!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings