What Happened to the "Update Asset" Workflow in AEM Assets as a Cloud Service?

[TaylorBa2]

I have an OSGi service that uses the WorkflowService API to programmatically trigger the "Update Asset" workflow that's forever been found at:

/var/workflow/models/dam/update_asset

It's missing in AEM Assets as a Cloud Service and I can't find clear documentation on triggering its equivalent. Does anyone here have advice on what needs to be done to trigger this or its equivalent from inside an OSGi service in Assets as a Cloud Service?

Note: The workflow model still exists in the Quickstart Jar from Software Distribution, so everything works fine for me locally.

For context: The reason why we're triggering the workflow is because we have custom OSGi code that pulls proprietary data from other systems and creates and updates both image Assets and Content Fragments. Updated images will create new Revisions of Assets through the AssetsManager API. The Update Asset workflow doesn't seem to fire the way it would if you manually made these same changes, so we're triggering the Update Asset workflow through the API as part of the image update process. It works perfectly on localhost author.

Thanks.

P.S. If someone comes back with "Rebuild the whole thing in Adobe IO microservices", I think I'll have an aneurism.

[giuseppebaglio]

The DAM Update Asset workflow has been fundamentally replaced in AEM as a Cloud Service by Asset Microservices.

The traditional /var/workflow/models/dam/update_asset workflow no longer exists because asset processing has been moved to external cloud-native microservices. This offloads CPU and memory-intensive operations (rendition generation, metadata extraction) from the AEM author instance to scalable cloud infrastructure. 

For programmatic asset updates that require additional processing, the proper approach is to use post-processing workflows, which automatically execute after asset microservices complete their processing.

If the issue is that manually created/updated assets aren't automatically processed, trigger reprocessing programmatically:

The AEM Cloud Service Assets UI includes a "Reprocess Assets" feature that sends assets through the entire microservices pipeline. While there's no official Java API documented for this, the HTTP endpoint can be called programmatically. Reference here and here.

Given that the OSGi code creates/updates both images and Content Fragments with proprietary data:

1. Create a custom post-processing workflow that handles proprietary data integration

2. Configure this workflow to auto-start on the specific folders where assets are being created

3. Ensure the workflow includes the "DAM Update Asset Workflow Completed Process" step at the end