Versioning helps you keep things aligned, but what happens when you are linking a subprocess via a Service Task and this has updated to a new version?

Currently, this would continue to call the previously linked subprocess version from your parent process – which is why you will need to update this manually by simply changing the ID in the link.

Step 1

Start by getting the process template ID from the URL on the Map view of the subprocess before you publish it.

You can locate the process template ID within the URL as it follows /templates/ and is an alphanumeric code, such as the example below:

https://yourworkspace.play.sodalabs.cloud/design/templates/5fbcf42ba3dc9c62e0975e44

Step 2

After getting the ID, you can publish the updated subprocess and go back to the parent process. There, select the relevant Service task that does the subprocess call, to edit it.

Step 3

In the URL field, you will need to replace the subprocess template ID with the ID of the latest published version.

For example, if this was the current URL:

https://yourworkspace.play.sodalabs.cloud/prototypes/api/StartMultipleWorkflowsFunction/workflowTemplate/5fad4bc6e022e61bf8b4ec66?code=3763593C-3840-4C1E-BA98-320C0CE4E415

You would need to change it by integrating the new ID after /workflowTemplate/. By doing that, the URL would change to:

https://yourworkspace.play.sodalabs.cloud/prototypes/api/StartMultipleWorkflowsFunction/workflowTemplate/5fbcf42ba3dc9c62e0975e44?code=3763593C-3840-4C1E-BA98-320C0CE4E415

This will align the subprocess to the new version.


Pro tip

By using annotation on the Service Task you can note the current subprocess version and that will help with version changes.


After changing the URL, you can finally publish the parent process and everything will be aligned to the latest version.

All done!


Read more: How to keep new versions of subprocesses aligned when called via a Call Activity

Did this answer your question?