A Fusion user needs to connect Workfront with a third-party system that does not have a dedicated app connector in Fusion.
What should the user do to build this integration?
Answer : A
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 like HTTP Request or Webhook to 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.
Adobe Workfront Fusion Documentation: Using Universal Connectors for Custom Integrations
Experience League Community: Integrating Third-Party Systems Using Workfront Fusion Universal Modules
Which two actions are best practices for making a Fusion scenario easier to read, share and understand? (Choose two.)
Answer : A, C
Step by Step Comprehensive Detailed Explanation:
Best Practices for Scenario Clarity:
Workfront Fusion scenarios can become complex. Adopting practices that enhance readability, shareability, and understanding ensures the scenario can be maintained and used effectively by others.
Option Analysis:
A . Naming all modules by providing short but relevant labels:
Correct. Proper naming helps identify the function of each module at a glance. For example, instead of generic names like 'Project Search,' use 'Search High Priority Projects.'
This makes it easier to debug, share, and update the scenario.
B . Insert Note Modules at the beginning of the scenario:
Incorrect. While notes are useful, inserting a Note module at the beginning is not always necessary unless clarification is required for the initial step. Adding notes throughout the scenario (Option C) is more beneficial.
C . Add notes where applicable to clarify what is happening:
Correct. Adding comments or notes helps explain the purpose of certain steps, making the scenario easier to understand for collaborators or when revisiting it in the future.
D . Attach the requirements document using the scenario settings:
Incorrect. Attaching a requirements document might be useful for reference but does not directly contribute to scenario readability or understanding within the interface.
Implementation Tips:
Use descriptive names for modules that clearly indicate their purpose (e.g., 'Update Project Status' instead of 'Update Record').
Add comments or notes at decision points or complex mapping expressions to explain logic.
In a Fusion scenario, a new project in Workfront will trigger the creation of a new project in ServiceNow. The name of the project in ServiceNow will be constructed in the following format:
Two Digit Year - Reference Number - Project Name
Which expression will generate the correct string?
Answer : C
Understanding the Requirement:
The desired output format for the project name in ServiceNow is: Two-Digit Year - Reference Number - Project Name
This requires dynamically constructing a string by combining:
The current year in a two-digit format.
The referenceNumber (a variable or input).
The name (a variable or input, likely the project name).
Why Option C is Correct:
The concat function combines multiple strings into a single string.
Expression:
concat(formatDate(now;YY), ' - ', referenceNumber, ' - ', name)
This ensures proper formatting with hyphens and spaces between the elements.
Breaking Down the Components:
formatDate(now;YY): Retrieves the current year in a two-digit format (e.g., '23' for 2023).
' - ': Adds the required separator.
referenceNumber: Dynamically adds the reference number.
name: Dynamically adds the project name.
Why the Other Options are Incorrect:
Option A ('formatDate(now;YY) - referenceNumber - name'):
This is not valid because it does not explicitly use a string concatenation function.
Option B ('join(formatDate(now;YY) - referenceNumber - name'):
The join function is used for concatenating elements of an array, not individual strings. Since the inputs are not in an array, this function will not work.
How This Solves the Problem:
The concat function correctly constructs the string with the desired format, dynamically generating the project name for ServiceNow based on the given inputs.
Reference and Supporting Documentation:
Adobe Workfront Fusion Functions Documentation
Workfront Community: Using the concat Function
In a scenario that searches for recently completed tasks, a user notices the following input and output for a date transformation.
Input: March 3, 2021 10:34 AM Output: March 1, 2021 10:34 AM
Which expression produces this date transformation?
Answer : A
Understanding the Date Transformation:
Input: March 3, 2021, 10:34 AM
Output: March 1, 2021, 10:34 AM
The transformation subtracts 2 days from the input date without altering the time.
Why Option A is Correct:
subDays(now,2) subtracts exactly 2 days from the given date and time.
It preserves the time component of the input (10:34 AM) while shifting the date backward by 2 days, which matches the given output.
Why the Other Options are Incorrect:
Option B ('addHours(now; -48)'): While subtracting 48 hours also results in a 2-day difference, this approach directly modifies the time. The resulting time could shift if the operation crosses daylight saving changes or edge cases with leap seconds. It is less reliable compared to subDays.
Option C ('addDays(today; -4)'): This would subtract 4 days, which does not match the transformation shown in the example.
Reference and Supporting Documentation:
Adobe Workfront Fusion: Date and Time Functions
Workfront Community: Using Date and Time Expressions
A global customer has end users who input date and currency data into fields in inconsistent formats. Despite continued training efforts, this continues to be an issue. Unfortunately, the third-party service that the end users are using does not support forcing a required field format. These input mistakes do not happen frequently, but they currently stop the scenario from executing after the default three retries.
In Fusion, which action can the admin take to ensure that errors are corrected after they occur in a scenario?
Answer : A
Understanding the Scenario:
The issue involves end users inputting inconsistent date and currency formats that result in errors in a Workfront Fusion scenario.
The default behavior of Fusion stops the scenario after three retries due to input mismatches or invalid formats.
Why Option A is Correct:
Storing Incomplete Executions: In Adobe Workfront Fusion, enabling 'Store incomplete executions' in the scenario settings allows administrators to capture incomplete runs without fully stopping the entire process. This feature stores all relevant data, even from incomplete runs, allowing administrators to identify and correct input issues manually.
Error Troubleshooting: By reviewing incomplete executions, admins can pinpoint where the scenario failed, resolve the issue, and potentially reprocess those incomplete records, preventing complete scenario stoppage.
Why Option B is Incorrect:
The 'switch module' can handle specific input variations, but it is not a comprehensive solution for handling unexpected or inconsistent formats entered by end users. While it might mitigate some errors, it does not address the root cause and can miss unanticipated input patterns.
Why Option C is Incorrect:
Setting up an error handling path to notify users and request corrections adds an additional manual step for users but does not resolve the problem efficiently within Fusion. Moreover, this solution does not prevent the scenario from halting after retries.
Steps to Enable Storing Incomplete Executions:
Navigate to the scenario in Adobe Workfront Fusion.
Open the Scenario Settings by clicking the gear icon.
Enable the option Store Incomplete Executions under Execution settings.
Save the settings and activate the scenario.
How This Solves the Problem:
Enabling this setting ensures that no data is lost when the scenario fails due to inconsistent inputs. Admins can access the incomplete executions through the scenario execution history, apply necessary corrections, and retry specific records or steps as needed.
Reference and Supporting Documentation:
Adobe Workfront Fusion Official Documentation: Scenario Settings
Workfront Community: Handling Incomplete Executions
What are two required elements of a test case? (Choose two.)
Answer : A, C
A . Expected Outcome of Test
A test case must clearly state what the expected outcome is, providing a standard against which the results can be measured.
This ensures testers can validate whether the scenario behaves as intended.
C . Clear Procedure for Completing the Test
A well-defined procedure outlines the exact steps required to execute the test, ensuring consistent and repeatable testing.
This reduces ambiguity and helps identify whether errors are due to the scenario configuration or improper test execution.
Why Not Other Options?
B . Name of Test Owner: While helpful for accountability, the name of the test owner is not a required component of the test case itself.
D . Source Code Being Tested: Fusion scenarios do not typically involve source code. Instead, the focus is on workflow execution and configuration, making this element irrelevant.
Workfront Training Materials: Test Case Design Best Practices
Adobe Workfront Fusion Documentation: Testing and Debugging Scenarios
Given this Fusion scenario, a user needs to access multiple fields from the Workfront module for mapped expressions in the HTTP PUT requests.
Which action should the user take?
Answer : A
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 a Set Multiple Variables module.
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 a Get Multiple Variables module.
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.
Reference and Supporting Documentation:
Adobe Workfront Fusion: Variables Module Overview
Workfront Community: Efficient Use of Variables in Fusion