Production module was renamed from Release Candidate 4 (“RC4” suffix) to Full Release (no suffix). Importing an Area object into a licensed site will no longer throw an exception about being unable to find the Site parent.Ĭorrected inverted import/export labels in MES Equipment Manager.Ĭorrected inverted import/export labels in the MES Equipment Manager.Ĭorrected an issue where, when grouping by time interval and using the Line Standard Count or Line Target Count or the Variance version of either data point, values would be less than expected if that time interval contained a shift change or day change.Ĭorrected an issue when grouping by time interval and using the Line Standard Count, Line Target Count, or Variance version of either data point, values would be less than expected if that time interval contained a shift change or day change.

Live analysis for Reject Count on cells should no longer lose counts. When artifacts are removed from the method, changelog data for that artifact version is also removed.

Multiple groups in analysis filter by will no longer cause no results to be returned.Īdded hidden, deprecated, versions of createOperation and createSegment that accept a boolean ignoreVersion parameter for backwards compatibility on scripts from Platform 2.0. This was caused by hash collisions on unequal group values. Redundant delays are now avoided, schedules are now cached, and schedule delays now happen asynchronously.Ĭorrected an error where analysis could return a message saying there are multiple unequal values, consider adding the datapoint to group by when the column is already in the group by. For my use case, option 1 seems like the appropriate solution.Responsiveness and turnaround times when performing schedule delays has been improved. The only solutions I can see currently are to create dummy alarms for each priority you don’t intend to configure, disable the overlay, or reduce the priorities you’re filtering for to only ones that you have configured. However, if no priority 4 alarm exists, and a priority 3 alarm is active, the REFERENCE_NOT_FOUND error appears, as the isAlarmActiveFiltered function for priority 4 alarms errors when no alarm is configured that meets the filter criteria. If a priority 4 alarm is configured and active, the expression appears to work fine.

For example, in my expression, I’m checking for the highest priority alarm active in a folder path specified by the UDT parameter *', '*', '*', 2, 2, 0, 1, 0), 2, 1))), 0)

From what I can tell, the REFERENCE_NOT_FOUND error is thrown when there are no alarms configured in the filtered path that meet all the priorities the expression is looking for.

Ignition 7.9 isalarmactive