Hey ​@nelson_prenga ,

Can you provide an example that you are trying to solve?

​@nelson_prenga ,

Thanks, now it makes sense. Unfortunately, the only way to solve this right now is to create several conditional branches in the playbook, where each branch will correspond to a different value in the list. 

Or to make a custom action that will take this input as a string, like you’ve tried already.

The platform has a list of predefined close reasons, this list is managed by the Admin of the platform to ensure consistency (e.g. dashboards metrics kpi)

(sorry for the oversized image, it wont let me resize)

Allowing a user to enter text here would conflict with this workflow.

As ​@ylandovskyy  states, it’s best to have a condition that takes 1-2 paths each to a different close Action that is hard set.  This has raised an idea for a FR to allow Dynamic close reasons (Soar settings, case data, close case) to be made available in the Action. I’ll log a FR!

 

Hello,

Thank you for the replies.
I understand you can control the close reasons, but I only used that action to illustrate the issue. There are many other actions that you can’t control those list parameters.
I know there is a feature request for this and it would be very helpful if it gets implemented.
Using conditions adds to the complexity of our playbooks and also copying actions to change their parameter types is not a good practice.

Thanks,
[removed by moderator]

And I am referring to a Feature Request for being able to use placeholders in list parameters, not the FR your mentioned above, though that would also be helpful.