Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

\/libs/cq/workflow/admin/console/content/instances.html View

Avatar

Level 6

Hello Team,

 

We have one Group of editors lets say G and 2 users usr1 and usr2 are part of this group.

 

usr1 has chosen to publish a page later so he opted for "Publish later" option. 

 

When usr1 access this url http://localhost:4502/libs/cq/workflow/admin/console/content/instances.html, usr1 can see what all pages are scheduled to get publish later like below:

 

arvind_2-1686146050625.png

 

Questions:

1) Since usr1 and usr 2 are part of same group and having same set of permissions, is it somehow possible that usr2 also can see what all pages are set to be "publish later" by usr1?

 

2) Why payload is showing /etc/workflows......, we expect here payload should be path of page that we selected to get published later?

 

Regards,

KTNR

 

 

 

 

 

 

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @arvind ,
To answer #2
When we use 'Publish later' option, it creates a 'generated-package'. the path you see in the screenshot is not the direct path of the page but a package with cq:template = /libs/cq/workflow/templates/collectionpage/. With a filter consisting of all the selected pages(resources) for publish later action. This is similar to to the vault package we get in package manager with the exception of mime type.

shubhanshu_singh_0-1686147882637.png

When scheduled time is reached, all the resources included in this package are published/unpublished based on selection in manage publication wizard.

For #1 
Usr 1 can view the workflow instance because he is the initiator of the workflow, Workflow initiator (the user), Workflow Administrators (group) and Administrators can view the running instance of workflows by design.

If you want all the users of group G to view the workflow instances with no custom implementation overhead, Add the group to Workflow Administrators group.
Moreover, you can select the running instance and click on view payload to see all the paths included in the package. 

Hope this helps!!

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @arvind ,
To answer #2
When we use 'Publish later' option, it creates a 'generated-package'. the path you see in the screenshot is not the direct path of the page but a package with cq:template = /libs/cq/workflow/templates/collectionpage/. With a filter consisting of all the selected pages(resources) for publish later action. This is similar to to the vault package we get in package manager with the exception of mime type.

shubhanshu_singh_0-1686147882637.png

When scheduled time is reached, all the resources included in this package are published/unpublished based on selection in manage publication wizard.

For #1 
Usr 1 can view the workflow instance because he is the initiator of the workflow, Workflow initiator (the user), Workflow Administrators (group) and Administrators can view the running instance of workflows by design.

If you want all the users of group G to view the workflow instances with no custom implementation overhead, Add the group to Workflow Administrators group.
Moreover, you can select the running instance and click on view payload to see all the paths included in the package. 

Hope this helps!!

Avatar

Employee Advisor

Hi,

 

Answering your queries:

  1. No, if usr1 and usr2 have the same group membership and permissions, usr2 cannot see the pages scheduled for "publish later" by usr1. Visibility is controlled by permissions.

  2. The payload shown in the Workflow Instances console represents the JCR path of the workflow's payload. For "Publish later" workflows, the payload is the workflow package containing the page or asset scheduled for publishing.

    The path shown as /etc/workflows is the default location where AEM stores workflow packages.