Sepasoft MES Module Suite
system.mes.workorder.getOperationsResponsesForWorkOrderUUID(workOrderUUID, beginDate, endDate)
Get a Work Order's Operations Responses between the given dates. This will typically be faster than getOperationsResponsesForWorkOrderName().
|
Gateway: When running this script in a gateway context (Tag Change Event script, Gateway Event script, etc.), it requires you to provide beginDate and endDate values. Client: When running this script in a client context, the user can pass 'None' for the dates, and it will return all of the operations requests. |
Syntax
system.mes.workorder.getOperationsResponsesForWorkOrderUUID(workOrderUUID, beginDate, endDate)
- Parameters
String workOrderUUID - The UUID of the Work Order to return the associated Operations Responses for.
Date beginDate - Date (inclusive) when the Operations Request for this Work Order was executed. Pass in 'None' to use the default date [1 Jan, 1970 00:00:00].
Date endDate - Date (inclusive) when the Operations Request for this Work Order finished executing. Pass in 'None' to use the default date [1 Jan, 2200 00:00:00].
- Returns
MESList<MESObjectLink> opsRspLinks - A list of MESObjectLinks that each have a reference to an MESOperationsResponse object.
- Scope
All
Python |
#This code will print the Operations Responses associated with a Work Order opsRspLinks = system.mes.workorder.getOperationsResponsesForWorkOrderUUID('72b408bf-aaf4-420f-9ec5-4aa7fabbff83', None, None) for operationsResponseLink in opsRspLinks: print(operationsResponseLink.getMESObject()) |
Output
Python |
OperationsResponse (fc00c9c3-d5a4-4e62-be2d-f4eb8eae520d, mtrl-Nuts Unlimited:MES-1767:Area-1767:Line-1767, 0 parents, 0 children, 0 custom properties, 1 complex properties) |
Sepasoft MES Module Suite