CASE PM-121754-19-202524:

Previously, the application had an inconsistency when working simultaneously on consoles CMDB and Specialist. When you open the Specialist since CMDB, the user’s session was unexpectedly logged out due to inactivity.

A setting has been implemented that corrects inconsistency in session management, allowing these sessions to remain active on both consoles independently.

It’s important to note that downtime is managed individually by each console. That is, activity on a console (e.g., CMDB) does not reset or affect the other’s idle timer (for example, Specialist).