Workflow Purge Config Not getting created on Higher Environments | Adobe Higher Education
Skip to main content
T
troubleshooter3
Level 3
October 24, 2023

Workflow Purge Config Not getting created on Higher Environments

  • October 24, 2023
  • 2 の返信
  • 1093 ビュー

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

このトピックへの返信は締め切られました。

2 の返信

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
October 27, 2023

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.html?lang=en#resolution-order-at-runtime

 

Hope this helps

Esteban Bustamante
    T
    troubleshooter3作成者
    Level 3
    October 27, 2023

    @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?

      T
      troubleshooter3作成者
      Level 3
      November 29, 2023

      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" }

       

      契約条件Accessibility statement

      Loading footer...