Version 1.33.0
This release improves user performance and updates platform design style.
Functional improvements include displaying REM attributes in list view, which allows working with them as with regular fields without opening record forms. Another important feature of the list interface is bulk editing of records.
In this version, we introduced the first stage of flexible interface style configuration that uses design tokens. The new standard supports centralized management of visual parameters and visual consistency of all system components.
New features
Use design tokens to configure interface
We implemented the first design tokens that define fonts and colors for system components. In this regard, you may notice some changes in the agent interface layout.
You can already try the new system configuration, but it is currently available only through configuration file editing. In the next versions, design tokens will be available in the agent interface.
Read more in Design Tokens.
Display REM attributes in the list view
List layout configuration now supports displaying columns for record extended models. REM attributes are available both for system-wide and personal list layout configuration.
You can add attributes of only one record extended model. The number of attributes is not limited.
The current version has some functional limitations on REM attributes in lists, namely: no inline editing, no report creation based on the REM attributes data, and other restrictions related to table data and personal settings import.
Read more in Record Extended Model.
Edit records in bulk
Now, you can edit the value of a column in all selected table records without opening their forms.
In this version, bulk editing is available only for the fields of type Choice and Reference, so you can assign or reassign several tasks to a specific employee, or change the state of the selected service requests.
Bulk editing can lead to inconsistent behavior of business processes implemented with custom logic. For example, if changing a field value requires additional actions from a user, such as adding a comment or an attachment, these actions will be skipped.
Read more in List Interface.
Improvements
API for Translated Text
For the developers and administrators of multilingual platforms, we added a new API for managing localized data. With this update, you can interact with the fields of type Translated Text, including REM attributes, with more flexibility and safety.
In the next versions of the platform, the System Translation (sys_translation) table will be deprecated, and you will not be able to use it any longer.
Starting from this version, we recommend:
- using new methods in scripts for working with the fields of type Translated Text,
- updating existing scripts that reference the System Translation (sys_translation) table.
To search for such scripts, configure the condition builder as follows:
JSON Copy contains "sys_translation
OR
JSON Copy contains 'sys_translation
OR
JSON Copy contains `sys_translation
Use the new set of methods to work with the translations:
- getTranslation() – returns a translation into the current or specified language as a String.
- setTranslation() – sets or edits a translation into the current or specified language.
- getTranslations() – returns an object with all translations. If there is no data, a default value is returned: {"en":""}.
- setTranslations() – sets or edits translations into the specified languages.
- getTranslatedText() – when called directly, it returns the value in the current user's session language, or in English as the default system language.
To reduce localization errors, the methods include a strict validation of input parameter types, and support only valid language codes.
Read more in Localization.
Compact view support in the Form SimpleTag
The Form SimpleTag now includes a compactView attribute that you can use to define the form view that overrides the Interface compact view value selected by the current user. If the attribute is not set, the view is defined by the Interface compact view setting.
The compactView attribute configuration does not apply to the remForm SimpleTag located inside of Form.
Read more in Form.
System Improvements
SimpleOne Platform support for RED OS
The SimpleOne Platform and its business applications are now compatible with the Russian operating system RED OS.
Read more in the Maintenance documentation.
Expanded real-time support for platform mechanisms
A single entry point has been implemented for all WebSocket connections through a full-featured proxy server. Client applications now connect to a single universal address instead of interacting directly with individual microservices, and the real-time messaging mechanism has been standardized and made more reliable.
Currently, the single entry point is used for the presence indication engine. In the future we plan to expand the real-time operation to support other features of the platform.
Read more in the Maintenance documentation.
Fixes
DEF0022746: A workflow terminated with an exception if fields of type WYSIWYG were passed to the Set Values block. This was caused by a mismatch between the data type expected by the block and the WYSIWYG data type. In this version, the Set Values block has been adjusted to work correctly with WYSIWYG data.
DEF0022716: When saving business rules, the error str_contains(): Argument #1 ($haystack) must be of type string, array given occurred when combining the Async/Async after trigger conditions with the contains/does not contain filter, which referenced a WYSIWYG field. In this version, the business rule logic has been updated, and the expected behavior has been restored.
DEF0022580, DEF0022143: System security has been enhanced through a scheduled update of outdated libraries and Redis.
DEF0021308: The Updated by field in the Indicators (sys_indicator) table displayed the name of the user who created the record. In this version, the behavior of the field has been corrected, and the indicators mechanism now correctly displays the name of the employee who applied the changes.
DEF0019015: When grouping records by a field of type Choice, the error Attempt to read property “display_value” on null occurred if one of the records contained a non-existent option value in that field. In this version, we have added additional checks performed during grouping and restored the correct behavior of the mechanism.
DEF0018099: Notifications displayed the employee sys_id instead of the caller's email address. This issue occurred if the notification rules for the Other Recipients field used the format ${current.caller} instead of ${current.caller.email}. In this version, we have restored support for both formats.
DEF0017950: Users can no longer change the values of fields protected from editing through quick import.