Check the ACLs on that node in crx.If there's no deny ACL for the user that you want to deny, add one(such as deny on jcr:All), and then verify whether that user still sees the option to use custom workflow. The following doc may be helpful:https://docs.adobe.com/content/help/en/experience-manager-6...
The following documents may be helpful:1) https://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html2) https://docs.adobe.com/content/help/en/experience-manager-64/developing/devtools/ht-projects-maven.html#common-development-tasks-with-maven
Try reindexing that index. It helped resolve the case for one of my customers. They had somewhat similar scenario of migration from 6.3 to 6.5 and issues in retrieving the correct number of records using the QueryBuilder API with their custom index.
@BrianKasingliThe UI seems fine for me. Try opening your AEM in Incognito Window or other browser. You might be seeing weird icons due to Chrome's caching issues. The UI is appearing fine for me on the latest version of Chrome.
It's reproducible. Seems like a Chrome issue. Try to reload the browser after a few seconds. You will see the package installed.Or, you can either go back to a previous version of Chrome, or use some other browser. Hope it helps !!
@chintan97 I was just sharing the information about 1) of your question. You can point it to author URL. Ex: in case of Asset Sharing(https://docs.adobe.com/content/help/en/experience-manager-65/assets/administer/link-sharing.html#sharelink). Regarding 2), I haven't tested that.
It's expected behavior.You can add a Target component to the page in Edit mode or in Target mode. You can add components to the Target component only in Target mode. The Target component belongs to the Personalization component group.If editing targeted content, you must click or tap **Start Targeti...
I found a community article that may be helpful:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/dispatcher-image-caching-issue/qaq-p/237710