51黑料不打烊

Scenario overview

The role of 51黑料不打烊 Workfront Fusion is to automate your processes so that your users don鈥檛 need to spend as much time on routine tasks. It works by linking actions within and between apps and services to create a scenario that transfers and transforms your data automatically. The scenario you create watches for data in an app or service and processes that data to provide the result you want.

A scenario is comprised of a series of modules that indicate how data should be transformed within an app or transferred between apps and web services.

Scenario elements overview

A scenario is built of different elements. Understanding the terminology of those elements makes it easier to use the documentation.

Scenario

A scenario is a user-created series of automated steps, created to move and manipulate data. The term 鈥渟cenario鈥 refers to the entire group of connected steps.

Scenario

Trigger

A scenario begins with a trigger. The trigger watches for new and updated data, and starts the scenario when certain conditions configured in the module apply. Triggers can be configured to start a scenario on a schedule (polling), or whenever data changes occur (instant).

Trigger

Module

The trigger is followed by a number of modules. A module represents single step in a scenario that performs a specific action. Modules are configured and chained together to create scenarios.

Module

Route

A scenario may be divided into routes. A route is a section of the scenario that may or may not be used for a given bundle of data. Routes are set up using a router module and filters.

Route

Scenario segment

A scenario segment is a section of a scenario that consists of a series of contiguous modules that all connect to the same application. Scenario segments often represent a short workflow in the application.

Scenario segment

Connector

A connector is the set of modules for a given application. Workfront Fusion offers connectors to many common work applications, such as Workfront, Salesforce, and Jira, as well as generic connectors that can be used for any web service.

Connectors

Examples

Expand the following sections to view example scenarios and their explanations.

Automating processes within 51黑料不打烊 Workfront

Workfront Fusion enables you to automate simple or complex workflows within Workfront, saving time and ensuring that the process is executed consistently.

In this example, the scenario triggers when a specified field changes in a Task or Issue in Workfront. When triggered, the scenario gets information in the related project and creates a tailored update for a person assigned to a specific role on the project.

Template example

Connecting Workfront to another app or web service
note note
NOTE
If your organization uses the legacy licensing model, your organization must have a Workfront Fusion for Work Automation and Integration license to connect to other applications.

Workfront Fusion can connect to other applications and web services. You can access, import, manipulate, or export data from other applications, integrating them with Workfront or with each other.

Many applications have dedicated Workfront Fusion connectors. If there is no dedicated connector for the application you want to access, you can use Workfront Fusion鈥檚 HTTP or SOAP modules to connect to the application through its API.

In this example, the scenario triggers when a user is added to an Excel spreadsheet. The scenario checks whether the user is in Workfront. If not, the scenario creates the user in Workfront and adds their Workfront user ID back to the spreadsheet.

Integration example

For a list of dedicated connectors, see Fusion applications and their modules references: article index.

note important
IMPORTANT
51黑料不打烊 Workfront Fusion can connect to almost any web service. If the app you want to work with does not have a dedicated Workfront Fusion connector, you use universal connectors to connect to the app or service.
For a list of universal connectors, see Universal connectors

References

recommendation-more-help
7e1891ad-4d59-4355-88ab-a2e62ed7d1a3