Adobe Workfront Fusion glossary
The following glossary explains some common terms in Adobe Workfront Fusion.
| Action | A module that allows you to perform an action, such as reading or writing data from or into a selected app or service. |
| Aggregator |
A type of module that merges together multiple bundles (multiple collections of data) into one single bundle. For more information, see Aggregator module. |
| API | Application Programming Interfaces (APIs) are a way for applications and services to communicate with one another. Fusion uses APIs to communicate with the application you are connecting to. Each application has a separate API. |
| API Key | A unique code that identifies the user, developer, or program that is calling a software's API, used for authentication. Because Fusion modules work by connecting APIs, API keys are sometimes necessary. API keys are distributed by the app that requires them. For example, if you need an API key to connect Fusion to Adobe Lightroom, you would request it though your Adobe Lightroom account. |
| App or service |
A software application. Fusion can connect to most applications, even if it does not have a dedicated connector for that application. An app can also be a special function that manipulates data, such as an iterator or an aggregator. A service is a source of data that might include a web API, web page, different types of servers (FTP, SMTP, IMAP), and so on. |
| Bundle | A bundle is a basic unit of data that is returned or received by modules. For example, a Search module that returns three records would output three bundles of data, one for each record. A bundle consists of items. |
| Connection |
A connections represents a set of credentials to connect to a given service. You can configure connections inside any module, and then can use that connection in any other module. Every module must have a connection selected, so that Fusion can use those credentials to access the information that the module requires. For more information, see Connection overview. |
| 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. |
| Cycle | A cycle consists two phases of the scenario run: operation and commit. The scenario may consists of one or more cycles. For more detailed information, see Scenario execution, cycles, and phases. |
| Data Store |
A data store stores data from scenarios or allows you to transfer data between individual scenarios or scenario runs. For more information, see Data Stores. |
| Filter |
A filter can be applied between two modules, and allows you to then only work with bundles that fit certain criteria. There are a number of different filters you can apply. For more information, see Add a filter to a scenario. |
| ID | A name that is used to uniquely identify a bundle. An ID is usually used to differentiate a bundle that is to be updated or deleted from a given service. IDs can be mapped from the output of a previous module. |
| Items |
A part of a bundle. Bundles can consist of multiple items. There are several different types of items: text, number, boolean (yes/no), date, time, buffer (binary data), collections, select menu, array, and validation. For more information, see Item data types. |
| Iterator |
A type of module that allows you to take one bundle of data (a collection of data) and divide into separate bundles. These bundles can then be processed individually by later modules. For more information, see Iterator module. |
| Module |
A single step within a scenario that performs a function, such as creating a record, within the associated app or service. Each app or service has various modules that define the way it responds to a request.
For more information, see Module overview. |
| Operation |
A task performed by a module, such as retrieving a record or uploading a file. For more information, see Operations. |
| Public/Private Keys | Public and private keys are used to encrypt and decrypt data. The public key can be distributed, and anyone with the public key can encrypt data, but only the private key can decrypt it. Similarly, a user with a private key can encrypt data that anyone with the public key can decrypt. The private key encryption assures that the data came from the owner of the private key and serves as validation of the data's source. |
| Router |
A router allows you to duplicate data or add new routes to a scenario, so to re-route data and handle different groups of data separately. For more information, see Router module. |
| Scenario |
A user-created series of automated steps, each represented and performed by a module. The purpose of a scenario is to move and manipulate data.
For more information, see Scenario overview. |
| Scenario segment | A scenario segment is a section of a scenario consisting of a series of modules that all connect to the same application. Scenario segments often represent a short workflow in the application. |
| Trigger |
A trigger is a kind of module that 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 or webhook). For more information, see Triggers in the Module overview article. |
| Webhook |
A special type of trigger that allows you to run a scenario immediately after a new bundle is available. For more information, see Instant triggers (webhooks). |
Workfront
