How Actions are Grouped and Assigned (Agents)

Technical Grouping Controls

  • Group Actions by – Detected Items are grouped based on the fields defined in this configuration option. The Group Actions by setting controls how Detected Items are aggregated into a single Action. The list of available fields is derived from the fields defined in the Group By configuration option in the Definition step.

  • Keep Top Actions – Only Detected Items with the highest potential impact, based on the first impact defined in the Impact Definition are considered. There is a system-enforced maximum limit of 500 Actions. If the configured value exceeds this limit, it is automatically reset to 500. The default limit is 20 Actions.

  • Ranking Based on Impact – When Actions are limited, the system retains the Actions with the highest impact, allowing users to focus on the most critical issues first. The resulting Actions are stored in the Actions Datamart Table. Detected Items that do not result in an Action being created are removed.

Action Assignment

Action Assignment is performed by the Assignment Fields in the Action Definition StepAssign to (fallback assignee) and Assign to per Dimension (dimension‑driven routing), including how mappings are derived from Definition dimensions and constrained by Group Actions by.

Role‑based Permissions on Actions and Action Plans

Who can create, view, edit Actions and Action Plans is depending on the Agent Business Roles.