Allow Rules Engine to populate custom Success Plan fields that are not editable on template

Ran into this at my previous org and had to just add into enablement “please please don’t touch this”. Fortunately our use case was simply to add an internal reference to documentation so end users changing it would only disrupt them, but if you rely on that info being able to write to it and lock it down from editing would be important.

Set my data freeeeee

I set the display field on these to “ADMIN ONLY field name” to try to help the CSMs as well, but it would be better to not be forced to do so

Definite upvote here. Use cases include:

• Bubbling up the date of a specific closed task and locking it in place
• Associating a NPS survey URL to the Success Plan for quick look up of info
• I really could keep going

Please consider a way to lock end users and allow the rules engine.

We do this via rules and API. Works pretty seamlessly.

Has anyone tried to mark the field editable, build the rule, save, and then go mark it uneditable and see if the rule still populates it?

@Wayne that is definitely an option, but not for most users. And I did try mapping the rule with the field as editable, then marking the field not editable.

It worked. BUT, the field disappears in the mapping of the Action. So you now have to remember what you did and when.

I believe this needs to be fixed within the product and a Gainsight workaround is not ideal for anyone.

Agreed, it’d be nice to have a UI side setting and backend side setting on everything. But, at least there’s a poor man version of a work around!