- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi everyone, I’m building a custom Employee Travel Request Management application to deepen my ServiceNow platform skills. My current architecture plan is to build the custom backend tables first and then expose them to users through a record producer published on the Employee Center. Before I dive into the configuration, I would love to know if this standard Service Catalog architecture is still the best practice for this use case, or is there a more efficient approach you would recommend?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @AdaOkoye,
Your proposed approach is good. Using custom tables for storing travel request details and a Record Producer to collect employee inputs through Employee Center is a standard and suitable approach for this requirement.
I would recommend the following architecture:
- Create a custom table: Create an Employee Travel Request table to store details such as employee, destination, travel dates, purpose, and approval status.
- Create a Record Producer: Use a Record Producer to collect the required information from employees through Employee Center and create records in your custom table.
- Configure Flow Designer: Create a flow to handle manager approvals, notifications, and subsequent activities based on the approval outcome.
- Use UI Policies and Client Scripts: Apply field visibility, mandatory checks, and client-side validations wherever required.
- Configure ACLs: Make sure employees can access only their permitted records, while managers and administrators have the required access.
- Add reporting: Create reports or dashboards to track pending approvals, approved requests, and travel request statuses.
- Configure SLAs: Create SLA definitions for different stages of the travel request, such as manager approval and request processing. Define appropriate start, pause, stop, and breach conditions to track whether requests are completed within the expected timeframe.
My recommendation: For a custom application like Employee Travel Request Management, I would prefer a custom table combined with a Record Producer and Flow Designer rather than using the Incident or another existing task table unnecessarily.
This approach keeps the application modular, easier to maintain, and scalable for future enhancements.
Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards,
Tarun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @AdaOkoye,
Your proposed approach is good. Using custom tables for storing travel request details and a Record Producer to collect employee inputs through Employee Center is a standard and suitable approach for this requirement.
I would recommend the following architecture:
- Create a custom table: Create an Employee Travel Request table to store details such as employee, destination, travel dates, purpose, and approval status.
- Create a Record Producer: Use a Record Producer to collect the required information from employees through Employee Center and create records in your custom table.
- Configure Flow Designer: Create a flow to handle manager approvals, notifications, and subsequent activities based on the approval outcome.
- Use UI Policies and Client Scripts: Apply field visibility, mandatory checks, and client-side validations wherever required.
- Configure ACLs: Make sure employees can access only their permitted records, while managers and administrators have the required access.
- Add reporting: Create reports or dashboards to track pending approvals, approved requests, and travel request statuses.
- Configure SLAs: Create SLA definitions for different stages of the travel request, such as manager approval and request processing. Define appropriate start, pause, stop, and breach conditions to track whether requests are completed within the expected timeframe.
My recommendation: For a custom application like Employee Travel Request Management, I would prefer a custom table combined with a Record Producer and Flow Designer rather than using the Incident or another existing task table unnecessarily.
This approach keeps the application modular, easier to maintain, and scalable for future enhancements.
Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards,
Tarun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you.