Policy workflow usage statistics and alerts

[anvabr]

Problem description

At present the SLA parameters of the usage (a.k.a. 'execution') of a published policy is completely opaque to its users. No parameters/metrics are collected and/or reported on. This denies the possibility of estimating/organising workflow SLAs around execution milestones (e.g. 'approvals') as users have no way of knowing when/how fast these stages usually take.

Requirements

1. Add a usage analytics/reporting interface which can show per-policy workflow user actions with average duration of periods between them. Averages should be calculated on the basis of previous executions ideally excluding outliers (rare events where time was by orders of magnitude longer/shorter than the rest).
2. For each user-interactive workflow step during the policy execution add a UI element showing average time this step has been taking, and the passed duration of the current period (e.g. when the document is 'waiting' for approval action by the user). Highlight the latter in red if/when it is longer than the average
3. In the analytics UI (p.1 above) allow administrators to configure user notifications for time periods above a certain threshold.

Definition of done

• Usage analytics and alerting functionality is implemented as described above
• Documentation is updated accordingly

Acceptance criteria

Policy workflows execution history is automatically analyzed and usage stats are displayed to users, which they can use to plan/prioritise their actions on the basis of urgency.

[dubgeis]

This looks good Andrey, from an implementation perspective since policies are defined in blocks, this may be best surfaced on a schema by schema basis or in groups like modules or stakeholder interactions.