Change Request - Mandatory Fields at Assess Stage Using State Model

[Richard T]

Hi

Looking for some advice or suggestions.

We have recently started using the state model for our change requests but I am having difficulty working out how best to make certain fields mandatory at certain stages/times for a Normal Request

When the Change is first logged and at New State, apart from the usual requested by and category etc, we only want Justification to be mandatory and this is fine, easy to do .

However, when the change is moved onto the Assess Stage we want to make implementation plan, backout and test mandatory BEFORE the technical approval takes place. When I use a UI Policy for this the fields all become mandatory the moment the Change hits assess and the only way the requestor can leave the form is with the back arrow. IT also makes the requestor think they have to complete these fields.

Basically, I want to try and avoid the change requestor thinking they have to ensure implementation plan etc is completed when I want it to be the responsibility of the technical approvers.

Am I just over complicating this 🙂

Cheers

Richard

[Anurag Tripathi]

Hi,

Basically how are you differentiating between requester and technical approvers? the latter mostly.

You can ass the condition in your ui policy script(not use ui policy action)

UI Policy condition: State <IS> XYZ

Execute if true script:

If(logged in user is requester)

{

//2 fields mandatory

}

else if(logged in user is technical approver)

{

//Other set of fields mandatory

}

Hope this helps.

-Anurag

[Richard T]

Thanks Anurag

Hadn't thought of that, will give it a go.

Thank you very much

[Anurag Tripathi]

Cool, Please mark my answer correct/helpful if it helps you solve your issue.

[Anurag Tripathi]

Did you try it yet?