3.81.8 Service Pack Release Notes
3.81.8 SP 6
3.81.8 SP4
3.81.8 SP3
- full item path to validation messages so users can more easily identify steps that have validation errors
- ability to use numeric comparison operators with Date data types in Transition Expressions
- logic to validate number data types when setting parameter values
- ability to sync the state to the command if the phase is set to PLI mode.
- an issue causing deleted Process Cells to appear as usable when creating a Batch in the Batch List
- an issue causing document text on Document phases in the Batch Recipe Editor to sometimes not be saved
- Resolved issue where Batch scripts would sometimes not register on module startup
- the current step being prematurely ended during restart
- When using batch phases that have Material Properties, if the Preallocate property is false, the lot quantity will always use the 'Actual_Quantity' instead of using the max(Actual_Quantity, Target_Quantity) when the actual_quantity changes
- Fixed regression that prevented copying recipes or templates with system.mes.batch.copyRecipe and system.mes.batch.copyTemplate scripting functions
- validation logic in Batch Recipe Editor to not allow usage of numeric comparison operators with non-numeric data types in Transition Expressions
- validation logic for date/time strings
- If an incorrectly formatted date/time string is specified, the user will be given a clear message with the correct format
- accuracy of large numbers in Perspective UI by handling validation on the server for large number data types (Double, Float, Long)
- Display an error in the UI when attempting to save a value that is out of range for number data types
- MESDocumentEditor to allow number data types to be attached to "text" input fields
- Document Viewer shows visual indicators on input fields when an error occurs while saving the provided value
- BC Charts with more than 1 Stateful RFM Node will no longer automatically fail
- Perspective Material Manager- Tree Table properly updates when locale changes
- New or Modified MES Work Order will properly update Perspective & Vision Work Order Table
- Importing State Codes in one State Class will not interfere with available codes in an unrelated State Class
- Child Equipment must not contain any active operations before deleting its parent
- The OEE Downtime Table and MES Work Order table will no longer interrupt user input when data refreshes while in an edit view
- Analysis will no longer fail when querying Counter data for Oracle DB Users
- Analysis will no longer fail when querying Differed State data for Oracle DB Users
- Counters now record values at end of run
3.81.8 SP2
Batch
Core
Core|Perspective
OEE/Downtime
Recipe
Recipe|SPC
SPC
Perspective|SPC
Trace
3.81.8 SP1
Batch
SPC|Perspective
3.81.8
Batch Procedure
FIXED
- Batch scripts are now only available if the module is installed
an issue in the Batch Recipe Editor that was preventing users from referencing parameters added to a Unit Procedure or Operation in a Transition expression
an issue causing incorrect logicOrder to be set on steps when using nested AND_BEGIN/END steps in a recipe
issue causing some dialogs and dropdowns to not be displayed in the "minimized" version of the Batch Message List component
an issue causing an exception to sometimes be thrown when restarting a Held Batch after restart
issue of phase UDT instances not being created when phase is added to parent Unit Class
batch recipe scripting methods which stated certain parameters were optional to be actually optional
IllegalArgumentException being thrown when Production is restarted before Preallocate Resources phase starts
Transition expression grouping fixed for expressions like (Condition1 AND Condition2) OR (Condition1 AND Condition3). Expression grouping shows in Batch Monitor and Batch Controller
issue preventing recipes from being saved before paths are added on Set Parameter and Value Prompt phases
an issue causing some built-in enums to not be created on startup
getBatchBOM script function not reflecting values from setBatchBOM function immediately
issue when recording trace data with new Sub Parameters in an Operation
the issue of unit procedures not executing when they follow a Or Begin element
issue causing an incorrect default minValue to be set for Double and Float data type parameters on a BatchPhase when the user leaves them undefined
an issue causing units list to not update when selecting a different recipe
issue causing newly added sub-params able to be deleted in the BatchPhaseManager edit view
issue in Recipe Monitor causing Transition_Expression to sometimes show "Invalid parameter value"
setParamKind
will not change the parameter kind after it has been created but will not throw an exception to keep existing scripts working
- Issue with synced parameters not being updated in phases when transitioning to running state
- Issue causing Operation parameters to not be able to be referenced from a different UP/operation
- Issue preventing steps from being able to be moved in Batch Recipe Monitor
- Issue causing colors/state from previously selected recipe to persist when changing to a different recipe in Batch Recipe Monitor
- Issue causing phases that are faulted to not be colored correctly in the Batch Recipe Monitor
- Issue causing users unable to set min/max value using the UI for date type params
IMPROVED
- logic for reducing/simplifying Batch Parameter paths when viewed in the Batch Recipe Editor or Batch Recipe Monitor
- recording trace information during a loopback if a phase has resource allocations
ADDED
- Logic to prevent renaming/deleting of certain built-in enums
- pre-allocation phase to work with the new data type of Material_In
- Unit_Quantity parameter to the unit procedure phase and consider its value during allocation. This solves the problem of receiving messages that units don't have enough capacity messages
- logic to check if stepNames in unitAssignments are valid stepNames in the recipe when creating a BatchQueueEntry using the "addEntry" script method
- more recipe validation for the preallocate resources phase to prevent illegal use.
- A message will now be displayed on the Batch Unit Manager component when a process cell cannot be determined, due to multiple process cells, or if there are no process cells defined in the environment
- equipmentFilter property to BatchList and BatchSelector components.
- BOM capability for recipes and batches sub-parameter viewing/editing capabilities to Batch components (Batch Phase Manager, Batch List, Batch Recipe Editor, Batch Controller, Batch Recipe Monitor)
- ability to add an ""empty"" option to enum definitions
- missing script documentation for enum script methods
- getDefinition(String name) and getDefinitionLink(String name) script methods for more convenience
- new data types for material and supplemental allocations and T&T integration "batchType" component property to control which ""batchType"" is returned in the BatchSelector list (Active or Executed)
- "maxResults" component property to limit number of batches that can be displayed in the BatchSelector
- "beginDateTime" component property to limit BatchSelector list to only include Executed batches that have a recently modified timestamp after the specified date/time
- "endDateTime" component property to limit BatchSelector list to only include Executed batches that have a recently modified timestamp before the specified date/time
- "placeholderText" component property to control the text displayed in the BatchSelector when the input field is empty "inputLabel" component property to specify the label text for the BatchSelector input field
- "system.mes.batch.queue.getExecutedBatchIDs" script method for getting a list of Batch IDs for batches that have already been executed and removed from the Batch Queue
- "viewMode" property to BatchList component which is used to determine which mode to run the component in and determines which type of batches to display (Local or Remote)
- processCell dropdown to BatchList edit view to specify what processCell the batch should be created for
- ability to create Batches from an Enterprise server to be synced down to a Site server
- logic to show errors next to required fields if they are blank when saving on the BatchListEditView
- Logic to remember pageSize selection in the BatchList component More default pageSize options to MESTreeTable
- Quantity check when Bypass_Quantity_Check is set to False Min/MaxValue values to getBatchBOM and getRecipeBOM script methods
- Logic to enforce min/max value when setting values using setBatchBOM
UPDATED
- to require Record_Trace to be set to True if a lot could not be assigned on the first attempt during preallocation default valueSource for Material_In/Out and Supplemental_Equipment sub-parameters
system.mes.batch.queue.setBatchBOM script method to throw an exception when attempting to change the value of param(s) that do not have a value source of "Recipe" or "Recipe and Execution"
setBatchBOM script method to ignore "None" values so current values are not overwritten Lot_Equipment and Lot_Manifest sub-params to allow freeform entry the starting width of Name & Value columns to 500px for Param Settings tables in BatchList and Recipe Editor components Made it so OEE Material Manager is available to be used as a perspective component as long as one of OEE, Batch, or the Track&Trace modules is installed Made it so the "Production Settings" view of the OEE Material Manager cannot be accessed if the OEE module is not installed "Message too large" link to a permalink
Batch Recipe Monitor side panel so parameter names and their values are more easily distinguishable Renamed getEnumOptionOrdinal script method to getOptionOrdinal to match other enum script methods
BatchSelector
- perspective component to use Autocomplete Re-enabled ability to add multiple process cells
REMOVED
- "createEntry" script method, the "addEntry" method should be used instead
CHANGED
- BatchPhasterManager to always show the "expand" button for Phase Classes in the list Batch|Trace
FIXED
- lot availability status not being updated when zero lot quantity remains when using the recordOperation and modifyOperation script functions
- issue preventing changing of the lot status once initially set using the recordOperation or modifyOperation script functions
- Prevent errors when auto creating supplemental equipment or manifests with system.mes.trace.recordOperation Added fix to return preallocated resources when completing an Equipment step before using any of the preallocated resources
UPDATED
- to allow consuming lots with zero or negative quantity when using the recordOperation or modifyOperation script functions
- autoCreateLot to a default value to True when using the recordOperation or modifyOperation script functions
OEE/Downtime
FIXED
- Issue preventing labels from displaying on MES Schedule View fields
- OEE/Downtime|Perspective|Production
ADDED
- confirmation dialog to prevent loss of unsaved changes to perspective components
- Perspective
FIXED
- SPC Charts no longer mess up the MES Object Selector styling
- Editing an inherited default setpoint definition on child equipment no longer damages the parent's definition
- Inherited default setpoint definitions can no longer have their names altered on child equipment
NEW FEATURE
- The SCO Variance Viewer has been implemented for Perspective
- The Settings and Changeover Changelog Viewer has been implemented for Perspective
- The Perspective Equipment Manager now handles default value assignments for SCO Setpoint definitions, similarly to the Vision Recipe Tree Editor
- The Perspective Equipment Manager now handles SCO setpoint security definitions, similarly to the Vision Recipe Tree Editor
- The Perspective Equipment Manager has a new "requireChangeNote" property. Setting this to true will require users to enter a change note (which will appear as an input field) in the SCO Setpoint security editing view as well as the SCO Setpoint definition editing view. An invalid change note will prevent saving. The SCO Setpoint definition editing view will only ask for a Change Note if the default-value field is altered
- The SCO (Master/Descendant Recipe) Tree Editor has been implemented
IMPROVEMENT
- Added task routing functionality to Gateway scoped MES script functions
- Perspective|SPC
FIXED
- Chart shows attribute and units on Y-Axis for C, NP, P, U, Median, XbarR, XbarS, Histogram, Box and Whisker, Process Cap, Process Perform, PCP, and Moving Range charts
- date row is no longer shown when showTable is false
- Pareto chart reorders data after taking weight into account
- look of Pareto chart, responsiveness to changing propertie
- All charts have had flickering reduction, especially when it comes to automatically adding new data points
- User input control limit value does not clear if entered before changing date on Edit Control Limits for Perspective Charts
- SPC Charts no longer throw an error when pointed to a non-existent definition in Ignition designer
ADDED
- Property to toggle showing units on Y-Axis label for C, NP, P, U, Median, XbarR, XbarS, Histogram, Box and Whisker, Process Cap, Process Perform, PCP, and Moving Range charts
- New styles for Perspective SPC Charts
- XBar and XDBar rows to the table of XBar Chart
REMOVED
- Scroll bar when table is hidden, showing entire chart at once for C, NP, P, U, Median, XbarR, XbarS, Histogram, Box and Whisker, Process Cap, Process Perform, PCP, and Moving Range charts
- Properties on SPC Charts that did nothing
- Production
IMPROVEMENT
- Made the Perspective Equipment Manager function in a task routing enviornment
- Recipe
UPDATED
- All Perspective SCO Components now have a name starting with the word "Settings."
SPC
ADDED
- All Perspective charts format their data
FIXED
- The SPC Individual Chart will no longer spawn Gateway warnings when it is open
- Labels for Individual charts now correctly state Individual and XBar
Known Issues:
- Unable to reference phase parameters inside an operation that is prior to the unit procedure/operation that the phase parameter is in.