How Does an Orchestrator Activity Determine if a Measurement Exists that can be Used or Know to Wait for a Scheduled Read or Request a Measurement?
(Doc ID 3075274.1)
Last updated on MARCH 04, 2025
Applies to:
Oracle Utilities Customer Cloud Service - Version 19C and laterOracle Utilities Meter Data Management - Version 2.2.0.3.0 and later
Oracle Utilities Customer to Meter Base - Version 2.6.0.1.0 and later
Oracle Utilities Meter Solution Cloud Service - Version 19C and later
Information in this document applies to any platform.
Goal
How Does an Orchestrator Activity Determine if a Measurement Exists that can be Used or Know to Wait for a Scheduled Read or Request a Measurement?
A customer would like to wait for the next scheduled read to complete an Orchestrator activity instead of automatically requesting a new read from the Head End System or via a Field Activity. In that case, they would expect a Wait for Scheduled Read child activity to be created but they keep getting a Field Activity child activity created to fulfill the measurement requirment.
What settings are determining this behavior and how should the configuration be set up in order to get a Wait activity generated in this case?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |