Storing of service providers data in ServiceNow
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
We have a requirement to store service providers data captured from RITM and its catalog task variables into a structured data model within ServiceNow, this data is critical to support the following objectives,
- For capturing fulfilment related information from respective service providers, including Project name, environment, client ID, project details such as account type, email, user roles.
- To provide end to end automation of cloud application provisioning, covering application setup, including its users, roles, project IDs, client IDs and other related attributes.
- To prevent any duplicate service request submission by performing necessary data validation on subsequent requests against existing stored data.
- To support all dashboarding, reporting and other operational visibility requirements
We have considered these below options for solutioning this,
- To store the data outside of ServiceNow and accessing it dynamically via Remote Table APIs for data validation during form submission. (to segregate the custodian of data not to be ServiceNow)
- Leveraging on demand REST API calls to retrieve data as and when required in form validation.
- Reviewing out-of-the-box (OOTB) options, such as user & groups table.
- Creating new scope table’s in ServiceNow App engine scoped tables, for proper data isolation within our scoped app.
Would like to know if there is any OOTB cmdb data model that could accommodate this requirement; for storing cloud application provisioning data, including its users and roles and other related information's.
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
@Vicky6 There is no OOTB CMDB data model to accommodate this requirement. Relying on Remote Table/REST API for validation will be prone to latency. Also, User and group table aren't the suitable tables either for this purpose.
Your best bet will be creating a new scope table in ServiceNow.
Hope this helps.