How to Prevent Executing an Action Without Filling Required Parameters ?

Gemini gave me some logic you might could use here:

1. Add a third option to your dropdown list called --- PLEASE SELECT AN OPTION ---.

2. Set this as the Default Value.

3. Use a Condition Step  to check if the selection equals that specific string.

4. If it does, the playbook loops back to the manual task until they pick one of your two "real" options.

Thanks for reply but its not appliable, since there is no infinite loop, no loop breaking box.

Did you ever find a solution for this? This is the closest thread I can find which describes similar problems to ours. 

Analysts can seemingly close a case at any point without having completed necessary actions. Although this is a training issue of sorts, Secops doesn’t make it easy to enforce a field completion before closure. 

We previously had IBM SOAR/Resilient to tackle this sort of thing with a simple condition which would prompt the user to complete fields before allowing closure of a case.

Thanks

Hello Chris,

Sadly no, when I'm working on this I found many things possible but not this :)
For example by playing with network packages : 

• you can create empty playbooks
• you can create a action box in IDE which has mandatory fields marked while you are implementing, and asked for you to fulfill in IDE but you can bypass filling mandatory fields so that it has to pass to Analysts (but no its still choosing a default first option)
• you can create a action box in playbook without filling any field and save it, which is normally shows as red and doesn't allow you to save playbook(but no it still chooses the first available option in Live

So basically, you as a developer, have to fill these fields, definitely, cant run away, but analysts can :D They can just hit execute button without any worry.