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.
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
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.
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.
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.
I just checked the eBook Pg 148, It literally states you CANNOT apply to all form views. And you CAN set categories as visible. B is the correct answer. I'm positive
According to the article,
https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/product/service-catalog-management/concept/c_ServiceCatalogUIPolicy.html
The option "C. Setting a catalog category to visible" cannot be defined or set through a Catalog UI Policy. The other options are supported by the policy:
A. "Setting a variable to mandatory" - UI policy can indeed make a variable mandatory.
B. "Apply a requirement to all form views" - UI policies can control the behavior of variables on forms.
D. "Setting a variable to read-only" - UI policies can also set a variable to be read-only.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
SHAJENEK
Highly Voted 1 year, 7 months agoservicemain01
Most Recent 1 month, 1 week agoHoneybadge
1 month, 2 weeks agohristiyant
11 months agoHoneybadge
1 month, 2 weeks agoSudarshan_Puppala
1 month, 2 weeks agoghzelmed
2 months, 1 week agoSudarshan_Puppala
5 months agosk_snow
5 months agoteleblazer
8 months, 3 weeks agohristiyant
11 months agorajesh_pavan_varma_kalidindi
1 year, 1 month agosubhadeep_ghosh
1 year, 3 months agoLaurys
1 year, 4 months agosubhadeep_ghosh
1 year, 4 months agoHoneybadge
1 year, 3 months agosubhadeep_ghosh
1 year, 4 months agoHoneybadge
1 year, 3 months agolyon301
1 year, 4 months agobrownbear324
1 year, 4 months ago