Skip to main content
Version: 1.15.1

Patch 1.15.1

In this version, we have introduced a new type of monitoring events – Instructional and improved the logic of assigning ITSM tasks to the current user. We have also corrected the logic of receiving messages from monitoring systems, which dramatically increases the performance of the Monitoring and Event Management module, and fixed an error in the Tickets section of the Portal.

caution

After upgrading to version 1.15.1, run the following scheduled scripts to ensure correct execution of the monitoring sources:

  • [ITSM] Update monitoring sources with endpoint, located at \{your instance URL}/record/sys_schedule_script/174306698700587731, for the monitoring sources of type JSON.
  • [ITSM] Update monitoring source with email, located at \{your instance URL}/record/sys_schedule_script/174307391504435032, for the monitoring sources of type Emails.

New features​

New monitoring event type​

A new monitoring event type has been created – Instructional, that allows to register the necessity of some work related to an event (for example, implementing a change), that does not lead to an incident.

For this purpose, a corresponding choice option has been added to the Type field of the Monitoring Event (itsm_monitoring_event), Monitoring Event Rule (itsm_event_rule), and Monitoring Rule (itsm_monitoring_rule) tables.

Read more on the new event type in the documentation.

Improvements​

Automatic change of Assignment groups​

To display up to date information on the responsible group in tickets, we have updated the behavior of the Start work and Assign to me buttons on the forms of ITSM entities. Now, when a user clicks one of these buttons on the forms of incidents, service requests, change requests, and problems, the Assignment group field is automatically filled in with the value of the Primary group field of the current user's record.

The following logic applies:

  • If the Primary group of the user's record is empty and the Assignment group field of the ITSM entity is filled, the value is cleared if the user does not belong to the specified group.
  • If the Assignment group field of the ITSM entity and the Primary group field of the user's record are both filled, the Assignment group field of the ITSM entity is filled with the group specified in the Primary group field of the user's record.
  • If the value of the Assignment group field is changed and the Assigned user field is empty, the members of the new group receive a corresponding notification.

Read more in the documentation:

Fixes​

DEF0020951: We have fixed the logic of data transfer from the monitoring system. Due to the use of import engine, a large number of VCS records were created on the instance for the Import Source (sys_import_source) table. In the new version, no unnecessary VCS records are created when receiving messages, which ensures a dramatic increase in the performance of monitoring event processing.

DEF0020912: We have fixed a defect that caused User Queries to appear in the Tickets section of the Portal. Now, this section only includes Incidents and Service Requests.