There is no ootb way @nithya90 You'll have to develop your own logic to check if the asset is already present at destination.What you can do is modify the move operation from granite UI to check for duplication first.You may need to check for yourself data fetching and passing into servlet calls in ...

I think using Sling Event Handler is much more apt way to achieve your use case.Attach a sling event handler/listener on Asset Modification and carry out the Asset Metadata updation in that osgi component.Here is a sample event handler for Asset Modification:Event Handler for Asset's modification (e...

Hi @anithara Same issue happened with me. What I was doing wrong was that my cookie scope was wrong i.e. when I checked my cookie was under wrong domain/path. When I corrected the cookie domain/path, it worked fine.Same check you can do, you can compare props for other cookies that are working fine ...

Hi @Rajumuddana The standard approach would be to use the ootb core breadcrumb component and customize it as per our requirement.In your case , you can use the Delegation Pattern for Sling ModelsUsing above you can modify your breadcrumb component sling model to serve breadcrumb items as per your bu...

Yes , given that you are looking for a permanent solve, you will have to rethink ACL division and hierarchy. 

If you only want to use ACL to achieve the same then one thing you can do is assign specific permissions to a user group that are required for moving pages with references to other non accessible regions, that is I think jcr:write and jcr:modifyProperties permissions for the content path root. Then ...

Hi @mmasonWD The simplest solution would be to give your authors a reference report.Best part is this will remain disjoint from your current ACL permissions and authors can make use of reference report to identify references before attempting a move so they can either remove or manually adjust refer...

Hi @sudeepKonjeti The composite attribute should be true if you’re storing multiple fields within each item.Make sure the name properties for the fields within the multifield are prefixed correctly (e.g., ./fieldName).

In the handler properties , you can mention event filterproperty = {EventConstants.EVENT_TOPIC + "=" + DamEvent.EVENT_TOPIC,EventConstants.EVENT_FILTER + "=(event.damType=moved)"}Check if this works.

@konstantyn_diachenko I did not want to modify the resource, as resource/asset modification also needs to be replicated at source(3rd party)Also we would need to remove this property after the scheduler job. Then again asset modification would take place.So keeping it separate makes sense to me.