The issue of the custom field not displaying correctly on a component is likely because the

namespace 'myProject' is not registered in AEM. AEM requires that custom namespaces be

registered before they can be used for storing metadata properties. Without registering the

myProject namespace, the system cannot properly recognize the custom property, leading to issues

displaying the value.

Namespace registration: Custom namespaces like myProject need to be defined in AEM before they

can be used to store properties.

Option A is incorrect because the text field should accept special characters, and Option B is incorrect

unless there is already a conflicting property name, which is not indicated in this scenario.

Refer to AEM documentation on namespace registration for steps on how to register a custom

namespace in AEM.

In AEM, for a custom workflow process to be available for selection in the dropdown menu of a

process step, the process.name property must be set in the @Component annotation. This property

defines the unique name under which the custom workflow process will be registered and visible in

the workflow model editor.

Here is an example of how this should be added to the existing code:

@Component(service = WorkflowProcess.class,

property = {"process.label=Custom Workflow Process",

"process.name=customWorkflowProcess"})

process.label: This is the label that appears in the workflow model editor dropdown.

process.name: This is the internal identifier used by AEM to register the workflow process.

Options A and B would define other properties but will not resolve the issue of the custom workflow

not appearing in the dropdown. The key property needed here is process.name.

For more details, refer to the AEM documentation on creating custom workflows and annotating

components.

In this case, the customer wants to define the linked folder structure based on the Workfront

Portfolio name, Program name, Project name, and Project Type. The Project Type is a custom form

field with specific choices like "Campaign," "Product Launch," etc.

The correct format to define the folder structure in AEM based on these elements would be:

Portfolio, Program, Name, projectType: This structure will create a hierarchical folder system in AEM

where the folders are nested by Portfolio, Program, Project Name, and Project Type (which is pulled

from the custom form field).

Option A includes an incorrect syntax with "DE

," which is not necessary, and Option C repeats the "Program" and misorders the fields.

Refer to Workfront Enhanced Connector documentation for further guidance on defining folder

structures using custom form fields.

In Adobe Experience Manager (AEM), when mapping metadata fields from Workfront, custom form

fields are referenced using the CUSTOM FORMS prefix followed by the internal name of the field. In

this case:

The Label is "Creative Manager"

The Name is "managerCreative," which is the internal field name in Workfront.

To reference this field in AEM metadata, you need to use the CUSTOM FORMS: prefix followed by the

field's name, making the correct reference CUSTOM FORMS: managerCreative. This ensures that

AEM can correctly pull the metadata value from Workfront when syncing or using the Workfront

enhanced connector for AEM.

Options A and B are incorrect because they either lack the proper formatting or are incomplete.

For more details on this configuration, you can refer to Adobe Workfront's enhanced connector

documentation for AEM, particularly around metadata mapping and field referencing practices.

In Workfront, the best way to ensure that all documents within a project are shared with a

designated team is to share the entire project. By sharing the project, all documents and related

assets within that project are automatically made available to the designated team members

according to the project's access permissions.

Option C is incorrect because sharing one document does not automatically inherit the same access

levels for the other documents. Option A suggests linking documents from AEM, but the question

pertains to sharing documents within Workfront itself.

Refer to Workfront’s documentation on document sharing for detailed instructions on how to share

all project-related assets with teams.

The Author permission role is necessary for the design team members who need to edit the proofs

before they are sent for review by legal and financial teams. This role allows them to make changes

directly to the proof and upload new versions, which is essential for their work in this multi-stage

automated workflow.

Author role: Grants permission to edit and manage the proof, which includes uploading new versions

and making changes to the existing proof content.

Options B (Reviewer) and C (Approver) are more restrictive roles that do not allow for editing proofs.

Refer to Workfront Proofing roles and permissions documentation for more information on the

different proof roles.

The requirement is to allow users to select a resource (Creative Manager) from a list of existing users

in the Workfront application. The appropriate solution is to use a Typeahead field with the User

object type.

Field type - Typeahead: This field allows users to start typing the name of an individual, and the

system will auto-suggest matching users from the Workfront database. This is ideal for scenarios

where you need to assign a specific role, like a Creative Manager, from a list of existing users.

Object type - User: By using the User object type, the field will link directly to Workfront's user

directory, ensuring that the selection is limited to valid, active resources in the system.

This combination of field and object type is the most efficient for assigning roles based on existing

users, as it prevents errors and ensures data consistency by utilizing Workfront’s internal user

directory.

Options B and C are not suitable because a calculated field is not required, and checkboxes do not

allow selection from a list of user names.

For further reference, consult the Custom Fields and Typeahead Fields sections in Workfront’s

documentation, which outline how to configure these fields to enable user selection from the

organization’s resource pool.

To enable the search of products by SKU number in AEM, two main configurations are required:

Multi Value Property Predicate: By using a Multi Value Property Predicate, users can search for

multiple SKU numbers at once. This is crucial if product owners need to query for multiple products

simultaneously.

Single Line Text Field for SKU: SKU numbers are typically unique, so adding a Single Line Text field to

the image metadata schema for SKU numbers ensures that each image has its own SKU field for

accurate identification during searches.

Option D is incorrect because SKUs are usually single, unique identifiers, so a Multi Value Text field

isn’t necessary for each SKU.

Refer to AEM’s documentation on customizing metadata schemas and Assets Admin Search to

implement these features.