I'm trying to figure out the best way to "sync" a boolean userfield and delivered field so that they are opposites of one another. Specifically, EligibleForRehire. We don't want to use this field as our primary field on the Terminate form (hidden) and instead want to create a field for IneligibleForRehire. This is because 99% of our ex-employees are eligible for rehire and this field gets missed quite often by our admins when terms/resigns are entered. I don't want to lose the built-in business class logic with EligibleForRehire and rehiring candidates through TA though, so I want to keep the fields and data in sync.
I've tried just a plain userfield (Persistent Field) and using "when value changed" in the LPL on the Terminate form with no luck. We do not want to show the EligibleForRehire, we just want to always be true when Ineligible is false and vice versa.
If using a different kind of userfield would do this I'm happy to try it out, but since I'm working with both a userfield and a delivered field and the userfield is the initiating condition, not sure how to write that out in a derived field. Perhaps a conditional field is needed to assist with the logic...? Any help is appreciated.
I've tried a myriad of variations but this is the most recent I tried that didn't work.
RUSHIneligibleForRehire
when value changed
EligibleForRehire = false
refresh EligibleForRehire
when (RUSHIneligibleForRehire)
EligibleForRehire
initial value is true
