by VIKTOR
Following our release schedule, we just released a new major version: SDK v14.0.0!
This new version contains two main features which we will be highlighting in this newsletter: UserMessage and Colorfield.
Besides these new features, this release also serves as a clean-up moment to remove previously deprecated functionality. Click here for the upgrade guide v13 → v14.
We noticed some VIKTOR users have not yet upgraded their apps from v12 to the latest SDK version. That is why we decided to extend the support period for v12 with 3 months. Please make sure to update any apps running on v12 before the end of July.
If you have any questions or encounter any problems, please reach out to the community.
Next to progress messages and UserErrors, we have added another method for informing the end user: non-interruptive user messages. There are three different types you can choose from: a 'warning', 'information' or 'success' message. Contrary to the UserError, when users receive this message type, their calculation will continue. This can come in handy when, for example, a certain sub-result can not be calculated or to confirm that the validation job succeeds.
Non-interruptive user message are shown are persisted in the job log and can be looked back in the interface. Visit the documentation to learn more.
For the release of SDK v14, we have added a new field to the SDK that allows end-users to easily select their desired color. With the ColorField
, end-users can visually select colors in your applications instead of using RGB values, HEX color code, or any predefined color options.
Visit the documentation to learn more about the ColorField
.
We have written a tutorial that outlines how to implement report generation in a VIKTOR app. In this tutorial, we explain how you can:
In the future, we will be adding more tutorials like this that explain step-by-step how to use certain features. If you have any recommendations or questions, please let us know in the community forum. Click here to start now!
SDK
PLATFORM
OutputField
TableField
defaults not being applied in the right order in public workspacesentity_type_names
are defined incorrectlyCLI
Subscribe to our newsletter and get the latest industry insights