That is exactly what I needed - thanks - I've been backtracking code and log files for hours......
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Janie Sent: Tuesday, August 12, 2008 3:37 PM To: arslist@ARSLIST.ORG Subject: Re: Major index problem ** The Cleanup for "HPD:CFG Ticket Num Generator" is handled from the 'SYS:Application Cleanup' form. There is an entry in the form for "HPD:CFG Ticket Num Generator" - most likely the retention period is 1 day, There is an escalation on the SYS:Application Cleanup form that runs every night at 12:05 AM. This sets the keyword to START, a filter then pushes the DELETE keyword to the "HPD:CFG Ticket Num Generator" form if the entries exceed the retention period and a filter on that form processes the delete action. That's why you have entries from yesterday - because it's only Tuesday - tomorrow you will see entries from Tuesday forward and Monday's should be gone. As for your statement of something is inserting the Incident Number - have you identified this workflow? The Incident Number on "HPD:CFG Ticket Num Generator" is Request ID field 1 - the workflow that uses this field is Filter: HPD:INC:GIN_010_SetINCNumber-P -- there are also other Active Links that use this when creating relationships from Incident to Incident. The general theory is that a Push fields action pushes the 'Submitter' field with the $User$ which creates an entry on the "HPD:CFG Ticket Num Generator", then a Set Fields action gets the $LASTID$. Have you been able to identify if this happening only when creating Incidents or is it occurring at a different time? Janie ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Roger Medsker Sent: Tuesday, August 12, 2008 11:51 AM To: arslist@ARSLIST.ORG Subject: Re: Major index problem I believe that the record is created with a value in one of the fields that triggers a filter on the form that performs an "Application-Delete-Entry" process call to delete itself. Roger From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Tuesday, August 12, 2008 11:36 AM To: arslist@ARSLIST.ORG Subject: Re: Major index problem ** I think you're right. On Tue, Aug 12, 2008 at 9:30 AM, William Rentfrow <[EMAIL PROTECTED]> wrote: ** Anyone know what escalation? There's no escalation based directly off of that table so I suspect it's one of the cleanup ones. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Tuesday, August 12, 2008 11:24 AM To: arslist@ARSLIST.ORG Subject: Re: Major index problem ** William, if memory serves, the records in that form get flagged for deletion after the Incident is created, and an Escalation deletes them. Rick On Tue, Aug 12, 2008 at 9:18 AM, William Rentfrow <[EMAIL PROTECTED]> wrote: ** We are having a fairly serious problem in IM 7.03. Sometimes - and with no consistency - users will get a "unique index violation" error when creating an incident. After extensive research I've found the following to be true: 1.) The error is valid. 2.) The error happens because the system is trying to insert a duplicate Incident Number into the HPD:Help Desk form 3.) The duplicate Incident Number that is attempting to be saved did NOT come from the same user - therefore it's not a client workflow issue. IE - it's not a workflow bug where the field isn't being cleared out on the client between creations of incidents. 4.) There appear to be old/extra records in "HPD:CFG Ticket Num Generator" from the past two days. There are no entries prior to Monday Does anyone know how the form "HPD:CFG Ticket Num Generator" works in terms of when/how it gets emptied? William Rentfrow, Principal Consultant [EMAIL PROTECTED] C 701-306-6157 O 952-432-0227 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
