Question about SN scoped application mapping within CSDM 5

Tom Sienkiewicz
Giga Sage

8 hours ago - last edited 8 hours ago

Hi SMEs,

 

I am thinking how to best handle the below scenario:

- We've built a scoped app in SN to manage/configure integrations more easily.

- I would not consider this to be a Business App. It does not fulfill any major business capability, EA will not be interested in rationalizing this, it is basically a "utility". It does not have a business/it owner.

- We would like to be able to raise incidents for this utility directly.

- We would like to potentially be creating demands for this utility as well.

How would you recommend to represent this in CSDM 5? My thoughts so far:

1. Just add this as a Technical Offering, then make this available both on INC and Demand. TSO would be connected to platform-level App service and Business App.

2. Add this both as TSO and also create a Product for this (here the issue is, there will not be a Business App to connect this product to).

3. Tried to look into Software Component Models but I don't quite see how this could work. In the end it would still be another Product type.

 

Do you have similar use cases and how do you deal with those?

 

EDIT: forgot to add, hoping for real human replies, not AI.

 

0 Helpfuls
  • 112 Views
1 REPLY 1

AustinN
Tera Expert

7 hours ago

Hello, you would have a ServiceNow Business Application right? In that case I would think it would make sense to build this new tool as an Application Service under your main ServiceNow Business App. That is what we do for scoped apps and OOTB applications (Change, Inc, CMDB, etc.) as they all have different owners than the main support team of the full platform.

0 Helpfuls