AEMaaCS Local instance Auto-start workflow option | Community
Skip to main content
rsl_lucky
rsl_lucky
October 16, 2023
Solved

AEMaaCS Local instance Auto-start workflow option

  • October 16, 2023
  • 2 replies
  • 1686 views

Hi All,

 

Unable to see "Auto-start workflow" option on asset folders in Local AEMaaCs SDK.

Looks like this feature is not enabled on any local set up its available on the Cloud Service Instance. 

Anyone can you let me know, how to configure custom workflow on folder for development activity as it involves lot of back and forth code fixes would happen based on test result.

Requirement to trigger custom workflow (post processing workflow) configured on the folder where assets upload happen. When upload of asset complete needs to auto-trigger custom workflow for updating custom metadata on assets.

Can you share your thoughts around it.

 

Best answer by lukasz-m

Hi @rsl_lucky,

This is correct behavior. Local AEM as a Cloud Service SDK is not supporting Auto-start feature, and other features that relays on Asset Compute service, which in general is available for remote/real instances.

Of course technically it is possible to switch this option on, and make it visible on SDK but it does not mean it will work correctly. To be more precise access to Auto-start feature is restricted via granite:rendercondition

/libs/dam/gui/content/assets/v2/foldersharewizard/jcr:content/content/items/form/items/wizard/items/settingStep/items/fixedColumns/items/fixedColumn2/items/tabs/items/tab2/items/col3/granite:rendercondition

Condition is using feature flag to determine if given option is available for user in the GUI or not. Auto-start depends on com.adobe.dam.asset.nui.feature.flag flag which in the end depends on Adobe Granite Access Token provider configuration.

So to enable Auto-start on GUI you have to follow below steps:

  1. Go to OSGi console (/system/console/configMgr), and find Adobe Granite Access Token provider and click on plus button on the right side to add new configuration.
  2. Create new configuration, please note that even if you do not now what data should be set, the main thing is to set proper Name, which in this specific scenario needs to start with Asset Compute phrase. You can try below configuration. In general I left all values as default except Name.

  3. Click Save and restart your instance.

As a result you will see locally Auto-start Workflow option visible.

Above elaborate and steps have been prepared for educational purpose only, to bring more context how certain features works, and get better understanding of it. The proper one will be to test you Auto-start setup on fully setup of AEM as a Cloud Service, e.g. using Rapid Development Option, or any other existing AEM as a Cloud Service environment e.g. dev

2 replies

ShaileshBassi
Community Advisor
ShaileshBassiCommunity Advisor
Community Advisor
October 17, 2023

Hi @rsl_lucky You can levarage the RDE (Rapid Development Environment) for the testing and development purpose.

Details on how to use RDE environment can be found in the link - https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/developing/rde/how-to-use.html?lang=en

 

Hope this helps!

Thanks

 

    lukasz-m
    Community Advisor
    lukasz-mCommunity AdvisorAccepted solution
    Community Advisor
    October 17, 2023

    Hi @rsl_lucky,

    This is correct behavior. Local AEM as a Cloud Service SDK is not supporting Auto-start feature, and other features that relays on Asset Compute service, which in general is available for remote/real instances.

    Of course technically it is possible to switch this option on, and make it visible on SDK but it does not mean it will work correctly. To be more precise access to Auto-start feature is restricted via granite:rendercondition

    /libs/dam/gui/content/assets/v2/foldersharewizard/jcr:content/content/items/form/items/wizard/items/settingStep/items/fixedColumns/items/fixedColumn2/items/tabs/items/tab2/items/col3/granite:rendercondition

    Condition is using feature flag to determine if given option is available for user in the GUI or not. Auto-start depends on com.adobe.dam.asset.nui.feature.flag flag which in the end depends on Adobe Granite Access Token provider configuration.

    So to enable Auto-start on GUI you have to follow below steps:

    1. Go to OSGi console (/system/console/configMgr), and find Adobe Granite Access Token provider and click on plus button on the right side to add new configuration.
    2. Create new configuration, please note that even if you do not now what data should be set, the main thing is to set proper Name, which in this specific scenario needs to start with Asset Compute phrase. You can try below configuration. In general I left all values as default except Name.

    3. Click Save and restart your instance.

    As a result you will see locally Auto-start Workflow option visible.

    Above elaborate and steps have been prepared for educational purpose only, to bring more context how certain features works, and get better understanding of it. The proper one will be to test you Auto-start setup on fully setup of AEM as a Cloud Service, e.g. using Rapid Development Option, or any other existing AEM as a Cloud Service environment e.g. dev

      rsl_lucky
      rsl_luckyAuthor
      October 17, 2023

      Thanks @lukasz-m for valuable inputs. Will try the option and let know in-case if anything.

        rsl_lucky
        rsl_luckyAuthor
        October 18, 2023

        Hi @lukasz-m ,

        Yes, as mentioned and by following above process can able to see the options available on assets folder and have enabled it (Auto-start workflow). But as you told, its not working as expected to get automatically trigger the post processing workflow specified on folder.

        Can we use Event Handler it captures asset creation event and executes to process custom metadata processing which required for the use case i.e As soon as new asset creation happen on AEMaaCS need to process custom metadata and replicate the asset.

         

        Really appreciate your help on inputs here.

         

        Thanks

          Terms & ConditionsAccessibility statement

          Loading footer...