Skip to main content

Release Notes

What is new in this version

Global

  • Bug fixes 
  • LDAP/LDAPs native support for authentication
  • Authentication forced to Local when the REST api is used and the primary authentication is SAML. 
  • BHOM: Support for multiple tenants

Blackout Management

  • BHOM: Support for blackout profiles
  • Preview capability
  • AutocommentAutomatic generation of description of profiles can be disabled (see DisableAutoComment in the module configuration).

Data Editor

  • Bug fixes
  • BHOM : support for multiple BHOM tenants
  • BHOM : ability to use BHOM DDEN table data as external sources.

Test Manager

  • BHOM : allow multiple BHOM tenants
  • Cmd can now be checked again regular expression in Text or attribute value in JSON

Known issues

Quick Query module

Reference

Description

Workaround

QQ6

When using oracle, it is not possible  to run “table” queries against the “date” slot – the “date” word being reserved on oracle

Use the mc_arrival_time instead.

QQ7

Microsoft SQL Server does not support searching using regular expressions. The match_regex operator is replaced by the LIKE operator when using Microsoft SQL Server

None.

Data Editor module 

Reference

Description

Workaround

DD1

Upload of Excel or CSV files is not possible from workstations where Excel is not installed.

On Windows systems you can import the registry key that contains the MIME type of the .xslx files.

We provide a copy of this key in $PRODUCT_HOME/tools/etc/ProactivePackWinReg

As always use caution when applying changes to the windows registry

Self-Service Monitoring Portal

Reference

Description

Workaround

SMP2

If a TSPS group is created when a Proactivepack TrueSight host group is created, it is thereafter not possible to delete the TSPS group using ProactivePack

The problem is due to a limitation of the BMC REST API.

The TSPS group must in that situation be manually deleted inside TSPS

SMP3

If a TrueSight CMA policy is subscribed/unsubscribed multiple times, it will still work fine but it will not be displayable and editable properly in TSPS as it supports a maximum a maximum of 3 nested agent conditions.

None (At least until TrueSight 11.3.03) – BMC defect reference : Defect#DRTMN-67.

SMP4

Discovery of Instance Information for “LOG” monitoring may fail in case multiple files with a same name but a different path are declared.

When creating a “Log monitoring – Text files” monitoring for a new file in CMA, make sure to provide a logical name.

 

Back to top