Custom Workflow Best Practice

@mrvnaz : Before suggesting alternatives, it would be important to know

• How is your content structured.
• Are you in process of defining the structure or it is already created and you have to implement a solution to access it now. If already created, you can judge if can be iterated based on paths or would require a query based approach to retrieve them better.
• Every workflow trigger would give the same response OR are there any input parameters on workflow.

Based on the answers of these, we can decide what may be an ideal approach to this. As a general rule, it is not advisable to do lot of queries in AEM as it will overburden your instance etc.
thanks.

Querying is most expexisve feature wothin AEM. In place of that you can overlay workflow process step dialog and add a path browser in place of writing lot of custom baked code. You can read it's metadata at the time of execution.

We can suggest more optimized soluion if you can elaborate your use case.

I am curious to know what the exact use case is, in workflow do you intend to show the items some where?  Or do you want to find child items or filter child items of the payload based on some criteria, etc Based on the usecase, it makes sense to decide if u want to use a query or not like the experts suggested before me. Perhaps details of the exact usecase can help u get more directons.

Thanks !

@mrvnaz  I am thinking it's just you need the list of assets inside a folder for a reporting purpose. Go through below article which gives you an OOTB feature to list down the assets as json structure. https://experienceleague.adobe.com/docs/experience-manager-64/assets/extending/mac-api-assets.html?lang=en#retrieve-a-folder-listing