Business Service, Technical Service, Application Service... Oh My.

[bartonj32]

Hello,

It has been a few years since I have been involved in architecture/configuration discussion related to SNOW. Our organization is now looking to move to a new instances in attempts to get back to SNOW best practices. The conversations taking place now are related to Business Services and Technical Services. I am told a lot has changed within SNOW in the past few years. I am trying to get up to speed on the definitions. I have found some posts that are over 8 years old, I found this link on Service and Service Offerings, but most of its links are broken which leads me to believe this is outdated.

I support several ALM application and my main concern is ensure I retain the ability for my users to open access requests, incidents and change requests. I am being told that we will need to create both a business service and technical service to support the above . My applications are of the shelf application (Azure DevOps, Jira, etc.) This does not seem right based on my previous understanding. Does this sound right?

Does anyone have an updated reference on best practices on implementing different services and/or definitions for for the different services 

[Josh Gold]

Hi @bartonj32! I'm from Unito, we're a ServiceNow partner with self-serve, no-code integrations for Azure DevOps, Jira, and ~50 other tools. If you want to share more details with me, I might be able to set up a more precise demo for you, otherwise here's a step-by-step guide on how to sync issues to records with 2-way updates. And here's more general information about Unito's integration for ServiceNow.

It is a paid integration platform, but the price is far below what it would cost to implement those tools with spokes or a custom integration.

Let me know if you have any questions!

[bartonj32]

Josh
I am not looking for no-code integrations, just an answer to a process questions.