I'm curious to find out the property which enables an OOTB workflow to be used.
There is an OOTB process step and workflow to add dam asset size (dam:size). Invoking this on an asset is resulting in the below warning. Any idea where this is configured to be skipped ?
12.05.2022 00:47:17.163 [cm-p16597-e60753-aem-author-79755bffdb-62c4w] *WARN* [JobHandler: /var/workflow/instances/server1261/2022-05-11/adddamsize_5:/content/dam/wknd/orange-unicorn.png] com.adobe.granite.workflow.core.job.JobHandler Skipping workflow step com.day.cq.dam.core.process.AddPropertyWorkflowProcess which is on the skip list. Continuing with the next step.
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @subsul1,
The behavior you have described is characteristic for AEM as a Cloud Service only. In general in AEMaaCS implementation of com.adobe.granite.workflow.core.job.JobHandler has changed a bit, reference to com.adobe.granite.workflow.skiplist.WorkflowProcessSkiplist which is responsible to control if certain processes will be run or skipped.
The list of processes is hardcoded and it is not possible to add or remove specific dam related processes.
There is one way to control if com.adobe.granite.workflow.skiplist.WorkflowProcessSkiplist will be used or not. This service relays on com.adobe.dam.asset.nui.feature.flag feature flag. Value of this flag depends on fact if you have Adobe Granite Access Token provider OSGI configuration with name starting with Asset Compute phrase.
Solution
Assuming you would like to Add dam size property (com.day.cq.dam.core.process.AddPropertyWorkflowProcess) process works correctly follow below steps.
*INFO* [FelixStartLevel] com.adobe.cq.assetcompute.impl.NuiFeatureFlag No Nui config found for com.adobe.dam.asset.nui.feature.flagIf it did not appear it means that Adobe Granite Access Token provider still exist, so maybe you will have to check configuration provided by your project or what is inside launchpad on OS level.
Summarizing, above behavior seems to be expected. If you are using Asset Compute service standard workflows for asset processing does not make any more.
Hi,
Which version of AEM are you using, this step is unsupported in AEMaaCS.
Hi @subsul1,
The behavior you have described is characteristic for AEM as a Cloud Service only. In general in AEMaaCS implementation of com.adobe.granite.workflow.core.job.JobHandler has changed a bit, reference to com.adobe.granite.workflow.skiplist.WorkflowProcessSkiplist which is responsible to control if certain processes will be run or skipped.
The list of processes is hardcoded and it is not possible to add or remove specific dam related processes.
There is one way to control if com.adobe.granite.workflow.skiplist.WorkflowProcessSkiplist will be used or not. This service relays on com.adobe.dam.asset.nui.feature.flag feature flag. Value of this flag depends on fact if you have Adobe Granite Access Token provider OSGI configuration with name starting with Asset Compute phrase.
Solution
Assuming you would like to Add dam size property (com.day.cq.dam.core.process.AddPropertyWorkflowProcess) process works correctly follow below steps.
*INFO* [FelixStartLevel] com.adobe.cq.assetcompute.impl.NuiFeatureFlag No Nui config found for com.adobe.dam.asset.nui.feature.flagIf it did not appear it means that Adobe Granite Access Token provider still exist, so maybe you will have to check configuration provided by your project or what is inside launchpad on OS level.
Summarizing, above behavior seems to be expected. If you are using Asset Compute service standard workflows for asset processing does not make any more.
Views
Likes
Replies