Overview

This node interacts with the BEAS Service Layer API to update a record in the Work Order Routing resource using a PATCH request. It is useful for scenarios where you need to modify specific fields of an existing work order routing entry in BEAS, such as updating routing details or statuses without replacing the entire record.

Use Case Examples

1. Updating the routing sequence or operation details of a specific work order routing entry by providing the document entry and line number along with the patch data in JSON format.
2. Modifying scheduling or resource allocation information for a work order routing item.

Output

JSON

• json - The JSON response from the BEAS Service Layer API after the PATCH operation, containing the updated work order routing record or relevant status information.

Dependencies

• BEAS Service Layer API with credentials including URL and service password

Troubleshooting

• Ensure the 'docEntry' and 'lineNumber' parameters are correctly provided and correspond to an existing work order routing record; otherwise, the PATCH request will fail.
• The 'patchBody' must be valid JSON; invalid JSON will cause an error indicating 'Invalid JSON in patch body parameter'.
• A failure to obtain a session cookie from the BEAS Service Layer login will result in a 'Failed to get session cookie' error, indicating authentication issues.
• If the API endpoint or resource is not supported, an error 'Operation Patch not supported' or 'Resource not supported' will be thrown.