Incident eBonding best practices

[Merit71]

Dear Team,

We are implementing incident eBonding between two instances one which is heavily customized (incident form). Looking for some guidance and best practices.

- Use of staging table or integrate with incident form?

- I. Hub spoke or scripted rest?

- Recommended authentication type?

- Any other suggestions/best practices?

Thank You.

[Community Alums]

Hello @Merit71 ,

U can use:

1. U can create custom solution using Integration Hub capabilities.

2. OR use OOTB solution of eBonding which is "Service Bridge".

Thanks.

[Ankur Bawiskar]

@Merit71 

Pointers from me

- Use of staging table or integrate with incident form? -> NA

- I. Hub spoke or scripted rest? -> Depends, if you don't want custom API response you can use Ebonding spoke, if heavy customization in API response, then go with scripted rest api

- Recommended authentication type? -> OAuth 2.0

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Merit71]

Hi @Ankur Bawiskar ,

Thanks for the response, just re-visiting the point 1 (use of intermediate staging table or import set table).

Will it be easier to manage and control incoming incident data (such as priority & other reference fields mappings) before pushing to actual Incident form?

[Ankur Bawiskar · Accepted solution]

@Merit71 

if the choice values etc are same then no need of import set table

but if heavy manipulation is required then I will suggest import set or scripted rest api

If my response helped please mark it correct and close the thread so that it benefits future readers.