Configurator on leave auto fill a character field question

Yahoo Archive
1
What you are doing is correct.

I don't recall the release but there was an issue in earlier E9 releases where required fields were being ignored, check with Epicor to see if there is a one off available.

Jim Kinneman
Encompass Solutions, Inc

--- In vantage@yahoogroups.com, "Gibby" <guyguy50@...> wrote:
>
>
> Okay I've a novice question then, how exactly can I prevent it from going to the next screen? I'v just started working with configurators, and not sure how to prevent it from going to the next page other then a required field similiar to what you described but it just exits configurator after stating that a field was required. It was code used before I was on board. Looks like this:
>
> HCrequired = if (Something = "X") Then "" Else "OK".
>
> --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> >
> > I tend to use a common "validation" procedure that is run as part of all on-leave statements. In it using IF and Case statement as appropriate it checks and updates everything based on the answers so far. If something hasn't been entered yet you skip over that part of the validation or updating.
> >
> > I usually define a procedure in the very first control on the screen that I can call from all the others. Since controls interact so much with each other it makes it easier to have all the code in one place even if some efficiency might be possible by spreading it out.
> >
> > In your example all on-leaves would be running this common code and you could check that everything is the way it needs to be.
> >
> > As part of this common code I also define a textbox that is a required entry but inaccessible by the user so the only way it can be populated is if the validation routine does it. This way unless all the values are entered AND correct the user can not leave the screen.
> >
> > Jim Kinneman
> > Encompass Solutions, Inc
> >
> > --- In vantage@yahoogroups.com, "Gibby" <guyguy50@> wrote:
> > >
> > > I've a curious question on how to deal with an issue I've noticed that I'm sure will cause an issue eventually.
> > >
> > > Okay here is the scenario I have a configurator that uses an external on-leave file with other .p files and such being used. Well when a particular element is changed say my onleave statement fills in something else if the criteria is right with a simple if statement or something similiar.
> > >
> > > If Chrtest = "MR" then do:
> > > run(chrValue, output chrValue2)
> > > end.
> > >
> > > Okay so if chrtest is MR then it runs the program doing what it needs. Works great just like it supposed. But lets say when using the configurator someone filles out a field and moves on realizing oops made a mistake so changes a field. So Chrtest is no longer "MR" so now since it was assigned prior in the configurator chrValue2 is still got a value that is now wrong since it never triggers the if statement since it is not true now. Where should I be having error checking for something like this? Without putting an else statement as since I have many many if statements due to dozens of possible configurated parts for a particular product this many well close to double my file size is there an easier way to reset some values?
> > >
> >
>
2
I've a curious question on how to deal with an issue I've noticed that I'm sure will cause an issue eventually.

Okay here is the scenario I have a configurator that uses an external on-leave file with other .p files and such being used. Well when a particular element is changed say my onleave statement fills in something else if the criteria is right with a simple if statement or something similiar.

If Chrtest = "MR" then do:
run(chrValue, output chrValue2)
end.

Okay so if chrtest is MR then it runs the program doing what it needs. Works great just like it supposed. But lets say when using the configurator someone filles out a field and moves on realizing oops made a mistake so changes a field. So Chrtest is no longer "MR" so now since it was assigned prior in the configurator chrValue2 is still got a value that is now wrong since it never triggers the if statement since it is not true now. Where should I be having error checking for something like this? Without putting an else statement as since I have many many if statements due to dozens of possible configurated parts for a particular product this many well close to double my file size is there an easier way to reset some values?
3
I tend to use a common "validation" procedure that is run as part of all on-leave statements. In it using IF and Case statement as appropriate it checks and updates everything based on the answers so far. If something hasn't been entered yet you skip over that part of the validation or updating.

I usually define a procedure in the very first control on the screen that I can call from all the others. Since controls interact so much with each other it makes it easier to have all the code in one place even if some efficiency might be possible by spreading it out.

In your example all on-leaves would be running this common code and you could check that everything is the way it needs to be.

As part of this common code I also define a textbox that is a required entry but inaccessible by the user so the only way it can be populated is if the validation routine does it. This way unless all the values are entered AND correct the user can not leave the screen.

Jim Kinneman
Encompass Solutions, Inc

--- In vantage@yahoogroups.com, "Gibby" <guyguy50@...> wrote:
>
> I've a curious question on how to deal with an issue I've noticed that I'm sure will cause an issue eventually.
>
> Okay here is the scenario I have a configurator that uses an external on-leave file with other .p files and such being used. Well when a particular element is changed say my onleave statement fills in something else if the criteria is right with a simple if statement or something similiar.
>
> If Chrtest = "MR" then do:
> run(chrValue, output chrValue2)
> end.
>
> Okay so if chrtest is MR then it runs the program doing what it needs. Works great just like it supposed. But lets say when using the configurator someone filles out a field and moves on realizing oops made a mistake so changes a field. So Chrtest is no longer "MR" so now since it was assigned prior in the configurator chrValue2 is still got a value that is now wrong since it never triggers the if statement since it is not true now. Where should I be having error checking for something like this? Without putting an else statement as since I have many many if statements due to dozens of possible configurated parts for a particular product this many well close to double my file size is there an easier way to reset some values?
>
4
Okay I've a novice question then, how exactly can I prevent it from going to the next screen? I'v just started working with configurators, and not sure how to prevent it from going to the next page other then a required field similiar to what you described but it just exits configurator after stating that a field was required. It was code used before I was on board. Looks like this:

HCrequired = if (Something = "X") Then "" Else "OK".

--- In vantage@yahoogroups.com, "jckinneman" <jckinneman@...> wrote:
>
> I tend to use a common "validation" procedure that is run as part of all on-leave statements. In it using IF and Case statement as appropriate it checks and updates everything based on the answers so far. If something hasn't been entered yet you skip over that part of the validation or updating.
>
> I usually define a procedure in the very first control on the screen that I can call from all the others. Since controls interact so much with each other it makes it easier to have all the code in one place even if some efficiency might be possible by spreading it out.
>
> In your example all on-leaves would be running this common code and you could check that everything is the way it needs to be.
>
> As part of this common code I also define a textbox that is a required entry but inaccessible by the user so the only way it can be populated is if the validation routine does it. This way unless all the values are entered AND correct the user can not leave the screen.
>
> Jim Kinneman
> Encompass Solutions, Inc
>
> --- In vantage@yahoogroups.com, "Gibby" <guyguy50@> wrote:
> >
> > I've a curious question on how to deal with an issue I've noticed that I'm sure will cause an issue eventually.
> >
> > Okay here is the scenario I have a configurator that uses an external on-leave file with other .p files and such being used. Well when a particular element is changed say my onleave statement fills in something else if the criteria is right with a simple if statement or something similiar.
> >
> > If Chrtest = "MR" then do:
> > run(chrValue, output chrValue2)
> > end.
> >
> > Okay so if chrtest is MR then it runs the program doing what it needs. Works great just like it supposed. But lets say when using the configurator someone filles out a field and moves on realizing oops made a mistake so changes a field. So Chrtest is no longer "MR" so now since it was assigned prior in the configurator chrValue2 is still got a value that is now wrong since it never triggers the if statement since it is not true now. Where should I be having error checking for something like this? Without putting an else statement as since I have many many if statements due to dozens of possible configurated parts for a particular product this many well close to double my file size is there an easier way to reset some values?
> >
>