Release Notes
What is new in this version
Global
- Bug fixes
- PHP 8.3 support
- API for the creation of a local user
Blackout Management
- BigPanda: Support for calendars
- BigPanda: Support for blackout profiles
- Preview capability
Data Editor
- BHOM : support for "advanced enrichment" policies
- BHOM : support for multiple BHOM tenants
- BHOM : support for the "lastmodifier" functionality
- BHOM : export cell DDA into BHOM enrichment table
- See parameters BHOMInfraType, BHOMTableName etc in Configuring Data Editor
Test Manager
- BHOM : allow multiple BHOM tenants
- Cmd can now be checked again regular expression in Text or attribute value in JSON
Self-Service Monitoring Portal
- Bug fixes for BHOM
Known issues
Global
|
Reference |
Description |
Workaround |
|
Global1 |
Authentication fails when password contains accents (é,è,à …) if using TrueSight Presentation Server |
This is a Remedy Single SignOn bug |
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. |