AEM workflow trigger by workflow launcher is not publishing asset to brand portal | Community
Skip to main content
chetan001
Level 3
July 15, 2021
Solved

AEM workflow trigger by workflow launcher is not publishing asset to brand portal

  • July 15, 2021
  • 2 replies
  • 1590 views

I have created simple workflow which is publishing asset to brand portal.

 

Step :   Start->>>> participant Step >>>>> process step(Scheduled to brand portal) >>>> end.

 

 When I start this workflow from  workflow model by passing payload and title and run the workflow. It is publishing asset .

 

But when I run this workflow from launcher configuration. This workflow getting initiated and also getting completed but asset is not getting published.

 

Do  I need to manage other configuration ?

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 diksha_mishra

@chetan001 You first need to configure Brand Portal publish setup as described here: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/assets/brand-portal/configure-aem-assets-with-brand-portal.html?lang=en

By default, the assets will only be published to the default publisher and not brand portal.

Once done, you can simply do a quick publish and check the asset in Brand Portal.

Hope this helps.

 

2 replies

diksha_mishra
Community Advisor
diksha_mishraCommunity AdvisorAccepted solution
Community Advisor
July 15, 2021

@chetan001 You first need to configure Brand Portal publish setup as described here: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/assets/brand-portal/configure-aem-assets-with-brand-portal.html?lang=en

By default, the assets will only be published to the default publisher and not brand portal.

Once done, you can simply do a quick publish and check the asset in Brand Portal.

Hope this helps.

 

chetan001
chetan001Author
Level 3
July 16, 2021
Thanks diksha_mishra for your reply, brand portal configuration is already on the place. it is issue with workflow launcher user access.
chetan001
chetan001Author
Level 3
July 23, 2021
This issue has been resolved by giving proper access to workflow-service user