CTA Field must be editable to be used in Rules, but then the value can be changed in the CTA

I was literally just searching for how other people have dealt with this situation, so I’m glad to see it was just requested by someone else.

I can use the workaround this time, but it would be great if all CTAs fields can be tokenised in the Setup Action page in Rules Engine even if they’re not editable by end-users in their Cockpit.

Thanks

Jon

I would also love to see this. We use custom fields and would love to be able write a specific ID to be referenced later in a DD job. Or add the function to be able to make fields hidden? 

This is a common pain point. For reporting/filtering/ etc purposes you’d want to be able to default certain fields and not have CSMs or users be able to edit later on.  Only thing you can do is put all those fields in a different “group” of fields and hope that the CSM follows instructions and does not edit.  Really would help to have this feature where only Rules Engine could edit certain fields.

Bump, this would be way cooler if you didn’t have to leave it as editable.

Same issue with programs, can’t populate the CTA fields unless they are marked as editable, but we dont want end users changing the value.