This topic describes the terms of Logic Composer.
A Logic Composer instance is an application that can be deployed and run independently. It holds a workflow and the service connections on which the workflow depends.
workflow
A workflow, which serves as the core concept of Logic Composer, defines a business process step by step.
It consists of a number of triggers and actions. You can edit a workflow visually or by writing code.
service connection
A service connection is a management set for identity authentication and operation authorization for a service to be accessed by workflows.
Logic Composer is a fully managed cloud service. Before Logic Composer accesses your resources and data through a service connector, it must obtain the corresponding permissions from you. Currently, two access authorization methods are available. For access to the APIs of Alibaba Cloud services, use a RAM role. For access to third-party services and custom applications, use OAuth 2.0, which is not supported in public preview of Logic Composer.
connector
A connector defines a connection for Logic Composer to quickly interact with a third-party application, service, or system through triggers and actions.
Two connector types are available:
Built-in connector: the connectors for accessing the general process services provided by Logic Composer, such as logic control, data processing, and HTTP request services. Triggers and actions provided by built-in connectors can be used without authentication or authorization.
Managed API connector: the connectors for accessing APIs of some public services that are fully managed on Alibaba Cloud. These connectors provide the authentication and authorization methods, triggers, and actions for accessing cloud services, custom systems, and applications. For example, you can use managed API connectors to access the APIs of Alibaba Cloud services.
trigger
A trigger, which is similar to an event, is the entry of a workflow. A trigger defines how Logic Composer starts a workflow when an event occurs or a specified condition is met.
Triggers work in either of the following modes:
Polling trigger: regularly checks whether the event occurs or the specified condition is met and runs the workflow accordingly.
Push trigger: creates an HTTP service subscription and provides an anonymous callback URL. When the subscribed event occurs or the specified condition is met, the callback URL is triggered and the workflow is run.
The following trigger types are provided:
Built-in triggers
Request: provides an accessible HTTP endpoint for a workflow. Recurrence: sets a fixed interval to run a workflow repeatedly. HTTP WebHook: creates an HTTP endpoint that can be called back and accesses a specified URL to subscribe to or unsubscribe from a service. The Recurrence and HTTP WebHook triggers are not supported in public preview of Logic Composer.
Trigger | Description |
Request (custom requests) | Provides an accessible HTTP endpoint for a workflow. |
Recurrence (scheduling) | Specifies a fixed interval to run a workflow repeatedly. The trigger is supported in the China (Shanghai) and Singapore regions. |
HTTP WebHook | Creates an HTTP endpoint that can be called back and accesses a specified URL to subscribe to or unsubscribe from a service. The trigger is not supported in public preview of Logic Composer. |
Managed API triggers
Trigger | Description |
APIConnection | Regularly accesses a managed API. The trigger is not supported in public preview of Logic Composer. |
APIConnectionWebhook | Accesses a managed API and creates an HTTP endpoint that can be called back to subscribe to or unsubscribe from a service. The trigger is not supported in public preview of Logic Composer. |
action
An action is a step to be performed when a trigger fires. It is a node of a business process to be orchestrated.
template
A template is a workflow predefined by Logic Composer based on a specific scenario or a custom workflow created by users. Saving a custom workflow as a template is not supported in public preview of Logic Composer.