In AEM 6.4, When a user is on a page, they can start a Workflow by going to Page Properties and selecting Start Workflow. Next a pop up is displayed which list the available workflows the user can start as shown below.
I would like to hide certain workflows in this list from certain users/groups. For instance, I want to show only the Download Asset and Project Approval Workflow for a group. Everything else should be hidden.
In the following article, How to hide workflow models in the start workflow list?
It states that I should be able to add the workflow:system tag to a workflow model to hide it. However, adding that tag did not work.
What is the recommended way of restricting the list of workflow models that appear when a user selects start workflow?
I've verified that this link How to hide workflow models in the start workflow list? still works for 6.4
1) Open workflow properties in Touch UI
2) Add the tag 'workflow:system' and remove other tags, if any.
3) Save the changes and close the properties dialog
4) Click on Sync button to propagate the changes to corresponding workflow model definition under /var/workflow/models/<name>/metaData node.
5) Validate that you can see "tags" property as "system" on the metaData node
6) That specific model with "system" tag would stop appearing in the dropdown on your content page.
I am facing the same issue you have faced for ActivationModel.
Getting error as - Resource at /libs/settings/workflow/models/activationmodel.html not found.
Tried with below path as well (Per Arun Patidar post), but same result (resource not found).
did you get a chance to resolve this issue, if so, can you please share resolution steps.
Thanks n Regards,
Any new or modified Workflow Models must be migrated to /conf/global/workflow/models.
When migrating modified AEM-provided Workflow Models
With the Workflow Model Editor open, modify the browser's address URL, and replace the path segment /libs/settings/workflow/models with /etc/workflow/models.
Enable Edit mode in the Workflow Model Editor which will copy the Workflow Model definition to /conf/global/workflow/models.
Tap the Sync button to sync the changes to the Runtime Workflow Model under /var/workflow/models.
Export both the Workflow Model (/conf/global/workflow/models/<workflow-model>) and Runtime Workflow Model (/var/workflow/models/<workflow-model>) and integrate into the AEM project.
For example, export:
Workflow Model resolution occurs in the following order:
Thus, any customizations of AEM-provided Workflow Models persisted in the Previous location must be moved to /conf/global/settings/workflow/models if they are to be retained, otherwise they will be superseded by the AEM-provided Workflow Model definition in /libs/settings/workflow/models.
I have one more issue that came up. I am unable to edit the OOB Workflow Model called, Activation Model. Not sure, if this is just an issue in my local (AEM 6.4).
I get an error stating No Resource found.
I'm adding the workflow:system tag to hide the workflows, as recommended earlier. I can add the workflow:system tag for some of the models but not for all.
For some models the UI for adding tags is grayed out.
And if I try to add the tags property through crx/de I get an error.
How do I add the system tag for these workflows?
If /useradmin doesn't work, then there is another tool for more granular permissions -- /crx/de
Create multiple groups and restrict the model paths for each group per your use case using this console. I would update this thread, if I get a better solution.
That was my approach initially but, when you go to /useradmin to set permission not all of the workflow models show up individually.
In the useradmin console when setting permissions, if you open the /var/workflow/models node you will not see all of the models that you see in crx/de under the /var/workflow/models. Essentially you cannot set permissions per workflow model.
Now my approach was to create a two sets of folders under the /var/workflow/models node. One for the restricted workflow models, /var/workflow/models/restricted, and another for the non-restricted workflow models /var/workflow/models/non-restricted. I would move the OOB workflow models to the restricted folder and deny read permissions. This works fine! But, the problem is when I update a workflow model and press Sync, it will create the updated workflow model under /var/workflow/models not the restricted or nonrestricted folder. I would also need to move the /conf or /lib configurations for the workflows to a new path. Next I have to consider these changes need to be propagated to multiple environments (Dev, QA, Prod). And of course there will be issues during upgrades.
The whole thing seemed really messy/buggy and I was looking for a more elegant solution.
"Adding the system tag hides the workflow model for all users." -- this is correct
"Is there a way to only hide the workflow models for certain groups or a user?" -- Never tried that but, in theory, you could remove the read access to /var/workflow/models/<wf_name> and corresponding model paths in /conf or /lib for that specific user/group and it should stop populating in the drop-down. This should work.