Issue #3606887: Add Retention, Execution and Versions operations to the workflow list

Fixes #3606887.

Problem

A workflow's Retention, Execution and Versions pages can only be reached by typing their path. Their tabs declare the workflow canonical page as base route, but that page is served by the modeler view (it renders no local tasks), so the tabs never appear there; and the model list has no operation linking to those pages.

Fix

orchestra_ui's hook_entity_operation adds Retention, Execution and Versions operations to each workflow on the model list, next to the existing Start. Ordering is improved: Start (the primary runtime action) sits just under Edit, and the three configuration pages group together at the end, before Delete. Core access-checks each operation route, so a user without administer orchestra sees only the operations they may use.

Test

The operations kernel test is extended (renamed WorkflowOperationsTest) to assert each operation is present and routed to its page with the workflow as its route parameter.

Merge request reports

Loading