|
Http Verb |
POST |
|---|---|
|
Url |
/work-orders/r1/operations/{operationId}/assets/batch |
|
Permissions required |
Permissions:
|
|
Personally Identifiable Information (PII) |
No |
|
Sensitive Information |
No |
|
Last Modified Version |
r1 |
|
Released since |
2026 W3 (FSM 24.0) |
|
Deprecated since |
|
|
Removed since |
|
|
Tech Tags |
|
Business Logic
This API associates a set of existing assets to a work order operation. If any check fails, an error is thrown and the execution stops.
Validations:
-
Asset has to be set
-
Work Order checks:
-
Work Order exists and must be in one of following status: OPEN, RELEASED, DRAFT
-
WO Operation exists and must be in one of following status: OPEN, RELEASED, DRAFT
-
Uniqueness checks for the couple WO Operation and Asset
-
The API processes records in batches of 300 at a time.
Path Parameters
|
Field |
Note |
|---|---|
|
operationId |
|
Query String Parameters
None
Header Parameters
Default.
Request Body
Array formed by:
|
Field |
Validations |
Note |
|---|---|---|
|
assetId |
Not Null |
|
|
active |
Not Null |
default true |
Response documentation
Response payload fields
|
Field |
Note |
|---|---|
|
List<id> |
Ids of the to created work order operation asset relations |
Response error codes
BASE_0001, BASE_0003, BASE_0006, WORKORDERS_051, WORKORDERS_052, WORKORDERS_053, WORKORDERS_054, WORKORDERS_055