Configure mandatory fields on an incident form (Task 2) ITSM Simulator

[Guichard C]

I've completed Part 1 but don't know where to start to complete Part 2 for the IU Policy

[Musab Rasheed]

Hi,

In your UI policy for Assigned To use 'Not one of operator' for 'New' and 'Closed' like I have used. Mark my answer as correct

[BrandonForet]

Do you happen to know the steps in completing the first part as well?

[Miguel Santiago]

Hi Brandon, 
The first part can be a little misleading.  Because the "Caller and Short description" fields are already set to mandatory. This is due to the UI Policy -Fields set to mandatory for all states.

That being said, the first inclination is to add the "Category and Subcategory" fields to the UI policy.  That works in theory, however it does not pass the task validation.

Give this solution a try:

• Configure the dictionary and set "Mandatory" field for the "Caller, Category, and Subcategory" fields because these are not related to the base Task table.
• Configure the dictionary for the remaining "Configuration item, Short description and Assignment group" fields with 'Dictionary Overrides'.   

  Cheers!

  Mark my answer as correct if that helps.

[rukshanakir]

Hey hi, I tried to use the 'is not one of' operator but I'm unable to select both new and cancelled within a single condition. Could you please help me with this. Did anyone encounter such a problem?