Does startprocesswrite work with activity chaining? I'm using the start

@robbier fn!startprocesswrite belongs to fire and forget category. So chaining can't be expected here. What you could only do is, you could only kick off a process with this function which runs asynchronously.

The task can't be chained immediately from the SAIL interface i.e. the chain breaks when human intervention comes into picture. But at the same time if you just proceed with system activities, you could run them synchronously (provided if the functionality is within chaining limits).

A work around you can think of is:
1. Include a functionality to write process id in your process model which is triggered from fn!startprocesswrite
2. In your SAIL code, query the process id written recently and get the active task using queryprocessanalytics or getportalreportdatasubset
3. Provide the link to task on the SAIL interface using the task id retrieved from Step - 2.

A similar approach to the above has been successfully implemented and tested (long back) for exporting the data to document and providing a link to document immediately on the SAIL interface.

Ah! Good to know. Thanks for the clarification.

I do hope that at some point in the platform there is a way to either a) pass more data into a Related Task---including local variables and/or b) launch processes (synchronously) from links in a SAIL form (at least from a record dashboard).

Again, thanks for the clarification!

:) Hope so!!