I did, thanks for the hint and the info!

Soto Cano bought Service Desk or HD 6 in 2003 or 2004 apparently. I
thought that they never installed it, but if this field exists, would
it have been added during install of that product?

Drew


On Wed, Aug 4, 2010 at 12:00 PM, LJ LongWing <[email protected]> wrote:
> That's a core 'guid' field...if you create a field with that ID it will
> automatically get set to a GUID on creation of the record...check it out in
> the docs.
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected]] On Behalf Of Drew Shuller
> Sent: Wednesday, August 04, 2010 11:46 AM
> To: [email protected]
> Subject: Re: Unable to trace workflow to find Run Process Set Fields
>
> It is!
>
> On Wed, Aug 4, 2010 at 11:43 AM, LJ LongWing <[email protected]> wrote:
>> Drew,
>> Is the field ID of this Char field 179 by chance?
>>
>> -----Original Message-----
>> From: Action Request System discussion list(ARSList)
>> [mailto:[email protected]] On Behalf Of Drew Shuller
>> Sent: Wednesday, August 04, 2010 10:58 AM
>> To: [email protected]
>> Subject: Unable to trace workflow to find Run Process Set Fields
>>
>> Hello everyone, I have a difficult problem.
>>
>> Workflow is setting a character field using the Application Generate
>> GUID command. This command runs off a button and it creates a field to
>> reference child tickets. The workflow does it's job very well. I was
>> modifying it a little, and when testing, saw that the Run Process is
>> running on more conditions than just the button. It runs when I open a
>> ticket to view it. So the field is null, until I open the record.
>>
>> No problem, run a log. Nada. Not even the field name is written to the
>> log. I re-synched the search database (it worked! yaaaaay!) and
>> disabled all the workflow (nothing unexpected showed up) that would
>> set that field, again, all on a button, but the field was still set.
>> Still no entry in an AL, Macro, API, Database, and Filter client-side
>> log file. I exported all ojects and searched the file for the field
>> name and for GUID. Nothing unexpected there - found the four AL's that
>> the synch database showed me. I ran a server log for API, filters,
>> thread, and aruser. Nothing in there an not much detail either. I
>> bounced the server, just in case, but that didn't help.
>>
>> I searched tickets from way back, before I was there, to see if the
>> field was created by workflow that has been in place, and yes, this
>> field has been being set on open of a ticket for quite some time.
>> Maybe this means that it's not causing a problem, but I want to find
>> the workflow or process that is setting this field, and I can't.
>>
>> Any suggestions? Is there a setting in the ar.cfg file that would give
>> me more detail in the server-side log files?
>> Please help!
>>
>> ARS 6.3 patch 20
>> MS SQL 2000
>> WIN 2003 Enterprise Edition
>>
>> Drew Shuller
>> Soto Cano Air Base
>> Palmerola, Honduras
>>
>>
> ____________________________________________________________________________
>> ___
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>>
>>
> ____________________________________________________________________________
> ___
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>>
>
>
>
> --
> Drew
>
> ____________________________________________________________________________
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>



-- 
Drew

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to