ActionSessionDate
Represents the specific dates on which a preventive action session is scheduled to take place.
Used to define when the corresponding ActionSession
will be carried out, ensuring proper planning and tracking of safety-related activities.
- Version
- 2.0.0
- OpenAPI version
- 3.0.0
Authentication
Section titled “ Authentication ”OAuth2
Section titled “OAuth2 ”Security scheme type: oauth2
Flow type: password
Token URL: https://auth.4hse.com/realms/4hse/protocol/openid-connect/token
Flow type: refreshToken
Token URL: https://auth.4hse.com/realms/4hse/protocol/openid-connect/token
AccessToken
Section titled “AccessToken ”Security scheme type: apiKey
Query parameter name: access-token
Operations
Section titled “Operations” POST /v2/action-session-date/index
Returns a paginated and filterable list of action session dates. Use POST to allow complex filters via JSON payload.
Authorizations
Section titled “Authorizations ”Request Body
Section titled “Request Body ”Parameters for searching action session dates
object
object
Additional data
The field of the model to sort the list for, use a minus to revert the sort. Es -name is to require the sort in reverse order
The field establishes whether to also include historized elements that are no longer active in the results. If you leave this parameter empty the response returns only actual entries.
Example
{ "filter": { "date_begin": "2024-01-01", "date_end": "2024-12-31" }, "per-page": 10, "page": 1, "sort": "date_begin"}
Responses
Section titled “ Responses ”List of action session dates
object
Additional data
Example
{ "action_session_date_id": "date-1", "action_session_id": "sess-1", "date_begin": "2024-01-10T09:00:00Z", "date_end": "2024-01-10T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
Headers
Section titled “Headers ”Current page
Total number of pages
Number of items per page
Total number of items
create
Section titled “create” POST /v2/action-session-date/create
Create a new action session date by providing the required details.
Authorizations
Section titled “Authorizations ”Request Body required
Section titled “Request Body required ”Action session date object to be created
object
Additional data
Example
{ "action_session_id": "sess-1", "date_begin": "2024-03-01T09:00:00Z", "date_end": "2024-03-01T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
Responses
Section titled “ Responses ”Action session date created successfully
object
Additional data
Example
{ "action_session_date_id": "date-3", "action_session_id": "sess-1", "date_begin": "2024-03-01T09:00:00Z", "date_end": "2024-03-01T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
GET /v2/action-session-date/view/{id}
Retrieve an action session date by its unique ID.
Authorizations
Section titled “Authorizations ”Path Parameters
Section titled “Path Parameters ”ID of the action session date to retrieve
Responses
Section titled “ Responses ”Action session date found
object
Additional data
Example
{ "action_session_date_id": "date-1", "action_session_id": "sess-1", "date_begin": "2024-01-10T09:00:00Z", "date_end": "2024-01-10T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
Action session date not found
delete
Section titled “delete” DELETE /v2/action-session-date/delete/{id}
Delete an action session date by its unique ID. If force=true, all related entities will also be deleted.
Authorizations
Section titled “Authorizations ”Path Parameters
Section titled “Path Parameters ”ID of the action session date to delete
Query Parameters
Section titled “Query Parameters ”Force the deletion of the entity and all related entities
Responses
Section titled “ Responses ”Action session date deleted successfully
If force=false, the operation is interrupted and the list of connected entities that will be deleted in case of confirmation (force=true) is returned
update
Section titled “update” PUT /v2/action-session-date/update/{id}
Update an existing action session date by its unique ID.
Authorizations
Section titled “Authorizations ”Path Parameters
Section titled “Path Parameters ”ID of the action session date to update
Request Body required
Section titled “Request Body required ”Action session date object with updated data
object
Additional data
Example
{ "date_begin": "2024-04-01T09:00:00Z", "date_end": "2024-04-01T17:00:00Z"}
Responses
Section titled “ Responses ”Action session date updated successfully
object
Additional data
Example
{ "action_session_date_id": "date-1", "action_session_id": "sess-1", "date_begin": "2024-04-01T09:00:00Z", "date_end": "2024-04-01T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
Action session date not found