Thanks Vanegi. I tried that. I expect that to work since it has event-user-data:changedByWorkflowProcess in the exclude list, but it doesn't. What am I missing? Do I need to set this changedByWorkflowProcess property somewhere?
Thanks @santhosh_kumark. This was one of the posts I'd already referred to and it mentions the need for multiple participants for the ParticipantStepChooser interface. We decided to go with creating a temporary group (mentioned by bsloki) for the duration of the workflow. We opted against creating o...
I have a launcher that is triggered on a cq:PageContent node on 'Node modified' and I have set a condition to prevent it from firing if a property exists. However, the OOTB Publish workflow is triggering this launcher.I've used the Exclude List to ignore any changes triggered by another workflow pro...
The OOTB Dynamic participant step takes in a single user or group. It would be great if it can take in a list of users or groups. We have this as a business need. We've tackled it by creating a temporary group for the duration of the workflow that contains the dynamic list of users that will act as ...
I have a launcher that is triggered on a cq:PageContent node on 'Node modified' and I have set a condition to prevent it from firing if a property exists. However, the OOTB Publish workflow is triggering this launcher.I've used the Exclude List to ignore any changes triggered by another workflow pro...