Hi, We're testing a migration from RT 3.8.x (with callbacks, etc) to RT 4.2.3
This thread is probably going to end up relevant to RT-Extension-MandatoryOnTransition which does not appear to have yet solved this issue. I'm a little stuck here and don't see how what I want to do will be possible with the current RT code. I am looking for another set of eyes on the issue if anyone is so generous. The gist is that I am trying to get a message to the user after they have submitted *Ticket/Update.html*. Specifically, they need to be informed that their 'resolve' was rejected due to a Custom Field not having an acceptable value yet. I have no trouble doing this in *Ticket/Modify.html*. That works both with my custom callback code and also completely reimplemented via the RT-Extension-MandatoryOnTransition code (I tested that as well). However, *Ticket/Update.html* redirects to Ticket/Display.html upon submission and is therefore different. Does anyone have any ideas? I've put in a couple of hours now and am still not really sure I understand Update.html and Display.html's interactions with each other (and when). For the time-being I am back to the WWW-circa-1995 behavior, in my callback for Ticket/Update.html, of using Abort("ERROR... hit back in your browser to correct the issue...") Jeff Blaine -- RT Training London, March 19-20 and Dallas May 20-21 http://bestpractical.com/training