Skip to main content
Version: 1.29.0

Version 1.29.0

Platform split into ESM and LCAP​

In this version, we split the platform into business tools of the Enterprise Service Management (ESM) platform and a Low-Code Application Platform to accelerate development and deliver updates faster. Now these platform components are stored as different applications and their updates can be released independently.

  • The Simple Application (SA) stores business tools of the ESM platform.
  • The Platform application stores low-code development tools and the platform configurations that must be protected from changes.

We have enhanced the system security with the new mechanism URL Security Rule that ensures the URLs of the external pages used in scripts are safe, and improved incoming email processing with the new Email Exception mechanism.

Simple Application​

New features​

Task Subscription​

Users of the self-service portal and agent interface can now subscribe to receive updates for specific task records. To subscribe, click Subscribe or the bell icon on a task form. To unsubscribe, click Unsubscribe or the bell icon again.

In the out-of-the-box version, this widget only appears on the task forms. However, you can also add it to forms of any other entities that support this mechanism.

Note that other similar subscription mechanisms that exist in SimpleOne business applications will be considered deprecated in the future releases.

Service providers and service consumers identification​

Starting with this version, you can define different branches of your organization as separate Service providers and Service consumers. The ability to identify multiple service providers within an organization is a key feature for creating a genuine ESM approach in companies. Unlike ITSM, where only one department is a service provider, with an enterprise service management approach, you can define different organization directions, such as Accounting, Administration and Maintenance Department, and HR as service providers and organize their own service management practices.

With this functionality you can track the responsibilities of participants, create reliable reports, accurately determine consumer costs for company services, and build comprehensive services involving multiple service providers.

Records of all service providers are stored in the Service Providers (service_provider) table, and the new Service Relationship widget displays information about the service provider and consumer for which the task was created.

Read more in the Service Providers article.

Service Relationship widget​

To visualize service relationships formed during task execution, we have created a new Service Relationship widget. The new widget displays the values of the Service Provider and Service Consumer fields. The widget helps agents quickly understand the context of a request or incident related to a specific service and resolve the issue.

The widget has a customizable title and description so that you can add more information to it.

In the out-of-the-box version, the widget is not added to the agent interface and self-service portal forms.

Read more in the Service Relationship Widget article.

Platform Application​

This release improves platform stability and performance and expands management capabilities.

New features​

URL Security Rules​

In this version, we have introduced a URL security verification mechanism with rules that prevent scripts from accessing undesirable resources. These rules are defined in the URL Security Rule (sys_url_security_rule) table, which has 10 pre-configured URL patterns. You can also add your own rules to this list.

For more information, see the URL Security Rules article.

Email processing exceptions​

In this release, we have enhanced the incoming email processing logic with a new entity: Email Exception (sys_email_exception). A record is created in this table for any email that the system fails to process.

This ensures that during the incoming email update cycle, the system skips problematic emails, allowing later emails to be loaded without interruption.

Each Email exception record contains details about the email, an attached copy of the original email in the EML format, and a processing error that caused the failure. In some cases the EML attachment may be missing.

Email record: New state and related list

The new state, Parsing error, is set when the system fails to process the email. If necessary, you can delete the record, the email will be reuploaded again.

The new Exceptions related list on the Email form contains related records from the Email Exception (sys_email_exception) table. Open them to see the error details.

Read more in the Incoming and Outgoing Emails article.

Improvements​

Passwords for RabbitMQ​

RabbitMQ credential passwords are now stored in an encrypted format in the records of the RabbitMQ Producer (sys_rabbitmq_producer) and RabbitMQ Consumer (sys_rabbitmq_consumer) tables.

caution

During the platform update to version 1.29.0, the current passwords for RabbitMQ Producers and RabbitMQ Consumers will be encrypted. We recommend that you change these passwords after the update to prevent them from being compromised using the VCS versions created on platform of previous versions. Avoid using special characters in the password to prevent connection failures.

Indicator optimization​

Now system verifies only relevant conditions, namely we have excluded from the validation process the indicators that have conditions that are irrelevant for the current record. This optimization reduces the system load when a large number of active indicators are applied to a single table.

Read more in the Indicators article.

Interface and texts​

  • The magnifier icon has been redesigned to improve accessability of the search bar.
  • The Choice Timeline widget layout has been fixed.
  • The list view of the Organization (org_organization) table has become more informative with the new Authorized employees field.
  • Deprecated fields of the contract form have been renamed to prevent them from being misused.

Fixes​

  • DEF0021632: We have updated the search icon to make the search bar easier to find.
  • DEF0021115: The Choice Timeline widget on task forms had a layout issue that caused indicators to appear too small. In this version, the layout has been corrected.
  • DEF0020872: Server scripts were able to access sensitive URLs. In this version, we have added URL security validation rules with 10 pre-configured patterns. For more information, see URL Security Rules article.
  • DEF0020682: In the previous version, the new Customer and Consumer fields derived from the Organization (org_organization) table were added to the Contract (contract) table. Due to identical labels for old and new fields, users could not distinguish between them. We have now updated the translations for the legacy fields to Consumer (Deprecated) and Customer (Deprecated).
  • DEF0020384: Creating a new column for a table under a heavy load would sometimes fail. This issue has been resolved by wrapping the column creation data and its addition to the target table in a single transaction.
  • DEF0019118: After making changes and saving a form, clicking on fields of type List triggered an error: Uncaught TypeError: Cannot read properties of null (reading 'style'). Now, users can edit fields of type List without triggering errors.
  • DEF0017930: Previously, the getErrors() method did not return errors if a record operation (create, update, delete) was canceled using the setAbortAction() method, as there was no mechanism to preserve the error. Now, errors are saved and displayed in toast messages.
  • DEF0017746: User session information was stored in the browser's local storage instead of cookies with the HttpOnly and Secure parameters. In this version, the system behavior has been fixed.
  • DEF0017580: The previous version of kafka-ui 0.6.1 that was used by the system was unavailable when working offline. In version 1.29.0, this component has been updated and the system is stable when offline.
  • DEF0016351: Passwords for RabbitMQ were stored without encryption in the records of the RabbitMQ_provider (sys_rabbitmq_producer) and RabbitMQ Consumer (sys_rabbitmq_consumer) tables. In this version, the passwords are encrypted.