Product area: Requests — Resource selection ("Choose your item" step in request templates)

Current behavior:

When a request template includes a resource catalog (e.g., a hardware selection step like "Choose a laptop computer model"), each item's details open in a small popup window one at a time. The popup shows product photos and a rich-text spec sheet, but the spec content requires scrolling and is not fully visible within the popup's viewable area. Requesters cannot view two or more items side by side, so comparing options (processor, RAM, display, battery, price, etc.) requires manually opening each item's popup, scrolling through it, and trying to remember details from the previous one.

Impact:

This creates unnecessary back-and-forth between requesters and IT/helpdesk staff, as requesters often can't confidently choose between catalog options without extra guidance. It also increases handling time on hardware request tickets, since technicians end up fielding comparison questions that a better self-service view would resolve.

Requested enhancement:

Add an optional "Compare" or grid/table view for resource catalog items within a request template step, similar to a standard e-commerce comparison table. Suggested capabilities:

1. Allow requesters to select two or more catalog items and view their specifications side by side in a single table/panel (no popup, no scrolling between items).

2. Allow admins to define which spec fields appear as comparable columns/rows (e.g., Processor, Memory, Storage, Display, Battery, Price) when building the catalog/resource entries, rather than a single free-text rich description field.

3. (Optional/stretch) Allow basic filtering on the catalog step — e.g., requester selects criteria like "needs cellular" or "budget under $2,000" and the list narrows to matching items — similar to a faceted product filter.

Why this matters to us:

Our hardware request template lets employees choose from several pre-approved laptop configurations. Without a way to compare specs directly, non-technical requesters are left guessing or asking IT for help distinguishing between very similarly named models, which adds avoidable ticket volume and delays for a routine, low-complexity request type.

Environment: 15.2 Build 15290

Happy to provide more detail or screenshots of our current template if that's helpful for your product team to evaluate this.