I know that you found a solution, but this may help someone else:
http://www.remedy.com/customers/dht/archive/02-01-2005_A.htm
from a Remedy Tips and Tricks entitled Custom Prompt for Required
Fields with Null Values

rp

Stephen Earl wrote:
> All,
>
> Thanks for the suggestions, great as always, however for completeness
> I managed to resolve our issue using one of the new run process
> actions Application-Copy-Field-Value which lives in a guide as
> follows:
>
> AL 1:
>
> Set Fields: set temp display-only field with value of fieldid from form2
>
> AL 2:
> Set Fields: set value field using the run process
>
> AL 3:
> Set Fields: evaluate if field is null or not
> Set Fields: if null set field name to display-only char field
> Set Fields: if null set field label red
>
> AL 4:
> Set Fields: set display-only fieldid to null, set value field to null
>
> set this guide to loop across the table rows, adding field names and
> label colours for each 'null' field
>
> Once complete open a dialog stating the error and giving a list of
> fields that have been left as 'null' which now also have the labels in
> red to prompt the user :-)
>
> Again thanks for the suggestions.... Also I couldn't do this with
> filters as we are evaluating on client before passing values back to
> the db.
>
> Thanks again
>
> Stephen
>
> On 22/08/06, Scott Parrish <[EMAIL PROTECTED]> wrote:
> > **
> >
> >
> > Stephen,
> >
> > Create a display only field on your form: ztmpQualification. Depending on
> > your workflow, you may want to add another: ztmpErrors
> >
> > Create the following:
> >
> >
> >
> > Active Link 0
> >
> > Run If: None
> >
> > If Action: Set Field
> >
> > Form Name: Current Transaction
> >
> > Set Field: ztmpErrors
> >
> > Value: $NULL$
> >
> > If Action 2: Call Guide
> >
> > Guide Name: Guide #1 Table Loop through your table
> >
> > If Action 3: Call Guide
> >
> > Guide Name: Guide #2 (No table loop)
> >
> >
> >
> > Active Link Guide
> >
> > Name: Guide #1 (In the guide, place the following active links)
> >
> >
> >
> > Active Link 1:
> >
> > Run If: None
> >
> > If Action: Set Field
> >
> > Form Name: Current Transacation
> >
> > Set Field: ztmpQualification
> >
> > Value: "'Column1' = $NULL$" (Something along those lines. Basically, we're
> > creating an external qualification. So that if  the value in Column1 were
> > say Case ID+ your ztmpQualification field would be set to 'Case ID+' =
> > $NULL$. Also, you are, of course, going to need to watch out for placing the
> > quotes around the set field string.)
> >
> >
> >
> > Active Link 2
> >
> > Run If: EXTERNAL(ztmpQualification)
> >
> > IF Action: (I'm not sure what you are attempting to accomplish at this
> > point, but you could copy the value in column1, which should be your field
> > name, to the ztmpErrors field so that you could collect a list of fields
> > with NULL values and present an error at the end of your active link guide
> > such as this:
> >
> > If Action: Set Field
> >
> > Form Name: Current Transaction
> >
> > Set Field: ztmpErrors
> >
> > Value: $Column1$ + <return>
> >
> >
> >
> > Active Link Guide
> >
> > Name: Guide #2 (In the guide, place the following active link)
> >
> >
> >
> > Active Link 3
> >
> > Run If: ztmpErrors != $NULL$
> >
> > If Action: Message
> >
> > Error Message: "The following fields must be populated before saving your
> > ticket:"<return>$ztmpErrors$
> >
> >
> >
> > Hope this helps. Of course, this assumes I know what you were trying to
> > accomplish. There may be some minor missteps in here, but I think you get
> > the idea of how it works.
> >
> >
> >
> >
> > Scott Parrish
> >
> > IT Prophets, LLC
> >
> > (770) 653-5203
> >
> > http://www.itprophets.com
> > ________________________________
> >
> >
> > From: Action Request System discussion list(ARSList)
> > [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
> > Sent: Tuesday, August 22, 2006 9:54 AM
> > To: arslist@ARSLIST.ORG
> > Subject: Re: Why oh why oh why won't this work.....
> >
> >
> >
> >
> >
> >
> >
> >
> > Stephen,
> >
> >
> >
> >
> >
> > I did something very similar.. in fact mine might be even more complicated
> > since I had to build a External filter qualification to check for database
> > values of fields against transactional...
> >
> >
> >
> >
> >
> > My requirement instead of making the field required was to audit fields that
> > were contained on form 2.. Whenever there was a change on form 1, on any of
> > the fields contained on form 2, to audit those fields by pushing the changes
> > into form 3...
> >
> >
> >
> >
> >
> > I even did this without the use of a table field :-) to run the loop over by
> > running a filter loop since I HATE server side Table fields because of
> > possibile performance concerns...
> >
> >
> >
> >
> >
> > So where is it failing for you?? What I have done here works perfect for
> > me.. maybe I might be able to throw in a clue as to where you might be going
> > wrong...
> >
> >
> >
> >
> >
> > Cheers
> >
> >
> >
> > Joe D'Souza
> >
> >
> > Remedy Developer / Consultant,
> >
> >
> > BearingPoint,
> >
> >
> > Virginia.
> >
> >
> >
> >
> >
> > ----- Original Message ----
> > From: Stephen Earl <[EMAIL PROTECTED]>
> > To: arslist@ARSLIST.ORG
> > Sent: Tuesday, August 22, 2006 10:25:08 AM
> > Subject: Why oh why oh why won't this work.....
> >
> >
> >
> > I have 2 forms.... data form and form containing a list of required
> > fields for the data form, lets call the form 1 (data) and form 2
> > (required fields)
> >
> > Form 2 contains 2 fields 'form name' and 'field name' on form 1 we
> > have a table field containing 2 columns from form 2 showing records
> > where form name equals the form name of form 1
> >
> > What I want to achieve is an AL guide that runs across the table and
> > checks the field name listed in the table and tests for it being NULL
> > however it appears there isn't a way with remedy workflow to achieve
> > this 'simple' operation.
> >
> > so basically what I have is a field name in another field and I want
> > to test if that field's content is null or not, should be simple
> > appears it isn't unless I'm missing something REALLY obvious....
> >
> > All help and suggestions welcomed :-)
> >
> > Stephen
> > __20060125_______________________This posting was submitted
> > with HTML in it___ __20060125_______________________This
> > posting was submitted with HTML in it___
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

Reply via email to