Yes.. and then some. ( But apparently I did not do a great job of explain it... I will try again...)
I said: " loop over a hidden table field and dynamically change fields attributes. (Hidden/disable ect...) based on the data in the table field. So you could configure your data into groups (via some kind of tag in the data) that an external qualification could use to select the correct records for that trip to the guide. " However the data in the table could also specify what should be done to the field that is listed too. (So the data could be used to do more than "just disable" the field.) So each row in this "change field action table" could define the field ID, and what to do with the field. (Hide and/or Disable and/or Change Label and/or Change font etc..) I think the only limit to how configurable the guide can be is only limited by the size/variety of the active links you put in the guide. I think the active links could be field ID generic (and fetched from a column of the table field) any only as specific as they need to be to be able to specify the each attribute to be changed. [Mostly because some of the "Advanced Change field" actions can not be specified as a "field reference". So, for example, there might be some limits to how many colors you want to support to keep the size of the guide as small as possible.] So... once built.. and attached to a given form... then any combination of changes could be made from setting a field to the "set of records to use" and then calling the guide. This technique could be used at any point in the workflow from any active link. (Window Loaded, on Button, On Return, etc..) Yes there is more run time overhead to this, but it also lets you alter the field changes based on the users Group List too. :) So the requirements could be much more complex without a need to alter the workflow. Also as new fields are added to the form, then new records are added and one more loop through the guide is needed. However, no workflow changes would be needed. All in all, I think data is easier to maintain than change field actions. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Nov 23, 2007 2:48 AM, Shyam Attavar <[EMAIL PROTECTED]> wrote: > I believe Matt is alluding to having a data driven setup that walks a table > to disable the fields (list of fields to be disabled are specified in > another form) and would require a AL Call Guide to loop over the table field > entries and the guide itself will have an AL with one action to disable the > field. > > If one chooses to hard code the list of fields in the AL action(s), then > what you are suggesting makes sense... > > Cheers, > -- > Shyam > > ----- Original Message ----- > From: "Rick Cook" <[EMAIL PROTECTED]> > Newsgroups: gmane.comp.crm.arsystem.general > To: <[email protected]> > Sent: Thursday, November 22, 2007 2:23 PM > Subject: Re: Disabling all fileds in a form > > > > Wouldn't that Guide still be calling the same AL(s)? Why add a layer of > > overhead to it, unless it was needed as a subroutine to use from other > > places? > > > > Rick _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

