Adobe AD0-E902 - Adobe Workfront Fusion Professional

Understanding Instant and Polling Triggers:

Instant Triggers:

Rely on webhooks to receive real-time data from a third-party system.

The external system sends a notification (webhook) to Fusion whenever an event occurs, triggering the scenario immediately.

Polling Triggers:

Regularly check (poll) the third-party system for new or updated records at scheduled intervals.

These are slower because they involve repeated API requests.

Why Option B is Correct:

Speed and Efficiency:

Instant triggers process data faster because they act immediately upon receiving a webhook. Polling triggers, on the other hand, may take time depending on the polling frequency and can result in unnecessary delays.

Reduced Load on Systems:

Instant triggers generate fewer API calls than polling triggers, which continuously check for new records even if no changes have occurred.

Best Practice: Use instant triggers whenever supported by the third-party system to ensure faster and more efficient scenario execution.

Why the Other Options are Incorrect:

Option A ("Instant triggers store received webhooks in a queue"):

Webhooks do not store data in a queue; they simply notify Fusion of events in real-time. Polling triggers also do not store records but remember the last processed record.

Option C ("A user must set up a webhook in Fusion"):

Instant triggers require setting up webhooks in the external system, not in Fusion. Fusion provides the webhook endpoint, but the user must configure the source system to send data.

Option D ("Only polling triggers can be set to run on a schedule"):

This is incorrect because instant triggers do not rely on schedules; they operate in real-time. Polling triggers, however, run on schedules and are used when instant triggers are unavailable.

References and Supporting Documentation:

Adobe Workfront Fusion Triggers Documentation

Workfront Community: Differences Between Instant and Polling Triggers

Instant triggers are the preferred option when available, as they provide real-time data processing with greater speed and efficiency than polling triggers.

Understanding the Issue:

TheWatch Eventsmodule is generating a high number of bundles because it monitors a broad range of project updates in Workfront, resulting in an overwhelming amount of data passing through the scenario.

The goal is to reduce the number of bundles by narrowing the scope of monitored events.

Why Option C is Correct:

Switching to Watch Record:

TheWatch Recordmodule allows users to monitor specific records (e.g., projects, tasks) with additional filtering options in thecriteriaorfilter box.

By applying filters, the module can focus only on relevant updates, significantly reducing the number of bundles being processed.

Example: Filtering for specific project statuses, update types, or assigned users ensures that only relevant changes are captured.

Why the Other Options are Incorrect:

Option A ("Reducing the maximum number of returned events on the trigger"):

This limits the number of bundles processed per cycle but does not address the root cause, which is the broad monitoring scope of theWatch Eventsmodule.

Option B ("Reducing the maximum number of cycles in scenario settings"):

The number of cycles determines how many iterations the scenario performs in one run but does not reduce the number of bundles entering the scenario.

Steps to Use the Watch Record Module:

Replace theWatch Eventsmodule withWatch Record.

Specify the record type to monitor (e.g., Project).

Use the optional filter box to apply criteria, such as specific project fields, statuses, or other conditions.

Activate the scenario to test the refined data flow.

References and Supporting Documentation:

Adobe Workfront Fusion: Watch Record Module

Workfront Community: Managing High Bundle Volumes in Fusion

When dealing with intermittent errors, such as "service is not reachable," the default error handling in Adobe Workfront Fusion is often sufficient to improve execution success rates.

Default Error Handling:

Fusion automatically retries operations when transient errors, such as network or connection issues, occur.

By leveraging this built-in functionality, the system will attempt to re-execute the failing module after a brief delay, which is often enough for the external service to become reachable again.

Why Not Other Options?

A. Adding an error handler that will notify the system owner: While notifying the owner can be useful for monitoring purposes, it does not directly address improving the success rate of executions.

C. Adding a Break directive to the module: Adding a Break directive will stop the execution entirely, which is counterproductive in this case, as the service typically becomes reachable again after a short time.

References:

Adobe Workfront Fusion Documentation: Default Error Handling Mechanisms

Experience League Community: Managing Intermittent API Errors in Fusion

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

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.