Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

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

chetan001
Level 3
Level 3

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 ?

1 Accepted Solution
diksha_mishra
Correct answer by
Community Advisor
Community Advisor

@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/configu...

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.

 

View solution in original post

3 Replies
diksha_mishra
Correct answer by
Community Advisor
Community Advisor

@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/configu...

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.

 

View solution in original post

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