This seems very promising and I greatly appreciate your input.We would
have to get the approval of our authors, but I l very much ike the idea
and regret not having thought about it myself.I'll keep this post
updated. Thank you so much.
@parag_dalal You should see those fields only when you integrate AEM and
Target using Adobe I/O only. If the integration method is same then just
check your AEM installation and find out if any of packages are in
uninstalled state. Also, see if the number of bundles in both instances
are same and in active state.
Thank you, this was it. I was convinced the team responsible for Target
had given me the correct informations, but it seems there had been a
misunderstanding. Thank you again for prompting me to check back with
Hi @parag_dalal , The component you are refering to "trouble component"
is to be configured only once and then to be used in all the pages. You
can achieve such a usecase with experience fragment. You can configure
such components on experience fragments and include the experience
fragment component on the structure of page so that it appears on all
pages. Here are the useful refrences to understand experience
There was indeed an overlay and it seems a team was toying with
customizing permissions; but since they assigned all users to the group
that was forbidden from editing, the options had disappeared. The issue
has been since resolved. Thank you, Vishu, for you precious suggestions.