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 internal marketing department is building a new workflow where they need to have the task assignee upload a document. That document then needs to be reviewed and potentially marked up with annotations as part of the review process. Then the document needs to be approved by the director of creative marketing and the customer. Which document management process meets this requirement?
For a workflow where a task assignee must upload a document, have it reviewed and marked up with annotations, and then have it approved by the director and customer, the best option is to upload the document with a proofing approval workflow attached. Proofing workflows allow for:
Annotations: Reviewers can mark up the document with comments and annotations.
Approvals: Once the document is reviewed, it can go through the necessary approval stages, including the director and customer.
Option A (using approvals under document details) does not allow for the same level of markup and annotation as a proofing workflow. Option C (uploading to a subtask) is not an ideal way to manage the review and approval process with annotations.
Refer to Workfront's proofing documentation for more information on setting up proofing workflows with annotations and approvals.
A company has a set of DAM assets related to 'hiking' Most of the assets have the keyword 'hiking'' In title and/or description in the metadata, and they are showing up in omnisearch while searching for 'hiking'. Another set of mountain assets are later added to the DAM without the 'hiking" keyword in their metadata.
what changes can be made to include the mountain assets in the top of the result while searching for hiking"?
To include the mountain assets in the search results for 'hiking' and ensure they show up at the top of the search, the best approach is to assign the 'hiking' tag to these assets. By using tags, you can enhance the discoverability of the assets without modifying their titles or descriptions. Tags are indexed and have a strong influence on search results in AEM.
Tagging assets is an efficient way to associate them with relevant topics or keywords, such as 'hiking,' which would improve their ranking in search results.
Option A suggests using 'search boosting,' which does not exist in AEM's metadata editor. Option C involves adding 'hiking' to the content and status fields, which isn't the best way to influence search ranking and could clutter the metadata.
Refer to AEM documentation on metadata tagging and search optimization for more details.
An AEM server is overloaded with too many concurrently running workflows. The developer decides to reduce the number of concurrent workflows. What should be configured?
In AEM, to limit the number of concurrent workflows running at the same time, you need to adjust the Maximum Parallel Jobs setting in the OSGI console. This setting controls how many workflow jobs can be processed simultaneously, and reducing this number will lower the load on the server by limiting the number of workflows that can run concurrently.
This setting can be found under the Day CQ Workflow - Workflow Engine configuration in the OSGI Web Console.
Options B and C refer to specific workflows and threads, but they do not directly address the overall system limit on concurrent workflow executions.
Refer to the AEM documentation on workflow scaling and performance for more information on how to adjust these settings in the OSGI configuration.
A user creates a custom metadata schema that includes a multi value text field After modifying the file that the metadata has been applied to, the user discovers that the property corresponding to the multi value text field contains a new value.
what caused the value to become populated?
If the multi-value text field is being populated unexpectedly, the most likely cause is that another field in the metadata schema is mapped to the same property. When multiple fields are mapped to the same property in AEM, any updates to either field will overwrite or modify the property, leading to the unexpected population of values.
This can happen due to schema misconfiguration, where fields unintentionally share the same JCR property path.
Option B is incorrect because the value being required would not cause it to be populated automatically. Option C suggests simultaneous updates by different users, which is unlikely to cause the issue described.
Check the metadata schema configuration to ensure fields are mapped to distinct properties.
