Bug fixes and improvements
In this release, our primary focus has been on performance enhancements and security improvements, knowing that these are top priorities for our customers. Additionally, to reduce manual configuration efforts and automate workflows even further, we are introducing Constants.
Constants
Managing environment-specific values can be cumbersome and error-prone, especially when dealing with configuration migrations. Consider the case of API Calls in a Sequencer - each request refers to an environment-specific URL. In the development environment, the API call points to a test server. Traditionally, when moving to production, each reference had to be manually updated.
With Constants, you can:
- Define a constant in the Resource Database (e.g.,
TEST_API_URL=https://test.example.com). - Reference the constant in the Sequencer’s API call.
- After migrating to production, update only the constant (
TEST_API_URL→https://api.example.com). - No need to manually modify every API request.
Create a constant
A new constant can be created directly in the Resource Database using the following schema:
name(string, required, max: 255 characters)- Must be unique.
- Used to reference the constant in sequences.
description(string, optional, max: 500 characters)- For internal documentation purposes.
data_type(enum, required)- Currently supports:
string.
- Currently supports:
value(string, required, max: 255 characters)- The actual value that will be stored.
Naming rules
To ensure consistency and proper migration, constants must follow strict naming rules:
- Allowed characters:
- Uppercase ASCII letters (
A-Z) - Digits (
0-9) - Underscores (
_)
- Uppercase ASCII letters (
- Must contain at least one letter (
A-Z). - Cannot start with a digit.
Migration behavior
Constants are migrated based on their name. Existing constants in the target environment are not overwritten - if a constant already exists, its value remains unchanged. Deleted constants in development are not removed from the target environment.
Referencing constants
Constants can be referenced in the Sequence Designer using:
{{constants.<CONSTANT_NAME>}}We support using constants in the API Call Actor fields:
- URL
- Parameters
Additional improvements
We’ve addressed multiple security vulnerabilities to enhance system protection and ensure a more resilient infrastructure. Alongside these security fixes, significant performance optimisations have been implemented to improve system responsiveness and scalability, particularly in operations involving user and group management. These improvements contribute to a faster, more efficient, and more secure platform for all users.