Adobe Workfront
Fusion Developer Professional

You should have:

• The ability to with Workfront API and API explorer, but not necessarily proficient in API calls
• The ability to use custom API calls for working with Workfront and other APIs
• The ability to use modules for the Workfront app and other actions like create, read, update, delete, and search
• The ability to build viable solutions that produce business outcomes without hitting Fusion guardrails
• The ability to select appropriate trigger module to accomplish business outcomes
• An understanding of how to use flow control (routes, iterators/aggregators, explain flow)
• The ability to conduct basic troubleshooting and error handling
• The ability to effectively test and go live with a scenario
• The ability to manage organization teams and users
• An understanding of the purpose and use of universal connectors for REST API Oauth2

Section 1: Foundational technical concepts (39%)

• Given a Fusion scenario with one field format that needs to be in another field format, provide the possible functions that could be used to transform the data correctly
• Given a Fusion scenario that requires a function to be nested inside another function, select the properly formed expression
• Identify ways to use teams to control access to connections and other Fusion features
• Given a Fusion scenario, identify system and feature limitations
• Given a Fusion scenario that requires timezone manipulation, distinguish between the user, visible organization, and where overriding the timezone is needed
• Given a Fusion scenario, select the appropriate Workfront module(s) or action(s)
• Given a Fusion scenario, select the Mapping Panel expression and/or module(s) that would appropriately transform input data to output data
• Identify the correct way(s) to utilize the Fusion Dev Tool to troubleshoot errors in execution or determine calls and responses made to third-party systems
• Given a Fusion scenario where data in one path is needed in another path, provide a set-get solution for making that data available on additional routing paths
• Identify the ways to use or produce a Fusion template for a business need
• Given a Fusion scenario, identify what to do to view executions and/or resolve errors
• Identify the different options in the Fusion scenario settings to address scenario needs
• Given a Fusion scenario, select the appropriate flow control and/or determine the correct combination of flow control module(s)

Section 2: Scenario design and architecture (35%)

• Given a list of steps, choose the correct sequence to parse JSON and convert to bundles
• Given a set of requirements, identify the correct data look up method
• Identify differences between instant and scheduled triggers
• Identify a correct module for uploading a document to Workfront
• Given a business requirement, identify the correct approach to track that Fusion processed a record (not a user) and when
• Given a Fusion scenario, identify an opportunity to simplify the design and/or optimize for maintenance
• Identify Fusion best practices for documenting scenarios
• Given a situation, identify an opportunity to reduce data flow through a scenario
• Given an example of the number of bundles shown on a search module and a following aggregator, explain the changes in the number of operations processed and displayed by the bundle inspector
• Identify information that is found in the bundle inspector
• Given a description of a need to archive a scenario for longer than 60 days and select the only possible way (import/export blueprint)
• Given an example of an Error 403: Forbidden, correctly select the origin of the error message and cause

Section 3: Testing and error handling (16%)

• Identify the elements of a test plan
• Identify the elements of a test case
• Given a Fusion scenario, correctly identify the appropriate directive to handle an unreliable service
• Identify the process to add custom error handling in a Fusion scenario
• Identify how to track, read, and resolve incomplete executions
• Given a Fusion scenario with missing required data, select ways to handle the invalid data

Section 4: Working with APIs (10%)

• Given a third-party API that returns a 429: Too Many Requests, identify a solution to prevent or handle the error
• Given a Fusion scenario where new functionality is not available in the Workfront module, identify the correct reference and module type to use the new functionality
• Given a third-party system that does not have a dedicated app, identify the HTTP app and select the appropriate module
• Identify the difference between CRUD operations and other common capabilities of REST APIs