The CreatorCon Call for Content is officially open! Get started here.

How to indicate an application entry is a 'component' (module) of an application

SuziQ
Giga Contributor

What is the best practice on how to indicate an application entry is a 'component' (ie module) of an application?

Example:  ServiceNow has an application entry.  Components could be ServiceNow CMDB, ServiceNow HR, ServiceNow IRM etc.

 

We need to ensure that integrations such as IRM, TRPM, SPM, BCM are able to see the details of an application component (module) but realize that this is a component and it is clear what the main application CI entry is.

 

In my past experience we used a specific relationship to signify something was a component of another app. 

--The Bus App had a 'consumed by ' relationship to its downstream Calculated Application Service(s), then there was a downstream 'containment' relationship to the Calculated Application Service for the 'component.  That 'containment' relationship between 2 Calculated Application Services indicated something was a component.  

While this was something that made sense to the CMDB team, we found this to be confusing to our customers since they were always expecting everything to be hanging directly off the Bus App whether it was a component or not.  We were considering hanging all the Calculated App Services off the Business App and adding a checkmark to signify it was a component.

 

How have other folks been handling this?  What would be the best practice to ensure we don't affect other key integrations relying on application data.

 

0 REPLIES 0