ServiceNow, Inc. · NYSE:NOW

ServiceNow — Technical Presentation (April 2023)

93 slides from ServiceNow's technical presentation, April 2023

1. Slide 1: Integrations: Definition and Design Workshop Presentation

   Integrations Definition and Design Workshop Presentation Speaker Name Asset number: 0002016 April 2023

2. Slide 2: User instructions

   User instructions PLEASE REMOVE THIS SLIDE BEFORE PRESENTING • Who: This deck is built for delivery of a ServiceNow product/capability. The delivery of this deck may be undertaken by Customers, ServiceNow Partners and ServiceNow Expert Services. Assigned Business Process Analysts, Business Process C

3. Slide 3: User instructions

   User instructions PLEASE REMOVE THIS SLIDE BEFORE PRESENTING • How: – Customers (self–implementation) – use the deck as it is or add to your corporate template. Alternatively, utilize individual slides to enhance your internal communications – Partner or Co-Delivery implementations - use the deck an

4. Slide 4: FAQs

   FAQs PLEASE REMOVE THIS SLIDE BEFORE PRESENTING • How can I provide feedback on this asset or other parts of Now Create? Now Create has a number of feedback buttons throughout the portal. When opening an asset, before you download it, there is a feedback button in the bottom right of the screen. Cli

5. Slide 5: Adding your Logo

   Adding your Logo PLEASE REMOVE THIS SLIDE BEFORE PRESENTING To provide credibility to ServiceNow documents, the ServiceNow and your logo should be visible, but not domineering. Click View > Slide Master > Slide > Select Page 1 What to do: • Download logos from the Brand Center site. • Scale logos to

6. Slide 6: Deleting the PartnerLogo

   Deleting the PartnerLogo 1 PLEASE REMOVE THIS SLIDE BEFORE PRESENTING 2 . . What to do: 1. Click ‘View’ at the top of the screen 2. Click on ‘Slide Master’ - this takes you to the 3 slide master for the slide you are looking at . 3. Scroll up to Slide 1 in the master view. You may have to pull out t

7. Slide 7: Housekeeping

   Housekeeping © 2023 ServiceNow, Inc. All Rights Reserved. 7

8. Slide 8: Housekeeping

   - Example - adapt to situation Housekeeping - *add breaks as necessary* • Start and finish on time • Breaks will be taken as needed; approximately every two hours • Return from breaks and lunch promptly. If late, catch-up during breaks or after Workshop • Points needing greater detail will be record

9. Slide 9: Agenda

   Agenda © 2023 ServiceNow, Inc. All Rights Reserved. 9

10. Slide 10: Agenda

    Update this slide Agenda based on your workshop content Introductions Integration planning • Key implementation steps Integration needs • Integration attributes • Integration capabilities Integration design • Connectivity and data flow • Integration leading practices Web services (REST and SOAP inte

11. Slide 11: Introductions

    Introductions © 2023 ServiceNow, Inc. All Rights Reserved. 11

12. Slide 12: Introductions

    Introductions • Customer project team – Name, Title – Name, Title • Partner project team – Name, Title – Name, Title • ServiceNow project team – Name, Title – Name, Title © 2023 ServiceNow, Inc. All Rights Reserved. 12

13. Slide 13: What to expect

    What to expect • Workshop activities: – High level recap on integration concepts – Review of available features and functions in the application for implementation consideration – Understand ServiceNow recommendations and best practices – Team-based alignment and decisions on how to integrate Servic

14. Slide 14: Guiding principles

    Guiding principles • Use baseline features and functions define the basis for all discussions • Focus on configuration, not customization • Challenge current practice • Do not break current business; look for opportunities • Eliminate pain points • Be lean, be agile – embrace change! © 2023 ServiceN

15. Slide 15: Expectations of participants

    Expectations of participants • Technical participants are expected to have ServiceNow Platform Administration certification, and have general experience and knowledge with integrations. • Workshop participants are selected to be champions for the decisions – be the agents for change! • Make clear de

16. Slide 16: Integration planning

    Integration planning Key implementation steps © 2023 ServiceNow, Inc. All Rights Reserved. 16

17. Slide 17: Key implementation steps

    Key implementation steps Preparing to implement integrations with ServiceNow 1. Define integration needs 2. Design integration 3. Implement integration 1. “What” we need to implement 2. “How” we need to implement • Defining our integration needs will provide a high- • Designing our integration will

18. Slide 18: Integration needs

    Integration needs Defining “what” we need to implement

19. Slide 19: Integration types

    Integration types External/3rd Party Presentation Systems UI L ev el Inte • Other Applications grat • Databases ion • ERP • CRM Business Logic Process Integration • Data Warehouse Client Side/Server Side • Inventory ion gr a t • Messaging Systems a I nt e Dat • Transaction Systems • LDAP Data • CMDB

20. Slide 20: Integration types use cases

    Integration types use cases Description: UI Level Integration UI Level integrations are commonly Presentation used to display information on the user interface to support the end-user in processing the current record. Description: Business Logic Process Integration Business logic integrations are co

21. Slide 21: Short introduction: Data Flow Diagrams

    Short introduction: Data Flow Diagrams • A Data Flow Diagram (DFD) maps out the Notation Symbol flow of information for any process or system • It uses four different symbols to show data Process ServiceNow inputs, outputs, storage points, and routes (or our system) between each destination • The da

22. Slide 22: Integration type: Data

    Integration type: Data The following examples will provide requirements as user stories that capture the need for integration on the left and the related data flow diagram on the right. Import users from directory Directory User data system System ServiceNow As a system administrator I want to be ab

23. Slide 23: Integration type: Business logic

    Integration type: Business logic Retrieve updates on tickets As a Process Fulfiller I want to be able to retrieve all updates to related tickets from the external ticketing system in order to keep all ticket-related Ticket data Ticketing information synchronized. ServiceNow System Updates to Ticket

24. Slide 24: Integration type: Presentation

    Integration type: Presentation Translate ticket content to English Translation Translation data As a Process Fulfiller ServiceNow System I want to be able to see translations of any ticket content in English if the content has been created in a different language in order to quickly understand it. R

25. Slide 25: Combining all integration types in a context diagram

    Combining all integration types in a context diagram • A Data Flow Diagram can dive into progressively more detail by using levels and layers, zeroing in on a particular piece. Level 0 is also called a Context Diagram • Level 1 would provide a more detailed breakout like the previous examples Direct

26. Slide 26: Integration attributes

    Integration attributes Building blocks to define an integration © 2023 ServiceNow, Inc. All Rights Reserved. 26

27. Slide 27: Integration attributes support high-level definitions

    Integration attributes support high-level definitions • An integration can be described on a high level with a common set of attributes to further define its goal and technical design • The flow of data is one of the attributes that can be used to provide insights into a given integration. The data

28. Slide 28: Integration attributes: Data flow

    Integration attributes: Data flow # Protoc Data flow Trigger Timing Execution Message Translator Security Records ol Bidirectional Unidirectional (Inbound) Unidirectional (Outbound) © 2023 ServiceNow, Inc. All Rights Reserved. 28

29. Slide 29: Integration attributes: Trigger

    Integration attributes: Trigger # Protoc Data flow Trigger Timing Execution Message Translator Security Records ol Bidirectional Manual Unidirectional Schedule (Inbound) Unidirectional Process (Outbound) driven Event © 2023 ServiceNow, Inc. All Rights Reserved. 29

30. Slide 30: Integration attributes: Number of records

    Integration attributes: Number of records # Protoc Data flow Trigger Timing Execution Message Translator Security Records ol Bidirectional Manual Single Unidirectional Schedule Batch (Inbound) Unidirectional Process Delta (Outbound) driven Event Full © 2023 ServiceNow, Inc. All Rights Reserved. 30

31. Slide 31: Integration attributes: Timing

    Integration attributes: Timing # Protoc Data flow Trigger Timing Execution Message Translator Security Records ol Bidirectional Manual Single Real time Unidirectional Near real Schedule Batch (Inbound) time Unidirectional Process Delta Scheduled (Outbound) driven Event Full © 2023 ServiceNow, Inc. A

32. Slide 32: Integration attributes: Response

    Integration attributes: Response # Protoc Data flow Trigger Timing Execution Message Translator Security Records ol Bidirectional Manual Single Real time Synchronous Unidirectional Near real Schedule Batch Asynchronous (Inbound) time Unidirectional Process Delta Scheduled (Outbound) driven Event Ful

33. Slide 33: Example integration: User data import

    Example integration: User data import Import users from directory # Data flow Trigger Timing Execution system Records As a system administrator I want to be able to periodically import users from the directory system in order to automatically create a ServiceNow user account for every person within

34. Slide 34: Example integration: User data import

    Example integration: User data import Import users from directory # Data flow Trigger Timing Execution system Records Bidirectional Manual Single Real time Synchronous As a system administrator I want to be able to periodically Unidirectiona Near real Asynchronou Schedule Batch import users from the

35. Slide 35: Example integration: Ticket updates (Part 1)

    Example integration: Ticket updates (Part 1) Retrieve updates on tickets # Data flow Trigger Timing Execution Records As a Process Fulfiller I want to be able to retrieve all updates to related tickets from the external ticketing system in order to keep all ticket-related information synchronized. T

36. Slide 36: Example integration: Ticket updates (Part 1)

    Example integration: Ticket updates (Part 1) Retrieve updates on tickets # Data flow Trigger Timing Execution Records As a Process Fulfiller Bidirectional Manual Single Real time Synchronous I want to be able to retrieve all updates to related tickets from the Unidirectiona Near real Asynchronou Sch

37. Slide 37: Example integration: Ticket updates (Part 2)

    Example integration: Ticket updates (Part 2) Retrieve updates on tickets # Data flow Trigger Timing Execution Records As a Process Fulfiller I want to be able to automatically send all ticket updates to the external ticketing system in order to keep all ticket related information synchronized. Ticke

38. Slide 38: Example integration: Ticket updates (Part 2)

    Example integration: Ticket updates (Part 2) Retrieve updates on tickets # Data flow Trigger Timing Execution Records As a Process Fulfiller Bidirectional Manual Single Real time Synchronous I want to be able to automatically send all ticket updates to the external Unidirectiona Near real Asynchrono

39. Slide 39: Example integration: Ticket updates (Combined)

    Example integration: Ticket updates (Combined) Retrieve updates on tickets # Data flow Trigger Timing Execution Records … Bidirectional Manual Single Real time Synchronous Unidirectiona Near real Asynchronou Schedule Batch Send updates to ticketing l (Inbound) time s system Unidirectiona Process Del

40. Slide 40: Example integration: Get translation on demand

    Example integration: Get translation on demand Get translation on demand # Data flow Trigger Timing Execution Records As a Process Fulfiller Bidirectional Manual Single Real time Synchronous I want to be able to automatically send all ticket updates to the external Unidirectiona Near real Asynchrono

41. Slide 41: Example integration: Remote tables

    Example integration: Remote tables Get translation on demand # Data flow Trigger Timing Execution Records As a Process Fulfiller Bidirectional Manual Single Real time Synchronous I want to be able to automatically send all ticket updates to the external Unidirectiona Near real Asynchronou Schedule B

42. Slide 42: Integration capabilities

    Integration capabilities Additional attributes to define what we can use © 2023 ServiceNow, Inc. All Rights Reserved. 42

43. Slide 43: The MID Server

    The MID Server Enable indirect access between ServiceNow and your company network Optional SNMP External Network Devices Credential Storage PowerShell Windows Servers SSH Job Queue HTTPS:443 Linux/Unix Server API Hypervisor MID Server Lightweight Java application CIM that collects data and make Stor

44. Slide 44: Integration attributes: Protocol

    Integration attributes: Protocol # Protoc Data flow Trigger Timing Execution Message Translator Security Records ol Bidirectional Manual Single Real time Synchronous REST Unidirectional Near real Schedule Batch Asynchronous SOAP (Inbound) time Unidirectional Process Delta Scheduled SFTP (Outbound) d

45. Slide 45: Integration attributes: Message

    Integration attributes: Message # Protoc Data flow Trigger Timing Execution Message Translator Security Records ol Bidirectional Manual Single Real time Synchronous REST JSON Unidirectional Near real Schedule Batch Asynchronous SOAP XML (Inbound) time Unidirectional Process Delta Scheduled SFTP File

46. Slide 46: Integration attributes: Security

    Integration attributes: Security # Protoc Data flow Trigger Timing Execution Message Translator Security Records ol Bidirectional Manual Single Real time Synchronous REST JSON ServiceNow Unidirectional Near real Schedule Batch Asynchronous SOAP XML Middleware (Inbound) time Unidirectional Process De

47. Slide 47: Enterprise Service Bus (ESB)

    Enterprise Service Bus (ESB) Description: Advantages: • An ESB acts as an intermediary, facilitating • It decouples systems from each other, which may result communication between ServiceNow and other in fewer changes connected systems • It typically allows integrations with a larger number of • Fro

48. Slide 48: Integration attributes: Translator

    Integration attributes: Translator # Protoc Data flow Trigger Timing Execution Message Translator Security Records ol Bidirectional Manual Single Real time Synchronous REST JSON ServiceNow None Unidirectional Near real Schedule Batch Asynchronous SOAP XML Middleware Basic (Inbound) time Unidirection

49. Slide 49: Integration security

    Integration security • Common concerns – By their nature, integrations allow the movement of data – This makes security teams concerned! • Default position – ServiceNow is hosted in the cloud, not in the customer’s datacenter. But this doesn’t mean it is insecure! ServiceNow is committed to looking

50. Slide 50: Describing Integrations with Attributes

    Describing Integrations with Attributes Presentation Integration Data flow: Inbound Trigger: Manual UI Level Integration #Records: Single Presentation Timing: Time Real Response: Synchronous Protocol: REST Message: JSON Translator: ServiceNow Business Logic Integration Security: OAuth 2.0 Data flow:

51. Slide 51: Define integration needs

    Define integration needs Create a high-level definition for all planned integrations 1. Define integration needs 2. Design integration 3. Implement integration High-level integration definition Practitioner insights: • Create an overview for all planned • Accurate and up to date integration integrat

52. Slide 52: Integration design

    Integration design Defining “how” we need to implement © 2023 ServiceNow, Inc. All Rights Reserved. 52

53. Slide 53: Integration options

    Integration options More support available • ServiceNow application included integration from the integration – Some apps already provide pre-built integrations, such as HR for Success Factors, vendor etc. • ServiceNow Store integrations – Integrations built by ServiceNow or a partner – Examples inc

54. Slide 54: Custom integration assumptions

    Custom integration assumptions An integration has two halves Consider Integration Hub using Flow Designer • Effort will be needed on both sides: On ServiceNow as well the remote system • Flow of Actions, which is a set of steps. These steps can be shared by plugins or scoped • Product specific exper

55. Slide 55: Custom integration assumptions

    Custom integration assumptions The design will be custom and specific to ServiceNow does things differently the customer • It is likely that the remote system will • Customer integration architecture should be need to be adapted to successfully reviewed, with an architect to contribute, integrate wi

56. Slide 56: Scenarios define detailed triggers for integrations

    Scenarios define detailed triggers for integrations # • High-Level definitions give us an Data flow Trigger Timing Execution Records overview of what the integration Bidirectional Manual Single Real time Synchronous needs to do in general Unidirectiona Near real Asynchronou • Scenarios break integra

57. Slide 57: Example scenarios ticket synchronization/bonding

    Example scenarios ticket synchronization/bonding Use Case Use Case Description Ticket is created in After a new ticket is created in ServiceNow the integration ServiceNow ServiceNow will create a new ticket in the 3 rd party system. Ticket is updated, After an existing ticket is updated, resolved or

58. Slide 58: Example Scenarios Ticket Synchronization/Bonding: Typical Implementation Pattern

    Example Scenarios Ticket Synchronization/Bonding: Typical Implementation Pattern Outbound Inbound ServiceNow • Create a REST Message • Create a business rule (server side script) that runs on the Updated New assignment of the task • Create a scripted REST Message Ticket Ticke • Accepts a non-standar

59. Slide 59: Connectivity and data flow

    Connectivity and data flow How is the connection initiated to make data flow? © 2023 ServiceNow, Inc. All Rights Reserved. 59

60. Slide 60: Initiating connections to allow data flow

    Initiating connections to allow data flow • In a default setup, ServiceNow is hosted in the cloud and not in the customer’s Other datacenter. Therefore, the connection must Data be established either directly or indirectly ServiceNow System via the internet • For every data flow in one direction the

61. Slide 61: Inbound, to ServiceNow

    Inbound, to ServiceNow • Communication initiated by another system – Example: Getting data from ServiceNow Other – Example: Creating a ticket in ServiceNow Data ServiceNow System • Used only for REST & SOAP web services – ServiceNow only supports HTTPS (always encrypted) Example: Other systems can s

62. Slide 62: Outbound, to ServiceNow

    Outbound, to ServiceNow • Communication initiated by ServiceNow – Example: Requesting data such as users Other Data from a directory system ServiceNow System – Example: Sending data such as updated ticket information to a 3rd party system. Example: Other systems can request data from other system •

63. Slide 63: Outbound, via MID Server or Through Tunnel

    Outbound, via MID Server or Through Tunnel • MID Server Other – Acts as a proxy for some functions, like LDAP import System Internet and SOAP messages ServiceNow – MID server picks up jobs from ServiceNow instance MID Server to execute – Asynchronous: Works near real time MID Server picks up job fro

64. Slide 64: Integration leading practices

    Integration leading practices © 2023 ServiceNow, Inc. All Rights Reserved. 64

65. Slide 65: Integration leading practices: 1

    Integration leading practices: 1 Know the data owner Synchronize relevant data • Engage with the person responsible for the • Don’t pull in more data than you need - data e.g., Consider delta over full data loads • Extract only relevant data from source systems whenever possible Establish “Single So

66. Slide 66: Integration leading practices: 2

    Integration leading practices: 2 Consider performance Consider Data Security • Execute large integration loads after hours • Adhere to Organization’s security policies or during a non-peak time of day to ensure compliance • Take advantage of staging tables if real-time • ACLs should be set to limit

67. Slide 67: Integration leading practices: 3

    Integration leading practices: 3 Create system properties pages Build integrations as scoped applications • Use properties pages to store attributes (e.g., credentials) for easy transferability • The process to create a spoke is the same between instances and easy maintenance as the process to creat

68. Slide 68: Integration leading practices: 4

    Integration leading practices: 4 Make informed technology decisions Handle errors • Decide carefully as different technical • Log all errors to a centralized location capabilities have their own requirements as • Errors should be classified in separate well as advantages/disadvantages buckets: Techn

69. Slide 69: Integration expectations

    Integration expectations You should conceptually understand the process work that happens in both systems as well as the data required for that work. Some starter questions: Remote system capabilities • What is the target system? Process requirements • What data is available? • How does this data su

70. Slide 70: Example JSON Message for REST

    Example JSON Message for REST { "result": [{ "user_name": "lucius.bagnoli", "name": "Lucius Bagnoli", "email": "[email protected]", "manager": { "link": "<instance>/api/now/table/sys_user/02826bf03710200044e0bfc8bcbe5d88", "value": "02826bf03710200044e0bfc8bcbe5d88" }, }] } © 2023 ServiceNo

71. Slide 71: Example mapping

    Example mapping Source field Target field Format Transformation? Coalesce? Example: Users from Active Directory samaccountname user_name String (< 16 chars) No Yes userprincipalname email String (< 16 chars) No No name first_name, last_name String Split data on space No Example: CIs from Active Dire

72. Slide 72: Design integration

    Design integration Create a design for all planned integrations 1. Define integration needs 2. Design integration 3. Implement integration Integration design elements Practitioner insights: • Most effective planning comes from a discussion around a whiteboard. Create • Do not forget to discuss: list

73. Slide 73: Web services

    Web services Supporting material for REST and SOAP © 2023 ServiceNow, Inc. All Rights Reserved. 73

74. Slide 74: Capabilities overview for REST web services

    Capabilities overview for REST web services Feature Description Integration Hub allows you to easily create reusable actions including (outbound) REST Integration Hub steps and/or use pre-build spokes for your integrations. The Table API allows you to perform create, read, update, and delete (CRUD)

75. Slide 75: Capabilities overview for SOAP web services

    Capabilities overview for SOAP web services Feature Description Integration Hub allows you to easily create reusable actions including (outbound) SOAP Integration Hub steps and/or use pre-build spokes for your integrations. Direct Web Direct web services allow to use a URL query to request any table

76. Slide 76: Example use cases for web services capabilities

    Example use cases for web services capabilities Outbound web service requests use cases Inbound web service requests • General scheduled/real-time requests: • Read-only access to data records – Integration Hub (pre-build or custom – Table API (REST) spoke) using REST web service requests. – Scripted

77. Slide 77: Inbound REST authentication options

    Inbound REST authentication options • Basic Authentication • Two factor authentication – Username and password sent in HTTP – Certain user accounts can be nominated for request. Protected by HTTPS 2FA – Authorization: Basic – A pin is generated using a secret stored YWRtaW46YWRtaW4= locally (admin:a

78. Slide 78: Inbound SOAP authentication options

    Inbound SOAP authentication options • Basic Authentication – Username and password sent in HTTP request. Protected by HTTPS. – Authorization: Basic YWRtaW46YWRtaW4= (admin:admin). – The default, and most common authentication mechanism. – Other options will take longer. • WS-Security – Used in addit

79. Slide 79: Outbound REST and SOAP authentication options

    Outbound REST and SOAP authentication options • Basic Authentication – As discussed previously • Custom, payload-based mechanism – The outbound message is frequently constructed programmatically – A custom token may be generated, but implementation would be project specific • Mutual Authentication –

80. Slide 80: Integration patterns

    Integration patterns Supporting material for integration patterns © 2023 ServiceNow, Inc. All Rights Reserved. 80

81. Slide 81: Describing integrations with attributes

    Describing integrations with attributes Presentation Integration Data flow: Inbound Trigger: Manual UI Level Integration #Records: Single Presentation Timing: Time Real Response: Synchronous Protocol: REST Message: JSON Translator: ServiceNow Business Logic Integration Security: OAuth 2.0 Data flow:

82. Slide 82: Integration patterns

    Integration patterns Integration Pattern Scenario Layer UI Reflecting The UI interface must be automatically updated as a result of changes to UI Integration Data Changes data. Process Integration Request and Reply NOW platform takes an action on a remote system. NOW platform sends a request to a re

83. Slide 83: Pattern – UI reflecting data changes

    Pattern – UI reflecting data changes Scenario: A user sends an email reporting a problem with a hardware. The system is designed to monitor those emails and create incidents based on the email content. The admin team gets the newly created incident updated on their screen automatically. Pattern to C

84. Slide 84: Pattern – Request and reply

    Pattern – Request and reply Scenario: In a global organization, employees can open tickets in their local languages. The Requirement is to translate all the ticket details from the local language to English. Pattern to Consider: Request & Reply Interface to Consider: REST or SOAP Integration Feature

85. Slide 85: Pattern – Fire and forget

    Pattern – Fire and forget Scenario: Each time a user login fails, you want to send a log message from the ServiceNow instance to an ArcSight Syslog server (or another one) inside a customer’s corporate firewall. Pattern to Consider: Fire and forget Interface to Consider: Syslog Probe Integration Fea

86. Slide 86: Pattern – Data push and pull

    Pattern – Data push and pull Scenario: You have another system working as your system of record and you want to use ServiceNow Platform as your system of engagement. Pattern to Consider: Data Push and Pull Interface to Consider: JDBC, ODBC, Data Import/Export Integration Feature/Capability: MID Serv

87. Slide 87: Pattern – Query interface

    Pattern – Query interface Scenario: You want to use ServiceNow as your System of Record and want to build a custom mobile app. Pattern to Consider: Query Interface Interface to Consider: REST API Integration Feature/Capability: Scripted APIs *ServiceNow provides a few API management features to mana

88. Slide 88: Pattern – Batch data processing

    Pattern – Batch data processing Scenario: A customer has decided to use External Data Sources Import Set Table Transform Target Tables ServiceNow Platform and would like to import all their data into ServiceNow. Their JDBC CMDB existing data is sitting in multiple systems: DB, FTP, Spreadsheets, etc

89. Slide 89: Pattern – Instance to instance

    Pattern – Instance to instance Scenario: You have multiple production instances in your environment, and you have a need to synchronize data across these instances. For example, one instance might manage internal applications (your source system) and another manages external customer facing applicat

90. Slide 90: Quick review

    Quick review • What decisions have been made? • Are there any risks? – Which system initiates the connection? – Are any approvals needed? – When is the connection initiated? – Are the right skills in place? – What data is transferred? – What could prevent progress? • What are the next actions? • Any

91. Slide 91: Questions?

    Questions? © 2023 ServiceNow, Inc. All Rights Reserved. 91

92. Slide 92: Thank you

    Thank you © 2023 ServiceNow, Inc. All Rights Reserved. 92

93. Slide 93: servicenow.

    servicenow.

ServiceNow — Technical Presentation (April 2023) on 6ix