During the configuration of the Enhanced Connector the consultant is working to make sure that the required packages are added to the pom.xmi of all subprojects. Which section should the packages be added to?
When adding the required packages for the Enhanced Connector in AEM, they should be added to the Embedded section of the pom.xml for all subprojects. The Embedded section is used to define dependencies that need to be bundled with the AEM project, ensuring that the connector's functionality is included in the deployment.
Option A (Tools) is incorrect because this section is used for development tools, not dependencies. Option C (Servers) refers to server configurations, which is unrelated to package embedding.
Refer to AEM Maven project documentation for more details on embedding packages in the pom.xml file.
A company has multiple departments that use AEM assets, but would like only one of the departments to use a custom metadata schem
a. They want to add a 'verifiedBy' user picker field for its image assets.
What action should be taken to implement this requirement?
In this scenario, the company wants only one department to use a custom metadata schema with a 'verifiedBy' user picker field for image assets. The best approach is to:
Create a new metadata schema for the specific department.
Extend the Coral UI Component to create a custom user picker field, which will allow the department to select users from the list of available users in the system.
Option A suggests modifying the default image metadata schema, which could impact all departments, and Option B involves manually adding users to a dropdown, which is not as efficient as using a user picker field.
Refer to AEM documentation on creating custom metadata schemas and extending Coral UI components for more information.
An implementation consultant wants to configure the enhanced connector inside a customer's Adobe experience Manager environment. The customer has expressed interest in automatically publishing assets when they ore sent from Adobe Workfront to Adobe Experience Manager. The customer does no! have an instance of Brand Portal running.
The customer has a project custom form field with the following details:
The customer wants this automatic publishing to be conditional on the value of the project custom form field being equal to, Yes.
Which option should be used to implement this feature?
To implement conditional automatic publishing of assets from Workfront to AEM based on the value of the custom form field, you should:
Check the option 'Automatically publish assets when sent from Workfront': This ensures that the assets will be automatically published to AEM when they are sent from Workfront.
Use the custom form field ('auto_publish_assets'): The system needs to check the value of this custom form field, and if it is set to 'Yes', the assets will be automatically published.
Set the Custom Form Field Value to 'Yes': In the configuration, you'll specify that automatic publishing only occurs when the field value is 'Yes.'
Option B incorrectly refers to 'Workflow' instead of 'Workfront,' and Option C refers to publishing to Brand Portal, which is irrelevant since the customer does not have Brand Portal.
Refer to Workfront for AEM Enhanced Connector documentation for step-by-step guidance on configuring conditional automatic asset publishing.
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?
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.
A user wants to send a new version of a document they have uploaded to Workfront (o make sure that this latest version is now available in Adobe Experience Manager Assets. This document has previously been uploaded into both Workfront and the AEM.
How should the user accomplish this?
To upload a new version of a document and ensure it is available in AEM Assets, the user must select the New Version option in Workfront. This triggers the version control process where the updated file can be uploaded.
By choosing the Experience Manager integration after selecting New Version, the system ensures that the latest version of the document is sent to AEM Assets, where it will replace the previous version without losing version history.
This workflow supports maintaining version control between Workfront and AEM, ensuring that the most current version of the asset is always available in both systems.
Refer to the Workfront-AEM Enhanced Connector Guide for further details on version control and document updates between Workfront and AEM.
