Request for Best Practice – Capturing Shipper Name and Tracking Number from End Users via Portal

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2025 06:48 AM
Hello all,
I’m seeking guidance on how to effectively collect shipping details (shipper name and tracking number) from an end user via the ServiceNow portal.
Use Case:
I have a scenario where a standard end user, with basic portal access, needs to provide shipping information, such as a UPS or FedEx tracking number, for an item they’ve sent as part of an open request (for example, a return or an asset shipment).
Key Question:
What’s the recommended approach for enabling users to submit this tracking data through the portal once the request has already been submitted and is in progress?
Considerations:
- The user is the requestor of the original item/request.
- The shipping information may be required after the initial submission.
- Ideally, this input would populate a field tied to the existing request record.
- We want to avoid granting users full access to forms or back-end records.
Has anyone implemented something similar, perhaps via a catalog task form, flow, or UI action exposed in the portal?
I’d appreciate any insights, best practices, or examples you’ve found effective.
Thanks in advance!