Exam CIS-ITSM topic 1 question 6 discussion

Correct is B, checked in PDI.

After playing around with Catalog UI Policies on my developer instance (Latest release -Vancouver), I am able to set categories as visible by creating or editing the Catalog UI Policy Actions in the the policy (Hint: must save form first before option is available). Options are Leave alone, True, and False. I DO NOT see an option anywhere to apply the action to ALL form views, These are the options: Applies on a Catalog Item view Applies on Catalog Tasks Applies on Requested Items So correct answer is B. CANNOT

b is the right answer

They propably meant for B to be the correct answer but based on the poor wording im going for C because I cannot figure out a way at all to show and hide catalog categories using a catalog UI policy but for B you can apply on all catlaog Tasks and Requested Item but im sure it applied to all of their views as well but cant remember.

Correct answer is B

According to "IT Service Management Implementation(Washington)" module 4.3 you B is the correct answer; HOWEVER, you cannot set a catalog category to visible through the use of a catalog UI Policy. This a poor choice of answers.

Like UI policies, Catalog UI Policies: • Allow variables to be set to mandatory, visible, or read-only based on defined conditions. These policies work on variables included on catalog item forms and variables displayed through a variables editor on the request, request item, and catalog task forms.- copy and pasted from Ebook pg. 148. There is also a chart for furth explanation that states you can not apply on all form views. Please check out the book and test in your free developer instance.

A Catalog UI Policy in ServiceNow is used to control the behavior of catalog item forms, including making variables mandatory, setting variables to read-only, and applying requirements to form views. However, it does not control the visibility of catalog categories. Catalog categories' visibility is managed through other means, such as user criteria or directly in the catalog category configuration.

Now i am sure it s C. Because UI catalog policy only control variable inside an item. You can not manipulate category with ctalog ui policy. We are not talking about UI policy. For B, while it still possible to assign a UI plicy to a specific view, with catalog UI policy, it s by default applied to all Views, you can't design a specific view as target... So B it s possible with UI calaog policy

A Catalog UI Policy in ServiceNow is used to control the behavior of catalog item forms, including making variables mandatory, setting variables to read-only, and applying requirements to form views. However, it does not control the visibility of catalog categories. Catalog categories' visibility is managed through other means, such as user criteria or directly in the catalog category configuration.

In this section, we have a comparison table between functionality of Catalog UI Policies and UI Policies. Under functionality "Applies on all form views", for UI Policies we have "optional" and for Catalog UI Plicies "NA" (Not Applicable). I could not find any statement on the visibility of category, thus answer B is more probable for me.

B - I don't see a UI config doing ALL views, some views may be custom to someone else

B table on p148 of eBook : "Applies on all form views - Not Applicable" for Catalog UI Policies Still not convinced about the categories though....

Catalog UI Policies only apply to catalogs, Not to forms

Both B and C. Catalog UI Policies cannot be applied to all form views and to set category visible.

it's not a UI policy variable, it says ''category'' visible... you can'dot do that

C is correct - catalog category cannot be manipulated through UI policy According to ITSM Implementation eBook page 148, option B is possible - hence not correct answer for this question.