AEM Page Properties

More details on Classic to Touch Ui migration for AEM

In our previous post on Classic to TouchUI migration we described some “quirks” that we have encountered. In this new post, we focus on the issue of migrating Page Properties, which must be done upfront since AEM doesn’t provide a compatibility mode for them, as it does for other dialogs.

Adobe Experience Manager provides Page Properties that store a page’s meta information, as well as some other page-related information. For most projects, customization of page properties across multiple templates is very common, so an approach to migrating these customizations to Touch UI in a large-scale AEM project is critical—in addition to the component dialogs themselves.

Why? If your plan is to switch the default AEM authoring experience to Touch UI, your publishers may be frustrated having to switch back to the Classic UI only to modify a page’s properties. There’s a switching cost here that needs to be addressed.

Page properties are defined in the dialog of the page rendering component which also must be migrated to TouchUI. But while AEM provides a so-called compatibility mode for component dialogs, there isn’t one for the page properties. Instead, the dialog of a default page (under /libs) is used.

Here are some tips that we’ve learned from migrating a large project’s page properties to TouchUI.

Prior to migration, collect all the information about all the customizations across all the templates

This might sound obvious, but it’s not so simple! Consider the following example: if we need to change a single field label in a page properties dialog in ClassicUI, we end up with this code:


As you can see, in ClassicUI even a small customization results in a significant amount of overrides. Luckily, for TouchUI, Sling Resource Merger resolves this problem (more on that later). So, listing all new tabs as well as the customizations made to out-of-the-box tabs will help you to reduce the amount of code (and overall work) that has to be done.

Consider using the Dialog Conversion Tool

The Dialog Conversion Tool might not solve all of your problems, but it’s a good starting point. We used it initially to migrate a couple of dialogs and then made some tweaks and fixed some bugs. Here are some issues that we’ve encountered along the way:

  • Select fields with ACS lists as values required some special attention, because in TouchUI their configuration differs from Classic. Of course, for such special cases, a custom Rewrite Rule can be created, but we decided to fix these cases manually.
  • Default values on select fields are also a little bit tricky. In Coral3 select fields, the preselected option is specified by setting selected=true to the option itself, while in ExtJS the preselected option is defined in the defaultValue attribute. Unfortunately, the Dialog Conversion Tool does not cover this case, so some special attention should be paid to these fields.
  • Also, special attention should be paid to dialog field inheritance. The Dialog Conversion Tool does not add inheritance ‘locks’ to custom fields, so if the custom field page property is subject to roll out, the cq-msm-lockable attribute should be configured for such properties.
  • The Tab’s column container is for some reason migrated to Coral2 version instead of Coral3.

Consider reorganizing the cq:dialog file.

The output of the Dialog Conversion Tool is a single cq:dialog file containing all the tabs, even if they were included via the ‘include’ xtype. You can leave it as is, but consider moving all the tabs into a separate folder and include them into cq:dialog (as is done with default page properties).

Dialog structure

This will significantly increase the readability and reusability of the code.

Use the Sling Resource Merger mechanism as much as possible

Our last trick is using Sling Resource Merger to significantly reduce the number of overrides. With this powerful mechanism we can provide only the “diff” (what is actually changed), instead of copying the whole structure. Here is what the Basic Tab from the previous example will look like:

As you can see, with Sling Resource Merger we only need to provide the JCR structure and the actual changes (i.e. diff) of the nodes. Besides a much cleaner structure and a smaller number of overrides, this approach also simplifies the maintenance of overridden code.

Author: Liubou Masiuk

How can we help you?
Contact Us