Increase Maintenance Counters#

Reports an explicit batch of maintenance event quantities through the counter service.

Inputs#

Set Increments in the task details. Use the value editor to select compatible results from earlier tasks.

Increments accepts a System.Collections.ObjectModel.Collection<Cmf.Navigo.BusinessOrchestration.MaintenanceManagement.InputObjects.Helpers.IncreaseMaintenanceCountersObject>. Enter a C# expression enclosed in {{ ... }} directly in this input, or reference an earlier output containing that type.

Property	Description
`Entity`	Persisted target entity reference, such as a loaded Resource or Container.
`EventName`	Event name used by the configured maintenance activity.
`PrimaryDeltaQuantity`	Optional decimal change in the units of the primary quantity counter.
`SecondaryDeltaQuantity`	Optional decimal change in the units of the secondary quantity counter.

Table 1: Maintenance counter increment properties

Outputs#

Use Increments, Count, Message in subsequent tasks.

Increment a Resource Runtime Counter

This example requires a loaded Resource and a maintenance activity configured to count primary quantities in hours for an event named RuntimeHours. Replace the event name with the one used by your maintenance configuration.

Use Load or Refresh Entities, named load, to load the target Resource.
Add Foreach after load. Set Collection to {{$load.Result}} and Item Name to resource.
Add Increase Maintenance Counters inside the Handler branch and name it increase.

Enter the following expression in Increments:

{{new System.Collections.ObjectModel.Collection<Cmf.Navigo.BusinessOrchestration.MaintenanceManagement.InputObjects.Helpers.IncreaseMaintenanceCountersObject> {
    new() {
        Entity = (Cmf.Navigo.BusinessObjects.Abstractions.IResource)$scope.resource,
        EventName = "RuntimeHours",
        PrimaryDeltaQuantity = 0.5m
    }
}}}

Use {{$increase.Count}} or {{$increase.Message}} in a subsequent task inside the same Handler branch.

Each iteration reports a half-hour increment for its Resource. The task does not convert units. A CountOne counter counts the event instead of using the supplied quantity. Count reports the number of submitted entries, rather than the number of counters changed.