AD0-E902 Exam Dumps : Adobe Workfront Fusion Professional

Understanding the Scenario:

The image represents a Workfront Fusion scenario with a Workfront module, HTTP modules, and routers splitting the execution path.

The goal is to reuse multiple fields from the Workfront module (e.g., data extracted or processed earlier in the flow) as mapped expressions in HTTP PUT requests located in the bottom paths.

Why Option A is Correct:

Set Multiple Variables Module: This module allows you to define and store multiple variables at a single point in the scenario (e.g., after the Workfront module). These variables can then be reused throughout subsequent steps in the scenario.

Get Multiple Variables Module: By placing this module between the Text Parser and the bottom Router, you can retrieve all previously stored variables, ensuring consistent access across all branches of the flow. This avoids redundancy and ensures the data is easily accessible for each HTTP request in the bottom paths.

Why the Other Options are Incorrect:

Option B ("Set Multiple Variables after Workfront, Get Variables before each HTTP module"): This is partially correct but less efficient. Adding multiple Get Variable modules before each HTTP request results in repetitive configuration and increases maintenance complexity.

Option C ("Set Variable and Get Variable for each HTTP module"): Using individual Set and Get Variable modules increases duplication. This approach requires separate variables for each data point, which is inefficient compared to using the Set/Get Multiple Variables module for multiple fields at once.

Steps to Configure the Solution:

After the Workfront module:

Add aSet Multiple Variablesmodule.

Define all the fields required for the HTTP PUT requests as variables, mapping them from the Workfront module outputs.

Between the Text Parser and the bottom Router:

Add aGet Multiple Variablesmodule.

Retrieve the previously stored variables, ensuring they are accessible for all paths.

In the HTTP modules on each bottom path:

Use the retrieved variables for mapping in the PUT requests.

How This Solves the Problem:

This approach centralizes variable management, making it easier to access and modify data as needed.

It avoids redundancy, as variables are defined once and reused across all paths, reducing the risk of errors and ensuring consistency.

References and Supporting Documentation:

Adobe Workfront Fusion: Variables Module Overview

Workfront Community: Efficient Use of Variables in Fusion

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.

Understanding the Issue:

The customer is syncing20,000+ Salesforce Opportunitieswith Workfront projects using a scheduled Fusion scenario.

After running for 40 minutes, the scenario unexpectedly stops.

Why Option C is Correct:

Workfront Fusion Execution Timeout:

Fusion scenarios have a default execution timeout of40 minutesper run.

If the scenario exceeds this time limit, Fusion automatically stops the execution to avoid resource overuse.

Handling Large Data Sets:

Scenarios involving large datasets (like syncing 20,000+ records) may require optimizations, such as breaking the data into smaller chunks using paginated requests or iterators.

In this case, the scenario stopped because the execution timeout was reached, not due to API limits or webhook restrictions.

Why the Other Options are Incorrect:

Option A ("Workfront API call limit"):

While Workfront does have API rate limits, they are generally generous and not the reason for the scenario stopping. Fusion scenarios are designed to manage API calls efficiently.

Option B ("Fusion times out if processing over 2000 records in 40 minutes"):

This is incorrect because Fusion does not have a hard limit on the number of records processed in 40 minutes. The timeout is time-based, not record-based.

Option D ("Workfront API stops webhooks after 2000 hits in 10 minutes"):

This does not apply to Fusion scenarios. Webhooks are separate from the API calls initiated by Fusion.

How to Resolve the Issue:

Split the Data: Use pagination or batch processing to divide the 20,000+ records into smaller chunks (e.g., 1,000 or 2,000 records per run).

Adjust Scheduling: Schedule the scenario to run more frequently with smaller batches, ensuring all records are synced over multiple runs.

Use Iterators: Add an Iterator module to loop through smaller subsets of data, preventing the scenario from exceeding the execution timeout.

Steps to Optimize the Scenario:

Add aSearch Moduleto retrieve opportunities in smaller batches (e.g., using limits or pagination parameters).

Use aRepeater Moduleto process each batch iteratively.

Save the scenario and schedule it to run nightly or more frequently, depending on the sync requirements.

References and Supporting Documentation:

Adobe Workfront Fusion: Execution Timeout Limits

Workfront Community: Managing Large Data Sets in Fusion Scenarios

By optimizing the scenario to handle smaller batches of data, the admin can avoid the execution timeout issue and ensure successful syncing of Salesforce Opportunities with Workfront projects.