ITSM Simulator Task 3 - Configure mandatory fields on an incident formについて(Rome)

[kim62]

お世話になっております。下記、ITSMのSimulatorで求められている1,2番について実行完了したのですが、検証すると完了ができないですが解決方法について分かる方いらっしゃいましたらご教授ください。※エビデンスは添付します。

In order to have more accurate data for reporting and trend analysis, certain data points should always be mandatory on an incident record. This will also help with more accurate routing and resolution work. 

Additionally, we need to ensure that an incident task does not get lost and is always assigned to an individual once it has been moved from the New state.

Tip: We do not want to impact any of these fields that appear on other record types. How might you use a dictionary override to make these mandatory on incident records only?

1. Set the following fields to be mandatory AT ALL TIMES for incident records:

  - Caller, Category, Subcategory, Configuration item, Assignment group and Short description.

2. Using a UI Policy, make the Assigned to field mandatory for all States values except "New" or "Canceled" 

[Anil Lande]

Hi,

You can use data-policy and make all fields mandatory true. Data policy can be allied to work on both database and UI level.

If you just want to make these fields mandatory on forms then you can use UI policies.

Create UI policy without any condition and add UI policy actions with mandatory true.

The screenshot you have shown is making Assigned-to mandatory when state is new, you have to update the UI policy action, Make Mandatory checkbox false.

Thanks,

Anil Lande

[Zengame]

お世話になります。

Now Learning上のITSMコースでの事象であれば、Now LearningでのCase起票すると
・課題を正しく設定していてValidateがうまくいかない場合は、Validateになるようにしてくれます
・課題を正しく設定できていない場合は、どういう問題があるかを教えてくれます
のどちらかで解決できるかなと思います。
#正しく設定しているのにValidateがうまくいかないというのは何度か遭遇してます。

[jay_mcc]

This is the least useful post I've ever seen.