View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003162 | 10000-005: Information Model | Spec | public | 2015-09-03 22:01 | 2016-12-14 23:13 |
Reporter | Assigned To | jeffhardingabb | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 1.03 | ||||
Summary | 0003162: OperationLimits.MaxMonitoredItemsPerCall and SetTriggering? | ||||
Description | CMPWG Sep-3-2015: The OperationLimits.MaxMonitoredItemsPerCall seems quite intuitive for CreateMonitoredItems, ModifyMonitoredItems, SetMonitoringMode, and DeleteMonitoredItems. But what about Triggering? The SetTriggering service does not have a "MonitoredItems" parameter, but has LinksToAdd and LinksToDelete. The MaxMonitoredItemsPerCall could work but: | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
Added additional text to "MaxMonitoredItemsPerCall" property description in Part 5 section 6.3.11 to explain how it applies to LinkstoAdd and LinksToDelete |
|
Agreed to changes edited in the meeting. |
Date Modified | Username | Field | Change |
---|---|---|---|
2015-09-03 22:01 |
|
New Issue | |
2016-03-08 16:55 | Jim Luth | Assigned To | => Thomas Rummel |
2016-03-08 16:55 | Jim Luth | Status | new => assigned |
2016-03-08 16:55 | Jim Luth | Target Version | => 1.04 |
2016-11-29 14:16 | Jim Luth | Assigned To | Thomas Rummel => jeffhardingabb |
2016-12-08 20:57 | jeffhardingabb | Note Added: 0007470 | |
2016-12-08 20:57 | jeffhardingabb | Status | assigned => resolved |
2016-12-08 20:57 | jeffhardingabb | Fixed in Version | => 1.04 |
2016-12-08 20:57 | jeffhardingabb | Resolution | open => fixed |
2016-12-14 23:13 | Jim Luth | Note Added: 0007543 | |
2016-12-14 23:13 | Jim Luth | Status | resolved => closed |