Why not have a trigger field? Say a radio button, Yes\No. Only when this trigger is activated, set to Yes, does your DSO filter fire. Add it to the last set fields.
Kind Regards, Basil Webster Siemens IT Solutions and Services (Pty) Ltd Remedy Developer Local Production Centre Infrastructure Operations Siemens Southern Africa Main : +27 11 652-2000 Direct : +27 11 652-7220 Fax : +27 11 6527501 Mobile : +27 82 4529389 E-mail : [EMAIL PROTECTED] www.siemens.co.za ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Hyslop, Bruce Sent: 12 September 2007 20:47 To: arslist@ARSLIST.ORG Subject: Does anyone know what constitutes a DSO update transfer I'm having a tough time with a DSO application we support that does a chained distributed transfer. In this process I transfer from one form to another with the Immediately Update option set. When the form I transfer to gets updated it does 158 Set Fields which I believe queues up 158 distributed update transfers (I see this in my logs but don't believe my eyes). When 158 transfers get queued it causes not only a DSO bottleneck but causes extra filter processing on the originating form. I'm thinking of getting rid of the Update Immediately option and controlling when updates get sent myself. Bruce Hyslop | Remedy Support - NADC Automation | GOIS Unisys | 3199 Pilot Knob Road | Eagan, MN 55121 | 651-687-2726 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
<<image001.gif>>
