Workflow Launchers - Touch UI vs Classic UI | Community
Skip to main content
A
Anonymous
October 16, 2015
Solved

Workflow Launchers - Touch UI vs Classic UI

  • October 16, 2015
  • 6 replies
  • 3400 views

Hello,

 

AEM 6.1

It seems that the workflows are quiet bugged/ documentation not up to date.

Being a normal User (without administrator group), selecting a page and deleting it in the TOUCH UI starts automatically the workflow "request_for_deletion". (which needs an administrator )

Doing the same in the CLASSIC UI, simply deletes the page. 

 

I can't find any relation to the workflow in the Launcher Tab. It is quiet hard to set the system properly up, when there are such strange behaviours.

1. Why is the workflow started, even though it is not mentionned in the Launcher TAB and how can I list all the other "magically" launched workflows?

2. What is the best way to deactivate and/or delete the workflow? 

 

 

Kind regards,

 

Jerry

    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 KishCq5

    I am able to answer partially to your question. the point i want to state is workflows will be triggered on the action of button click. if you see the functionality of Activate, once the button is clicked default "request for activation" workflow will be triggered you can check the code /libs/wcm/core/content/siteadmin/actions/activate/menu/activateNow the handler CQ.wcm.SiteAdmin.activatePage will be fired in /libs/cq/ui/widgets/source/widgets/wcm/SiteAdmin.Actions.js. in the same way it might be happening in Touch UI

    6 replies

    Lokesh_Shivalingaiah
    Lokesh_Shivalingaiah
    Level 10
    October 16, 2015

    Hi Jerry,

    Even though it launches the workflow behind, it should not have any manual intervention however. Can we know the concern here ?

    K
    KishCq5Accepted solution
    Level 3
    October 16, 2015

    I am able to answer partially to your question. the point i want to state is workflows will be triggered on the action of button click. if you see the functionality of Activate, once the button is clicked default "request for activation" workflow will be triggered you can check the code /libs/wcm/core/content/siteadmin/actions/activate/menu/activateNow the handler CQ.wcm.SiteAdmin.activatePage will be fired in /libs/cq/ui/widgets/source/widgets/wcm/SiteAdmin.Actions.js. in the same way it might be happening in Touch UI

    A
    Anonymous
    October 16, 2015

    It seems normal to me, if the workflow is launched that it would need manual intervention.

    The workflow is attached as picture.

    Example how to reproduce (must be in Touch UI, because the workflow isn't launched in classic ui):

        Our users/developpers aren't in the administrator group. They do have read, modify, create, delete  on /content/<site-name>

        If a normal user deletes the page, it stays in his interface.

        Logging in as administrators, I see the page with a note "Request for deletion" and the admin has to delete the page.

     

    The issue is, that I can't find a trace in any tab, why it is executed. Shouldn't it be listed somewhere in the Launcher Tab?

    Lokesh_Shivalingaiah
    Lokesh_Shivalingaiah
    Level 10
    October 16, 2015

    It uses 'Request for Deletion' workflow which is listed in workflow 'Models' which uses /etc/workflow/models/request_for_deletion/jcr:content/model

    A
    Anonymous
    October 16, 2015

    Yes, I know that. The attached picture was the workflow.

    The question is not what is triggered but more a why is that workflow triggered.

     

    I can't find any trace which links the button delete to the workflow!

      P
      petr_beranek
      January 14, 2016

      Has this been resolved? I'd also like to understand how this new feature got to AEM - it wasn't there in the past, so what update package contains this feature that such workflow is triggered automatically? Which release notes contain info about it?

      Terms & ConditionsAccessibility statement

      Loading footer...