AD0-E908 Exam Dumps - Adobe Workfront Core Developer Professional

ï‚·Objective: Understand how requests are routed when the default assignee in a routing rule is deactivated.

ï‚·Routing Behavior:

Explanation: Workfront does not automatically reassign requests when the default assignee is deactivated. Requests will continue to be routed to the deactivated account unless manually reconfigured.

ï‚·Create the report:

Ensure that the reports intended for use in dashboards are created beforehand and contain the necessary data.

To export all calculated custom fields and associated custom expressions to an Excel file, the system administrator should:

Create a Parameter Report: Generate a parameter report within Workfront, filtering it to include only those parameters where the type is "Calculated."

Export to Excel: Once the report is generated, it can be exported to Excel. This method provides a comprehensive list of all calculated custom fields and their expressions, which can then be used to create a data dictionary.

References

Workfront documentation on creating and exporting parameter reports includes instructions on filtering by parameter type and exporting data to Excel​​​​.

ï‚·Objective: Ensure that everyone in the organization can fill out the general project custom form associated with the general project template.

ï‚·Form Sharing Settings:

Correct Setting: Update the form sharing to "Make this visible system-wide so that everyone in Workfront can see it".

Explanation: This setting ensures that the form is accessible to all users within the system, allowing anyone to fill out the form as required.

In Adobe Workfront, Custom Forms can be shared by their authors with specific permissions. The author of a Custom Form has the ability to control who can view, share, and edit the form. These permissions can be set for individuals, roles, groups, teams, and even across the entire company. This functionality is critical for maintaining control over who can access and modify the forms, ensuring that only authorized users have the appropriate level of access.

References

This information is consistent with the permissions settings outlined in the Workfront documentation and in various training resources provided by Adobe​​​​.

ï‚·Objective: Set up a consistent review and approval process where the approvals are first routed to the users' team and then to their manager.

ï‚·Workflow Setup:

Step 1: Create an automated workflow template within Workfront.

Step 2: Define two stages in the workflow template:

Stage 1: Approval by the team members.

Stage 2: Approval by the manager.

Step 3: Apply this workflow template to the uploaded proof assets.

Explanation: This ensures a structured and consistent approval process, routing the assets first to the team for feedback and then to the manager for final approval.

For the successful conversion of requests to projects using a template, it is essential that the Triage team is properly set up in Workfront. Specifically:

Part of the Routing Rule: The Triage team must be included in the routing rule on the request queue. This ensures that the requests are directed to them for review.

View Access on Templates: The Triage team needs to have "view" access to the applicable templates. This access allows them to utilize the templates when converting requests into projects.

References

Workfront documentation on setting up request queues and routing rules highlights the importance of including the correct teams and assigning appropriate access rights​​​​.

ï‚·Objective: Track project metrics based on the submitted request without allowing the requester to fill in this information.

ï‚·Configuration Steps:

Step 1: Create a Custom Form with the necessary metric fields.

Step 2: Do not include these metric fields in the part of the form visible to the requester.

Step 3: Add these metric fields to the project details section instead.

Explanation: This ensures that the requester does not input the metric information, but the information can still be tracked and recorded as part of the project details.

Objective: Identify benefits of utilizing a project template for a new digital deliverable process workflow.

Benefits:

Benefit 1: Adherence to an accurate, repeatable process

Explanation: Using a template ensures consistency and accuracy in the process, as the same steps are followed each time.

Benefit 2: Sharing settings completed by default

Explanation: Templates can have predefined sharing settings, reducing the need to manually configure these settings for each new project.

Benefit 3: Efficiency in creating new projects

Explanation: Templates streamline the project creation process, saving time and effort by providing a pre-defined structure.

ï‚·Objective: Share a financial report with internal users while preventing external vendors from viewing it.

ï‚·Steps:

Step 1: Open the financial report settings in Workfront.

Step 2: Configure sharing settings to give view access only to users within the primary company.

Explanation: By restricting view access to only the internal users of the primary company, external vendors will not have visibility of the financial report.

Inherited status names:

Sub-groups inherit the project status names from their parent group unless explicitly overridden. Therefore, the AP sub-group under the Finance group will use the same custom project status names assigned to the Finance group.

For efficient use of a project template that captures phases within each project and supports critical-path timelines, the following elements are essential:

Predecessors: These define the relationships between tasks, ensuring that the sequence of tasks reflects their dependencies. This is crucial for maintaining the integrity of the critical path.

Milestone Tasks: These are key tasks that mark significant points or stages in the project timeline. Including milestone tasks helps in tracking progress and ensuring that critical deadlines are met.

References

The importance of predecessors and milestone tasks in project templates is emphasized in Workfront's project management guidelines and best practices for creating reusable workflows​​​​.

ï‚·Objective: Customize a layout template for a group of users in Workfront.

ï‚·Customizable Items:

Option A: Views, filters, and groupings used with reports

Explanation: You can customize how data is displayed in reports by setting specific views, filters, and groupings in the layout template.

Canvas Dashboards:

Canvas Dashboards provide users with the ability to build effective reporting visualizations, offering increased visibility and flexible layout options. They allow for the integration of various report types and interactive elements.

Identify the Requirement: The admin needs to set up an Automated Workflow Template and ensure that the design team can view the new templates.

Understanding Sharing Mechanisms in Workfront: Workfront allows administrators to share templates, projects, and reports with specific users or groups to ensure visibility and collaboration.

Creating the Automated Workflow Template:

Navigate to Templates: In Workfront, go to the Templates section.

Create New Template: Select the option to create a new workflow template.

Define Workflow: Set up the workflow steps, including tasks, approvals, and dependencies, as required for the design team's processes.

Save the Template: Ensure the workflow template is saved correctly in the system.

Sharing the Workflow Template:

Select the Template: Go to the created workflow template in the Templates section.

Share with Design Team: Use the sharing options to specifically share the template with the Design Team group. This ensures that only the design team has access to the new workflow template.

Set Permissions: Define the level of access the design team will have, such as view, edit, or manage permissions.

Communication and Training:

Notify the Design Team: Inform the design team about the new workflow template and how they can access and use it.

Provide Training: Offer training sessions or materials to help the design team understand how to use the new automated workflow template effectively.

To ensure that progress on the board is also tracked in a project, a project manager can use connected cards. Connected cards link tasks or issues on an agile board directly to tasks or issues within a project, ensuring that updates made on the board are reflected in the project and vice versa.

Enable Agile in the Project:

Navigate to the project settings.

Ensure that the project is set up for agile tracking by enabling the relevant agile settings.

Create Connected Cards:

Within the agile board, create connected cards by linking tasks or issues directly to the corresponding tasks or issues in the project.

This can typically be done by selecting the task or issue on the board and choosing the option to connect it to a project task or issue.

Update and Track Progress:

As team members update the connected cards on the agile board, the progress will automatically be tracked in the linked project tasks or issues.

This ensures that both the board and the project reflect the same status and progress.

References:

The use of connected cards for ensuring synchronization between board progress and project tracking is covered in the agile and project management training materials provided by Workfront (webinaradminessentialsuxinterfacedesignmar1520231678820264387)​​.

Widgets in Canvas Dashboards:

Canvas Dashboards support the addition of widgets, which are not available in legacy dashboards. Widgets provide dynamic and interactive elements that enhance the visualization of data.

Identify the Requirement: The client needs to track "breaks" during the employees' workday to report on utilization. This requires a way for employees to log their break times accurately.

Understand Workfront's Time Tracking Capabilities: Workfront allows the creation of different hour types which can be assigned to timesheets. This flexibility helps in categorizing time entries for various activities, such as work, meetings, training, and breaks.

Creating a "Break" General Hour Type:

Navigate to Setup: As a system administrator, go to the Setup area in Workfront.

Access Hour Types: Under the "Timesheets & Hours" section, select "Hour Types".

Add New Hour Type: Click on the option to add a new hour type.

Define Hour Type: Name the new hour type as "Break". You can provide a description for clarity. This will help users understand that this category is specifically for logging break times.

Save the Hour Type: Ensure to save the new hour type so that it becomes available for timesheet entries.

Assigning the "Break" Hour Type to User's Timesheet Profile:

Navigate to User's Profile: Go to the user's profile settings.

Edit Timesheet Profile: Within the profile, locate the section for timesheet settings.

Add Hour Type: Include the newly created "Break" hour type to the list of available hour types that users can select when logging their hours.

Save Changes: Ensure that all changes are saved so users can start using the "Break" hour type in their timesheets.

Implementation and Training:

Communicate with Users: Inform users about the new "Break" hour type and provide instructions on how to log their break times in their timesheets.

Monitor Utilization: Track the usage of the new hour type to ensure that it is being utilized correctly and effectively for reporting purposes.