Experience Manager Guides

sschnelbach · 12/8/25

I cannot create a condition preset in a map CREATED in v5.1.1, but I can create a condition preset in old maps that were created in previous versions of Guides on our testing server. I can apply conditions in older DITA files and new ones created in v5.1.1, but the Map Console isn't loading the conditions that appear within the new map.

What am I missing? The Conditions exist in the Folder Profile. I can apply them in the topics, but the new map isn't loading them for selection.

AEM 6.5.23

AEM Guides 5.1.1

DivrajSingh · 12/10/25

@sschnelbach: are you trying to create condition preset on the output preset in the map console or in the map dashboard?

If a map has conditions in its content that are same as available values on the folder profile (chosen in user preferences) then they should show up in the Condition Preset on map.

Also, can you try to run parent map indexing for the new map where conditions are not showing up. [steps given in the upgrade guide - refer deep link to that section]

Would you be able to share a screenshot or sample content? that can help us comment further.

sschnelbach · 12/10/25

I am trying to create a Condition Preset on the Map Console > Condition preset screen.

I can create a new preset, but none of the Attributes present in the topics within the map load for selection to include/exclude. This only happened with the map I created in v5.1.1. Existing maps created in v4.6 and earlier do allow me to create a new preset (the attributes load) or edit an existing preset.

And yes, the topic I use for testing conditions is in this map.

DivrajSingh · 12/10/25

@sschnelbach Is it possible for you to check if the conditions are extracted in the topic metadata ?

To verify can you check if the jcr:content/metadata has the property "attrValList" (see [1]) with the expected condition values. Because this is the basis of showing the conditional attr/val from the map content.

If above is also available, and based on what you have stated earlier - it may need to be debugged on your setup/content.

[1]:

sschnelbach · 12/10/25

I just confirmed that the older maps (created in v4.4 and v4.6) are also not working correctly with regard to conditions. I can create Condition presets, but only some of the attributes display, not all of them.

And yes, I verified they were defined in the folder profile on the test server and they are selectable in the Editor to apply (props). We did not create any custom attribute names (platform, props, audience, product), only the values (platform=datasheet, manuals; props=discrete, analog; product=dxm, multifhop, etc).

DivrajSingh · 12/10/25

@sschnelbach can you try to run parent map indexing for the map where conditions are not showing up. [steps given in the upgrade guide - refer deep link to that section]

It is a POST request to the server (with authentication) -

POST-
https://<server:port>/bin/guides/map-find/indexing

You can pass specific paths of the maps to index them, by default all maps will be indexed 
For example : https://<Server:port>/bin/guides/map-find/indexing?paths=<map_path_in_repository>