You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
External API has the ability to get all data using /api/subjects, /api/encounters etc. However, if we have data for an entity type that is voided, there is no way to assign the API user access to this endpoint, and it fails with a 403. The only way we can do this now is by adding privileges manually to the screen.
With this story, we fix it by showing voided entities in the system on the "Permissions" tab on "User Group" screen
Acceptance Criteria
There is a "Show Deleted" switch on the "Permissions" tab to show/hide deleted entity types. This is by default switched off
Do not add permissions by default for voided entity types. Add them if they are explicitly added on the screen
Add permissions when explicitly given from the UI
The text was updated successfully, but these errors were encountered:
Motivation
External API has the ability to get all data using /api/subjects, /api/encounters etc. However, if we have data for an entity type that is voided, there is no way to assign the API user access to this endpoint, and it fails with a 403. The only way we can do this now is by adding privileges manually to the screen.
With this story, we fix it by showing voided entities in the system on the "Permissions" tab on "User Group" screen
Acceptance Criteria
The text was updated successfully, but these errors were encountered: