Categories:Child Document
by Rohit |
on February 2, 2023 |
0

UI Policy

  1. ServiceNow Application Developer
  2. ServiceNow Scripting Objects
  3. ServiceNow Scripting API
  4. GlideRecord – Create, Read
  5. GlideRecord – Update & Delete
  6. Popular ServiceNow API Methods
  7. UI Action – Server Side & Client Side
  8. UI Policy
  9. Client Script – OnLoad
  10. Client Script – OnChange
  11. Client Script – onSubmit
  12. Scripting Best Practices
  13. Client Script Best Practice
  14. Client Script Requirement
  15. Business Rule Requirments
  16. Inbound Action
  17. Requirement Sheet
  18. Only Admin should be able to see Resolution Information tab
  19. From P3 & P4 user can’t derectly set to P1 but from P2 they can set P1
  20. Directly P1 Incident can’t be created
  21. Child Incident should close once parent Problem close
  22. Populate list type of fields in servicenow in Incident Form
  23. For Critical Priority, font will be bold and background will be red
  24. Create a field on Incident form called Expected Data, if incident move to Pending this date will be add 7 days from current date

UI Policies are used to dynamically change the behavior of form elements like fields, related lists, and sections based on predefined conditions.

Purpose of UI Policy:

  1. Hiding a Field Based on a Condition
  2. Making a Field Mandatory
  3. Setting a Field as Read-Only

Requirement Example:

  1. Make configuration item is mandatory on an incident in progress state.
  1. Service field mandatory when incident state set to on hold.
No Tag

Total Views: 1351

No responses yet

Leave a Reply

Your email address will not be published. Required fields are marked *