From what I see, there should not  be a need to add this node manually. The node structure created automatically seems to be incorrect. Nested parsys path should auto-point to the correct path under designs.

Sure.. I have created a package with 2 teaser components - one using teaser and other one with experience. Here is the link:experience-campaign.zip - Google Drive Check page : http://localhost:4502/cf#/content/geometrixx-outdoors/en/men/coats/edmonton-winter.html - In first component, I have using c...

You can take a look at my comment on this Re: How to add multiple rootPath in Coral 3 Pathfield 

I am not sure if and how that can be done..

You will need to overlay/extend this component... - Overlay /libs/granite/ui/components/coral/foundation/picker/picker.jsp to accept multifield.- Overlay /libs/granite/ui/components/coral/foundation/picker/picker.jsp to check for multiple root paths instead of single, in method "getCrumbs".

It depends on the campaign structure. If all are under a single campaign, use teasers and campaign path would be used to resolve these. If they are spread across different campaigns, use "experience". Instead of "campaign path", "location" in teaser component is used to resolve experiences.

You can cache the necessary things in JCR..Load dropdowns from JCR, if not there -> call API.. Once API returns, store the info in nodes again...

smacdonald2008​: This is just a clarification and not the correct answer. The issue is still there

You can overlay or extend "/libs/cq/workflow/components/model/participant" and update the dialog as per your needs

I tried your code on 6.3.. The handlers are getting triggered correctly. When you say " I activate the page second or third time, the Event handler does not react", do you make any change before activating the page again?When there is no change, activation is never really triggered, so corresponding...