Can you try to debug your code by putting either debugger or putting console.log to check if your Java script is getting executed as per expectation and the variables are having the expected values to do the hide and show?
I believe only admins can modify the metadata schema. There is no harm in testing with updating the user create, modify and delete permission to /conf/global/settings/dam/adminui-extension/metadataschema/
Aem content copy tool: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developer-tools/content-copy
If the associated metadata of assets are attached with the assets then it will be copied as well and if that’s not the case then you can use metadata e...
Are you referring to initiator of the workflow user if that’s the case then please refer to https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/is-it-possible-to-get-the-current-user-in-the-workflow/m-p/446998
current user can be found from session object
session.getUserID();
...
type= cq:Page is not required for the full text for your use case as this property is associated with the page node only. For your use case you can use type=nt:unstructured filter for your search query
No that should not happen. Once you create/update the user permission it’s get stored on aem repository. Restarting of aem shouldn’t reset the permissions. I am hoping you are having a persistent/ permanent volume or memory assigned to your server. If your custom package installation is doing the re...
Normally those connections are on author only like target and launch integration. For the JWT to oauth migration it depends how your existing setup is and need to be migrated for all. If currently you don’t have any JWT integration with publisher then you don’t need to do anything with publisher.
ho...