|
Http Verb |
POST |
|---|---|
|
Url |
/work-orders/permits/r1/required |
|
Permissions required |
Permits View/Edit Permission:
|
|
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 logically insert a required permit
It enforces these rules before insertion. If any check fails, it returns a domain validation error.
-
Field validation checks:
-
Code not null and max 255 characters
-
Institute max 255 characters
-
Description required multi-language values
-
-
Validates that the work order and optional operation exist and are in valid states.
Also checks that the work order is not in a bundle. -
Work order editability – Rejects the request if:
-
Required permit is blocker AND work order status is not OPEN, RELEASED, LOCKED, PARTIALLY_ACCOUNTED, or TO_RESCHEDULE
OR -
Required permit is not blocker AND work order status is CLOSED, CANCELLED, ALIGNED, or TECHNICALLY_CLOSED
-
-
If work order operation is assigned, checks if permit is blocker AND work order operation status is not OPEN, SCHEDULABLE, LOCKED, or TO_RESCHEDULE
-
Uniqueness check
Path Parameters
None
Query String Parameters
None
Header Parameters
Default.
Request Body
|
Field |
Validations |
Note |
|---|---|---|
|
code |
Not null |
|
|
description |
|
|
|
typeId |
Not null and must exist |
Related to permit type table |
|
workOrderId |
Not null and must exist |
Related to work order header table |
|
workOrderOperationId |
Optional, must exists if setted |
Related to work order operation table |
|
institute |
|
|
|
blocker |
|
|
|
|
|
|
|
|
|
|
Response documentation
Response payload fields
|
Field |
Note |
|---|---|
|
id |
Id referred to created required permit |
Response error codes
BASE_0001, BASE_0003, BASE_0006, BASE_0007, PERMIT_0006, PERMIT_0015, PERMIT_0016, PERMIT_0017, PERMIT_0018, PERMIT_0030