7.2: Migration and Integration Flashcards
Application Scopes
- Application scoping protects applications by identifying and restricting access to available artifacts and data.
- Applications developed prior to application scoping are in the global scope.
- All custom applications have a private scope that uniquely identifies them and their associated artifacts. 367
367 - 371
Adm ini st rat ors can specify w hat part s of an applicat ion are accessible t o ot her applicat ions from t he cust om applicat ion record and each applicat ion t able record.
For example, suppose t hat you creat e a conference room booking applicat ion in i t s ow n applicat ion scope. By defaul t , t he applicat ion can access and change i t s ow n tables and business logic but not other applications unless you give them explicit permission. 367
The application scope ensures:
- The conference room booking application does not interrupt core services
- Other applications do not interfere with i s normal functioning 367
By default , the application can access and change its own tables and business logic but not other applications unless the receiving application allows access. The application scope prevents naming conflicts and allows the contextual development environment to determine what changes, if any, are permitted. Application developers specify an application scope when they create an application. 367
The global scope is a special application scope that identifies applications developed prior to application scoping or applications intended t o be accessible to all other global applications.
The system adds a namespace identifier to the front of application artifacts such as tables, scripts, and configuration records. 367
System Update Sets
An Update Set is a group of configuration changes that can be moved from one instance to another.
Update Sets allow administrators to group a series of changes into a named set and then move them as a unit.
Every instance of ServiceNow has a default update set, however, admins should use named update sets for moving customizations between instances. 368
An update set i s an XML fi le that contains
- A set of record details that uniquely identify the update set .
- A list of configuration changes.
- A state that determines whether another instance can retrieve and apply configuration changes.
Update set s t rack changes to applications and system plat form features. This al lows developers to create new functionality on a non-product ion instance and promote the changes to another instance. 368
Basically, an Update Set record i s a “point in time” XML snapshot of process records. An Update Set works by writing changes from t racked tables to the Customer Update [sys_update_xml] table.
An Update Set is used to apply changes that have been checked and verified in another instance. When merging multiple Update Sets, if several Update Set s have modified the same object, (for example: the Incident form), the most recent change w i l l be the one moved to the new, merged Update Set . 368
Batch update sets enable you to
group update set s together so you can preview and commit them in bulk. 368
An Update Set i s a container for configuration records. By nav igat ing to Al l > System Update Sets > Local Update Sets, you can create a new Update Set or set an exi st ing one as your current Update Set . Use an Update Set to migrate your code. When an Update Set i s completed, you can t ransfer i t to another instance to move customi zations from development, through test ing, and into product ion. 368
The defaul t update set captures changes made to the instance wi thout adding those changes to any user-created update set s. It i s recommended to avoid using the Defaul t Update Set for mov ing customizations between instances. Instead, use a named Update Set (user-created). 368
What is Captured in an Update Set? Process Records
- Business Rules * Client Scripts * UI Policies * Fields * Forms and Form Sections * Report Definitions * Tables * Views *
List Configuration - Roles * Flows/Published Workflows 369
What is Captured in an Update Set? Data
- New Data Records * Modified Data Records * Tasks * Modified CIs * New Users and Groups * Schedules * Scheduled Jobs * Dashboards* 369
What is captured in an Update Set is typically a customization or a configuration change and does not include changes to data records. For example, update sets track report definitions and related data such as data source, report type, style, and sharing settings. However, the actual data and report out put are not tracked in an update set . These are some examples of w hat i s and w hat i s not captured in an Update Set , not an exhaust iv e list .
NOTE: Data is no t captured in an Update Set . Examples: a new incident or new change record would not be in an Update Set . 369
When complet ing w ork, you may w ant t o move dat a reco rds w ith your updat es. These records can be useful for t est ing or t rai ning. Dat a (such as user reco rds, CIs, o r locat ions) can be mov ed using t he Expor t XML funct ion. 369
