I've been playing around with this as well. Any chance to get an idea of a workflow to be build with this? One way I could imagine doing is by trying to build our workflow into ITSM 2.0. That would then probably translate to:
<div><br></div><div>- Create change</div><div>- Add WO: build the change</div><div>- Add WO for approval: one WO for each CAB member that needs to approve</div><div>- Add rest of the WO&#39;s describing the work to be done</div>
<div>- Add PIR WO</div><div>- Add condition: if WO status of the build change WO is closed, set Change state to Pending Approval, and set WO state of approval WOs to ready (?)</div><div>- Add condition: if Change state of all WO&#39;s for approval are set to accepted, Change state should be set to approved.</div>
<div>- Add condition: as soon as one of the other WO&#39;s changes state to &quot;in progress&quot; set the change to &quot;in progress&quot;.</div><div>- Add condition: as soon as all WO&#39;s change to &quot;closed&quot;, set Change state to Pending PIR</div>
<div>- Add condition: as soon as Pending PIR WO has been closed, the Change can be closed too. </div><div><br></div><div>However, there are some issues here:</div><div>- I hope the complete logic can be saved in templates as well :-)</div>
<div>- The approval WO&#39;s are a bit... uneasy. When I can already set the CAB, it would be cool if there was some mechanism to automagically request approval from each CAB member.</div><div>- Use Ready or Accepted for the WOs?</div>
<div>- Not sure how I can do a successful close/failed/... depending on the PIR.</div><div><br></div><div>BUT, then again, maybe I&#39;ve totally overseen something here. I&#39;d really be happy if somebody could give an example of such a workflow. And I guess, I&#39;m not the only one :-)</div>
<div><br></div><div>Thanks,</div><div>Arthur</div>