Happy new year from our team! Thank you for being with us. We appreciate your trust in choosing our platform. Our team is working in full capacity to provide new exciting features without forgetting to fix some outstanding problems along the way to improve your user experience.
The release 22.02 includes lot’s of work under the hood. Our team is working to improve and refactor some of the core microservices.
Our team is working towards more uniform component deployment mechanism. The one which would work without involvement of our team. Many scenarios and mechanisms are being considered. More details will come in our future releases.
With this release we have refactored an outdated code from the
to prevent component configuration change every time we deploy the platform code.
When you deploy a new version of your component code our system builds it and saves it in the docker registry. This process also checks the version of the deployed code. If the version (or component semver) is the same or below the deployed version the deployment fails. Previously, the semver check would happen as a last step of the component deployment causing unnecessary delays for the component developer and resource consumption on the platform side.
In 22.02 we change this behaviour. Now the platform would perform semver check in the beginning and reject with the message Error: Repo Build with version x.y.z already exists if necessary.
The three dots
... for opening thread details in the end of the log string at
the Logs page now displays permanently instead of appearance on mouse hover.
Enable download attachmentsto actions:
Lookup Set of Objects
Read from Branch
Lookup Documents (Lookup Objects Plural)action
Make Raw File Upload Requestaction