Adobe Workfront AD0-E902 Question # 2 Topic 1 Discussion

Step by Step Comprehensive Detailed Explanation:

Problem Summary:

The Fusion scenario updates the project condition multiple times, once for each high-priority issue.

The desired behavior is to update the project condition only once, based on the overall condition of all associated issues.

Option Analysis:

A. Change the issue search module to result set of First Matching:

This would limit the search to only the first issue. However, this does not account for all issues on the project, leading to incomplete logic for setting the project condition.

B. Add an Ignore error directive as an error handler route for the update module:

Ignoring errors does not prevent multiple updates; it only suppresses errors in the workflow.

C. Create a separate scenario to update the overall project condition:

Correct. By separating the project update logic into a different scenario, the developer can ensure the condition is updated only once after analyzing all issues. The project condition is calculated holistically, based on the state of all high-priority issues.

D. Apply the Run Once flow control function:

"Run Once" controls execution at the scenario level, not within a module's iteration. It cannot prevent multiple updates in this context.

Why Separate Scenario is Best:

Simplifies Logic: A separate scenario can be designed to run after all issues have been checked, ensuring only one update per project.

Avoids Redundancy: Prevents unnecessary API calls to update the same project multiple times.

Improves Performance: Reduces the number of operations and bundles processed in the main scenario.

Implementation:

Create a separate scenario triggered after the issue-checking scenario completes.

Use aggregate data (e.g., a data store or intermediate processing) to evaluate the overall project condition before performing a single update.