<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=big5">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [rt-users] using approvals in RT3.0</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>1) Create a global (or not) template. This template will be used to create "approval tickets".</FONT>
<BR><FONT SIZE=2>Name it as you want, and but the text between the "--------" below in "content" section.</FONT>
<BR><FONT SIZE=2>----------------------------</FONT>
<BR><FONT SIZE=2>===Create-Ticket: codereview</FONT>
<BR><FONT SIZE=2>Subject: Code review for {$Tickets{'TOP'}->Subject}</FONT>
<BR><FONT SIZE=2>Queue: Approbations</FONT>
<BR><FONT SIZE=2>Type: Approval</FONT>
<BR><FONT SIZE=2>Depended-On-By: {$Tickets{'TOP'}->Id}</FONT>
<BR><FONT SIZE=2>Content: Someone has created a ticket. you should review and approve it, so they can finish their work</FONT>
<BR><FONT SIZE=2>ENDOFCONTENT</FONT>
<BR><FONT SIZE=2>--------------------------</FONT>
</P>
<P><FONT SIZE=2>When fired, this template creates a ticket in queue "approbations" (change it for your queue) of type "approval" and links it to the parent ticket.</FONT></P>
<BR>
<BR>
<P><FONT SIZE=2>2) Create a scrip in your main queue (in order to avoid loops in tickets and approval creation, they should not reside in the same queue). Parameters are :</FONT></P>
<P><FONT SIZE=2>- Condition : On creation</FONT>
<BR><FONT SIZE=2>- Action : Create ticket</FONT>
<BR><FONT SIZE=2>- Model : using template above.</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>3) Now, if you create a new ticket in your main queue, a children ticket of type approval will be automatically created in the approval queue. you'll see it by clicking on the "approbation" link. You can approve, reject, or do nothing on the ticket.</FONT></P>
<P><FONT SIZE=2>This is a very basic example just to give you a start. You can find more details in Jesse's documentation on which variables can be used in ticket creation to get some more useful behaviour.</FONT></P>
<BR>
<P><FONT SIZE=2>Blaise.</FONT>
</P>
<BR>
<BR>
<BR>
<P><FONT SIZE=2>On Tue, Mar 25, 2003 at 10:53:13AM -0500, Chris Hardie wrote:</FONT>
<BR><FONT SIZE=2>> Can anyone offer any pointers (okay, step-by-step instructions would be</FONT>
<BR><FONT SIZE=2>> nice too :) for getting approvals working?</FONT>
</P>
<P><FONT SIZE=2>(Not much a pointer but a heads-up)</FONT>
</P>
<P><FONT SIZE=2>I'm currently busily implementing an alternative UI set for RT,</FONT>
<BR><FONT SIZE=2>and just finished the Workflow editing part, which saves the</FONT>
<BR><FONT SIZE=2>admin from hand-editing the Create-Ticket templates; it also sets</FONT>
<BR><FONT SIZE=2>up the CreateTicket actions automagically.</FONT>
</P>
<P><FONT SIZE=2>A screenshot is available at <A HREF="http://aut.dyndns.org/tmp/workflow.jpg" TARGET="_blank">http://aut.dyndns.org/tmp/workflow.jpg</A></FONT>
<BR><FONT SIZE=2>and the code lives in <A HREF="http://p4.elixus.org/depot/RT/104/" TARGET="_blank">http://p4.elixus.org/depot/RT/104/</A>. I'll be</FONT>
<BR><FONT SIZE=2>de-chinesify the UI in the next week and hopefully merge the</FONT>
<BR><FONT SIZE=2>functionality back to the 'canonical' UI (if time allows), which</FONT>
<BR><FONT SIZE=2>will then be available at our development branch snapshot:</FONT>
</P>
<P><FONT SIZE=2> <A HREF="http://p4.elixus.org/snap/rt.tar.gz" TARGET="_blank">http://p4.elixus.org/snap/rt.tar.gz</A></FONT>
</P>
<P><FONT SIZE=2>Note that this is a branch, not a fork -- the tree merges from Jesse's</FONT>
<BR><FONT SIZE=2>main tree at every point release, and merges upstream periodically.</FONT>
</P>
<P><FONT SIZE=2>Thanks,</FONT>
<BR><FONT SIZE=2>/Autrijus/</FONT>
</P>
</BODY>
</HTML>