Workspaces can be used to organize your work/ processes. There are individual workspaces as well as shared workspaces. Within a shared workspace admins can manage (add/ remove) users.
Every account offers a personal workspace where users store their processes and credentials. Company accounts have the ability to share their workspace with other users in their organization.
While for free accounts users only have access to the workspace associated with that account, Development accounts have access to the project collaboration functionality. This means that they can invite users to join their workspace and share their resources within a specific workspace.
The owner of the Development account has full administrative rights, including user management and can add and remove users to the workspace according to their projects needs.
In order to add new workspaces to a Development account you will need to reach out to the support team through the chat.
PROCESIO allows you to connect to other platforms, servers, applications in a no-code way by using dedicated actions (e.g. Call API action, Send email). Use the Credentials Manager to configure the authentication credentials of the REST API or email server you want to access. Once created, you can use that configuration in actions such as Call API without reconfiguring the authorization steps every time.
Use the Data Model Designer to create your custom data type. It helps you define the relationships between the data elements (attributes) you have, to give it a structure. Data models are a key concept in PROCESIO as they can be used to configure the data type of process variables.
Scheduled processes are automated tasks that can be performed at a specific time or on a recurring schedule.
A process that needs to be run:
- once on a specified date or time or
- on a regularly recurring basis, say once a week, twice a month or once a year
Is a task for the scheduler, as the scheduler will automatically run processes for you. You can add contacts that will receive an email notification based on process completion status (completes/fails/both).
A process variable acts as a placeholder for data when configuring a process. When the process is running, it passes dynamic data between actions.
Call subprocess action enables users to use existing processes within another process (parent process). When a parent process calls a subprocess (a child process), the child process executes in a sequential manner. Once it completes, the execution control is then transferred to the main parent process.
Get File Data
Get File Data action enables you to pull in tabular data from an Excel/CSV file and map it to a process variable. This will allow you to use data coming from external files in process flows.
You can proceed with the action configuration by manually creating the structure of the file (header) that will be uploaded.
You need to map the file structure created to a process variable which will give you the possibility to use the data in other actions in process flows.
Call API action
Allows users to connect to any external system exposing an API.
Decisional action will execute one of the many branches configured, depending on whether a specified condition is met. If no condition is met, you have the option to define a Default path for the action.
You can add several actions after a decisional and build as many cases as you need. A case configuration consists in defining the condition and its successor branch (called "target"). A target action is an action connected to the Decisional as a successor.
For Each action
ForEach actions performs an action (or a set of actions), actions included within the ForEach border. ForEach action enables you to step through lists and iterate through the data and process each information individually (row by row).
The elements of a list can be referenced in the action(s) within the border by creating and using a local variable (iterator).
Join action is used to unify (bring back together) 2 or more branches in one branch after a decisional action. After Join - only one action can be connected as a successor. When branches are unified in a Join, we only need one of them to be executed in order to start executing the “Join” action. The process then continues.
Send Email action
Use the Send Email action to send a message (Body and Subject) to one or more recipients (To, CC and Bcc). The Send Email action gives you the possibility to include attachments along with your message.
PROCESIO integrates Send Email action with your email server configurations. This means that once you configure the Email server to use (check Working with Credentials Manager), you can start configuring the Send Email action in any flow.