@shashi122 The http asset api does not have any way to get the annotations added to any asset. I tried it using the assetmanager and asset apis. But still unable to fetch the annotations

Hi, I have a requirement to share the assets stored in my aem server (6.5) to be shared to an external system via api.The shared data should have entire metadata i.e annotations, renditions everything.Any pointers appreciated !!

Hi,I have a requirement to-1)path based slinghttpservlet to execute some business logic and set attributes a, b in the slinghttpservletrequest2)Use the above set slinghttpservletrequest attributes, i.e a and b in sightly code.Please suggest how can slingMOdel with adaptable as slingHttpSErvletReques...

@BrianKasingli It was a custom model. The issue is now resolved. The issue was, if any of the step fails, all steps from start till before the failed step are not shown in history of workflow. Thanks!!

The same process step is working with the existing. workflow. Also, I tried using OOTB Activate process. The workflow instance history is still the same. when seen the history, the initiators are different. For thhe existing workflow the initiator is workflow-service, while for the fresh one the ini...

Hi,I am facing an issue with creating and starting workflow in aem 6.5.I tried creating a workflow model in aem 6.5.Now when I run the workflow, when i open the history in instances tab, I can just see 2 steps - first and last. I am unable to see the middle steps. It seems node transition is not wor...

@hamidk92094312@berliant We do not have any search requirement associated with this node and properties.Its just like we want to persist it on jcr and fetch the properties using sling/jcr to render the page.Will it still have any issue ?

Is there any restriction to number of properties those could be added to a node in aem 6.3?Also , is there any impact on the instance if the number of properties in a content node increases? How is the instance impacted with more number of properties.This is specific with respect to aem 6.3 version.

The issue is now fixed. The root cause for this issue was that there is a custom ajax call made which too was trying to update the node. Hence we were getting the node already checked in exception.Thanks !!

There is no publishing  involved. This issue occurs in author