Application
|
A collection of files and data that deliver a service and
manage business processes
| ![]() |
Application Scope
|
Protects applications by identifying and restricting access
to application files and data
| ![]() |
Private
|
By default, all custom applications have a ________ scope that uniquely identifies them and their associated artifact with a
namespace identifier
| ![]() |
Global Scope
|
Special application scope that identifies applications developed prior to application scoping or applications
intended to be accessible to all other global applications
| ![]() |



________ applications can bypass scope protections, allowing
them to:

-Read records
-Run API requests
-Create Configuration records
|
False
|
True//False: Assume an application scope, sn_my_app,exists. Scripts from other application scopes can never
delete records from tables in the sn_my_app scope.
| ![]() |
All application scope,
This application scope
|
The application Access settings for a table are:
| ![]() |
True
|
True//False: An application owns its tables and determine
whether other application can access resources from them
| ![]() |
DO NOT
|
Developers DO/DO NOT create application file records
directly from the Application File table
| ![]() |
contextual
|
The platform is a ____________ development environment that displays the currently selected application, identifies the scope of every application artifact, and prevent any
changes that violate the access settings for an application
| ![]() |
Application Access Settings
|
____________________ is similar to ACLs in that it allow you to restrict access to certain resources, but instead of restricting tables and records from users - they restrict
application resources from other applications
| ![]() |
Runtime Access tracking
|
-Allows administrators to manage script access to application resources be creating a list of script operations and targets that the system authorizes to run
-Options: None, Tracking, Enforcing
| ![]() |
Cross-scope privilege record
|
-Runtime access tracking uses __________________________ to determine which script operations and targets the system allows to run
-System creates this when: Runtime Tracking is set to
"Tracking" or "Enforcing"
| ![]() |
Script API, Web
Services
|
Runtime access points
| ![]() |
Application List
|
Allows application developers to view and select
applications
| ![]() |
Application Picker
|
Allows application developers to view and select the
application where their changes apply
| ![]() |
False
|
True//False: Removing a field from a form using the Form
Designer deletes the field from the database table.
| ![]() |
Application Creation
|
-Start from scratch
| ![]() |
options
|
-Create a custom application
| |
-Start from a template
| ||
-Start from an existing service
| ||
-Start from global
|
Start from scratch
|
-Create an empty application
-Good for application that only use one configuration record, such as workflow or script-based application
| ![]() |
Create a custom
application
|
-Create an application with UI and data elements
-Good for applications that require UI elements and tables
| ![]() |
Start from a template
|
-Create service management application
-Good for applications that need to track the status of requests or task-driven records
| ![]() |
Start from an existing service
|
-Convert an existing service to an application if service creator is active
-You may want to convert successful services into full application to utilize application features like contextual
security, data or UI Policies, UI actions, and auditing
| ![]() |
Start from global
|
-Create an application in the global scope
-Required role: admin
-Set the system property glide.app.creator.global to true
| ![]() |
Studio
|
Made up of:
-Header
-Application Explorer
-Content Frame
-Status Bar
| ![]() |
Source Control Integration
|
Allows application developers to integrate with GIT source control repository to save and manage multiple versions of
a sub-production instance
| ![]() |
source control
|
Linking to an application to ___________ allows application developers on sub production instance to:
-Import applications from a GIT repository
-Pull and apply changes from a GIT repository
-Commit all local changes on a instance to a GIT repository
-Create tags to permanently link to a given version of an application
-Create branches to maintain multiple versions of an application simultaneously
| ![]() |
Operations
|
-Import from Source Control
-Link to Source Control
-Edit Repository Configuration
-Apply Remote Changes
-Commit Changes
-Stash Local Changes
-Switch Branch
-Create Branch
-Create Tag
-Manage Stashes
-Create Repository:
-Create credentials:
-Grant Access to Repository
| ![]() |
Sharing methods
|
-Publish internally to company instances
-Publish to the ServiceNow Store
-Publish to an Update Set
-Push to team development instances
| ![]() |
Team Development
|
Supports parallel development on multiple, sub-
production ServiceNow instances
| ![]() |
Team Development
|
Provides the following features:
-Branching operations, including pushing and pulling record versions between instances
-The ability to compare a development instance to other development instances
-A central dashboard for all Team Development activities
| ![]() |
Team Development
|
Good for:
-Providing change management across multiple instances
-Allowing multiple developers to work on applications
-Organizations that have access to several sub-production instances
Future considerations
-Works best when each development team has access to a dedicated development instance
-Requires developers to manually merge colliding changes
-Works only for instances owned by the same organization
| ![]() |
Update Sets
|
Good for:
-Storing changes to a baseline or installed app
-Storing and applying a particular version of an pp
-Producing a file for export
Future Considerations:
-Manually create update sets to store a particular application version
-Use update sets to deploy patches or changes to
installed apps
| ![]() |
Application Repository
|
Good for:
-Installing and updating apps on all company instances
-Automatically managing applications update sets
-Restricting access to applications to the same company
-Deploying completed applications to end users
Future considerations
-Consider publishing to ServiceNow Store
-Allow installation of and update to latest version only
-Use Update Sets to store prior application versions
| ![]() |
Local Changes
|
_________ table tracks which customized record have current versions that exist on the development instance but not on
the parent instance
| ![]() |



-Matched an exclusion policy
-Private properties
-Collisions
-Previously resolved collisions
-Skipped
|
Team Dashboard
|
Provides a central place to manage all Team Development
activities on your development instance
| ![]() |
Team Development instance hierarchy, grant
access rights
|
To enable parallel development on multiple sub- production instances, administrators can set up the __________
and __________ for developers
| ![]() |
False (uses version
records)
|
True//False: Team Development uses Git to manage
versions
| ![]() |
Credentials for Team Development access
|
-Access to the Team Development application
-Right to register a remote instance
-Right to push changes to the parent instance from the developer instance
-Right to compare to a registered remote instance
-Access to the Code Review Requests module
| ![]() |
Access to the TeamDevelopment
application
|
Credential: A user with the admin role on the instance you are accessing
| ![]() |
Right to register a remote instance
|
Credential: One of the following
-A user with the admin role on the instance you are registering
-A user with the teamdev_user role on the instance you are
registering
| ![]() |
Right to push changes
|
Credential: One of the following
| ![]() |
to the parent instance
|
-A user with the admin role on the parent instance
| |
from the developer
|
-A user with the teamdev_user role on the parent instance
| |
instance
|
No comments:
Post a comment