Ok, I seem to have trouble getting anything right. The offending filter I mentioned in the original email, the one that encounters the error, starts with: INT:HPDSLM:INC:SLMSetTarget_
and NOT INT:HPDSLM:INC:SLMSetTarget_7 There are 3 of these filters starting with the above string, all inside filter guide: INT:HPDSLM:INC:CalculateDates which is triggered by this On Modify filter on Incident form: INT:HPDSLM:INC:SLMSetTarget_780_CallGuide The modiy is initiated by this On Delete filter on SYS:Action: INT:FNDHPD:ACT:CALCULATE_SLMDATES_500_PHPD which does a push field to the incident with value z1D Action = "CALCULATE_SLMDATES" The delete action, in my tests, was result of manual delete of SYS:Action records by me. The errors on arerror.log, I am guessing, were caused by workflow trying to delete SYS:Action records. Not too sure. Looking to see if there's any other timed event that may be triggering the sequence leading to the error. By now if you've started to think I take pleasure in spitting out copious amount of barely comprehensible info to tire you out, that's not true. If I've managed to actually tire you out, well...I don't blame you. --- Rabi Tripathi <[EMAIL PROTECTED]> wrote: > Where I said form "HPD:HelpDesk_Interface_Create" > below, I should have said > "HPD:IncidentInterface_Create" instead. > > I can never get this form's name right. > > --- Rabi Tripathi <[EMAIL PROTECTED]> wrote: > > > Joe, Gotto love your speed! > > > > Relying on a coin toss seems like trouble, so I > need > > to figure out what's the right value to stuff in > > 'SLMLookupTblKeyword' field. > > > > I haven't been able to locate any document that > > talks > > about how SLM works behind the scenes...what > forms, > > for what purpose, when does it create records for > > what > > purpose etc. Does anybody know of any doc such as > > "SLM > > architecture"? I have very limited insight into > the > > overall architecture. > > > > In a way it's fun to go down to this level to look > > into nuts and bolts of an app, but at the same > time > > it's sad that I HAVE TO learn the dirty details to > > get > > something to work. > > > > Related question, nobody ever got ARERR [102] in > > their arerror.log? If you have Incidents being > > created > > through HPD:HelpDesk_Interface_Create form, and > you > > have played with SLM on Incidents, I would think > > this > > error is bound to show up on arerror.log > > > > --------- > > From Joe D'Souza <[EMAIL PROTECTED]> > > reply-to arslist@arslist.org, > > to arslist@arslist.org, > > date Nov 5, 2007 8:03 PM > > subject Re: ARERR [102] Name parameter... is > empty; > > field 'SLMLookupTblKeyword' on HPD:Help Desk > > > > hide details 8:03 PM (15 hours ago) > > > > > > > > Reply > > > > > > ** > > ARERR 102 is an error that happens when a field > that > > is used in 'Advanced' workflow to reference a form > > or > > server name or 'Advanced' table fields to > reference > > a > > form or server name is empty. This typically > happens > > when there is missing data in containers that have > > information about servers or forms, and a set > field > > operation that finds no data set fields to null. > It > > also could happen if you have changed a form name > > and > > the data containing form names may have not been > > edited to reflect the renamed form. > > > > So check the underlying data configuration forms > > where > > the data for the field 300427600 is being set. > > > > Hope this helps.. > > > > Cheers > > > > Joe D'Souza > > > > -----Original Message----- > > From: Action Request System discussion > list(ARSList) > > [mailto:[EMAIL PROTECTED] Behalf Of Rabi > > Tripathi > > Sent: Monday, November 05, 2007 7:23 PM > > To: arslist@ARSLIST.ORG > > Subject: ARERR [102] Name parameter... is empty; > > field > > 'SLMLookupTblKeyword' on HPD:Help Desk > > > > > > The short question is: has anybody had issue with > > SLMLookupTblKeyword field on HPD:Help Desk records > > on > > IM 7 being blank, regularly causing the following > > error in arerror.log? > > > > ARERR [102] Name parameter (or name field in a > > parameter) is empty : 300427600 > > > > This is the long story: > > After seeing the errors, I did some digging in and > > it > > turns out that... > > system (ITSM 7) is having trouble deleting records > > on > > SYS:Action form...related to HPD:Help Desk > record's > > SLM stuff. > > On manually trying to remove the offending record > on > > SYS:Action, I get the same error. > > > > Because filter INT:HPDSLM:INC:SLMSetTarget_7 > > encounters some issue. > > Because it references the top table on SLM tab, > > CurrentSLAs_tbl, and this table's source form name > > is > > supposed to be held in field SLMLookupTblKeyword, > > which is a real field, not a display only one, > > ...but this record (and many others) have this > field > > empty. > > > > On further digging in (by this time I am at a dark > > and > > uncomfortable depth), it turns out that most > > HPD:Help > > Desk records have value "SLM:Measurement" in this > > field, the right source form of this table, but > many > > records have this field blank. > > > > I did some more digging in and it turns out the > only > > workflow setting this field (at least the only > ones > > on > > HPD:HelpDesk form) are some active links such as > > "HPD:INC:SchemaNameLookup_10_NoSLM", and they set > > the > > field to "SYS:SLM:Measurement_Clone". > > It **looks like** when there is no SLA attached, > > this > > "clone" form is used as source. And this form is > > just > > a trick to improve performance by avoiding > > unnecessary > > search on SLM:Measurement, because the "clone" > form > > seems to never have records. My interpretation. > > > > Now the question for me is why do many HPD:Help > Desk > > records have field SLMLookupTblKeyword blank. > > Related > > question, what's setting it, in the first place? > I'm > > guessing SLM code, but where, how and why is it > > shirking its duty on some records? > > > > And a bonus question, what are those clown active > > links doing? They seem to be good for > > nothing...other > > than upping the total number of active links in > ITSM > > 7. > > > > Ah...answered my own question before hitting > > send...turns out all the HPD:HelpDesk records with > > this issue were created not by people, but came > in > > thru the form HPD:HelpDesk_Interface_submit > > (incoming > > email, web services etc). They should have > rememberd > > to have the code on this intermediate form set > > SLMLookupTblKeyword field, but they didn't, so I > get > > to do the honor. I will set it to...I don't know > if > > I > > should set it to "SLM:Measurement" or > > "SLM:Measurement_Clone". Bummer. It's late so I'm > > tossing a coin and then going home. > > > > TIA. > > > > ps: It took a while to type this, so I'm sending > > this > > instead of discarding it...hopefully will help > === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
