Developer Activities
The following table describes the details of the various Developer activities supported in the Workflow Canvas:
|
Activity Name |
Icon |
Description |
|---|---|---|
|
Condition |
|
This activity configures conditions that branch the workflow, adds one or more branches, and groups multiple branches. This allows the workflow to take different actions depending on the customer’s actions or the data received. |
|
Set variables |
|
This activity sets the value of variables in the workflow. For more information, refer to the Variables topic. |
|
HTTP request |
|
This activity allows you to configure the HTTP activity to access RESTful Web APIs in your workflow. You can send requests using HTTP to web services to retrieve or update data. The HTTP activity encapsulates the header and body of the API request, making it easy to use within your workflow. |
|
Log |
|
This activity adds log messages, which provide additional information for debugging a flow. |
|
Terminate |
|
This activity allows you to stop the workflow execution completely. |
|
For each |
|
This activity allows the workflow to iterate through an array and execute activities on each item. |
|
Go to |
|
This activity allows you to redirect the flow of a workflow. The workflow will continue executing the activities as indicated in this activity. |
|
Break |
|
This activity breaks the workflow from the current logical flow. This is commonly used with a For Each activity to stop iterating through the array and continue the workflow before all items are evaluated. |
|
Delay |
|
This activity allows you to delay or pause the workflow for a specified number of milliseconds (1000 milliseconds = 1 second). |
|
Continue |
|
This activity breaks from the current logical flow and continues at the next iteration of a loop. It is commonly used with a For Each activity to stop the current iteration and continue with the next entry in the array. |
|
Bookmark |
|
This activity pauses the workflow for a specified time while waiting for an action. If the action does not occur before the configured timeout value, the workflow resumes. |
|
Open session |
|
This activity opens a new session for the workflow based on an identifier, such as a call ID or session ID. This is typically used in conjunction with a Bookmark activity. When the Open Session activity is executed, it will check if an existing session exists for the workflow running with the same identifier. If so, that session is resumed, and the existing Bookmark exits. Otherwise, a new session is created. |
|
JavaScript |
|
This activity supports native JavaScript functions implemented directly in the JavaScript engine and does not require additional libraries. It can perform basic functions such as formatting or parsing data. The activity has access to all the workflow variables and can return a result to the workflow, along with additional data, when it is complete. |
|
Cloudlink subscribe |
|
If the workflow requires CloudLink notifications, the Subscribe activity can specify the topic, subject, and method, along with a filter for specific notification events. For example, to monitor the state of a call at an endpoint, the workflow can use this activity to receive notifications from platform-api-media for that specific endpoint and call. Refer to the CloudLink API documentation for further details. |
|
Cloudlink unsubscribe |
|
This activity cancels a subscription set up for CloudLink notifications through a Subscribe activity. The Subscribe activity returns the Subscription ID(s), which is passed to the Unsubscribe activity to stop receiving the requested CloudLink notifications. |
|
Parallel |
|
This activity executes two or more branches in a workflow simultaneously. Each branch executes simultaneously, and the workflow waits for all branches to complete or one of the branches to complete, depending on the configuration of the Parallel activity. |
|
Try-Catch |
|
This activity creates two branches: the "Try" branch will execute, and the workflow will continue with the "Catch" branch if an error is encountered. This allows you to add error handling to your script. |
|
While |
|
This activity causes a workflow to repeat activities until a condition is met. For example, while the variable count < 3, continue to repeat an activity and increment count. It can be executed in two different modes. "While" mode evaluates the condition first, and the loop is not executed if it is already met. "Do While" mode executes the loop and then evaluates the condition, so it is guaranteed to execute it at least once. This activity is used with a Continue or Break activity to return to the While activity and evaluate the condition or break out of the While loop. This activity should be used carefully so that an infinite loop is not created. |