Is there such a thing as a 'gold build' or 'golden client' in ServiceNow?

[kc99]

Hello,

I wonder if anyone would like to share any ideas they have as an MSP with a single instance using domain separation.

In the past I have worked with SAP which uses the concept of a 'Gold/Golden Client' that would be used as a reference for new client copies as required.

My line manager is of the opinion that we should be able to create a 'gold build' customer that will then be used as a reference customer for copying when new customers come on board.

We already have several customers (each with a   new company and domain) as an MSP and I still haven't yet seen an easy way to set up a new customer using another customer as a reference.

Am I missing something here? - should we simply use the OOTB setup as the base (ITIL compliant) reference site?

As far as I can see we will always have to setup the new domain, service catalog , groups, roles, ACLs as well as amend forms, lists and provide a bespoke CMS ESS site where required.

If there are any other MSP ServiceNow developers who could share their thoughts on what they do when they take on a new customer I would be most grateful,

many thanks,

Keiron.

[bernyalvarado]

You can accomplish that by having one or more update sets the ones you can have as your base ("golden") build for your customers.

Thanks,

Berny

[kc99]

Thanks for the quick reply Berny.

I guess we should have asked for more advice from ServiceNow before we started on the MSP route.

We've also lost a couple of the original members of our SN development team which is why I have to ask so many questions.

When you refer to update sets, how could we use these to set up a new customer as the update sets would all reference objects in the base 'golden' client?

Thanks,

Keiron.

[bernyalvarado]

You're welcome Keiron. This base update sets are often build from a OOB/fresh instance and are portable (meaning that they're not dependent on object which sys_ids could change). OOB objects/tables in ServiceNow hold the same sys_id across instances and that's why this approach works.

Thanks,

Berny