Activity Chaining

RE: Activity Chaining

EugeniaYoung — Tue, 13 Feb 2024 04:51:12 GMT

Thanks for the info, I also want to know it.

RE: Activity Chaining

Abhay Dalsaniya — Tue, 06 Feb 2024 20:19:43 GMT

Few more:

- Using chaining you can override assignment for the next attended activity even if the current user is not an assignee.

- Chaining allows users to step back to current node from the next chained activity (if the option is selected).

RE: Activity Chaining

Harshit Bumb (Appyzie) — Mon, 29 Jan 2024 06:43:22 GMT

For my ease of understanding, I categorize them as foreground (chaining) and background (no chaining). In case you want something to happen while you wait for it and want to see the result, you add the chaining.

RE: Activity Chaining

Mike Schmitt — Sun, 28 Jan 2024 23:56:52 GMT

Chaining is also useful for on-interface calls of a!startProcess() if you need to get the data resulting from any part of the process to pass back onto your form.

RE: Activity Chaining

Mathieu Drouin — Sun, 28 Jan 2024 21:20:40 GMT

IMO, activity chaining should be used for either API requests or interfaces.

For APIs, it's mostly because you might need a certain amount of nodes to complete to be able to return values to the person calling the API.

On interfaces, you usually chain database writes to ensure that when you refresh the screen, the values are displayed.