Enhanced Requests experience - Source configurations

[Mike S1]

Now that we've converted over to the Enhanced Requests Experience, let's see what we can do with it. First up are source configurations. This is from the July 2025 quarterly release for Employee Center.

Let's open up the Source Configuration record for HR Cases and see what the settings are. As these records are added to the Source Configuration table, we're basically blending each new type of tasks into the filtered tabs of the portal widget. What are some of the options available for these records?

1. Portals - A Source Configuration can be applied to all portals, or you can select them from a list.
2. Filter - This had access to any fields on the HR Case table to use in filtering. For example, if I wanted to only show 401k related cases, that could be added as a filter.

In theory, you could have 2 sources for a single table to control what portion of the data goes where. I tested by setting up two records for HR Case, one for Dental services and another for 401k services. It didn't seem to work that way on the widget as it only displayed Dental records on ESC. There are active and order fields on these records included in the call by the query, but still only one set of records showed up in the widget.

The next three options determined how the cards were displayed

1. Title field - The primary line on the card below state and last updated date.
2. Description fields - You have a the ability to add 2 fields here. Fields get a maximum of a row and a half of card space before being truncated.
3. Portal page - What page the card links to when clicked

So a setup like this:

Would look like this and link to hrm_ticket_page:

[Vegard S]

Don't forget the most critical part, adding the tables to the Filter definitions (sn_ex_sp_request_filter_config) table, which functions as a primary filter. 

For example, the View Filter record contains the Tabs that will appear, and those again contain the different tables we want to include. The Created for you record must contain the tables with the primary base filter as well. 

[MeghaB]

Hi @Mike S1 , I am trying to use this 'Enhanced Requests Experience filter' capability on a custom table that extends [cmdb_ci] table, in a custom page in Employee Center

Filters needed are Manufacturer | Location etc

Inspite of the restriction that the table has to be a child of task table- else the table wont be available for Request Filter creation, I have been able to create the Filters, on my custom table which does not extend task table.

What I am looking for to understand is:

a. Had this been an extension of Task table- the records would have come under my 'requests' menu in Employee center- upon which the filters could have been applied to.

b. But here, since these records of my custom table- cant appear as a task, under myrequests in Employee Center. Is there a way to apply 'Enhanced Request experience filters' outside of myRequests menu in employee center?