What all information is required for eBonding integration for incident by scripted rest API

Priya Singh 2 2
Tera Contributor

Hello Experts,

I have got a new project in which I need to stop manual incident raising work from our end and from 3rd party end and we have come through best solution as "eBonding", we don't want to do it by Integration Hub/flow designer, we are planning to do it by scripted rest api, and client also wants to do this integration for requests as well. 

 

I need to prepare one PPT in which I need to provide information what all things are required for client end and from our end, I am not sure about it. Please help me with it.

1 ACCEPTED SOLUTION

Gaurav Shirsat
Mega Sage

Hello @Priya Singh 2 2 

here you will find all Details about Implementation of your REST API Ebonding.

https://www.youtube.com/watch?v=D2xyjJHZqBI&list=PLgGgIYwZFdFlqD3SMJzJdgIGku6bY_385

4th video of this series can provide you exact Outbound

Apart from this, when You are Going to have Discussion Workshop with Clients You need to First Discuss Internally amongst your Team as Below :

1) What are the Fields that are in Scope :

Like for us we only Consider below fields for consideration

Short Description, Description, Impact, Urgency, Work Notes, Assignment Group, Caller, Contact-Type, Configuration Item, state, Customer Fields (we have 3), Correlation ITD, Reference ticket, Resolution Code, Resolution Notes, On Hold Reason

2)What are the Fields that are not in scope : SLA,KB Article etc

3) What Priority Ticket is in Scope P1-P2-P3-P4

4) Bidirectional or Unidirectional E bonding is this?

5)What about Attachment if attached to Incident

6)Trigger Conditions : Priority, Assignment Group, Category-Subcategory or any other

7)Details To be send in Outbound as below sample

Field NameCharacter Limit
Short Description255
Description5000
Work Note2000
Impact 
Urgency 
Assignment Group 
External Ticket Number40
State 
Number 

😎 Field Mappings :- Backend Values of State to be discussed as what is your insatnce and what is in Client Instance

9)Priority Mapping : Your P1 to be mapped for clients P1/P2/P3/P4

10) on Hold Values to be set (may be fixed for the client)

Use Cases :

Creation :

when to outbound Incident to client incident, i.e. Trigger Condition and what Primary Value to be Send

Update : 

Any Thing Can Change as Category/Sub Category/ State/ Work Note/ Additional Comment.

Discuss with them what to be done all scenarios.

10) Ask for REST Message, End Point, Instance Credentials, User Profile

 

Thanks and Regards

Gaurav Shirsat

ServiceNow Community MVP

Feel free to reach out on Linekdin

View solution in original post

3 REPLIES 3

Gaurav Shirsat
Mega Sage

Hello @Priya Singh 2 2 

here you will find all Details about Implementation of your REST API Ebonding.

https://www.youtube.com/watch?v=D2xyjJHZqBI&list=PLgGgIYwZFdFlqD3SMJzJdgIGku6bY_385

4th video of this series can provide you exact Outbound

Apart from this, when You are Going to have Discussion Workshop with Clients You need to First Discuss Internally amongst your Team as Below :

1) What are the Fields that are in Scope :

Like for us we only Consider below fields for consideration

Short Description, Description, Impact, Urgency, Work Notes, Assignment Group, Caller, Contact-Type, Configuration Item, state, Customer Fields (we have 3), Correlation ITD, Reference ticket, Resolution Code, Resolution Notes, On Hold Reason

2)What are the Fields that are not in scope : SLA,KB Article etc

3) What Priority Ticket is in Scope P1-P2-P3-P4

4) Bidirectional or Unidirectional E bonding is this?

5)What about Attachment if attached to Incident

6)Trigger Conditions : Priority, Assignment Group, Category-Subcategory or any other

7)Details To be send in Outbound as below sample

Field NameCharacter Limit
Short Description255
Description5000
Work Note2000
Impact 
Urgency 
Assignment Group 
External Ticket Number40
State 
Number 

😎 Field Mappings :- Backend Values of State to be discussed as what is your insatnce and what is in Client Instance

9)Priority Mapping : Your P1 to be mapped for clients P1/P2/P3/P4

10) on Hold Values to be set (may be fixed for the client)

Use Cases :

Creation :

when to outbound Incident to client incident, i.e. Trigger Condition and what Primary Value to be Send

Update : 

Any Thing Can Change as Category/Sub Category/ State/ Work Note/ Additional Comment.

Discuss with them what to be done all scenarios.

10) Ask for REST Message, End Point, Instance Credentials, User Profile

 

Thanks and Regards

Gaurav Shirsat

ServiceNow Community MVP

Feel free to reach out on Linekdin

1 An Introduction of ServiceNow Integration| Rest Integration Part-1 in ServiceNow| Overview Topics are covered in this video - What is ServiceNow Integration Uni-directional & Bi-directional Integration Flow Https Methods Rest & SOAP web services API ServiceNow APIs Inbound & Outbound Integration

@Gaurav Shirsat thank you for resolving all my queries related to this integration.