Skip to content

System actions

ModuleCatalogs
Suggested profileAdministration
PermissionSTAFF_TYPES: WRITE / ADMIN
StatusValidated

Objective

Define the special actions of the system (SHOW_LOGS, AGENDA_PARAMETERS, BLOCKING_REASONS, etc.) and their availability per HCP type. The route is /manage-hcpsTypes/hcpTypes/actions.

How the screen is organized

Table with the system actions: key, description, status. Additionally, from the Staff types tab, it is configured which actions are allowed for each type.

Available actions

  • Create action: high dialog with key, description and status.
  • Edit action: adjust description or status.
  • Activate or deactivate: the action stops being available in the flows.
  • Delete: requires STAFF_TYPES: ADMIN.

Permissions

  • STAFF_TYPES: WRITE to create and edit.
  • STAFF_TYPES: ADMIN to delete.

Before starting

  • Know the action keys that the system uses (for example, AGENDA_PARAMETERS, BLOCKING_REASONS, AGENDA_BRANCHES, CASH_BOX_PARAMETERS, SHOW_LOGS).
  • Have the HCP types defined.

Step by step - Assign actions to an HCP type

  1. Enter the Staff types and actions module.
  2. In the Types tab, locate the type.
  3. Click the Configure actions icon (side drawer).
  4. In the drawer, check the actions that the HCP type will have available.
  5. Confirm.

Expected result

  • The actions are assigned to the type.
  • When a user with that HCP type logs in, the actions are available.
  • The system shows a success message.

Pending: add screenshot of catalogos-acciones-01-drawer.png.

Common errors

SituationWhat to do
The action does not apply to the userConfirm that the HCP type of the user has the action assigned.
The action does not appear in the sidebar or menusVerify that it is active and that the user's HCP type has it.

Suggested permissions

  • STAFF_TYPES: WRITE.

Operational recommendations

  • Document internally which actions are necessary for each HCP type.
  • Change actions carefully; if you deactivate a used action, users will lose access to the related functionality.

Relation with other modules

  • Staff types: actions are assigned per type.
  • Users: the user's HCP type determines which actions they have available.
  • Specific modules: each action is validated in the corresponding module (Schedule, Cash box, etc.).