Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Can restrict triggering a workflow if already an instance is running

saibul
Level 4
Level 4

Server: AEM 6.5.5

 

We have a requirement like triggering a custom workflow  programmatically on scheduled basis at the same time the scheduler should not trigger a new workflow instance until the existing instance is complete or terminated. Do we have any config or property to manage this or we need to maintain some configs on our own.

 

Appreciate your suggestions.

 

 

1 Accepted Solution
vanegi
Correct answer by
Employee
Employee

@saibul,

You cannot restrict to one workflow in Touch UI you need to use classic UI, if you still want to use Touch UI you need to write a custom script. The restriction we see in the Classic UI is at the UI level. So Classic has it and Touch UI does not. As far as the AEM Workflow engine is concerned - it can have the same page as payloads in multiple workflows. Hope this clears it up.

 

Please have a look at below threads for more clarification and several alternative approaches we can take:

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/prevent-multiple-workflow-...

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/restricting-a-page-to-be-s...

 

Thanks!!

 

View solution in original post

3 Replies
vanegi
Correct answer by
Employee
Employee

@saibul,

You cannot restrict to one workflow in Touch UI you need to use classic UI, if you still want to use Touch UI you need to write a custom script. The restriction we see in the Classic UI is at the UI level. So Classic has it and Touch UI does not. As far as the AEM Workflow engine is concerned - it can have the same page as payloads in multiple workflows. Hope this clears it up.

 

Please have a look at below threads for more clarification and several alternative approaches we can take:

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/prevent-multiple-workflow-...

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/restricting-a-page-to-be-s...

 

Thanks!!

 

View solution in original post