A custom field must be created to represent the Creative Manager and allow the selection of an existing resource name in the Workfront application Which type of field and object type should be selected?
When configuring metadata mapping between Adobe Workfront custom form fields and Adobe Experience Manager metadata properties, you can use Issue and Document custom forms to define these mappings. These types of forms are commonly used for tracking and managing work items and documents, both of which need to have their metadata synchronized between the two systems.
Issue custom forms: Used for tracking work requests, such as issues or tasks.
Document custom forms: Specifically used for managing metadata related to documents, which can be mapped directly to AEM assets.
Options C (Portfolio) and D (Program) are not typically used for metadata mapping related to assets or documents.
Refer to Workfront Enhanced Connector documentation for more information on mapping custom forms to AEM metadata properties.
Lorrie
4 months agoLaurena
4 months agoJuan
4 months agoVicente
5 months agoChan
5 months agoMalcom
5 months agoJamal
5 months agoLouvenia
5 months agoDevorah
6 months agoKanisha
6 months agoVallie
6 months agoFletcher
6 months agoVanda
6 months agoCarlene
6 months agoDesirae
11 months agoShawnda
9 months agoLeonard
9 months agoGlenn
10 months agoTerrilyn
11 months agoJerry
11 months agoDorinda
10 months agoRosendo
10 months agoBeata
11 months agoElina
11 months agoTequila
12 months agoLyla
10 months agoStephaine
10 months agoWalton
10 months agoFrancene
11 months agoSharika
12 months agoMaryln
12 months agoEvette
12 months ago