...
| Page Properties |
|---|
Link | https://ehealthmisapi1.docs.apiary.io/#reference/public.-medical-service-provider-integration-layer/employees/deactivate-employee | Посилання на Apiary або Swagger | Resource | /api/employees/{{id}}/actions/deactivate | Посилання на ресурс, наприклад: /api/persons/create | Scope | employee:deactivate | Scope для доступу | Components | Employees, Legal Entity, Divisions | Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription | Microservices | API paragraph not found | Перелік мікросервісів, які використовує метод API, наприклад: Auth, ABAC | Protocol type | REST | Тип протоколу, який використовується запитом, наприклад: SOAP | REST | Request type | PATCH | Тип запиту API, наприклад: GET, POST, PATCH… | Sync/Async | Sync | Метод є синхронним чи асинхронним? |
|
Logic
...
Preconditions
API paragraph not found
...
If an employee moved to a new legal entity during the reorganization, his old record (with the same speciality_officio) with the declaration, remain active in the reorganized legal entity.
The owner of the legal successor legal entity can dismiss this employee if necessary. See more details about reorganization process.
If employee id relates to $.related_legal_entities.merged_from_id legal entity OWNER can dismiss this employee
in case no employees were found return 404 with msg (Employee not found)
...