Custom Table global scope and licensing

[Anirban Roy]

Hi Community,

I want to create a custom table in global scope for some requirement. I want to know if there are any drawbacks in not creating the table in scoped application in terms of licensing and subscription model taking into picture.

To elaborate a bit, as per servicenow subscription management, customer subscribes or buys various subscriptions and each subscriptions will contain limited entitlements. Finally those entitlements are connected with the custom tables, which helps in monitoring and tracking the custom table subscription usage and compliance check.

Please help me in drawing out the pros and cons. 

Regards,

Anirban

[Anirban Roy]

Hi Mark,

I have marked the response as 'answered' now. 

I have a small follow-up query though, what is a general recommendation -

i) create the custom table with itil role to fit it under ITSM licenses, OR
ii) create the custom table with custom role(s)/ acls, to fit it under custom app engine 

Regards,

Anirban

[Mark Roethof]

A nice question! A few weeks back I had a similar question for myself while building a custom app for a customer.

Normally I would have gone for option II. Though, because under the customer's contract this would have meant they would need to purchase new licenses for a minimum amount of tables for custom app engine.
Therefore, I don't like it, we went for adding the itil role to the custom tables. As well as the custom roles. By adding the itil role, suddenly the tables are counted for the ITSM licenses. Where the customer still did have room for new custom tables within their licensing.

Kind regards,
Mark
2020 ServiceNow Community MVP
2020 ServiceNow Developer MVP

---

LinkedIn
Community article list

[Anirban Roy]

Thank you Mark. This is helpful and makes sense.