Hi Folks, We are working on a requirement where a workflow should start when a specific metadata property changes from either false to true or true to false. There are other metadata properties as well, but any update on the resource should not start the workflow as we need to keep the running instances to a minimum.
We looked into ObservationListener - Property updated, but I reckon that is not 100 percent safe on cloud, as pods might restart, and we can lose some events. Launcher is another option, but it listens to node modified event instead of property updated.
Any thoughts or inputs will be helpful. The solution should be scalable, and extendible to other properties as well.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
@shubhanshu_singh how the property will be changed? automated or via some authoring?
External system pushes the data to AEM for metadata updates.
@shubhanshu_singh If the ingestion of data from external system through your code(servlet/service), you have the control of viewing the metadata before making the update and you can flag that asset/page for workflow run after the update for the specific property change. How does the external system ingesting data into AEM?
Data will be ingested from workfront
hi @shubhanshu_singh we have a similar requirement , where in if some specific metadata properties change on AEM , it should call a launcher which in turn calls a webhook to update these values back in wkft (bidirectional sync) ? It will be helpful if you can share what you did and what challenges you faced?
Views
Replies
Total Likes
Hi Shubhanshu, we have a similar requirement, which solution you opted for? and challenges faced?
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies