Dropdown list field mapping in CTA rules.

As we mature, we are pushing our CSEs to follow better process. This allows us to automate next steps, which include opening new CTAs. If someone has entered info and we want to bring it over, dropdowns need to be included.

I even tried using the API, but that method also doesn’t allow updates.

Thanks for your attention!

Christopher

Plus-one to this request.

We’ve recently run into roadblocks with creating new workflows due to not being able to map a value to a dropdown field.

It’s important our teams choose from specified options, and leaving that a manual entry means reporting can get skewed.

Plus one to this. Should it be moved to Ideas so we can get product’s input on it?

Definitely not a lot of activity on this Idea unfortunately.

I am in a position where this is causing me to have to build 18 different Critieria/Action combinations for the correct CTA Creations where it would have only require TWO of them if this functionality was consistent with the way that Rules Engine interacts with Pick-list (drop down) value assignments when writing to other Gainsight objects such as Company for example.  The inconsistencies in how functions work in Rules engine from one aspect area to another are extremely confusing and frustrating.

PLEASE take another look at this one.  Basically is is changing what field types would be allowed to reference for setting of a Pick-list (dropdown) in CTA actions.  This should not be a heavy technical lift to make this change.