Launcher gets triggered by another workflow | Community
Skip to main content
A
AnjaliBiddanda
New Participant
October 20, 2020
Solved

Launcher gets triggered by another workflow

  • October 20, 2020
  • 4 replies
  • 1747 views

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 process by adding this:
event-user-data:changedByWorkflowProcess

That didn't help. The user data "changedByWorkflowProcess" would already be set by this OOTB publish workflow I'd imagine. 

I've also tried adding the following to the exclude list, with no luck:

cq:lastReplicated,cq:lastReplicatedBy,cq:lastReplicationAction,jcr:baseVersion,jcr:versionHistory.

Any suggestions?

CC: @smacdonald2008 ; @joerghoh (I've read your post on https://cqdump.wordpress.com/2020/01/03/prevent-workflow-launchers-from-starting-a-workflow/)

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by anjali_biddanda

Thanks Jorg. You're right, I think the event-user-data can only be used for the Assets workflows. Btw, the answer for this has been updated here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/launcher-gets-triggered-by-another-workflow/qaq-p/383822 

I had incorrectly raised this question under Forms, and there's a duplicate question raised in AEM.

4 replies

anjali_biddanda
anjali_biddandaAccepted solution
New Participant
October 25, 2020

Thanks Jorg. You're right, I think the event-user-data can only be used for the Assets workflows. Btw, the answer for this has been updated here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/launcher-gets-triggered-by-another-workflow/qaq-p/383822 

I had incorrectly raised this question under Forms, and there's a duplicate question raised in AEM.

    joerghoh
    joerghoh
    Employee
    October 22, 2020

    Hi,

     

    I am not sure that the user data you mentioned is used by (all!) workflows to prevent other workflows from firing. Where did you find this documented?

    Regarding your usecase you have test many different conditions (actually a lot of changes happen on cq:PageContent nodes). Maybe an ObservationListener or a ResourceChangeListener are better suited here.

    A
    AnjaliBiddandaAuthor
    New Participant
    October 20, 2020
    Thanks @ Kosta_Prokopiu1. I've raised it there. I don't know how to delete this one though?
    Kosta_Prokopiu1
    Kosta_Prokopiu1
    Employee
    October 20, 2020
    This does not sound like an AEM Forms related question. You should place it higher up in the Adobe Experience Manager section
    Terms & ConditionsAccessibility statement

    Loading footer...