-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Similar to CAM-9395
AT
- Introduce new historic process resource with permission READ
- The historic process instance authorizations are enforced for the following queries
- Historic Process Instance
- Historic Activity Instance
- Historic Task
- Historic Variable & Detail
- Identity Link Log
- Historic Incident
- Job Log
- External Task Log
- User Operation Log
- History Cleanup
- When a user creates an authorization on the historic process instance resource and enters a resource id of an existing historic process instance, the root process instance id and if already present the removal time is set to the authorization
- The batch operation "Set Removal Time for Processes" takes historic process instance authorizations into account
- The cleanup execution takes historic process instance authorizations into account
- The legacy history cleanup mechanism (end time based) does not take historic process instance authorizations into account
- When enableHistoricInstancePermissions is disabled, ...
- and a user proactively creates a historic process instance authorization, the root process instance id/removal time is added if available
- the extra SQL for queries is skipped
- Historic process instance authorizations are removed when the historic process instance is removed via API
- In Admin, I can grant the newly introduced authorizations
- I can read docs