OK - I don't know if this is obvious or byzantine..
What I am trying to do is set some sort of validation rules (probably through expressions) so that if one field has one value you cannot input certain values in another field.
The actual situation is this:
The form is for managing calling setting callback statuses for survey respondents and also for applying codes to their cases. [Note- it is a voluntary government study not one of those pestering ones]
E.g. Under Decision you could put "Everything OK" or "Requires Callback" as well as other options.
Under Callback you could put "Callback for information", "Not in service", "Callback Completed" etc.
The problem is - I cant allow Decision to be "Everything OK" and Callback to be "Callback for information", or Decision to be "Requires Callback" and Callback to be "Callback Completed".
Of course the controls run off of lookup tables:
Callback:
Code |
Description |
1 |
CALL BACK COMPLETE - CASE FIXED |
2 |
CALL BACK COMPLETE - CASE UNCHANGED |
3 |
INCOMPLETE - PENDING CALLBACK |
4 |
UNABLE TO COMPLETE CALLBACK |
Decision:
Code |
Description |
1 |
CALL BACK (MAKE NOTES) |
2 |
ALL IND TO YEARLY SALARY |
3 |
ALL IND TO HOURLY WAGE |
4 |
ALL IND TO PIECEWORK/COMMISSION |
5 |
OTHER (MAKE NOTES) |
6 |
EVERYTHING OK (MAKE NOTES IF NECESSARY) |
So, you cant have Callback = 1 and Decision = 1, as well as other variations.
In pseudocode what I am imagining is an expression like:
Code:
If[Callback]=1, then [Decision]cannot =1
or
Code:
If[Decision]=6 then [Callback] cannot = {3,4}
and other variations.
The problem isnt the combinations, it is CAN and WHERE and HOW can I put validations like this into the form so that the coder cannot say a case is completed but also have it in a callback status of requires callback.
There are tens of thousands of cases to manage soooooooooooooo.........yeah........
Anyone have ideas on how I can set up a form so that one control's validations are based on another control's status?
Thank you so much!!