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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Workflow Payload

Avatar

Level 3

Happy New Year everyone !

I have few queries on workflows (AEM 6.2). 

1. A workflow can be initiated with a single Payload only, except using Workflow Packages. Is this correct?

2. Workflow payload cannot be modified once the job has been started? I cannot add or delete a payload from the workflow instance.

3. Workflow packages allow using multiple pages, assets in a single Workflow job but packages can only be used through Classic UI only

With all these constraints, Is it not inefficient to run workflow processes this way?

TIA 

 

AEM 6.2

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Please find answer to your queries:

1 - Correct. A workflow can be initiated only on single payload unless you opt to use workflow packages.

2 - Workflow payload can be modified even it payload is under workflow. You can also opt to lock your payload if you want to restrict any editing while the payload is still under workflow. Same rule applies to delete, i.e. you can delete a payload if its under workflow, unless you decide to lock it. If you are using workflow packages then you can add more payload to workflow package even in midst of workflow execution.

3 - Workflow packages UI is still not build in TouchUI, so yes - you will need to use classic UI if you plan to use workflow packages. I am sure in near future releases, the workflow packages UI too will be enabled on TouchUI.

I could not get your point on limitation and inefficiencies, can you please let me know which use-case you are exploring using a workflow?

Also for more details you can refer to link shared by Scott.

- Runal

View solution in original post

4 Replies

Avatar

Level 10

Hey - watch this Ask the AEM Community Experts session on Workflows presented by Will - one of the Workflow Eng members: 

https://helpx.adobe.com/experience-manager/using/Workflows.html

The link is in the table at the start of the article. He covers a lot of WF information. 

Avatar

Correct answer by
Community Advisor

Please find answer to your queries:

1 - Correct. A workflow can be initiated only on single payload unless you opt to use workflow packages.

2 - Workflow payload can be modified even it payload is under workflow. You can also opt to lock your payload if you want to restrict any editing while the payload is still under workflow. Same rule applies to delete, i.e. you can delete a payload if its under workflow, unless you decide to lock it. If you are using workflow packages then you can add more payload to workflow package even in midst of workflow execution.

3 - Workflow packages UI is still not build in TouchUI, so yes - you will need to use classic UI if you plan to use workflow packages. I am sure in near future releases, the workflow packages UI too will be enabled on TouchUI.

I could not get your point on limitation and inefficiencies, can you please let me know which use-case you are exploring using a workflow?

Also for more details you can refer to link shared by Scott.

- Runal

Avatar

Level 3

Runal.Trivedi wrote...

Please find answer to your queries:

1 - Correct. A workflow can be initiated only on single payload unless you opt to use workflow packages.

2 - Workflow payload can be modified even it payload is under workflow. You can also opt to lock your payload if you want to restrict any editing while the payload is still under workflow. Same rule applies to delete, i.e. you can delete a payload if its under workflow, unless you decide to lock it. If you are using workflow packages then you can add more payload to workflow package even in midst of workflow execution.

3 - Workflow packages UI is still not build in TouchUI, so yes - you will need to use classic UI if you plan to use workflow packages. I am sure in near future releases, the workflow packages UI too will be enabled on TouchUI.

I could not get your point on limitation and inefficiencies, can you please let me know which use-case you are exploring using a workflow?

Also for more details you can refer to link shared by Scott.

- Runal

 

Users usually deploy  multiple webpages together (at least in my environment). they have to go to old AEM interface and create a package and then start the workflow. This seems like a small step but from content authors point of view it is additional work.It would be much more convenient for them to select multiple pages from sites and start the job.

Technically they can select multiple pages and start the workflow from sites view but it creates one job instance for each page. This way it create 10 jobs if i am deploying 10 pages together. This is not much efficient as this whole processing could have been done in one job instead there were 10 different jobs. Also the approval process for each one of the page will happen separately which is inefficient from business point of view.