J.T.

There is another way. As everyone has pointed out the first Error is a
fatal event for the entire ARS operation. (Escalations, Modify, etc..)

This however is only a default behavior of the canned ARS
server/clients. So if you write a small ARS API client to do the work
of the Modify (or if you might want to think of it as a "Modify All"
like operation) then your API program can "just keep going" even when
updating a record produces an error. The client could be written in C,
Java, or even ARSPerl if you prefer. All the program has to do is:

) Login ( with the proper/needed permissions)
) Do the search to find the records to process.
) Loop over the results and change as little as one fields value to
get filters to fire for that record.
  ) If an error happens.. the client can ignore it and just keep
processing the records until it has finished the whole set.
  ) If you want more advanced branching on the various errors then you
could do that to.
    -> Like building a Site when the "Incorrect/missing Site" error
happens etc...
) Log out.

If you need to know when the Escalations are done then you could also
write a flag to the file system or some other such "notify" type
action so that your external client knows when to start. (Assuming a
variable starting time.)

You can be as elaborate or simple about this as you choose too.

You could even write the filters to mark the records as "Processed"
when they are done so that your client can just "keep trying" to
process the records every 30 minutes. Some records will just keep
producing some error, some records will complete. If you wanted to the
script could even mark the records as "Error" and log what error
happened in a second modify to the record too. When the script runs
and only finds errors, then maybe it waits 2 hours and tries again. (
I hope you get the idea.. It is all up to you. )


BTW: Some people use this same idea to avoid the single threaded
Escalations universe that also exists prior to v7.1 too. So you are
kind of killing two birds with one stone.

HTH.

-- 
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.



On Dec 6, 2007 8:10 AM, J.T. Shyman <[EMAIL PROTECTED]> wrote:
> 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

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to