[rt-users] Approvals status open->resolved RTx-WorkflowBuilder?

[Richard Foley]

Hi Chia-liang,

Ok, thanks for the reply and the patch to prove your point, even though this 
doesn't work for me.  I believe that the internal approval system is assuming 
certain things about the tickets its handling, such as that the approval will 
be created along with the initial ticket, instead of possibly on an arbitrary 
status change, thus the initial state of the original ticket will not be "new" 
at all, but possibly "pending", or "resolved", or whatever.  As soon as the 
expected sequence of statuses is disturbed, the approval flow appears to fail 
to work as expected.  I think this is going to catch a lot of people out.

Perhaps RTx-WorkflowBuilder will be a more generic solution?

-- 
Richard Foley
Ciao - shorter than aufwiedersehen

http://www.rfi.net/

On Saturday 14 February 2009 02:22:46 Chia-liang Kao wrote:
> Richard,
> 
> 
> Richard Foley <Richard.Foley <at> rfi.net> writes:
> 
> > 
> > Hi Chia-liang,
> > 
> > Ok, so now I've got this:
> > 
> >     if ($passed) {
> >         $top->SetStatus( Status => 'resolved', Force => 1 );
> >         $self->RunScripAction('Notify Owner', 'Approval Ready for Owner',
> >                               TicketObj => $top);
> >     }
> 
> the change seems to work for me.  Here's the change to the test in
> t/approval/basic.t that demostrates the original ticket got set to resolved 
> upon all approval passed: 
> 
> http://fsck.com/~clkao/rt-approval-autoresolve.patch
> 
> 
> 
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com
>

-- 
Richard Foley
Ciao - shorter than aufwiedersehen

http://www.rfi.net/