After a record has been changed (by a user or directly on the database), the changed data must be forwarded to an API. In the update trigger of the relevant table, a task is called that collects the data and converts it to JSON. In a process flow with the above task of process action type "Start task" as starting point, which then passes the data to an "HTTP connector" that calls the API. When a record is changed, the task is activated by the trigger, but the process flow is never started. How do I get the process flow started, what am I overlooking?
Solved
Process flow does not start with "start task"
+1- Sidekick
- 11 replies
Best answer by Erwin Ekkel
No, a trigger can never be a starting point for a system or process flow. Your best bet would be to have the trigger fill a staging table and create a system flow that polls ever 5 minutes (or whichever interval you like) if there is data in the table.
This topic has been closed for replies.
You can’t activate a process flow from a trigger. Either create a system flow that polls if there is anything to send. Or make a process flow with a task and have the task handle the changes to the tables with the next step being the HTTP connector.
+1- Sidekick
- 11 replies
Hi Edwin,
Thank you for your response. Can the proposed system flow have an "Execute sytem task" called from the trigger as its starting point? And will this be picked up and handled by Indicium?
No, a trigger can never be a starting point for a system or process flow. Your best bet would be to have the trigger fill a staging table and create a system flow that polls ever 5 minutes (or whichever interval you like) if there is data in the table.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.