Hi Mezam,
That's a common question, Rundeck doesn't work in that way. If I understand your use case, you want to put some manual values in the middle of execution and depending on that values the script starts a conditional behavior.
In that case, the best approach is to define a behavior using the
Ruleset Strategy (only for Process Automation, formerly "Rundeck Enterprise"), but always the behavior is pre-defined in the Workflow.
On Rundeck OSS you can put all the workflow logic in a script step depending on some job options (if... then... else), but like Ruleset Strategy, the behavior is explicitly defined in your workflow.
A good approach in your use case could be to split your script into two jobs: the first one that saves the output in a file and the second one that collects those results and ask the user to execute an action from a job option.
Hope it helps!