Hi Jörg,We've created a sample page (/content/vanity/vanity-test) and authored a Vanity URL(/content/vanityTest) on that page.We've updated the Default Replication Agent of Author instance with "aliasUpdate" property to true and also updated the Dispatcher Flush Agent of Publish with "aliasUpdate" p...

For your reference, Please find the screenshot of the configuration dialog of the invalidation agent.

I tried checking for that but "Alias Update" Check box is not available in the Configuration Dialog. We're using AEM 6.1 version.

Hi Everyone,We're trying to clear the Dispatcher Cache of the Vanity URLs using some custom logic, where it is not exactly working.We've created a page and configured some Vanity URLs for that page.  Now when we activate the page all the URLs(Page URL and Vanity URLs) are passing through the Dispatc...

Hi Rima,Thank you for that. But what if we add new Vanity URLs for the same page having some Vanity URLs. Does AEM by default clear the cache or else here also we need to have a custom logic.Thanks you.

Yes, Session has all the permissions. Actually, after having further more debugging on the issue we noticed that mostly it is failing for the pages which are having the "jcr:primaryType"  as "nt:unstructured". It is a success for the pages which are having "jcr:primaryType" as "cq:PageContent" in th...

Forgot to mention, if I edit the Vanity URL which is added through the code and then Save it through CRX then it is getting added in the JCR Resolver.

Yes, it is working perfectly for adding the properties (sling:vanityPath) in JCR Node. But not sure where it is getting internally failed for adding the vanity paths in JCR Resolver Mapping. Actually all the properties are getting added in the JCR Node but some are not getting added in the JCR Resol...

Hi Everyone,I am trying to add the "sling:vanityPath" to the existing pages using a Script, where it is adding the property to all the pages correctly but that Vanity Path is not getting assigned or not getting registered in the JCR Resolver (http://localhost:4502/system/console/jcrresolver ) for wh...

If we configure "/amazon" on any page, let's say "/myapp/home" page and access the home page using the Vanity Path "/amazon", will it cache the "/amazon" in Dispatcher? If yes, then what if we update the "/amazon" vanity path to "/Amazon" and activate the home page, will the AEM clear the Dispatcher...