Seamless Integration

What We’ve Got Here Is Failure to Communicate – Part 2

In Part 1 of this article, I delved into Inbound and Outbound design considerations. Now, in Part 2, I’ll cover considerations for a true eBonding type integration as well as other general tips I’ve learned through the years building integrations. eBonding Design Considerations and Good Practices As mentioned previously, the example I’m working from is a bi-directional application to application integration, meaning that the systems are integrating application records throughout the lifecycle of that application’s workflow. For example, an Incident in system X that integrates with a ServiceNow Incident and exchanges updates throughout the life of both incidents, regardless of…
Integration puzzle piece

What We’ve Got Here Is Failure to Communicate – Part 1

Good Practices for Designing Integrations in ServiceNow Captain: You can have the easy way, Luke... Or you can have it the hard way... It's all up to you. - Cool Hand Luke If you work in a ServiceNow environment in 2023, it’s more than likely you’ve got it integrated with other systems. Given ServiceNow’s place in the market, it’s unlikely that an instance is running in an environment small enough or segregated enough to not need to be integrated with other systems. At the very least, you’re likely getting your core data from somewhere outside of ServiceNow, and hopefully not…