Best Approach for Service Catalog requiring Database Lookup before end user submission

[ShaliniJain]

Hi All,

Submitting this question to seek help on the best approach for one of the Service Catalog Use Case I am building

Use Case - Tranform ecisting legacy application into Service Catalog Request Form . As per requirement, User is allowed to proceed for Submission when they don't already have access on a particular server. To identify whether the user has access, there is an inventory of 100K records (which is 20 years old inventory).

Post Service Request Submission also, we need to create a new entry and store for future purposes.

So, I am confused what is the best approach here -

1. Should I migrate all 100K records to ServiceNow and create new records here? 

2, Or should I keep inventory outside of ServiceNow and do fetching and update of records in real time and in Flow Designer?

I am thinking to avoid ServiceNow because ServiceNow is not a database and hence do not want to create dependency on ServiceNow. 

The only Pro I see of using ServiceNow is everything will be in one application but then will it be good architecture given such requests can come in future also from other service owners?

Looking forward to some guidance from fellow architects and developers who have implemented such scenarios?

Thanks & Best Regards,
Shalini Jain

[Ankur Bawiskar]

@ShaliniJain 

Yes when you use ServiceNow it will act as single repository for everything

now whether you  need to use ServiceNow as a platform depends on your customer and their decision.

My thoughts

1) Use Import set capability to migrate the 100k legacy data which helps in raising the catalog item for correct user.

2) don't use real-time checks with external system. you can have this using some schedule like once in a week or month etc as per your requirement

If my response helped please mark it correct and close the thread so that it benefits future readers.