There are three different environments that service now provides:
1. Dev Instance : Used for development, Unit testing, Developer works on the Dev Instance.
2. Test Instance : For Testing (Client testing or Testing Team). Usually requested for a client sign off in the instance so that the changes can be moved into production instance.
3. Prod Instance : The changes are moved during the change window depending on the release cycle.
--> Everything in ServiceNOW is stored in the tables.
--> Users are all stored under sys_user table. Sys_user is a system table.
--> All the tables in ServiceNOW have two names
1. Logical name (sys_user) (Navigate from the application navigator using the sys_user.list)
2. Display name (Users table).
--> End user do not have any roles.
--> ITIL user has the knowledge (process owner) of ITIL(Incident, problem, change etc.,)
-> Anything related to the list (under the configure go the column headings and do a right click)
-> Anything related to the form (create a new record to open form and then right click to configure)
-> To remove the new button and add a new record by double ,,,,, to make this change go to list control and check - Omit new button and List edit insert row.
-> Modules are convenient links under the application menu. They can link to different
kinds of features, such as filtered lists, record-creation forms, reports, surveys, and much
more.
-->
UI policies are client-side logic that governs field behavior and visibility on forms.
ServiceNow automatically generates client-side Javascript that the browser executes to enforce policies on the form being displayed. Each policy has a condition that must resolve as true to be executed. Policies determine the following field attributes and behaviors:
- Make the field mandatory
- Show or hide the field
- Make the field read-only
