Workfront's training on scenario testing emphasizes the importance of a well-structured test plan to

ensure scenario reliability and accuracy. The three essential elements include:

B . Description of Expected Behavior:

This provides clarity on what the scenario is supposed to achieve when executed successfully.

It serves as a benchmark for evaluating the outcome of test executions.

C . Specific Event/Trigger per Scenario:

Identifying and testing specific triggers ensures that the scenario starts under the correct conditions.

This is crucial for verifying the proper configuration of the scenario’s start point.

D . Description of Testing Steps:

Outlining step-by-step instructions for the testing process ensures that all aspects of the scenario are

tested systematically.

It helps identify potential bottlenecks or areas for improvement in the scenario’s configuration.

Why Not Other Options?

A . Roadmap requirements: This pertains to project planning and is not directly relevant to scenario

testing.

E. Executive sponsor expectations: While valuable for overall project alignment, it is not an essential

component of a technical test plan.

Reference:

Workfront Training Materials: Best Practices for Scenario Testing

Experience League Documentation: How to Design and Execute a Test Plan for Workfront Fusion

Scenarios

Step 1: Query Workfront for User Based on Email Address

Salesforce provides the email address of the user. Since Workfront uses user IDs for task

assignments, the email address can be used as a unique identifier to query Workfront’s database.

A query module in Workfront Fusion retrieves the corresponding Workfront user ID using the

provided email address.

Step 2: Assign Task Using Returned ID

After retrieving the Workfront user ID, use it in the assignment field of the task module in Fusion.

The task assignment process requires a valid user ID, ensuring proper linkage and assignment within

Workfront.

Why Not Other Options?

A . Assign the task using the provided user ID > add the user ID to the assignment field: The

Salesforce user ID is not recognized by Workfront. It is necessary to query Workfront to convert the

email into a Workfront-compatible user ID.

C . Query Workfront based on the user's name > assign task using returned email address: Workfront

uses user IDs, not email addresses, for task assignments. Names are also not unique and could cause

assignment errors.

Reference:

Adobe Workfront Fusion Documentation: Task Assignments Using User IDs

Experience League Community: Mapping Salesforce Data to Workfront Tasks

Object ID in CRUD Operations:

REST APIs commonly use CRUD operations to interact with resources. The Object ID serves as a

unique identifier for the resource and is generally required for the following actions:

A . Update:

To update a specific resource, the API must know which resource to modify. The Object ID is used to

identify the exact resource that should be updated.

Example: A PUT or PATCH request typically requires the Object ID in the URL or body of the request.

URL Example:

PUT /tasks/{id}

B . Delete:

Similarly, when deleting a specific resource, the Object ID is needed to ensure the correct resource is

removed.

Example: A DELETE request requires the Object ID in the URL to target the specific resource.

URL Example:

DELETE /tasks/{id}

Why Not Other Options?

C . Respond: This is not a standard CRUD operation in REST APIs and does not involve an Object ID.

D . Create: The Create operation (typically POST) does not require an Object ID because the resource

does not yet exist. Instead, the API usually generates the Object ID after creation.

Reference:

REST API Documentation Best Practices: CRUD Operations

Experience League: Understanding CRUD in Workfront APIs

Step by Step Comprehensive Detailed Explanation:

Scenario Summary:

The source system provides a list of users, job roles, and departments.

The destination system requires a mapping of job roles to different departments.

Updates to this mapping are infrequent, and there is a concern for more security than a spreadsheet

offers.

Option Analysis:

A . Switch: A switch function in Workfront Fusion is used to make decisions based on specific

conditions but does not maintain persistent data like mappings over time. It is not suitable for storing

mappings that require infrequent updates.

B . Spreadsheet: Spreadsheets may be simple to use but are less secure and not ideal for integrating

with Workfront Fusion workflows due to their lack of direct integration features or control over

changes.

C . Data store: A data store in Workfront Fusion is specifically designed for storing persistent data,

such as mappings or reference tables. It is secure, easy to manage, and integrates seamlessly with

workflows, making it the best choice for this use case.

D . Table aggregator: A table aggregator is used for combining or processing data within a workflow

but is not suitable for storing persistent mappings outside of a running scenario.

Why Data Store is Appropriate:

Persistence: A data store is ideal for maintaining the job role and department mappings across

scenarios.

Security: It is managed within Workfront Fusion, offering better control and access restrictions

compared to a spreadsheet.

Ease of Integration: Data stores can be directly queried or updated in Fusion workflows, allowing

seamless handling of mappings.

Scalability: While updates are infrequent, the data store can handle changes easily and scale if the

volume of mappings increases.

Implementation in Workfront Fusion:

Create a data store for job roles and departments in Workfront Fusion.

Set up fields for Job Role and Department in the data store.

Use Workfront Fusion scenarios to retrieve and update mappings from this data store based on

requirements.

Reference:

This approach aligns with the Workfront Fusion documentation on data stores, which are designed

for secure and efficient storage of persistent data used across scenarios. See Workfront Fusion

resources for data store setup and use cases for further details.

When encountering the error 429: Too many requests, which indicates the web service is being

overwhelmed by requests, the following actions can help:

A . Add a Sleep Module:

Adding a Sleep module introduces a delay between iterations, reducing the frequency of API calls.

By slowing down the rate of requests, you avoid hitting the rate limits of the web service, thus

reducing the chances of receiving a 429 error.

This approach is useful for managing high-volume iterations without overloading the external

service.

C . Add a Module to Test the Service for Errors:

Adding a module to test the service's response before making a call can help prevent the 429 error

by checking if the service is ready to handle requests.

This preemptive check allows the scenario to conditionally execute, ensuring that it doesn't

overwhelm the service and respects the API rate limits.

Why Not Other Options?

B . Use an Ignore Directive: Ignoring errors can be risky because it would cause the scenario to ignore

429 errors, possibly leading to failed API calls that are not addressed. Ignoring an error doesn’t solve

the issue of too many requests being sent to the service.

D . Use a Break Directive: The Break directive would stop the execution, which is counterproductive

when trying to resolve the issue by reducing the rate of requests. It would not address the root cause

of too many requests.

Reference:

Adobe Workfront Fusion Documentation: Handling API Rate Limiting with Sleep and Error Handling

Experience League Community: Managing Web Service Errors in High-Volume Iterations