A custom field needs to be mapped in AEM metadata mapping the field details are below: Label - Creative Manager Name - managerCreative Description The resource assigned the creative manager role How is the field from Workfront referenced in AEM?

When configuring metadata mapping between AEM and Adobe Workfront using the enhanced connector, custom fields must be referenced with a specific prefix to distinguish them from standard fields. The correct syntax is CUSTOM FORMS:, where is the programmatic name of the field in Workfront, not its display label. In this case, the field's name is managerCreative, so the correct reference in the AEM metadata schema mapping is CUSTOM FORMS:managerCreative.

A. CUSTOM FORMS Creative Manager: This is incorrect because it uses the field's display label ("Creative Manager") instead of its unique programmatic name (managerCreative).
B. managerCreative: This is incorrect because it omits the mandatory CUSTOM FORMS: prefix required for all fields originating from a Workfront custom form.

1. Adobe Experience League Documentation: Configure the enhanced connector for Adobe Workfront. Under the section "Configure metadata mapping between AEM and Workfront," the subsection "Map Workfront custom form fields" explicitly states: "To map a Workfront custom field, the mapping value must be in the format CUSTOM FORMS:." This confirms the required syntax. (Source: Adobe Official Vendor Documentation).