3.81.2 Release Notes

Core | OEE/Downtime

FIXED

Fixed an issue where the characters \ or ' could be stored in the database as two characters instead of one

Recipe

FIXED

Deleting new recipes in an Enterprise context syncs correctly

When a production equipment item syncs to another server, it will include references to all assigned Recipes.

Extended characters are now supported for S&C Security.

Equipment can now be bound to Master Recipes, even if they are already bound to Descendants under that Master Recipe.

Recipe Changelog events from Platform 2 now properly upgrade to 3.

The Platform 3 Settings & Changeover system now uses the Analysis datasource for all transactions.

Recipe 2 can now be upgraded to Settings & Changeover 3 if the Local and Analysis Datasources differ.

S&C Setpoint scalars are now implemented when displaying Variance Tracking History.

Binding S&C Enable-Recipe and Recipe-Scale Tag collectors no longer breaks MES and OPC S&C tags for Ignition 7.

The Recipe Variance Exists tag will go low (int=0 or bool=False) when the Recipe is canceled. This behavior is intended to match platform 2.0.

Made it easier for users to cleanly create new Recipe Value Security Complex Properties.

Made it easier for users to set a Default Recipe Value's Security Mode.

Added validation for Recipe Value Security; a corresponding Setpoint Definition must exist on the Equipment item.

Added Validation for Recipe Value Security, so that the user is prevented from entering malformed arguments. Some leniency is still given for disabled Security Values.

Core | Recipe | Trace

FIXED

NPE no longer thrown when comparing null lots.

Core | Recipe

FIXED

Invalidate MESObjectCache when transitioning redundancy active state to clear out possibly stale objects.