Table of Contents

General Main Release 10.5.0 – Breaking changes

Note

For known issues with this version, refer to Known issues.

Parameter latch states will now be reset after every DataMiner restart [ID 39495]

In order to increase overall performance when starting up elements, parameter latch states will no longer be persistent by default. They will be reset after every DataMiner restart.

If you want to have persistent parameter latch states, do the following:

  1. Open the MaintenanceSettings.xml file.

  2. In the AlarmSettings section, add the PersistParameterLatchState option, and set it to true.

    <AlarmSettings>
   ...
   <PersistParameterLatchState>true</PersistParameterLatchState>
   ...
</AlarmSettings>

  3. Restart the DataMiner Agent.

Important
  • From now on, by default (or when the PersistParameterLatchState option is set to false in MaintenanceSettings.xml), parameter latch states will no longer be written to or fetched from the database. This means that, after every DataMiner restart, all parameter latch states will be reset.
  • Element, service and view latch states will remain persistent as before.

GQI - 'Get alarms' data source: Updated 'Alarm ID' and 'Root Alarm ID' columns [ID 40372]

In the Get alarms data source, the following columns have been updated:

Column Former contents New contents
Alarm ID HostingDMAID/AlarmID DMAID/EID/RootAlarmID/AlarmID
Root Alarm ID HostingDMAID/RootAlarmID DMAID/EID/RootAlarmID
Note

"DMAID" refers to the DataMiner ID of the DataMiner Agent where the element was originally created. "HostingDMAID" refers to the DataMiner ID of the DataMiner Agent currently hosting the element and managing its alarms. Most of the time, these two values will be the same, but they may differ, for example, when an element is exported from one Agent and imported onto another Agent. In this case, the element retains the original DMAID, but the HostingDMAID will reflect the new Agent's ID.

Automation: SubScriptOptions.SkipStartedInfoEvent will now by default be set to true [ID 40867]

If you have created an Automation script that launches subscripts, you can use the SkipStartedInfoEvent option to specify whether "Script started" information events should be generated for the subscripts or not.

Up to now, this SkipStartedInfoEvent option would by default be set to false. From now on, it will by default be set to true.

DataMiner Object Models: An exception will now be thrown when an issue occurs for any of the DomInstances that are created, updated, or deleted in bulk [ID 41546]

From now on, if an issue occurs for any of the DomInstances that are getting created, updated, or deleted in bulk (e.g. validation), a BulkCrudFailedException<DomInstanceId> will be thrown. The Result property in the exception can be used to check for which DomInstances the call succeeded or failed. For information on how to implement this flow, refer to the Checking issues example.

As an alternative, the TryCreateOrUpdate or TryDelete methods can be used. When the operation fails for one of the DomInstances, those calls will return false. The result output parameter will contain:

  • The list of successfully processed items, as is the case for CreateOrUpdate and Delete.

  • A list of DomInstance IDs that failed to be created, updated, or deleted.

  • The trace data per DomInstance ID.

For each of these methods, the trace data of that call is still available and will contain the trace data for all processed DomInstances.

Important

In DataMiner versions prior to DataMiner Feature Release 10.5.0/10.5.2, when any validation issue occurs, no exception is thrown (even when ThrowExceptionsOnErrorData is true) when calling the CreateOrUpdate or Delete methods. Instead, the result of the call should be used to check for which DomInstances the call succeeded or failed.

Note

When creating, updating or deleting a single DomInstance, you can now also use the TryCreate, TryUpdate and TryDelete methods as an alternative in order to avoid having to check for exceptions. These methods are also available for other objects that make use of the CRUD helper component.

Improve this page