4.83.0 SPx

Improved:

• batch.queue.getParameterValue(...) and getParameterValueAsString(..) script functions have been updated to not require a Batch to be running to get the value of a parameter

For parameters with a Calculation Expression, if the batch is not active, the last calculated value is returned (if available); otherwise, the Calculation Expression is returned.

• Updated batch.queue.* script methods to accept either a BatchQueueEntry object or a Batch ID, where possible.
  
  

  batchID

  A batch ID is a unique identifier assigned to a batch within the Sepasoft MES (Manufacturing Execution System). It is used to reference and manage specific batches during their lifecycle in the batch queue. The batch ID is crucial for retrieving associated control recipes and logic objects, as well as for tracking the status and parameters of the batch.

  For example, in the function system.mes.batch.queue.getBatchObjects(batchID), the batch ID is passed as a parameter to retrieve the control recipe and logic objects associated with that specific batch.
  

• Implemented logic that automatically inserts a Start step into a BatchMasterLogic when addStep is invoked before one exists, and links it to the newly added step, streamlining the creation of templates and recipes through scripting.
  
  
• Changed behavior of the Back button in the Batch Recipe Editor component Settings view to go back to the recipe/template list if the item is a template and doesn't have a unit class assigned

Fixed:

• Fixed an incorrect/misleading error being thrown in scripting when trying to add a link between two steps that are already linked.

• Fixed an incorrect/misleading error being thrown in scripting when trying to getParameterValue for a parameter that does not exist

• Improved error messaging in scripting when trying to save a template or recipe that has sublogic steps that did not have a valid logic reference set on them
  
  
• Fixed issue in BatchRecipeEditor where the diagram would not be centered on load if the item was a template and didn't have a unit class assigned

Added:

• Added logic to prevent saving a BatchMasterLogic object that does not have a Start step
  
  
• Added logic to prevent removing the Start step from a BatchMasterLogic using the removeStep() method
  
  
• Added logic to prevent adding more than one Start step to a BatchMasterLogic object
  
  
• Added restrictions to BatchMasterLogic#setLogicType(String) method to prevent changing the logic type under certain conditions:
  • Prevent changing the logic type to UNKNOWN
  • Prevent changing the logic type to Procedure
  • Prevent changing the logic type if logic item is a Procedure logic
  • Prevent changing the logic type if logic item has parent logic (e.g., Unit Procedure logic, Operation logic, or Operation Template)
  • Prevent changing the logic type from template to non-template or vice versa
  • Prevent changing the logic type if sublogic steps are present or child logics have been created from the logic item
    
    
• Added restrictions to BatchMasterLogic#addStep method to prevent adding a step under certain conditions:
  • Prevent adding a step if the logic type is UNKNOWN
  • Prevent adding a step if the phase type is UNKNOWN
  • Prevent adding a step if the step order is negative
  • Prevent adding a sublogic step of the same type, e.g., UP -> UP or Op -> Op
  • Prevent adding a sublogic step of a higher type, e.g., trying to add a UP step to Operation logic
  • Prevent adding a sublogic step of a lower type, e.g., trying to add an Operation step to Procedure logic

 Added new convenience scripting methods:

• BatchMasterLogic#addStep(String name, MESObjectLink phaseLink) - add a step with the specified name of phaseLink type at the next available stepOrder
• BatchMasterLogic#addStep(MESObjectLink phaseLink) - add a step with a default name ("step") of phaseLink type at the next available stepOrder
• AbstractBatchLogicStepsProperty#setTransitionExpression(String expression) - Set the Transition_Expression parameter on a Transition step with the specified expression
• AbstractBatchLogicStepsProperty#getTransitionExpression() - Get the Transition_Expression for a Transition step
• AbstractBatchLogicStepsProperty#getPhaseType() - Get the logic phase type for a step

 Other methods that do the same:

• getLogicPhaseType()
• AbstractBatchLogicStepsProperty#getOrder() - Get the stepOrder for a step
• Other methods that do the same:
• getLogicOrder()
• getStepOrder()

Fixed - Script methods getBatchEBR, getBatchBOM, and getRecipeBOM now return values using their actual data types when possible, instead of inconsistent types.

Improved - Phase start logic now records the initial parameter values to the EBR when a new phase execution begins.

Improved - Updated several eSignature parameters to record all history so they appear in the EBR when an eSignature phase starts as expected.

Fixed - MESIconButton no longer shows a title tooltip when it should not.

Fixed - Resolved a deadlock caused by lock-order inversion when setting the Batch Recipe State.

Improved - UserMessage and equipment-type phases no longer record MESSAGE_ACK_* parameters to the EBR when message acknowledgement is not required.

Fixed - Convert large numbers to String to prevent precision loss when displaying very large numbers in the EBR Viewer.

Improved - Set the Batch List default sort order to Priority and Batch ID.

Improved - The EBR now records Command None entries for better visibility into how the batch engine issues and handles commands.

Fixed - Null or empty RecipeExecutionState values no longer default incorrectly to an ordinal value instead of a UUID.

Fixed - Null or empty State values now appear in the EBR as Unknown instead of UNKNOWN.

Fixed - Null or empty Command values now appear in the EBR as None instead of NONE.

FIXED:

• Parameter paths in calculation expressions were being improperly encoded when parameter names are named similarly. This has been fixed.
  
  
• When editing a previously saved Template that is missing a Unit Class, clicking the Save button appeared to do nothing. This has been fixed.

ADDED:

• Validation for Calculation Expressions in Batch Recipes/Templates (BatchRecipeEditor and scripting).
  
  
• Recipes with Calculation Expression errors will no longer be valid for Execution until the Calculation Expression errors are resolved.
  
  
• Inline validation for Calculation Expressions in the BatchRecipeEditor component.
  
  
• Added a "Save with errors" toggle that will allow users to still save the Parameter Settings when there is a known Calculation Expression error.

IMPROVED:

• Improved logic for parsing Calculation Expressions to find "param(...)" calls to be more robust

Fixed - Synchronize Logic parameters with templates

Fixed - Prevent an error removing extra sub-parameters from logic objects when a unit procedure or operation comes from a template

Fixed - The SCO CSV export system no longer includes child equipment assignments that do not actually exist.

Improvement - The Perspective SCO Tree Editor now accepts SCO CSV files (in addition to XML).

Feature - Scripting functions system.recipe.exportRecipeXML and system.recipe.importRecipeXML have been added as counterparts to the legacy CSV versions.