Michael, I know this thread is a bit old, but I thought I would chip in all the same...
I am not sure what you mean by a "normal programming language", however, here is one way to approach this idea in ARS... The trick will be to trigger the workflow. Since you want the trigger to be "user focuses on <Field ID/Field Name>" then you will need an active link for every field that the user can set focus to. Think of these Active Links as HTML attributes of a form field of "onMouseOver" or "onFocus". ( Not that I would call HTML a "normal programming language". :) Now what you likely want to trigger is a reusable subroutine. In ARS you can think of an Active Link guide as that kind of construct if you can correctly identify all that you need to do in a generic way for the function/Sub to be generic enough to work for all cases. In this case I think you can do exactly that. And to finish the programming speak... ARS only has a "global scope" for all active links on a given form. So your Guides do not loose access to any of the fields on the form when they are called, and any changes to the values that they make will be retained after the guide finishes. [Oh.. and there is a special case for communicating between forms in a session, and between forms of the same class(form name) but those are other "programming concepts in ARS" best addressed in other threads.] In the Active Link Guide you need one or two more Active Links. The first active link does a SetField action to get the data from the form that holds the help text using the keywords $SCHEMA$, and $FIELDID$ (or $FIELDNAME$ if you prefer, but I would go with FIELDID) and it would return the HelpText value from the other form to a local field on the screen for the user. The second one might add some default text to the returned HelpText field if it is still null, and maybe do some extra workflow to request someone to write some helptext for the field. (Like open a ticket, or do a Push action to trigger some emails to be sent, etc...) Another approach would be to not have a form to hold this data. You could also use the keyword $FIELDHELP$ to get the help that has been defined for the field via the Admin tool too. However I do see the advantages to holding this data in a data form and not in the ARS Object definitions if the help information changes often enough. HTH. -- 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 7/25/07, Durrant, Michael M. - ITSD <[EMAIL PROTECTED]> wrote: > ** > > Here's my idea - tell me if I'm crazy: > > I want to create a form with the following: > Form Name > Field ID/Field Name > Help Text > > When a user focuses on <Field ID/Field Name> on <Form Name>, a text field > would be set with the contents of <Help Text>. I know I could do this with > a truckload of Active Links - but I really don't want to > > I know how I could do it in a "normal" programming environment - how can I > do it in Remedy? > > Thanks, > > Michael _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
