All, I believe the confusion surrounding field ID 179 is this: Prior to ARS 6.3, if you wanted to use a GUID for creating parent/child relationships, the GUID had to be created using the Application-Generate-GUID process (there was no field Id 179).
In ARS 6.3, Remedy introduced field ID 179. This field is auto-populated by the system and is available throughout all three phases of filter processing (unlike the Request ID field). By adding field ID 179 to a form you can push the value of the field in a Phase 1 filter push that executes on submit (even though you have not specifically set the field's value). In addition, the value is also available for any active link push fields that execute on Submit. Chris Woyton's email below points out that the auto-population of this field does not work prior to 7.5. I cannot attest to whether it works in 6.3, but I know it works in 7.0 and above. Ben is correct, except that field ID 179 behaves differently than field ID 1. The value of field Id 179 is available immediately upon submit (population of the field does not rely upon the completed commit to the database). I hope I have not further confused the situation. Scott Parrish IT Prophets (770) 653-5203 www.itprophets.com From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ben Chernys Sent: Tuesday, December 07, 2010 12:29 AM To: [email protected] Subject: Re: GUID FIELD 179 ** The GUID field has always (since its invention) been automatically populated ON SUBMIT - that is when all workflow has fired and the record is being written to the database - much like field 1. If you need it ahead of that (in filters or ALs) then you need to populate it. Cheers Ben Chernys www.softwaretoolhouse.com<http://www.softwaretoolhouse.com> From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Chris Woyton Sent: December-07-10 05:14 To: [email protected] Subject: Re: GUID FIELD 179 ** The GUID isn't automatically populated in earlier versions of ARS (I believe 7.5 is the first version which does). For lower versions you need to use a run process as you have been doing. Sounds like there's either a documentation bug or you're looking at a newer help file. On Mon, Dec 6, 2010 at 9:19 AM, Gadgil, Abhijeet <[email protected]<mailto:[email protected]>> wrote: Potentially you could write an active link on say lose focus of a field to call $PROCESS$ @@:Application-Generate-GUID and set the output to a field on the form This way you will have the GUID created. Now when you save / submit the request then an entry will be created in database. This way you can have the GUID created even before a entry is created at the database level hope that helps Regards, Abhijeet The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. ________________________________ From: Action Request System discussion list(ARSList) [ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
