Enable expression

[Mark Williams]

I have a field in a UX named Tracking_Num. I have several validation rules defined for this field that work as expected (no special characters, 6 digits, don't allow letters). It the user enters an invalid value it generates an error as expected.

Even though the field shows an error if invalid data is entered, it still allows you to submit the record with the invalid data.

I have a 'Submit' button that I am attempting to create an "Enable Expression" for so if the Tracking_Num is invalid, the field is disabled.

In the below picture, the tracking_num field is required to not be blank, but I'd also like it to check to make sure the above validation rules are met in order for the field to be enabled.

Is this possible?

[Lance Gurd]

How is your UX set up?

Is it data bound or not?

How is your Submit button set up, what fires when you push the submit button?

[Mark Williams]

How is your UX set up?

Is it data bound or not?

How is your Submit button set up, what fires when you push the submit button?

It is data bound and the submit button performs a geolocation capture of the users current location.



2022-02-28_07-56-17.png

[madtowng]

Hi Mark,

At the very least use Tracking_Num <> "" or Tracking_Num != "".
There might be a more elegant method, but I would expect using a regex or a simple function to confirm each character is between 0 and 9.

[Lance Gurd]

You could use {dialog.object}.setDisabled('Submit,false) in the javascript validation of the Tracking_Num field something like

var dataN = $u.s.toNum(data);
if(dataN > 10) {
return {dialog.Object}.setDisabled('Submit',false);
} else {
return true;
}

Where entering more than 10 in the field enables the submit button

[madtowng]

This javascript function will report true if the tracking_num is 6 digits.

function checkingTrackingNum(vcode){
var response = /\b\d{6}\b/g.test(vcode);
return response
}

[Mark Williams]

I am still trying to get this to work and have been unsuccessful getting the recommendations above to work.

I have gotten closer by doing the following:

I added the following to the submit button enable expression:

Tracking_Num >= "400000" and Tracking_Num <= "999999"

(Note: Tracking_Num is a character field)

Now I am getting somewhat odd results...

Tracking_Num: 399999 = disabled submit button (expected result)
Tracking_Num: 400001 = enabled submit button (expected result)
Tracking_Num: 401 = enabled submit button (why does this result in enabled)
Tracking_Num: 501 = enabled submit button (why does this result in enabled)
Tracking_Num 400001* = enabled submit button (shouldn't the asterisk cause the button to be disabled?

Thanks for any suggestions.

[madtowng]

I'd be willing to do some testing with the partial solution I provided if you supply a copy of the ux
and some test data.

[Lance Gurd]

Hi Mark,

It is the character field that is causing you problems because you are testing it mathmatically.

There is another way of looking at this, your Tracking_num field could have client side formating with a mask set to 000000 to allow 6 figures only, therefore anything other than a number would not be recognised/input. Then your submit button could have an enable expression on len(Tracking_num)>5.

see attached. tracking.a5wcmp

[madtowng]

Hi Mark,

It is the character field that is causing you problems because you are testing it mathmatically.

There is another way of looking at this, your Tracking_num field could have client side formating with a mask set to 000000 to allow 6 figures only, therefore anything other than a number would not be recognised/input. Then your submit button could have an enable expression on len(Tracking_num)>5.

see attached. [ATTACH]n935934[/ATTACH]

Did you see the little regex js function in post#6 ?

[Lance Gurd]

Hi Gregg,

Yes I did and it's a nice bit of code, however it does not stop the end user typing alpha characters etc.

[madtowng]

They can type anything they want, but any 6 character string that isn't all digits will return false.
I could probably configure another one for they keyup event, but we would need to determine what
to do with backspace and left arrow.

[Mark Williams]

Hi Mark,

It is the character field that is causing you problems because you are testing it mathmatically.

There is another way of looking at this, your Tracking_num field could have client side formating with a mask set to 000000 to allow 6 figures only, therefore anything other than a number would not be recognised/input. Then your submit button could have an enable expression on len(Tracking_num)>5.

see attached. [ATTACH]n935934[/ATTACH]

Works great - thanks, Lance!