Hi Vijay, it seems like you are not using editable policies to setup the availability of components. are you sure, you are doing from editable template config console because below screen shots doesn't looks like??? refer this - https://myaemlearnings.blogspot.com/2018/03/policies-in-editable-templa...

Hello, I think iparsys by default configured for disable targeting, did you check that?? also, if underneath parsys component still targetable then check /libs/foundation/components/iparsys/iparsys.jsp from line 111 to 119, hope that will give some clue when debug. THanks,

Hello, first of all thanks for sharing that you were successfully able to deploy your local git repo via using cloud pipeline. now, as per my understanding the deployment workspace will be created based on GIT repo so in your case the project C git repo will be treated as separate workspace then to ...

Hello, the answer is in your question only. you should be configuring that parsys from editable template and enabling component for the parsys " create/modify the policy)If parent parsys is already enabled the component then you need not require to do for child parsys rather it will inherit thanks!!...

Hello,Did you try adding msm related clienlibs to enable/execute necessary checks at component dialog level like cq.wcm.msm.properties and if necessary others. refer /libs/wcm/foundation/components/basicpage/v1/basicpage/cq:dialog to check those libraries and dependencies which helps /libs/wcm/found...

Hello, Did you configure your next site under same domain or using separate domain?? Thanks,Pawan

above document i went through but it did not explain how i can use because once i created touchUI dialog using xtype, its not working. Now looking for any approach to make it work without writing same xtype again using coral/granite api.

It means there is no solution to upgrade custom widget (ext js) to touch ui?? or no process around that??

Hello,I am looking for a method replacement for  mboxCurrent.getParameters() returns all the parameters passed during mbox call (used to be available in earlier mbox.js) in target premium (at.js response) which i can use. I know there are methods for example mbox.param('param_name') but it only work...

I would say, it doesn't require to check for null because if you look at the details about adaptTo() it says "The adapter target or null if the resource cannot adapt to the requested type" it means will only return null if resourceResolver object (if exist) can not map to session (type) and it will ...