Enhance collection module to force a collection if the configured extended DQ has changed

Big Picture User Experience

Allow the collection module to recognize and force a collection if the configured extended Data Attribute has changed

Detailed Description

If the configured Data Attribute in the DQFlagConfiguration table is configured and enabled for collection and explicitly configured to trigger collection due to a change in the attribute, the whole point must be collected. For example, if flag.flash will change it state from yes to no or vise versa, the point must be collected.

Business Value

Provide grater collection granularity for collect and increased accuracy and data available to PI and Connect Data Services.

PSR - Performance, Scalability, Resilience

Important PSR aspects for this feature? We need to me minded of how much more records will be collected with this change.

It is important to note that if two value change as part of one change. Only one record should be written to the historical DB.

What if there are 10,000 of these?
Same as our regular PSR. Feature test should focus on the functional accuracy as such I dont envision change to the PSR framework.

How quickly is this expected to react/respond? Slow than it does today, but not too slow

Does this impact failover / mode switch? yes

Is this assumed to have performance impact, or not? TBD

Risks/Mitigations

None.