AD0-E902 Exam Dumps : Adobe Workfront Fusion Professional

Understanding the Image and Context:

The image provided represents anHTTP modulein Workfront Fusion with a URL that dynamically references various data points (e.g., parameterID, customer.domain, emailAddr).

The structure of the URL indicates a call to the Workfront API (/api/v1.0/), using parameters to pass dynamic data such as parameterID, username, and password.

Why Option A ("Custom API Call") is Correct:

The HTTP module shown in the image is acustom API callbecause it interacts with Workfront's API endpoints by passing dynamic parameters through the URL.

Custom API Callmodules allow users to manually configure requests to endpoints in cases where no predefined Workfront Fusion module exists for the operation. This is evident in the example, where specific fields like parameterID, customer.domain, and others are manually mapped to the API URL.

Example Use Case: Dynamically creating custom form field options by sending a POST/PUT request to the Workfront API with specific parameters (like label and value) for each environment.

Why the Other Options are Incorrect:

Option B ("Misc Action"): This refers to predefined actions in Workfront Fusion for handling simple tasks. The HTTP module is not categorized under Misc Actions as it involves direct API interaction.

Option C ("Read Related Records"): This module is used to fetch data related to Workfront objects (e.g., related tasks or documents). It doesn’t allow dynamic parameter passing or URL customization as seen here.

Option D ("Search"): The Search module is used for querying Workfront objects based on specific criteria but does not involve making direct API calls or sending HTTP requests with custom parameters.

Steps to Configure a Custom API Call in Workfront Fusion:

Add theHTTP Moduleto your scenario.

Select the appropriate HTTP method (e.g., GET, POST, PUT). In this case, aPOSTorPUTmethod would be used to create or update custom form fields.

Enter the API endpoint in theURLfield, as shown in the image.

Map dynamic values to the parameters by referencing fields from previous modules in the scenario. For instance:

customer.domain: Extracted from prior steps.

parameterID, label, and value: Dynamically passed based on input data.

Authenticate the request using a username and password or an API token.

Test the module to ensure the API call works as expected.

How This Solves the Problem:

By using a Custom API Call (via the HTTP module), the user can dynamically interact with the Workfront API to create or modify custom form field options across multiple customer environments, passing the required parameters programmatically.

References and Supporting Documentation:

Adobe Workfront Fusion HTTP Module Documentation

Workfront API Documentation

Workfront Fusion Community Forum: Using HTTP Module for API Calls

Understanding the Requirement:

The project name in Workfront must include:

Purchase Order Number (PO#).

Name of the product.

PO Fulfillment Date (formatted as YY/MM/DD).

If a discount is provided, append the discount percentage and the approver's last name in the format: 15% Discount - UserLast.

Example Output:

sql

Copy

2837 - Compendium-Premium Running Shoes - 21/02/16 - 15% Discount - UserLast

Why Option A is Correct:

The expression in Option A achieves the desired result step-by-step:

3.PO#: Includes the PO number.

3.Name: Appends the name of the product.

formatDate(3.PO Fulfillment Date, YY/MM/DD): Formats the PO Fulfillment Date in the desired YY/MM/DD format.

if(3.Discount Provided? = "Yes"; "- " + 3.Discount % + " Discount - " + 3.Approver Last Name):

Uses the if function to check if a discount was provided.

If "Yes," it appends the discount percentage (3.Discount %) and approver's last name (3.Approver Last Name) with the required format.

Why the Other Options are Incorrect:

Option B:

The expression is incorrect because it places if(3.Discount Provided?...) directly after PO Fulfillment Date without using formatDate for date formatting. This results in an unformatted date.

Option C:

Uses parseDate instead of formatDate, which is incorrect in this context. parseDate is used to interpret strings as dates, not to format dates for output.

Option D:

The expression does not include any conditional logic for checking if a discount is provided. It simply appends Discount - Approver Last Name regardless of whether a discount was given.

Steps to Use the Expression in Workfront Fusion:

Place the expression in the module that defines the project title in Workfront.

Map the fields (PO#, Name, PO Fulfillment Date, etc.) to the respective columns from the CSV data.

Test the scenario to ensure the output matches the desired format.

Final Expression (Option A):

3.PO# + " - " + 3.Name + " - " + formatDate(3.PO Fulfillment Date; YY/MM/DD) + if(3.Discount Provided? = "Yes"; " - " + 3.Discount % + " Discount - " + 3.Approver Last Name)

References and Supporting Documentation:

Adobe Workfront Fusion Functions Documentation

Workfront Community: Handling Conditional Logic and Date Formatting

Step by Step Comprehensive Detailed Explanation:

Scenario Context:

The goal is to assign a user to all tasks on a project where the role is Copywriter.

The chosen method should minimize the number of operations to ensure efficiency.

Option Analysis:

A. Searching for all assignments in the project where the role is Copywriter and add the user to each assignment:

This approach involves searching assignments, iterating through them, and adding the user individually. Each iteration generates multiple operations, making it less efficient.

B. Searching for Tasks in the project with the Copywriter role and assign the user to each task:

Similar to Option A, this approach also requires iterating through tasks and assigning users one by one, resulting in a higher number of operations.

C. Using the Misc Action module for the project to assign all Copywriter assignments to the user:

Correct. The Misc Action module can perform bulk actions (e.g., assigning users to roles) in a single operation.

This method is the most efficient, as it minimizes the number of operations while achieving the same result.

Why the Misc Action Module is Best:

Efficiency: Bulk operations reduce the number of API calls and iterations.

Performance: Using fewer operations optimizes scenario execution and reduces resource consumption.

Simplicity: Avoids the complexity of iterating through tasks or assignments individually.

Implementation:

Add a Misc Action module to the scenario.

Configure the module to assign the user to all tasks with the Copywriter role on the selected project.

Test the module to ensure it performs the bulk assignment as expected.