Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.

Workflow Purge Config Not getting created on Higher Environments

Avatar

Level 3

I have set a environment specific configuration through my code base in config.author folder using OOB workflow purge osgi service i.e Adobe Granite Workflow Purge Configuration, after deploying the code it gets created in local author and works fine but it is not getting created in any of the above higher environments, however configurations directly created from author instance on higher environments web console are working fine. This is only happening for Granite Workflow Purge Configuration and not for any other configs.

 

 

Our XML file in config.author  folder is named as : com.adobe.granite.workflow.purge.Scheduler-myconfig and Below is the file:

 

 

 

 

<?xml version="1.0" encoding="UTF-8"?> 
<jcr:root 
   xmlns:sling="http://sling.apache.org/jcr/sling/1.0" 
   xmlns:jcr="http://www.jcp.org/jcr/1.0" 
   jcr:primaryType="sling:OsgiConfig" 

scheduledpurge.daysold="60" 
scheduledpurge.modelIds="[/var/workflow/models/dam/dam-update-language-copy,/var/workflow/models/dam-xmp-writeback,/var/workflow/models/dam/update_asset]" 
scheduledpurge.name="workflow-purge-job" 
scheduledpurge.workflowStatus="RUNNING"/>

 

 

I am on AEM 6.5.15

3 Replies

Avatar

Community Advisor

Most likely, your configuration is deployed, but it is not being considered due to priority resolution. Perhaps at some point, you manually changed the OSGI config, which takes precedence over an OSGI config from the codebase. You can find more information here about this: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/configuring-osgi...

 

Hope this helps



Esteban Bustamante

@EstebanBustamante  com.adobe.granite.workflow.purge.Scheduler is the factory service and it must allow multiple configs either from code or one those are manually added isnt that right?

Avatar

Level 3

This is very strange but for Granite Workflow Purge Configuration I was able to make it work through JSON based configuration instead of XML.

 

created a json config file com.adobe.granite.workflow.purge.Scheduler-myconfig.cfg.json

 

added below configs to the file:

 

 
 

 

{
"scheduledpurge.modelIds":[
"/var/workflow/models/dam/dam-update-language-copy",
"/var/workflow/models/retouching_request_workflow",
"/var/workflow/models/dam/dam_set_last_modified",
"/var/workflow/models/dam-xmp-writeback",
"/var/workflow/models/dam/update_asset",
"/var/workflow/models/request_for_deletion",
"/var/workflow/models/request_to_complete_move_operation"
],
"scheduledpurge.daysold": "60",
"scheduledpurge.name" : "workflow-purge-job",
"scheduledpurge.workflowStatus": "RUNNING"
}