Controls

Re: Conditional Formatting Conflict on Validate Button

Bill McGuire — Tue, 01 Dec 2009 12:06:52 GMT

Hi Qazi

Thanks a million, such a simple correction.
I had assumed that with the "and", that they would cancel each other out as both users could not be logged in at the same time to the form!
But not that I see it, it makes sense.

Cheers
Bill

Re: Conditional Formatting Conflict on Validate Button

Qazi Anis — Tue, 01 Dec 2009 11:24:37 GMT

hi Bill,

the condition is wrong try using this one

stage=4 and username # hrvalidation and username#hrvalidation

the conditions are cancelling out because when stage = 4

no matter what is the login name it will either be equal to HRvalidation or HRvalidation2 there is where the conditions fail

Conditional Formatting Conflict on Validate Button

Bill McGuire — Tue, 01 Dec 2009 07:37:47 GMT

My contract approval form follows a workflow updating a stage field at each level of approval or rejection. The last approval is at stage 4 of the workflow and requires HR to give final approval. At this point I want to give 2 HR staff member’s access to approve and validate the form. What we have done is to create 2 fields HRValidate & HRValidate2. Each one holds one username as the value. We then use the conditional formatting "Stage = 4 and UserName ≠ HRValidation or Stage = 4 and UserName ≠ HRValidation 2, hide this control".

With only one of these conditions set, this works fine, but as soon as we add the “or” i.e. the second condition, the validate button is hidden from the word go so no one can use the form! This validate button also has several rules attached to set other field values based on what occurs in the earlier stages.

Any ideas as to why these two conditions are cancelling themselves out?

Many thanks in advance

Bill