Activities define the actions that are executed in a microflow or a nanoflow.
There are different types of activity, and they are grouped together in the Studio Pro Toolbox. All the activities are listed below. Click on each activity for more details.
Most activities can be used in both microflows and nanoflows. However, some can only be used in one of these types of flow, or the behavior may differ between in microflows and in nanoflows.
Object Activities
Object activities can be used to create and manipulate objects. The domain model defines the object types (entities) that can be used.
In combination with an object type decision allows you to use the specialized members of the object. For more information on the specialized members of an object, see Entities.
Rolls uncommitted changes back that were made to an object in the part of the microflow preceding the activity. Furthermore, it deletes objects that have been created but have never been committed.
List Activities
List activities can be used to create and manipulate lists of objects.
Can be used to enable the browser to download a specific file. The user who calls the microflow in which this activity is used gets a download pop-up window, or the file is shown directly in the browser.
Can be used to call an external action from a consumed OData service. You can configure the parameters and if available, store the result in a variable.
Can be used to call a REST endpoint. You can use mappings to map results to entities or entities to requests. You can also use string templates and store the result in a string variable.
Can be used to call one of the imported web services. The content of the request can be edited. Furthermore the response of the webservice can be mapped to entities, stored in a variable or be ignored.
Can be used to parse the data in a string variable or data stored in a file document, and store them to entities defined in the domain model of the database. An import mapping is used to map the incoming XML or JSON to entities.
Can be used to export the data stored in domain model entities into an XML or JSON string. It can also be stored in a file document. An export mapping is used to map domain model entities into XML or JSON.
Allows the workflow to jump to a selected activity. This activity should be used after the Generate jump-to options activity that generates the list of possible workflow activities the workflow can jump to.
Sets which outcome the user task should follow. For example, this activity can be used to complete a user task using a microflow with custom validations.
Allows you to generate a list of workflow activities where the workflow can jump to as its next step. The Apply jump-to option activity should be used after the Generate jump-to options activity to let the workflow continue from the selected activity.
Allows you to retrieve a list of System.WorkflowActivityRecord objects for a given workflow instance. Each System.WorkflowActivityRecord represents a snapshot of a workflow activity.