- Print
- DarkLight
- PDF
30 Sept 2020
Corezoid.com
New Features
Aliases. Now you can give the process a symbolic name (short name) and use it instead of a numeric (ID). For example: 12345 -> send-email.
Aliases will simplify the migration of processes between environments and companies, as well as help organize the versioning process.
If Alias is assigned to a process, its name can be used instead of process ID in Call Process, Copy Task and Modify Task nodes, as well as when creating tasks in the process by Direct URL.
An example of access to Alias via Direct URL:
https://corezoid.com/api/2/json/public/@system-state/0/i320506142/2132b12e579c402c9ed17f2ef1c8e7a37e3bbc7b
Aliases also works in Corezoid API methods, for example, to create a task send a request:
{
"ops": [
{
"type": "create",
"obj": "task",
"obj_alias": "sms-sender",
"ref": "1598950142_2",
"data": {
"version": "Corezoid 5.5.0"
},
"company_id": "i320506142"
}
]
}
The CONV function also supports working with aliases - you can use the short name of an alias instead of its ID: {{conv[@send-email].ref[{{channel}}_{{chat_id}}]}}
.
More details about setting up and working with aliases in the documentation.
Improvements
Added an alternative construction for getting tasks parameters from state diagrams - {{proc[].ref[].key}}
.
Fixes
- Fixed saving the edited description for Dashboards by clicking the Save button.
- Fixed a bug due to which data was not always read from state diagrams using the conv[].ref[] construction when specifying the diagram identifier as a parameter, for example
{{conv[{{conv_id}}].ref[]}}
.
Private Cloud and On-premises Hosting type
Include all the features/improvements/fixes of Corezoid.com and:
New Features
Added Limit Management API. Allows you to fine-tune the limits for:
- Request per Second (RPS) at the instance, company, user and process level.
- The minimum time interval setting for the tasks in the Delay node.
- Maximum task size in the processes.
- Maximum task size in the state diagrams.
You can manage limits in the SuperAdmin application.
Improvements
- Added storing of the full history of changes in the Task parameters when it passes between nodes. The
write_data_to_history
parameter of the worker config section is responsible for this. - Now you can specify a separate database to store the Task archive, for this the
HOST
parameter in the pgsql_task_history config section is responsible. - Added a flexible configuration of the environment file system - works with AWS S3 and environment file storage (file_f3). The setting is done in the
default_file_storage
parameter.
Detailed instructions on how to work with the new config parameters will be attached to the manual for updating/installation of the version.