Duh on my part, thinking of E9. For 8, set the prompt when to false, set the width, height, x and y to zero. I tend to put these type of variables early in the tab order, typically before any that the user will see. To make that easy to do the first control I add to a form I make a tab index of 100, then I can go back and move new Variables that are being just used as variables to earlier tab indexes.
Jim Kinneman
Jim Kinneman
--- In vantage@yahoogroups.com, "Butler, Bruce" <bbutler@...> wrote:
>
> Jim,
>
> Where is the "invisible" setting for the input field?
>
> Bruce Butler, IS Manager
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of jckinneman
> Sent: Wednesday, March 28, 2012 4:05 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: 8.03 - Product Configurator - Set field Case Statements
>
>
>
> Unfortunately you can't declare variables as standard variables and have them survive until the method rules run.
>
> Create a form field but hide it (invisible) and then just treat it like a variable. For the configurator this is standard practice. For complex configurators I have had 20-30 of these just for use as variables.
>
> Jim Kinneman
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "Bruce Butler" <bbutler@<mailto:bbutler@>> wrote:
> >
> > Thanks for the info. Jim. In the past I have created a field on the form to store the value for later use. This looks sloppy.
> >
> > When you say "have the result stored in a single variable," does that mean I can store this without having to add form field? If so, how is that variable defined?
> >
> > Thank you,
> >
> > Bruce B.
> >
> > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "jckinneman" <jckinneman@> wrote:
> > >
> > > Sounds like two questions, one on syntax and one if can it be done. If that is the case for the syntax I'd recommend picking up the OpenEdge Development ABL Reference guide. The configurator uses Progress/OpenEdge ABL. I can't put my finger on the link at the moment but it has been referenced in several messages on this group previously that you should be able to search for.
> > >
> > > CASE expression :
> > > { WHEN value [ OR WHEN value ] ... THEN
> > > { block | statement }
> > > } ...
> > > [ OTHERWISE
> > > { block | statement }
> > > ]
> > > END [ CASE ]
> > >
> > > CASE pay-stat:
> > > WHEN 1 THEN
> > > field = 1.
> > > WHEN 2 THEN
> > > field = 2.
> > > WHEN 3 THEN
> > > field = 3.
> > > END CASE.
> > >
> > > Now whether you can use it for a set field statement, haven't tried it that I remember but worth a try. An alternative if that doesn't work is to put the case statement on the page on-leave statement and have the result stored in a single variable that you then use on the set field statement.
> > >
> > >
> > > Jim Kinneman
> > > Encompass Solutions, Inc
> > >
> > > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "Butler, Bruce" <bbutler@> wrote:
> > > >
> > > > I should have mentioned that I am using this based on a radio selection.
> > > >
> > > > Thank you,
> > > >
> > > > Bruce Butler, IS Manager
> > > >
> > > > From: Butler, Bruce
> > > > Sent: Wednesday, March 28, 2012 11:23 AM
> > > > To: 'vantage@yahoogroups.com<mailto:%27vantage%40yahoogroups.com>'
> > > > Subject: 8.03 - Product Configurator - Set field Case Statements
> > > >
> > > > Can you use a Case statement (vs. if/then/else) when setting up a set field rule? If so could you post a sample of how the set field rule would look?
> > > >
> > > > Thank you,
> > > >
> > > > Bruce Butler
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
>
>
>
> [Non-text portions of this message have been removed]
>