While I understand the historical reasons for filter phasing as an approach to transaction management, I think at this point, it has become a serious hinderance.
Especially for applications as complex as ITSM but even for non-trivial homegrown apps, tracing a single transaction across multiple forms, for the purposes of troubleshooting is a complete freakin' nightmare. Not to mention the overhead of carrying a complex rat's nest of a filter stack forward through multiple versions of an application. Doing something as seemingly simple as adding a filter with a push fields action to a supporting form can cascade failures across an entire application. Tracing that kinda mess out and fixing it can eat up entire days or even weeks of dev time. ARS desperately needs something better in my opinion. For instance, a checkbox on filter guides that treats everything in the guide as a single transaction, and explicitly executes every thing in the guide in order, and rolls it all back in reverse order if there's an error? Or perhaps a special run process that let's me explicitly start a transaction and end one. There has to be a better way though. But that's just my long winded opinion :-) Andy On Friday, June 27, 2014, Sweety <[email protected]> wrote: > Something interesting here > https://docs.bmc.com/docs/display/public/ars81/Filter+processing+in+BMC+Remedy+AR+System+server > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
