A source system provides a list of users and their job roles and departments. The destination system requires the job role values be revised to match…

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.