ORIGINAL AIR DATE: Thursday, June 18, 2015 | 10:00 AM (PDT) | 1:00PM (EDT)
Join John Chapin on Thursday, June 18, 2015 as he discusses Domain Separation in this session to examine the basics that include:
Global Scope
The Top domain
Process Domains
Data Accessibility
Process Inheritance
John Chapin has been in IT for over 20 years. Prior to joining ServiceNow he migrated from Remedy to ServiceNow while working for a financial firm in New York city.
Over 4 years ago he came to ServiceNow as an Engagement Manager in Professional Services. John is currently a Senior Solution Consultant at ServiceNow, working with our MSP partners.
We have to really check if separating the Model / Model Categories table would be a desired solution since it will involve lots of testing to check functionality. SN does not suggest to domain separate OOB tables so I am really worried about this once.
2nd Option to have model per customer basis to ease the things, but that will create redundant entries in the system.
3rd Option to check if changing cost and status field on model have any impact on software licenses costing. If software licenses costing is independent of "cost" against model, then we might not have to worry.
I also like the idea of Vanilla implementation with limited customization.
