Hi group,
At our side, we solve these problem with a system wide "validation" process
defined on all SBfields which check if mandatory fields sequentially defined
"before" the current field are empty.
If one is found it output a error message and exit with @RTN.FLAG =
{mandatoryfield} else it
John, what you've described is a feature of the GUI; the ability to click
through prompts in any order. If there are mandatory fields you shouldn't
be able to save the record until those fields have a value, but if those
fields are not mandatory the validation may never run. This can, of course,
Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R.
Sent: Friday, September 24, 2010 3:21 PM
To: 'U2 Users List'
Subject: Re: [U2] SB Client - Disable TAB
Yeah, we could do that on a screen by scr
-boun...@listserver.u2ug.org] On Behalf Of Dave Davis
Sent: Friday, September 24, 2010 3:12 PM
To: U2 Users List
Subject: Re: [U2] SB Client - Disable TAB
I think this is more of an issue with @WORK fields than @RECORD fields.
In any case, perform a validation after screen accept if it's impo
I think this is more of an issue with @WORK fields than @RECORD fields.
In any case, perform a validation after screen accept if it's important.
If it's important that the user not enter a field until other fields "before"
it have been entered, bounce them out by using the process before field s
