Level 2

Solved

Adobe Campaign Classic: Change Content selector’s default search from Name to Label

6 replies
61 views
Translate All

Hi everyone,

We are using Adobe Campaign Classic 7.4.2 and in a workflow’s Content Management activity, we select Explicit and open the Content selection dialog.

The dialog’s default search field is “Name contains”, which searches the content’s internal name (@name). Our users identify content by its Label (@label), rather than its automatically generated internal name. We would therefore like the default search field to be “Label contains”. Is there a supported way to configure this selector to search by Label instead of Name?

The relevant input in the xtk:workflow input form is:

I tested adding filterEditField="@label": <input filterEditField="@label" img="ncm:content.png" xpath="content"/> but the selection dialog still displays “Name contains”.

For context: The target schema is ncm:content. Its compute string is already <compute-string expr="@label"/>. The ncm:core navigation hierarchy defines the content list under ncmChannel, with @label as the first column. Searching through Advanced filter → Label → contains works, but we would like Label to be the default quick-search field.

Where is this default search configured: in the input form, the target schema, a predefined filter, or elsewhere? Ideally, we would like a solution scoped to this selector and implemented in our own namespace, without directly modifying out-of-the-box objects or changing the content’s internal-name key. Any guidance or a working XML example would be greatly appreciated.

Thanks!

Amine_AbedourAccepted solution

Community Advisor and User Group Leader

Hello @Cl4ud ,

the form part of the filter is :

it is defined as default for ncm:content documents here :

Maybe this predefined filters is stored elsewhere in your instance, please verify by querying the data schema queryFilter like this :

if needed here is the filter in a package :

<package author="Administrator (admin)" buildDate="2026-10-20 10:16:59.456Z" buildNumber="9402"
         buildVersion="6.7">
  <entities schema="xtk:queryFilter">
    <queryFilter default="1" hasForm="1" label="By name" name="byNameContent" schema="ncm:content">
      <where filteringSchema="ncm:content">
        <condition enabledIf="$(/tmp/@text) != ''" expr="@name LIKE '%' + $(/tmp/@text) + '%'"
                   internalId="1"/>
      </where>
      <form>
        <input label="Name contains" noTransaction="true" type="edit" xpath="/tmp/@text"/>
      </form>
      <folder _operation="none" name="xtkQueryFilter"/>
    </queryFilter>
  </entities>
</package>

I hope this is helpful for you.

Br,

Amine ABEDOUR

Amine_Abedour

Community Advisor and User Group Leader

Hello @Cl4ud,

There is a predefined filter which is set to be the default for the ncm:content schema. It is based on the @name field, and you can change it to your liking.

Br,

Translate

Amine ABEDOUR

Cl4udAuthor

Level 2

Thanks Amine! I checked Administration → Configuration → Predefined filters in our DEV instance (ACC 7.4.2). With both search fields cleared, the list shows 69/69 filters, but none targets ncm:content, and byNameContent is not listed.

Nevertheless, the Content selector still displays “Name contains”.

Could you share the XML definition of byNameContent, including its form and how it is configured as the default for ncm:content? Is it supplied by a particular Content Management package, and where does the selector obtain its default search when that predefined filter is absent?

We would prefer a custom-namespace solution scoped to this selector.

Thanks again!

Translate

Amine_Abedour

Accepted solution

Community Advisor and User Group Leader

Hello @Cl4ud ,

the form part of the filter is :

it is defined as default for ncm:content documents here :

Maybe this predefined filters is stored elsewhere in your instance, please verify by querying the data schema queryFilter like this :

if needed here is the filter in a package :

<package author="Administrator (admin)" buildDate="2026-10-20 10:16:59.456Z" buildNumber="9402"
         buildVersion="6.7">
  <entities schema="xtk:queryFilter">
    <queryFilter default="1" hasForm="1" label="By name" name="byNameContent" schema="ncm:content">
      <where filteringSchema="ncm:content">
        <condition enabledIf="$(/tmp/@text) != ''" expr="@name LIKE '%' + $(/tmp/@text) + '%'"
                   internalId="1"/>
      </where>
      <form>
        <input label="Name contains" noTransaction="true" type="edit" xpath="/tmp/@text"/>
      </form>
      <folder _operation="none" name="xtkQueryFilter"/>
    </queryFilter>
  </entities>
</package>

I hope this is helpful for you.

Br,

Translate

Amine ABEDOUR

Cl4udAuthor

Level 2

Thank you for you clarity Amine! i must rectify my answer: i could in the end find the right filter and change it as i wanted but the remaining issue is the selector’s initial folder/channel. It opens in AC_default → Resources → Contents, whereas our content is stored in company-specific Contents folders. Searching by Label only returns results after selecting the appropriate folder. The navigation model uses folderLink="channel", and ncm:content/channel joins @channel-id to ncm:channel/@id. Is there a supported input-form setting to specify the initial channel, or search across accessible channels, scoped to this workflow selector rather than globally?

Translate

Amine_Abedour

Community Advisor and User Group Leader

@Cl4ud,

If I understand correctly, you want to restrict the folder selector choices to custom, company-specific content folders. If so, you can use the folderFilterChoice form input setting. Take a look at out-of-the-box forms like nms:newdelivery to see how it's configured.

Br,

Amine

Translate

Amine ABEDOUR

Cl4udAuthor

Level 2

Hi Amine,

Thank you for your help and the suggestion regarding folderFilterChoice.

I ultimately took a different approach: instead of further configuring the standard selector, I replaced it in the workflow’s Explicit content selection mode with a dedicated metadata picker.

The picker uses a subFormLink containing a linkListChoice for ncm:content. It displays Label alongside our custom metadata columns, allowing users to identify the content more easily.

After the user confirms a selection, we copy the selected content’s @id and @_cs into the activity’s existing content reference attributes. We then display the selected name and ID in two read-only fields:

<input label="Selected content" readOnly="true" xpath="@content-cs"/> <input label="Content ID" readOnly="true" xpath="@content-id"/>

The key part of the picker’s <leave> handler is:

<set expr="[/ignored/lfContentChoice/content/@id]" xpath="@id"/> <set expr="[/ignored/lfContentChoice/content/@_cs]" xpath="@content-cs"/> <set expr="[/ignored/lfContentChoice/content/@id]" xpath="../@content-id"/> <set expr="[/ignored/lfContentChoice/content/@_cs]" xpath="../@content-cs"/>

These read-only fields update immediately after confirming the picker, without needing to confirm the parent activity dialog or save the workflow. Cancelling the picker preserves the previously confirmed selection.

We removed the standard content selector from Explicit mode because its displayed name could remain outdated. The other content selection modes remain unchanged.

This is an alternative UI approach rather than a configuration fix for the standard selector initial folder/channel. It does involve updating the xtk:workflow form, so it does not fully meet our original preference for a custom-namespace-only solution.

One practical lesson from testing: clear the client’s local cache after updating the form, otherwise the console may continue using the previous definition. :D

Thanks again for pointing me in the right direction!

Translate

Sign up

Login with SSO

Login to the community

Login with SSO