Hello, I don't think there are versions managed in publish because it beats the purpose repo size management (optimizing the publish instance) and author version management for same reason. Purging only needed on author. Thanks

Hello, Page will not have information related to workflow.Only way to find out the details are workflow Instances or Launcher. (otherwise you can develop custom feature to pull required info) hope it helps.

Hello, Target has server side API to trigger, did you look at that option https://developers.adobetarget.com/api/delivery-api/#section/Getting-Started Hope it will help!!

Hello,Its development team job to do that configuration based on above suggestion. it can be viewed/configured from /crx/de/index.jsp via following the right path. thanks.

Hello, its AEM installed folder structure which you should access from your server (not as url) and then run shell or similar command mentioned above. Thanks!!

Hello, The log file describe the error coming from file layoutloanofficers_html.java at line 39 Now, to find the file go to /crx-quickstart/launchpad/felix and search for your class file layoutloanofficers_html.java (sightly java file) using below shell command find . -name "layoutloanofficers_html....

Hello, While configuring multified along with multifield items like "textfield" or "textarea" you have a property name maxlength (long) you can configure to set the limit. I would suggest to use "textarea" if you have lengthy text to be authored.(for widget reference)https://www.adobe.io/experience-...

the code you are using is correct. couple of things to check 1. are you getting pageLocale correctly2. if for corresponding locale tags are configured if not then at least default system locale tag is setup above will return not if one of them doesn't match. so i suggest to cross check.  

refer this to start with - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/cug-page-in-aem5-6-1-login-redirect-not-happening/qaq-p/216569

Hello, I think, it should be other way around because target response is asynchronous you should be looking from page or component load side (same we have done in our side as well) as and example refer - https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implemen...