Figure 6

2.1.5 Configure ServiceNow Instance Records

​

Blueprint AI is designed to be self-contained within a single instance and uses the context of the instance it is installed on to develop update sets. However, if development needs to occur using the context of another instance—such as Development, Test, or Sandbox—instance records can be used to facilitate communication between Blueprint AI in Production and those external instances. This feature is especially useful for partners who need to manage and coordinate development across multiple client environments from a central Blueprint AI instance.

​

2.1.5.1 Mandatory Instance Record

1.   Login as a user with the “x_blsog_blueprint.admin” role to the ServiceNow Production instance
2.   Navigate to All > Blueprint AI > Administration > ServiceNow Instances

3.   Click “New”

4.   Fill out the form as follows:

      a.   Name: [Instance Name]

      Note: The instance name identifies the specific ServiceNow instance and must match exactly—including case sensitivity—the instance name in the URL. It is typically a unique identifier or custom domain name associated with your organization’s ServiceNow environment. For example, in the URL https://instance_name.service-now.com, the instance name is instance_name.
      b. Type: Choose instance type (Production, Test, Development, Sandbox)

      c.  Active True

​​

2.1.5.2 Optional Instance Record(s)

​

1.  Login as a user with the “admin” and “x_blsog_blueprint.admin” roles to the ServiceNow Production instance
2.  Navigate to Organization > Users
3.  Click “New” and create a new user with the following fields:
        a.  User ID: blueprint
        b. First name: Blueprint
        c.  Last name: AI
        d.  Active: true
        e.  Web service access only: true
        f.  Internal Integration User: true
        g.  Roles: admin and snc_read_only
4.  Click “Submit”
5.  Click “Set Password”
6.  Click “Generate”
7.  Click “Save Password”    
8.  Once the user has been created, navigate to All > Blueprint AI > Administration > ServiceNow Instances
9.  Click “New”
10.  Fill out the form as follows:
        a.  Name: [Instance Name]
             Note: The instance name identifies the specific ServiceNow instance and must match exactly—including case sensitivity—the instance name in the URL. It is typically a unique identifier or custom domain name associated with your organization’s ServiceNow environment. For example, in the URL https://instance_name.service-now.com, the instance name is instance_name.
         b. Type: Choose instance type (Production, Test, Development, Sandbox)
         c.  Active True
         d.  Username: Enter the username of the user previously created.
         e.  Password: Enter the password for the above user.
11.  Click on ‘Validate Connection’. [Figure 7]
12.  Go back to the “ServiceNow Instances” list view. [Figure 8]

​​

Figure 7

3. Additional Configuration

​

3.1 Blueprint Approvals in Other Portals​

If users access approvals through other ServiceNow portals—such as the Service Portal or Employee Service Center (ESC)—they may encounter Blueprint AI approval records that they are not authorized to view or act upon. This can lead to confusion or an inability to complete the approval process as intended.

To ensure that Blueprint AI approval records are only reviewed and actioned within the Blueprint AI Portal, ServiceNow administrators should implement a filter on the sysapproval_approver records displayed in other portals. This filter should exclude Blueprint-related approvals by leveraging conditions based on record type, table, or other identifying attributes unique to Blueprint AI.

By isolating Blueprint approvals to the designated portal, you maintain a clear separation of responsibilities, reduce approval errors, and provide a streamlined experience for both approvers and requesters.

​

3.2 Enable Test Management 2.0 Integration

Blueprint AI includes optional support for Test Management 2.0, allowing users to automatically generate test cases alongside requirements, technical designs, and solutions. This integration enables platform teams to accelerate quality assurance efforts by embedding test coverage into the development lifecycle.

Notes: 

• This step is only necessary if your organization is using or desires to use Test Management 2.0 within your ServiceNow instance.

• Test Management 2.0 may require an additional license depending on your ServiceNow subscription. Please consult your ServiceNow account representative or review your current entitlements to confirm access before installing or enabling this application.

​

3.2.1 Install Test Management 2.0

1.  Login as a user with the “admin” role to the ServiceNow Production instance
2.  Navigate to System Applications > All Available Applications > All [Figure 1]
3.  Search for “Test Management 2.0”
4.  Click the “Install” button
    Notes:

• The ServiceNow progress bar may appear to be stuck or remain at the same percentage for several minutes. If this happens, please continue to wait.

• You can choose to “Run in Background” if you prefer to perform other tasks while the installation is in progress.

5.  Once the install is finished, click the “Close” button
6.  To ensure the application has been installed, refresh the browser and search for “Test Management 2.0” in the application navigator. [Figure 12]

4. Appendices

​

Glossary of Terms