Adobe recommends you create a custom copy of the DAM Update Asset workflow model | Community
Skip to main content
sindhug14537977
sindhug14537977
Level 2
August 23, 2019
Solved

Adobe recommends you create a custom copy of the DAM Update Asset workflow model

  • August 23, 2019
  • 4 replies
  • 3788 views

AEM 6.5

i've copied OOTB "DAM Update Asset workflow Model" in aem and changed launchers for create, update, modifying assets to this new model.

but workflow is not being triggered when i upload an asset.

are there specific instructions to overlay a workflow model and customize it.

how do we persist the customization from code repository to  avoid any overrides ?

Thanks in advance!!!

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by user05162

    Hotfix and Upgrades will only affect /libs directory. So, any workflows under "/conf/global/settings/workflow/models" and the corresponding runtime models under "/var/workflow/models" will not be overwritten.

    Example: customized version of the Dam Update Asset will be stored at the paths below:

    /conf/global/settings/workflow/models/dam/update_asset

    /var/workflow/models/dam/update_asset

    So, If you want to move this workflow to another instance, you can create the package of the above 2 nodes. Similar steps can be followed for other workflows.

    4 replies

    U
    Adobe Employee
    user05162Adobe Employee
    Adobe Employee
    August 23, 2019

    If you open the OOTB DAM Update Asset workflow from touch UI and make changes to it and sync it, AEM will automatically create a custom copy of the workflow under /conf.

    If it is not getting triggered probably something wrong with the launchers. Compare it with OOTB launchers and make sure OOTB launchers for the same configuration is disabled

      V
      Adobe Employee
      vish.dhaliwalAdobe Employee
      Adobe Employee
      August 23, 2019

      The custom workflow will exist under conf and the sync button will sync the changes to the Runtime Workflow Model under /var/workflow/models. The workflow will be there under both locations.

      Make sure your custom changes are propagated to var location as well.

        sindhug14537977
        sindhug14537977Author
        Level 2
        August 23, 2019

        Thanks for quick response. JaideepBrar​ Vish.dhaliwal​

        yes! this worked. and all my launchers are working fine.But,

        will this workflow stay same and not get lost when there's a hot fix or an upgrade?

        how do we persist the customization of this workflow from code repository.

        should i just create the same structure (/conf/global/settings/workflow/models) in my code repository and deploy it.

        if not through code repository, should i package it and install on my stage and prod servers?

        U
        Adobe Employee
        user05162Adobe EmployeeAccepted solution
        Adobe Employee
        August 23, 2019

        Hotfix and Upgrades will only affect /libs directory. So, any workflows under "/conf/global/settings/workflow/models" and the corresponding runtime models under "/var/workflow/models" will not be overwritten.

        Example: customized version of the Dam Update Asset will be stored at the paths below:

        /conf/global/settings/workflow/models/dam/update_asset

        /var/workflow/models/dam/update_asset

        So, If you want to move this workflow to another instance, you can create the package of the above 2 nodes. Similar steps can be followed for other workflows.

          Terms & ConditionsAccessibility statement

          Loading footer...