I am by no means an expert but I built some receiving workflow for our warehouse team using a custom shipping/receiving form. When they receive a CI via this form I have a filter set $PROCESS$ Application-Generate-GUID into a field on the custom form, then a later action in the same filter pushes that field into the Instance Id field of the appropriate AST:* form.
So far we have not had any problems with this process but as always YMMV. -Rick From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Andrew Hicox Sent: Wednesday, April 01, 2015 6:35 AM To: [email protected] Subject: Setting 'InstanceId' on AST:* submit? ** Hi everyone, I have a situatuon where some home grown workflow needs to create CI's. I'm doing this by pushing fields directly to the AST:* form corresponding to the Class we want to create the CI in, and up to that point it works flawlwssly. However, I need to pull the 'InstanceId' of the CI I just created back into the form where the workflow fired the push fields (so I can set up relationships, etc). Doing this reliably has become more of a headache than I'd imagined. There are almost no uniqueness restraints in cmdb (sort of a corollary to Igor's thread about unique indexes). So there's almost nothing I can search by other than 'InstanceId', that's guaranteed to get 1 or 0 results. so here's my question. What if I generate my own GUID and push it into 'InstanceId' on the AST:* form? Does anyone know of this will break something in asset or cmdb? On the surface, this seems like a legitimate thing to do, but just wondering if anyone has been down this road before? -Andy _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
