Many years ago I submitted a suggestion to have the db contents of a diary field available to workflow. I've never heard back on it.
Any reason why it wouldn't be a good idea? Dwayne Martin James Madison University ---- Original message ---- >Date: Thu, 25 Oct 2007 08:40:50 -0700 >From: Rick Cook <[EMAIL PROTECTED]> >Subject: Re: Diary Fields >To: [email protected] > > ** > Andy, workflow can only evaluate the current entry > into a diary field - all existing ones are > considered to be invisible to the transaction. > > Rick > > On 10/25/07, LJ LongWing (Head) > <[EMAIL PROTECTED]> wrote: > > ** > Not a dumb question actually....that qualification > in an AL will give you only the 'change' to the > diary. To determine if a diary has previous > values you should do a setfield of the entry into > a 0 length display only field and then check to > see if it is null... > > ------------------------------------------------ > > From: Action Request System discussion > list(ARSList) [mailto:[email protected] ] On > Behalf Of Mayfield, Andy L. > Sent: Thursday, October 25, 2007 8:08 AM > To: [email protected] > Subject: Diary Fields > > ** > > This may be a dumb question, but..... > > Can you use the qualification of != $NULL$ on a > diary field? I want to have an active link fire > if there are any previous entries in a diary > field, but it doesn't seem to be working. > > Andy L. Mayfield > Sr. System Operation Specialist > Alabama Power Company > Office: 205-226-1805 > Cell: 205-288-9140 > SoLinc: 10*19140 > > __20060125_______________________This posting was > submitted with HTML in it___ Dwayne Martin Computing Support James Madison University _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
