Enterprise Modelling to create Application Services/Service Instances

SimonO375140483
Tera Contributor

yesterday

I hope someone can clarify whether I am doing something incorrect or just ServiceNow screwing with me.  I am attempting to model Business Application and a number of Service Instances (Application Services) using the Enterprise Modelling functionality.   This is currently in our Dev instance where we are running Zurich with Enterprise Modelling Common version 3.8.0 and Enterprise Modelling and Visualizing ver 6.8.0. 

When I add a new CSDM Application Services (Service Instance) item to the diagram and create a new item I fill in the prompted details (just name for speed).  As this is a new item the diagram needs to be Reviewed and Committed. Once committed the new Application Service is not created as an Application Service (csdm_app_services table), but as a Business Service (in the cmdb_ci_service table), we can change the Service Classification by this really has no effect as the Service is created in the wrong table AFAIAK.  Following this method, then blocks the creation of the Depends On/Used By relationship between these two entities. 

Can someone explain the difference between these two different 'Application Services', why we have two different methods of creating, and which type of Application Service should we be using. 

Is this a Bug in the Diagramming module or has something changed in how / where Application Services and now created since they have been reclassified into Service Instances. 

Thanks for your responses

Simon

0 Helpfuls
  • 204 Views
3 REPLIES 3

yogesh41
ServiceNow Employee

yesterday - last edited 3 hours ago

Hi,

 

Your observation is correct and technically it is not bug in EA Diagramming either. 

 

The Service <cmdb_ci_service> Service Classification has default value as "Business Service". That is the reason newly created record from diagramming commit flow has service classification as "Business Service".

 

One quick workaround is to set appropriate Service Classification value while creating new records from diagramming.

1. Navigate to EA Workspace > Setup > Entity Configuration 

2. Search record with name as  "Application Service.."

3. Update "view" value as "apm_services" so it required fields will be available in side panel to update.

 

This will ensure that "Service Classification" can be updated while creating new Application Service from diagramming. 

Application Service creation form with apm_services viewApplication Service creation form with apm_services view

 

I agree with you that this experience is restrictive to achieve end to end business solution. I will take it as feedback for product for permeant fix. 

 

Yogesh

0 Helpfuls

SimonO375140483
Tera Contributor
In response to yogesh41

yesterday

Yogesh,  Thanks for the proposed solution. I have attempted to change the Entity value on the Application Service (Service Instance), entity configuration to apm_services. But the field is reporting that it cannot find 'apm_services'. Is this a version specific solution ? We are currently running Zurich  with Enterprise Modelling Common version 3.8.0 and Enterprise Modelling and Visualizing ver 6.8.0

 

Thanks Simon

0 Helpfuls

yogesh41
ServiceNow Employee
In response to SimonO375140483

3 hours ago

Hi,

I have updated the instruction as below, workaround is to set required view name for the Application Service entity. This will make sure required fields will be available in side panel form view. 

Here are the instructions 

 

1. Navigate to EA Workspace > Setup > Entity Configuration 

2. Search record with name as  "Application Service.."

3. Update "view" value as "apm_services" so it required fields will be available in side panel to update.

 

Yogesh

0 Helpfuls