On Fri, Mar 07, 2014 at 03:39:36PM -0500, Jeff Blaine wrote: > 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 surprised at this statement since MandatoryOnTransition works on Create.html and Update.html but not on Modify.html, but you claim the problem is in Update.html. > 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. Ticket/Update.html does not redirect to Display.html on submission. It runs and then calls Display.html like any other mason component call using $m->comp (equivalent to <& &>. Display.html then redirects to itself if needed. MandatoryOnTransaction uses Update.html/BeforeUpdate to break out of calling Display.html if there was an error. You would use the same callback. If BeforeUpdate sets skip_update and pushes things into the @$results_ref array ref then control will not be dispatched to Display.html and instead Update.html will redisplay with a message at the top for the user. Simple code that demonstrates this not working, or a MandatoryOnTransaction config where this does not work are needed to continue this conversation. -kevin
pgpZsjIJDgbfC.pgp
Description: PGP signature
-- RT Training London, March 19-20 and Dallas May 20-21 http://bestpractical.com/training
