OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

This epic includes the tasks that are needed to design and implement a consistent, flexible, and user-friendly interface for executing automation actions within the ACM UI. This includes rendering the playbook details, capturing user input, validating the selection context, and presenting job progress and results — whether the action is triggered manually, scheduled, or event-driven (EDA).

Why is this important?

We want to bridge Between the resources selection and execution.
We need to allow several flows of executions had-hoc , scheduled, or generate EDA rules. 

We wnat the integration with AAP to be seamless. The Admins and users of ACM should not be considered as Ansible developer and for them we need to simplify the AAP pages with the minimal information that they need.

AAP has a proved UI that we can leverage and create a scaleable solution based on it.

Scenarios

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)