5.0.5
The new version of the platform becomes available on December 19, 2023.
In the latest version, we are excited to introduce a range of improvements, and new features to elevate your experience.
Home Application Enhancements.
Streamlined Navigation: We've reorganized the Home application, to make it easier to navigate, and find the tools and information you need.
Organization settings.
We have also added the ability to add and delete environments and allocate slots.
If you lack sufficient deployment slots or developer seats in your subscription plan, you can add more.
The database can be added in minimal steps of 5 GB.
Environments. To adjust your environment settings (create, rename, allocate slots) visit the Organization Settings page.
Deployments. The number of slots used for a deployment can be changed within the deployment section.
Logs. Logs are currently accessible on two levels: environment and deployment. Deploy logs have been expanded to track the entire process of creating a deployment. We've also added a new "Trace ID" filter, allowing you to trace deployment errors at every step of the deployment process.
User invitation. The Owner or Administrator can invite users to the organization team. To become a part of the organization's team, the user needs to accept the invitation has been sent by email. The email contains information on how to join the organization, along with a link to the platform.
Wizard - a component to make the process of organization creation easier was added. Wizard allows you to select subscriptions, invite a team, configure the environment, and buy additional resources during the creation process.
AI assistant in the flow builder. When assigning one of the structure attributes, the system analyzes and suggests adding all the remaining elements from the structure. Similarly, the system works when filling in structure values. This principle applies not only to the Assign node but also to each node inherited from the resource node: function call, subflow, assets (decision tables, scorecards, pmml, etc.)
Horizontal Scaling Functionality. We have increased the speed of the system to enhance its productivity.
We have upgraded Crypto RSA keys. To deploy JAR and WAR archives exported from the system successfully, it is necessary to set specific environment variables: crypto.rsa.key.public and crypto.rsa.key.private.
The registration and authorization process has been updated, and verification codes have been added. These changes enhance the security of the application use.
New features have been added to the Expression Editor.
The name validation rules have been changed, and underscores at the beginning of structure names are no longer allowed.
Added the ability to import structure from JSON object in the structure section.
The date Format has been updated to the ISO 8601 date format (yyyy-MM-ddTHH:mm:ss.sssTZD) for all requests.
Password encryption methods have been changed.
The latest version has more detailed and accessible descriptions of nodes and entities to facilitate the visual development process.
How to Configure Your Project After Updating to a New Version
The new version brings several significant changes in structure generation, date format, and password encryption methods. Please, follow these guidelines to ensure a smooth transition:
Changes in the Structure Name
Starting from project version 5.0.5, we have modified to structure names. If your structures have been created by the connector builder and the original data model included a reserved word (auto-generated), an underscore (_) is inserted at the beginning of its name. However, in the new version, the name validation rules have been changed, and underscores at the beginning of structure names are no longer allowed.
Recommendation: If you encounter errors related to this change, they will be identified in the error panel. To correct mistakes, replace the underscore in structure names with a different prefix. For example, replace “_” with "gen_".
Date Format Updating
We have switched to the ISO 8601 date format (yyyy-MM-ddTHH:mm:ss.sssTZD) for all requests in this version. This change ensures that requests are more consistent and strictly typed.
Format Example: “yyyy-MM-ddTHH:mm:ss.sssTZD” (eg “1997-07-16T19:20:30.023+01:00” or “2013-12-24T09:12:14.232344Z”)
TZD: Time zone designator (Z or +hh:mm or -hh:mm)
When loading an example request, the test helper will automatically generate dates in this format:
Default Format: yyyy-MM-dd'T'HH:mm:ss.SSSXXXZ"
SSS: Milliseconds
XXX: Time zone offset relative to UTC
Input Options: two possible date formats for input are:
"2013-12-24T09:12:14.232-04:00"
"2013-12-24T09:12:14.232344Z"
Recommendations:
Verify that the dates are received as input in the flow according to the full-time format.
Adapt your systems to handle the full-time format both in input and output. Pre-process data if necessary.
Use debugging tools to confirm that date transformations achieved the expected results.
Changes in Password Encryption Method
Password encryption methods have been changed in this version.
Recommendation: Resave all passwords stored in global variables to ensure compatibility with the new encryption method.
Crypto RSA keys updating
To deploy JAR and WAR archives exported from the system successfully, it is necessary to set specific environment variables: crypto.rsa.key.public and crypto.rsa.key.private.
Recommendation: These variables should be set in the configuration files of the Tomcat or WildFly application servers. If you are using a Standalone server, you can add these variables to the standalone.xml configuration file, containing all necessary environment variables to be set before starting. The values of these variables can be seen on the organization settings page.
We believe these improvements will greatly enhance your experience in the platform.
Thank you for your support, and we are looking forward to delivering more significant value in future updates.
Last updated