@Shaheena_Sk I see similar issue at https://github.com/Netcentric/accesscontroltool/issues/368Not sure what's the reason is.

@Dinu_Arya Seems like whitelisting is the only way. https://stackoverflow.com/questions/50054862/using-tokenutil-to-create-credentials-in-aem-6-3Try raising a day care ticket with Adobe.Thanks,Nikhil

@jag01 Try removing the older version of ACS AEM Commons that you were using it for AEM 6.3 and use instead use the latest one may be 4.8.2Thanks,Nikhil

@Riten Can you share the error that you are getting and where exactly it comes up ?Thanks,Nikhil Kumar

@JonMaguire Refer the below link of latest archetype where the clientlibs clientlib-dependencies and clientlib-site inside ui.frontend.general in clientlib.config.js file.If you don't have ui.frontend.general then look inside ui.frontend.https://github.com/adobe/aem-project-archetype/blob/master/src...

@ranjitha29 I assume you are able to select the custom workflow that you have created while activating the workflow. Is so simply activating a page won’t trigger your custom workflow. You need to add your custom workflow as part of activation trigger by going to properties. http://scottsdigitalcommu...

Then you should update the config file which is minifying it. And the clientlibs that you mentioned above are the OOTB generated clientlibs. If you want add any further code customisation, I suggest you to go ahead with creating a new clientlib.

You can update in configuration file inside the react-app folder’s config.js.

You can create your own clientlib and add its category as part of editable templates policy and add this clientlib as dependency to the existing react app’s clientlib.

Which version of AEM are you using, In my current AEM architecture which is on AEM as clous SDK parsys ideally comes inside Layout container. I guess better approach would be to go with the parsys inside layout-container and then annotate the component.