The CreatorCon Call for Content is officially open! Get started here.

ITSM Simulator Lab

cjv
Tera Expert

Hello,

 

Hoping someone can point me in the right direction for this lab I'm going crazy:

 

Change approvers should have all necessary information on the change request at the time of submission, including:

   - Requested by

   - Configuration item

   - Impact

   - Description

   - Planned start date

   - Planned end date

1. In addition to any fields already mandatory, the fields above must also be mandatory any time a change request is not in a New or Canceled state.

Hint: No existing configuration should be modified to satisfy the requirement, create your own UI policy.

Tip: Review the existing UI policy named Mandatory - Assignment Group for clues on how to get started!

 

All the fields are mandatory and still receiving the same error.

 

Any assistance would be greatly appreciated.

1 ACCEPTED SOLUTION

cjv
Tera Expert

Solved 🙂

Conditions only work for State is not one of New and Cancelled.

 

View solution in original post

7 REPLIES 7

cjv
Tera Expert

Solved 🙂

Conditions only work for State is not one of New and Cancelled.

 

Thivagar
Tera Contributor

Crazy, shouldn't it work for 'is one of' as well? 🙂

AdeyemiB
Tera Contributor

Hey there!

The solution is no longer visible. Please share if you can.

Thanks.

Jean-Lou
Giga Guru

Thanks a lot, I could get my head around this after half a day, was ready to give up...

 

As they say to use 'mandatory - Assignement group" I did an insert and stay and the condition is the other way around...

 

They should accept both solutions is one of or is not one of....

 

Really helpful thanks