[rt-devel] Scrip feedback
bradleyb at uw.edu
Tue May 28 18:41:14 EDT 2013
On Tue, May 28, 2013 at 1:47 PM, Kevin Falcone
<falcone at bestpractical.com> wrote:
> On Tue, May 21, 2013 at 12:14:29PM -0700, Bradley Bell wrote:
> One concern is that RT's Scrips were never intended to be synchronous
> and if we ever move to an asynch model, then pushing messages to users
> would be harder/impossibler.
> Regarding your lifecycle condition suggestion, have you seen
I just saw that the other day. It does look useful, but I decided to
make my own extension, with api wrappers and a custom lifecycle,
because my needs are fairly specific. Feedback is provided both in the
api and using callback for purely informational things.
The project right now is a basic asset reservation system. Anyone
who's interested can check it out here:
I welcome feedback of any kind.
Classroom Support Services | University of Washington
035 Kane Hall | Box 353095 Seattle, WA 98195-3095
p 206.543.9900 | f 206.685.7892 | www.css.washington.edu
More information about the rt-devel