Problem Statement
~~~~
We have developed a playbook and created multiple tags within the tags section of the template. The "Prompt on Launch" option has been enabled. However, when launching the template, all tags are selected by default.
~~~~

Expected Solution
~~~~
We expect that the tags section should be empty by default when the template is launched, and no tag should be pre-selected.
Our goal is to require the admin to consciously select the relevant tag from the dropdown list each time.
The current behavior poses a risk: if a team member mistakenly clicks "Next" multiple times, the playbook will execute all tasks at once, which is not desired.

Ideally, the system should prompt the user to select the intended tags before execution. This will ensure that admins are attentive and deliberate in their selection, fully understanding the implications of the tags they choose.

If the tag field is left blank initially and the admin is required to select the appropriate tag from the dropdown, we can mitigate the risk of accidentally running the entire playbook. We also want to avoid a scenario where the admin manually types the tag name during launch.
~~~~

Business Justification

Requiring manual selection of tags at runtime enhances operational safety and governance by:
1. Preventing accidental full execution of the playbook due to default tag selection.
2. Reducing human error, ensuring admins consciously select the correct tag.
3. Enforcing process control, aligning with best practices for change management and infrastructure automation.
4. Minimizing risk of service impact, especially in environments where playbooks include critical tasks.

By making the tag field blank by default and requiring explicit selection, we increase reliability and accountability in playbook execution.