Custom request fullfilment process disadvantages?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2024 08:59 PM
One of my client doesn't want request item tables and process.
He came up with an architecture with custom tables extending task table to create a request through custom table.
I was trying to pushback by giving certain reasons like we do not have catalog item table where variables are defined
they saying they will use record producers and map it to custom request table
Can i get any potential risks pointers if we do not use service catalog for request fullfillment process?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2024 01:47 AM
Hi @Kiran Kumar 76 ,
Here are my few inputs:
1. Workflows, flows will also get hampred.
2. You can compare his custom table along with OOTB request table to see how much of devation is. if its minimal then you can try suggest to have those minimal customiztion in OOTB request.
3. OOTB notifcaiton will get impacted.
4. You will face issues while accessing catalog varaibles.
5. It becomes hard to track the assocaiation of REQ, RITM and SCTASKS.
6. And it can be more based on Business..
Try to check whats the intention behind having custom table rather not using OOTB , try to compare and see if we can achive it using OOTB any way with minimal impact and customization. and see whats the main reason for going with custom solution rather OOTB.
I Hope this helps...
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....