Thanks for All good ideas: After reading the filter phases again to be sure, I cannot use push fields because they fire in phase 2 ;-( before the commit.
Tricky idea about after submit active link. But that won't fire in cases where the transaction was triggered by an API call instead of the User Tool. And I'm still in the dark ages using v7.1, but I did think about the notification API. I had previously thought about using a run process, but that can get out of control quickly by spawning many extra unix processes. Here's what I've decided upon: I'm going to use DSO to push to another form and then call the filter API from there. Thanks, -Geoff Endresen On May 7, 2011, at 8:30 AM, Jarl Grøneng <[email protected]> wrote: > If your on 7.6.4 you can use the Alert --> Web service plug-in in AR > System. This is asyncron, and will probably do what you want. > > Page 260 in BMC Remedy Action Request System 7.6.04 Configuration Guide > > -- > J > > > > 2011/5/4 Geoffrey Endresen <[email protected]>: >> ** >> We generally use Filter APIs during set fields operations that would be >> Phase 1. >> >> But we have a feature where we want call the Filter API that would run after >> the ticket is committed to the DB. >> >> Any ideas? >> >> -- >> -Geoff Endresen >> Amazon.com >> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
