02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Implementer</strong> and <strong>MKS</strong> Integrity Integration<br />

6 Under the Capabilities tab, you can define state-based capabilities. State based capabilities<br />

allow the check out, promotion, or rejection of members in <strong>Implementer</strong> while an issue is<br />

in a given state.<br />

If the issue state does not allow open change packages, <strong>MKS</strong> Integrity prompts you to<br />

close the issue’s change package before you move any issue to that state.<br />

If an issue state does not allow open change packages, you cannot create new change<br />

packages for any issues in that state.<br />

To display all available state-based capabilities, from the Filter list select .<br />

To display only enabled state-based capabilities, from the Filter list select<br />

.<br />

To define <strong>Implementer</strong> state-based capabilities:<br />

a) From the Filter list, select <strong>MKS</strong> <strong>Implementer</strong> to display only the state-based<br />

capabilities related to this integration.<br />

b) From the list, select the development activities that are allowed while an issue is in<br />

this state.<br />

IMPORTANT If using the <strong>MKS</strong> Source integration as described in “<strong>Implementer</strong> and<br />

<strong>MKS</strong> Source Integration” on page 259, the development state (*TST) must have the<br />

capability Allows open SI change packages to exist.<br />

211

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!