When a tenanted deployment is triggered, a task is created for each tenant. But when the deployment process consists of multiple steps, the deployment of the tenants is done somewhat in parallel.
For instance, the following could be the execution flow:
- Process step 1 for tenant A
- Process step 2 for tenant A
- Process step 1 for tenant B
- Process step 3 for tenant A
- Process step 1 for tenant C
- Process step 2 for tenant B
etc.
Is it possible to configure that the deployment of each tenant needs to be fully compete, before the next tenant is handled? So:
- Process step 1 for tenant A
- Process step 2 for tenant A
- Process step 3 for tenant A
- Process step 1 for tenant B
- Process step 2 for tenant B
- Process step 3 for tenant B
- Process step 1 for tenant C
- Process step 2 for tenant C
- Process step 3 for tenant C
A workaround would be to create a separate trigger for each tenant on a specific time, but that is very cumbersome.
PS: I know that when setting the task cap to 1 solves the issue, but this solution does not work when the process uses a chain deployment; this uses a second task.
Kind regards,
Bastiaan Molsbeck.