AD0-E902 Exam Dumps : Adobe Workfront Fusion Professional

Understanding the Requirement:

If a third-party system does not have a dedicated app connector in Workfront Fusion, users can still build an integration using Universal Connectors.

Universal Connectors in Fusion allow users to configure custom API calls, enabling communication with systems that lack pre-built integrations.

Steps to Build the Integration:

Determine the API Structure: Review the third-party system's API documentation to understand the available endpoints, data formats (e.g., JSON, XML), and request/response structure.

Identify Authentication Protocols: Determine how the third-party system handles authentication (e.g., API keys, OAuth 2.0, Basic Auth).

Configure the Universal Connector: Use modules likeHTTP RequestorWebhookto make API calls to the third-party system based on the documented structure.

Why Not Other Options?

B. Create a new connection to the third-party system in the connections area and then the Universal Connectors will be available for use: Creating a new connection in the connections area is only applicable for predefined connectors, not for Universal Connectors, which require manual configuration for unsupported systems.

C. Use the Workfront Custom API module to set up the connection using API calls to the third-party system: The Workfront Custom API module is specifically designed for Workfront’s own API, not for connecting to third-party systems.

References:

Adobe Workfront Fusion Documentation: Using Universal Connectors for Custom Integrations

Experience League Community: Integrating Third-Party Systems Using Workfront Fusion Universal Modules

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

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