Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Contextual development environment release notes

Contextual development environment release notes

ServiceNow® contextual development environment enhancements and updates in the Kingston release.

The platform is a contextual development environment that displays the currently selected application, identifies the scope of every application artifact, and prevents any changes that violate the access settings for an application.

Activation information

Application restricted caller access is inactive by default. To activate application restricted caller access, you can:

  • Activate the Scoped Application Restricted Caller Access plugin (com.glide.scope.access.restricted_caller).
  • Request the Security Incident Response or HR Service Delivery applications. These applications have application restricted caller access active by default.

New in the Kingston release

Application restricted caller access settings
Track or restrict cross-scope applications or scripts that request access to an application or application resource. Using the Restricted Caller Access [sys_restricted_caller_access] table, you can:
  • Track cross-scope requests for access to an application resource.
  • Approve or deny any cross-scope requests for access to an application resource.
  • Allow all scope-to-scope requests, or allow all future requests to all application resources in the target scope.

To activate application restricted caller access, you can:

  • Activate the Scoped Application Restricted Caller Access plugin (com.glide.scope.access.restricted_caller).
  • Request the Security Incident Response or HR Service Delivery applications. These applications have application restricted caller access active by default.

Changed in this release

  • Application Administration:
    • If application administration is enabled for an application, only an application administrator of the target application can delegate developers to the application. If application administration is not enabled, an admin user can delegate developers.

      If you do not want the application administrator to have the admin role, the application administrator can make themselves a delegated developer. Once a delegated developer, the application administrator can perform a subset of administrative tasks without having the admin role, such as accessing files, managing ACLs and roles, and writing scripts.

    • To enable application administration, use the Application Administrator check box in the role record.

Removed in this release

  • The Assignable by field in the role record is no longer in use. To enable Application Administration, use the Application Administrator check box. On upgrade, Application Administrator is selected by default for any role in the Assignable by field.

This site is scheduled for a small content update on Monday, November 19th, between the hours of 3:30pm and 5:00pm Pacific Time (Nov 19 23:30 – Nov 20 1:00 UTC). Acces to this site may be slightly delayed during that time.