Skip to main content
Version: 2.1.1

Version 2.1.1

In this version of the ESM platform, we completed implementing multilingual support for announcement content. This feature is designed for international companies and enables fast, accurate delivery of information to clients and partners in any language.

The financial module now supports Payment Request (payment_request). The table includes minimal configuration so you can set up the payment request process according to your organization's policies.

The new Currency Exchange Rate (currency_exchange_rate) dictionary provides access to up-to-date exchange rates from configurable external sources, such as the Central Bank of Russia. This functionality provides greater control over financial flows in organizations that operate with multiple currencies.

For example, in payment requests, the amount can be displayed both in the system default currency and in the currency specified in the invoice.

You can now create configuration items for services and view the dependency maps that include them.

It is now also possible to define rules for relationships between configuration items using the CI Relationship Rule (sys_cmdb_ci_relationship_rule) table. These rules specify which classes of configuration items can be related and the types of the relationships allowed. You can also configure how relationship lines are displayed on dependency maps.

caution

After upgrading to version 2.1.1, perform data migration to ensure correct application behavior. Run the following scheduled scripts:

Required:

Optional:

Read more about running the scripts in this article.

New functionality​

Announcement translations widget​

You can now use a new widget on the Service Announcement (announcement) and Announcement Template (announcement_template) forms to create announcement content and translations. The widget supports:

  • Creating and editing the subject and contents of announcements in the languages available on the platform
  • Setting a default announcement language used when the user language does not match available translations or when the user does not have a SimpleOne account
  • Adding separate signatures for each translation
  • Formatting text using a rich text editor
  • Opening translation records in the Announcement Localization (announcement_localization) table from the kebab menu on the language tab

If users do not have the permission to view or edit announcement content and translations, a placeholder is displayed: Data unavailable.

Read more in Announcements.

To migrate the content of the Subject, Body, and Signature fields of the existing announcements into the new widget, run the Migration script for announcement scheduled script.

Payment requests​

You can now register payment requests in SimpleOne. The Payment Requests (payment_request) table uses references to the Company (org_company) and User (user) dictionaries and also supports requests for goods and services from new companies.

Payment requests support tracking of payment obligation status and required payment details. On the request form, you can attach documents or indicate that they are available in the electronic document management system.

The ESM platform provides base logic for payment requests, which supports safe extension and customization of business logic in related tables across applications.

Read more in Payment Requests.

Currency rates​

You can now use the Currency Exchange Rate (currency_exchange_rate) dictionary to obtain up-to-date data for financial operations, which is important when the company's primary currency differs from the transaction currency. Exchange rate data can be imported regularly from external sources or entered manually.

By default, exchange rates are imported from the Central Bank of Russia and stored in the Exchange Rate History related list on the currency form.

The Amount in default currency and Default currency fields are now available in the existing Actual Cost Item (actual_cost_item) records. To populate these fields, specify the default currency in the currency.default system property and run the Set amount in default currency in Actual Cost Items scheduled script. For details, see the upgrade instructions.

For more information, see Currencies.

CI relationship rules​

You can now configure how relationships between configuration items are displayed, including the connecting line color and style on dependency maps. The new CI Relationship Rule (sys_cmdb_ci_relationship_rule) dictionary is available to define the classes of configuration items that can be related, as well as the relationship direction and type.

The system prevents the creation of cyclic relationships and relationships of configuration items with themselves.

Relationship types are stored in a dedicated dictionary and include:

  • Name
  • Active state
  • Line type
  • Color
  • Highlighting

A separate configuration item class is now defined for services.

Read more in СI Relationship Rules.

We also added a script CI relationship rules that creates CI relationship rules for configuration items based on the existing records in the CI Relationship (sys_cmdb_relationship) table. Each rule includes two configuration item classes and the allowed relationship types. You can also create rules manually.

Improvements​

Auto-population of Service and Consumer in tasks​

Now the Consumer and Service fields are populated automatically when a request is created from a request model where they are already defined. This helps agents save time working on the requests.

Read more in Task table.

After upgrading to version 2.1.1, perform data migration to set the Class to Service for all records in the Service (sys_cmdb_ci_service) table.

Employees​

The Active checkbox and Password field are now included in the Default view of the Employee (employee) table. This reduces the need to switch views during frequent record management.

Fixes​

DEF0017734: We implemented additional access restrictions for personal data.

DEF0016832: In this version, we fixed logical and syntax errors in user import scripts that caused incomplete data retrieval from LDAP.

Migration scripts​

Migration script for announcement​

To run the Migration script for announcement scheduled script, follow the steps below:

  1. Navigate to System Scheduler → Scheduled Scripts.

  2. Open the Migration script for announcement script, also available at the {your instance URL}/record/sys_schedule_script/175940959704560366 address, and complete the fields as follows:

    FieldValue
    ActiveYes
    Run frequencyOnce
    Run date and time

    Specify the time when the system load is minimal, for example, after midnight.

    Example: 2025-09-01 01:01:00

    The system will run the script according to the time set in the Preferences menu of the platform, not the time set on your device. If they differ, for your convenience, edit the time zone in the Preferences so that it coincides with the time on your device.

  3. Click Save to apply the changes. The script will be executed at the specified time.

As a result, in the records of the Service Announcement (announcement) table, the Subject, Body, and Signature fields of the widget are completed with the relevant data.

Service Class Mapping​

After upgrading to version 2.1.1, perform data migration to set the Class to Service for all records in the Service (sys_cmdb_ci_service) table.

To perform the migration after the SOP file with the update is installed, do the following:

  1. Navigate to System Scheduler → Scheduled Scripts.

  2. Open the Service Class Mapping script, also available at the {your instance URL}/record/sys_schedule_script/175698014118761868 address, and complete the fields as follows:

    FieldValue
    ActiveYes
    Run frequencyOnce
    Run date and time

    Specify the time when the system load is minimal, for example, after midnight.

    Example: 2025-09-01 01:01:00

    The system will run the script according to the time set in the Preferences menu of the platform, not the time set on your device. If they differ, for your convenience, edit the time zone in the Preferences so that it coincides with the time on your device.

  3. Click Save to apply the changes. The script will be executed at the specified time.

After execution, the Class field is set to Service for all records in the Service (sys_cmdb_ci_service) table.

CI Rules Migration​

warning

The CI relationship rules migration script does not validate cyclic relationships. If such relationships may exist in the system, create the CI rules manually.

  1. Navigate to System Scheduler → Scheduled Scripts.

  2. Open the CI Rules Migration script, also available at the {your instance URL}/record/sys_schedule_script/175853165213089861 address, and complete the fields as follows:

    FieldValue
    ActiveYes
    Run frequencyOnce
    Run date and time

    Specify the time when the system load is minimal, for example, after midnight.

    Example: 2025-09-01 01:01:00

    The system will run the script according to the time set in the Preferences menu of the platform, not the time set on your device. If they differ, for your convenience, edit the time zone in the Preferences so that it coincides with the time on your device.

  3. Click Save to apply the changes. The script will be executed at the specified time.

After the execution:

  • The Source class field is set based on the class of the Source CI in the CI Relationship record.
  • The Recipient class field is set based on the class of the Recipient CI in the CI Relationship record.
  • CI Relationship type field is set to Dependency.
  • If any relationship between two classes is bilateral, the rule is set to Interdependency.

The rules are not created for relationships within the same class or if a rule already exists for the same pair of classes. Cyclic relationships are not validated with the script.