I was hoping to avoid having to reinvent the wheel and pre-test every OOD test in CTM:People.
Guess that can't be done unless AR 7.1 is in use with its "error" filter directive. J.T. Shyman Column Technologies -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eli Schilling Sent: Wednesday, December 05, 2007 5:11 PM To: [email protected] Subject: Re: Error Handling What I did was find out every piece of information that is checked when you submit something to the CTM people form. I then created filters to validate this information before a push to the CTM people form. When the second escalation fires I have about 22 filters that run in a guide to validate company info, site, phone number, org/department data, etc. If any of these fails to validate I return an error to the staging record and exit out. If everything checks out I finish with a push to CTM:People. I can then go back a few times a week to find the records that errored out and figure out what went wrong. Hope this helps. -Eli ________________________________ From: Action Request System discussion list(ARSList) on behalf of J.T. Shyman Sent: Wed 12/5/2007 12:01 PM To: [email protected] Subject: Re: Error Handling ** Yes, thanks! Not sure what you are talking about will help me but it is worth a shot. Here's where I am now: I've got an escalation that pulls data from LDAP into a staging form. That works perfectly. I've got another escalation that sets a field on the staging form to "Attempted" and a filter that fires on modify of the staging form to push the record to CTM:People. This works fine as long as there aren't any major errors like "The Company, Organization and Department combination entered does not exist. Please select a valid Company, Organization and Department combination using their respective related menus." in which case the filter keeps pushing the same record from the staging form and, quite predictably, keeps getting the same error message. It seems Remedy is seeing the escalation and filter as a single process. Since the filter fails the setting of the field to "Attempted" doesn't happen on subsequent records because the filter keeps failing on the same record. Strange behavior and I cannot get past it. J.T. Shyman Column Technologies ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eli Schilling Sent: Wednesday, December 05, 2007 11:51 AM To: [email protected] Subject: Re: Error Handling I am doing something similar in 7.0.1; I use two escalations to execute this process. The first simply does a push fields from my LDAP form into my staging form and sets a status of "New" on all created or updated records. This process takes about 75 minutes so I have another escalation scheduled to run 2 hours later. All it does is run through the "New" records and set them to "Trigger". This status causes a series of filters to fire that push and pull fields from hither and thither. Most of the filters end in `! so that they execute regardless of the phase. This enables the system to write errors out to a field or other form. There are several error checks along the way to determine whether or not to continue to the end of the process chain. I actually got help on this entire process from another lister several months back. If you'd like to see more detail I'd be happy to pass it along. Cheers! Eli ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of J.T. Shyman Sent: Wednesday, December 05, 2007 8:27 AM To: [email protected] Subject: Re: Error Handling ** Unfortunately, we're on 7.0.1. Thanks for the tip, though. J.T. Shyman Column Technologies ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Easter, David Sent: Wednesday, December 05, 2007 11:25 AM To: [email protected] Subject: Re: Error Handling If you are on AR System 7.1.00, the new filter error handling feature may be of use to you. That way, if you get an error condition, you could fire the error handling workflow to (a) write out the information you need and (b) enable the process to continue. This is the primary use case of Error Handling and why we added it to the product. Check out the documentation for details. Thanks, -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. 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) [mailto:[EMAIL PROTECTED] On Behalf Of J.T. Shyman Sent: Tuesday, December 04, 2007 7:46 AM To: [email protected] Subject: Error Handling ** Hello ARSers! I'm writing a process that will import user information from LDAP, put it into a staging form, and then push the information to CTM:People. I do some validation prior to pushing the records but I will always still get some failures. The problem is twofold: the push runs in phase 1 and any error stops the import cold and I don't know how (or if it is possible) to trap the error and send it to a log so a human can look at it and correct it. The idea is that the whole import process would run via escalation and errors would be written to another form for an administrator to deal with when convenient. Thanks in advance for any insight. J.T. Shyman __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

