IT and operations on ServiceNow

Change advisory board on ServiceNow

Runs the weekly change advisory board on the live change calendar: every change with its risk, conflicts and affected services, and the decision written back to the change request.

SCREENSDATA HANDLERSSERVICENOW · READ IN PLACES01 This week's changesS02 Change detailS03 Impact assessmentS04 Board reviewS05 CalendarS06 Change boarddh_change_requestChange requestchange_request · change_task ·sysapproval_approverdh_configuration_itemConfiguration itemcmdb_ci · cmdb_ci_server · cmdb_rel_cidh_incidentIncidentincident · problemdh_employeeEmployeesys_user · sys_user_grmember ·sys_user_groupWRITE BACK TO SERVICENOWChange request → PATCH table/change_request · PATCH sysapproval_approverrows stay in ServiceNow · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the ServiceNow object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
4
objects read in place from ServiceNow
catalogue
6
screens on those rows
catalogue
4 days
to production-grade
estimate
1
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The ServiceNow objects behind each handler

Tables are read in place through the Table API with the integration user's access control lists, so the app sees exactly the records that user may see. The rows stay in ServiceNow.

ObjectRead fromFields the app usesFreshness
Change requestchange_request · change_task · sysapproval_approverchange_request.start_date (start) · change_request.type (type) · sysapproval_approver.state (approval) · change_request.number (number)live through the API
Configuration itemcmdb_ci · cmdb_ci_server · cmdb_rel_cicmdb_ci.sys_id (id) · cmdb_ci.name (name) · cmdb_ci.sys_class_name (class) · cmdb_ci.owned_by (owner)live through the API
Incidentincident · problemincident.number (number) · incident.priority (priority) · incident.state (state) · incident.assigned_to (assigned)live through the API
Employeesys_user · sys_user_grmember · sys_user_groupsys_user.employee_number (id) · sys_user.name (name) · sys_user.department (org unit) · sys_user.title (position)live through the API
The trigger

The start criterion in ServiceNow's own fields

In plain words: A normal change waiting for board approval whose planned start is within the next 14 days.

The criterion runs in ServiceNow through the data handler, so only the matching rows return. The editor shows the rows it selects, and their count, as it is written.

# start criterion in ServiceNow fields
change_request.type = 'normal' and sysapproval_approver.state = 'requested' and change_request.start_date <= today + 14

# the same criterion in canonical fields
{change.type} = 'normal' and {change.approval} = 'requested' and {change.start} <= today + 14
What the app writes back

Through released interfaces

Writes go through the Table API (POST and PATCH). Each call returns the sys_id and number of the record, and the app records both beside the decision. Approvals raised from the app appear in the ServiceNow approval list, so people can act in either place.

ObjectWhat changesInterface
Change requestboard decision written to the approval record; state set to scheduled, deferred or rejected; start and end updated when the board moves the window; note addedPATCH table/change_request · PATCH sysapproval_approver
Acknowledged and logged

Each write stores the identifier ServiceNow returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.

Access and prerequisites

What is in place before the first build

Groups and roles are mapped to Lima access policies once. A change manager sees the same change requests in the app that they see in ServiceNow.

  • An integration user with the table roles for the tables the app reads and writes
  • Access control lists reviewed for the fields the app writes
  • Allowed IP or private connectivity to the instance
  • Assignment groups agreed with the process owner
Register the handlers4 objects from the catalog; each shows its rows at once.
Nearby

This app on other systems, and other apps on ServiceNow

Change advisory board on

Other apps on ServiceNow

Terms on this page

Normal changeA planned change that needs the board's approval; standard changes run by rule and emergency changes are reviewed within hours.
Configuration itemThe record in ServiceNow for a server, database or application, with its relations to other items and to services.
Read in placeThe rows stay in ServiceNow; the handler sends the filter and the columns and ServiceNow returns the matching rows.
Questions

Does this app copy data out of ServiceNow?

The screens read through handlers that leave the rows in ServiceNow. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.

What does ServiceNow need to allow?

The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.

Can I run it on another system as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, and the app's other system pages show them.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.