Can you lock a custom feild once the value of a different custom feild is set?

[Brandon Forslund]

I have a custom field with a bunch of different options that tell us thr version for something in our project that I want my users to be able to edit and I have another custom field that uses to tell us if its been approved or not. Is there a way to use an automation that prevents the version field from being edited once the approval feild has been check off? 

[Tim Metivier]

I'm not aware of a way to "lock" a field, however, you could use automation to see if the approved field is set, and set the version back to the prior value .

Trigger: When value changes for: Version
Condition: If Approval is set
Action: Set Version to previous value using {{changelog.Version.fromString}}

You would need to have another rule to verify that the user initating an update to the Approval field belongs to the proper group or role.

Trigger: When value changes for: Approval
Condition: If users isn't authroized
Action: Set Approval to previous value using {{changelog.Approval.fromString}}

This isn't an ideal solution, but one I've used to prevent field values from changing after they've been set. It doesn't notify the user that the field value was reset.

Hope this helps!