Hi guys<br><br>I&#39;m trying to identify a solution about following &#39;scenario&#39;:<br><br>- Change lifecicle management: I&#39;m modelling a workflow based on a specific workorder (type &#39;approval&#39;) to modify the change&#39;s state on<br>
the workorder&#39;s state change. Modifying this workorder would be available only to itsm-change-manager group.<br><br>-  I would introduce operational  workorder (type workorder), linked to a change, where describe the operation needed to implement the change<br>
<br>-
 The last workorder type would be assigned to a &#39;basic&#39; agent (only itsm-change group
 assignment), but that basic agent would be able to change the 
agent&#39;s assignment,<br>   routing the work to another collegue.<br><br>So if I 
enable some &#39;basic&#39; agent to take the workorder (or change the 
assignement) listing their id into the 
ITSMWorkOrder::TakePermission::List parameter, they will be able to take
 <br>also the &#39;approval&#39; workorder, but I would avoid it, of course.<br><br>I&#39;m
 investigating ACL&#39;s to solve the problem, but after read the documentation, I didn&#39;t find 
any reference to change or workorders, it seems only ticket&#39;s attributes could be used.<br><br>So I&#39;d like to know if I can use ACL on change and 
workorders or not, or if someone has an alternative solution to meet my 
requirements.<br><br>best regards<br clear="all"><br>-- <br><div style="font-family:verdana,sans-serif"> <b><i><br><font size="4"><span style="color:rgb(51,51,255);font-family:trebuchet ms,sans-serif">Stefano Boccanera</span></font></i></b></div>

<br>