Exam AD0-E902 Topic 3 Question 1 Discussion

* 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