View Issue Details

IDProjectCategoryView StatusLast Update
001039110000-004: ServicesSpecpublic2025-10-09 14:20
ReporterAlexander Allmendinger Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilitysometimes
Status assignedResolutionopen 
Product Version1.05.04 
Summary0010391: Specify initial DataChangeNotification as trigger for triggering
Description

The specification is not clear whether the initial DataChangeNotification of a Triggering item is to be considered a trigger.

Assuming the following workflow:

  1. CreateSubscription with PublishingEnabled = false
  2. CreateMonitoredItems (1 MonitoredItem with MonitoringMode Reporting, several others with Sampling)
  3. SetTriggering with a Trigger and the others as LinkedItems
  4. SetPublishingMode to PublishingEnabled = true
  5. Publish

In this scenario the UA Working Group in the meeting on 24th of June agreed, that the initial value for the trigger item is also triggering the publish of the LinkedItems. But there are major SDKs which behave differently so the group sees the need to describe the two use cases being possible with triggering by changing the order of the calls to ensure the same behavior between the products. The first option is what was outlined above the second option is to call publish after the creation of the MonitoredItems but before calling SetTriggering. In this case the initial value of the monitored item was already reported and the trigger would not occur.

Here is a text proposal for the specification to add a paragraph to 5.13.1.6 Triggering model:

The order of service calls when using the triggering model affects the behavior during initialization. Clients can choose between two approaches depending on whether initial values for the LinkedItems are required.

  1. When initial values for LinkedItems are required:
    The Client shall call SetTriggering before sending a Publish request to the Server. In this case, the initial value of the triggering item has not yet been reported to the Client. When the Server subsequently receives the Publish request and generates a NotificationMessage, the triggering condition is met, and the current queues for both the triggering item and the LinkedItems shall be reported.
  2. When initial values for LinkedItems are not required:
    The Client shall first call Publish after creating the MonitoredItems, and only then call SetTriggering. In this scenario, the initial value of the triggering item has already been reported. Since the links are created after the initial Publish, no triggering event occurs, and therefore the LinkedItems are not reported.
TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2025-10-09 14:20

administrator   ~0023458

Discussed in the Genoa F2F. Can't reach consensus for 1.05.06 -- needs further design.

Issue History

Date Modified Username Field Change
2025-06-25 11:14 Alexander Allmendinger New Issue
2025-07-15 16:29 Jim Luth Assigned To => Matthias Damm
2025-07-15 16:29 Jim Luth Status new => assigned
2025-07-15 16:29 Jim Luth Commit Version => 1.05.06
2025-07-15 16:29 Jim Luth Fix Due Date => 2025-09-15
2025-10-09 14:20 Jim Luth Note Added: 0023458
2025-10-09 14:20 Jim Luth Commit Version 1.05.06 =>
2025-10-09 14:20 Jim Luth Fix Due Date 2025-09-15 =>