|
Http Verb |
GET |
|---|---|
|
Url |
/work-orders/r1/work-orders/calculated-operation-center |
|
Permissions required |
|
|
Personally Identifiable Information (PII) |
No |
|
Sensitive Information |
No |
|
Last Modified Version |
r1 |
|
Released since |
2024 W3 (FSM 18.0) |
|
Deprecated since |
|
|
Removed since |
|
|
Tech Tags |
PAGINATION |
Business Logic
This API returns the id of the operation center deducted from the input information.
The deduction is performed by following the order of the deduction criteria assigned to a work order type, to see which one are enabled and its order you can call this api: GET /work-orders/r1/work-orders/{typeId}/operation-center-assignement-criteria
A short recap of the deductions:
-
From Work Order Type: this deduction will will deduce the operation center from the relations between asset and operation center
-
From Asset: this deduction will deduce the operation center from the asset related to the address
-
From Territory: this deduction will deduce the operation center from the operation center composition, that involves the microclusters
-
From Custom: this deduction can be implemented as custom
Query String Parameters
Filter ℹ️
|
Field |
Validations |
Note |
|---|---|---|
|
workOrderTypeId |
|
Collection of Ids |
|
addressId |
|
Collection of Ids |
|
referenceDate |
Reference date refers to the date that will be used as range → start date, end date in searching the validity periods associated with structures |
Order ℹ️
Default Order
Possible order values
No other ordering options available.
Page ℹ️
Default.
Fields ℹ️
Default.
Header Parameters
Default.
Response documentation
Response payload fields
|
Field |
Note |
|---|---|
|
operationCenterId |
|
Response error codes