Custom Scoped Application
Overview
Application scoping protects applications by identifying and restricting access to application files and data. This document walks through the key operations for creating and managing custom scoped applications in ServiceNow.
- Navigate and search for in ServiceNow Studio
- Click on Create Application UI action.
- Provide Name and in the advanced setting select scoped.
- Provide required roles.
- Give the table name.
- Another way click on CREATE NEW TABLE
- We can create new table which is extended from task
If we select from list we can create the table from here
- Another way click on CREATE NEW TABLE
- Navigate to studio and click on create new.
Select table from the data model.
Goto scope=list view
- Goto Data model ⇒ table
- Configure related list
- Since table extended from task so it is always we need to edit in GLOBAL scope
Open assigned to field.
You will see the field which is extended from the task table.
Goto file and click on create file .
- See my table and other table
- create=form which table you want this form
- After creating ⇒ see form design
- We know there are two ways to configure a form .
- a.form design
- b.form layout
Do changes as per your requirement
Also verify after you apply those changes.
You will see the form which we have designed.
We can create module for that purpose search for application menu on the navigation pane.
- On the related list click on New ui action.
- Make sure your module is in the global scope.
- You are able to create module in global scope because of application access =All application scope
- Now GOTO è module work_assignment è Configureè Table
You will see it is accessible from All application scope only.
Now change to this application scope.
- Changed scope to global.
- Open application.
And Create module.
You will see there are no matched found.
Next, create script include in Global application.
Check in Background script
Output
You will see your script include with same scope.
Check in Background script-same scope.
Output
Also, Check in global scope.
Output
Open the application.
See From here we can publish in update set
Scoped application caller tracking and caller restricted
- caller tracking –After calling script then get access, it will track data.
- caller restricted- After calling script then restricted
- Application -work assignment, caller restricted Associable from=all application scope
- SCRIPT INCLUDE created in work_assignment application and now we will write background script on Advanced work_assignment.
- Function is caller restricted.
Output
- To remove restricted access.
- Goto =application Application administration = true.
In the Related section you will see restricted caller access privileges
- Now check in advanced work_assignment scope
Output
- Create 2nd script include
- Application scope should be –work_assignment.
- Caller Access -caller tracking.
- And accessible from=all application scope.
You will see the scope is advanced work_assignment in background script.
Output
Navigate and type sys_scope_privilege.LIST
Custom Application Form fields
Field name | Type | Description |
Name | String | The display field for the package |
Version | String | Identifies the latest version of the package in dot decimal notation |
Scope | String | Identifies unique application scope [x_companyCode_shortAppID] See properties Glide.appcreator.company.code |
Application administration | Boolean | When checked system administration will be preventing from accessing the application |
Can Edit Application in Studio
| Boolean | Allow user to edit application file in studio |
Run time access tracking | Choice
a. Tracking log-access the system and allows script to execute | Script interaction with other application is controlled by the system runtime access system
Use Runtime Access Tracking to manage script access to resources from other applications
|
Restrict Table Choices | Boolean | Restrict design time access to table outside application scope |
Licensable | Boolean | Licensable or not |
Subscription requirement | Choice
a.Monitor b.Required | Subscription requirement for usage of this package |
Subscription model | Choices
a.NA b.fulfiller /requestor c.procedure d.capacity e.mixed f.Application in use | Subscription model is defined here
|
Subscription | Reference | Refer to license_details |
Menu | Reference | Refer to sys_app_application This application primary menu where default table module will reside |
User role | Reference | Refer to sys_user_role Role required for end user to access this application and its table |
Short description | string | Short description for application |
logo | User_image | Logo for application |
Guided Setup | Reference
| Refer to gsw_content Guided Setup to start when to application is installed/upgraded |
Related links
- Manage Collaborators
- Collaboration descriptors let you assign, manage, and monitor permissions for each application or across multiple applications consistently
- Collaborators -a person who works together with others for a special purpose
- Navigate and search for collaborators.
Related link -click on manage collaborator.
See user can do following thing
Move restricted to tracking
- It will simply just move Whatever configuration we have done on custom scoped application restricted to tracking
- Move tracking to restricted
- It will simply just move Whatever configuration we have done on custom scoped application tracking to restricted
- View License Definitions
- It will redirect to sys_app_license_defn_list
Publish to Update Set
- Publishes all the code from an app to a newly created updated set that can be used to transfer the app between instance.
Grant app administration to all admins
- Grand a role that are required for the admins to be able to grand any of the applications role
Enable Session Debug
Scan Application
Convert to Application Repository Mode
- When your applications are placed in the Custom Applications table [sys_app], you can’t upgrade them directly through the Application Repository. This procedure helps you do a one-time conversion when you want to migrate deploying your applications using the Application Repository.
- After you convert the application, it is no longer enabled for development on the instance where the conversion is performed. For a scoped custom application, all associated records in the Customer Updates table are deleted for this application.
After this see application
Resync Collaboration Permissions
- Refresh delegated development permission for collaborators
