'Requested for' user details not getting auto populated through postman ebonding integration request
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
Hi Community,
I have a requirement in a catalog item to Autopopulate 'Requested For' user in a reference variable [EU03] which references to User table. Based on this user I need to autopopulate next two variable fields in the catalog item. i.e Email ID [EU04] and User ID [EU05] of requested for user. And the EU04 and EU05 should change according to the user selected in EU03 field as it user can select any user. For this requirement I'm using 2 catalog client scripts.
This is working as expected in both native UI and portal. But when RITM is raised through postman ebonding request the fields which I want autopopulate are coming empty.
What could be the reason and what is the alternate solution to acheive this requirement? Please provide your valuable inputs.
Onload client script to autopopulate requested for user:
onchange client script to autopopulate email id and user id according to user selection:
#developer #catalogitem #clientscript #requestedfor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10 hours ago
Hi @SumajRajNk
If you are using the Table API through Postman to auto-populate variables, Catalog Client Scripts will not work.
The reason is:
Catalog Client Scripts execute exclusively in the user's browser (client-side). However, REST API calls made through Postman interact directly with the ServiceNow server and do not trigger client-side scripts.
Recommended approach:
If you need to implement validations or custom business logic for API requests, use a Scripted REST API to handle the required logic on the server side.