Creates an order using an order connector created within Operations1. See in our guide section how to configure an Operations1 order connector.
The request body needs to contain all properties defined in the order connector configuration. You will find an example payload in the specific order connector configuration page in Operations1. If the order connector creation is successful, the response will contain the created order object with a status code of 201. If something is incorrect with the payload you will get an error with status code 422 with a more specific error code and message explaining the problem.
We are using the provided data to find fitting class characteristics. The provided values need to match the identification properties of the class characteristics. The found class characteristics are then used to find documents with matching class characteristics. These documents will be attached to the created order. The order is automatically started. If no document is found, the order creation will fail with a 422 error. If multiple documents are found, all documents will be attached to the order.
To assign groups to the created order, configure the responsibleGroups property in the order connector configuration (e.g., "responsibleGroups": "assigned-groups"). During execution, provide this key in the request body with an array of group external IDs as the value (e.g., "assigned-groups": ["Assembly Team", "Quality Control Group"]). The external IDs corresponding to the groups will be assigned to the created order. Ensure all provided group external IDs exist in the system - any non-existent group IDs will be ignored during order creation.