Service Portal: How to make Incident links show summary page like requests?

[Isaac10]

I am setting up our portal. Out of the box when I use the My Requests widget the links rendered take a user to the summary page. For Incidents I configured the Simple List widget the same way SN has theirs configured in the sample portal. In their portal when I click the link on one of my incidents it takes me to the incident summary page. In my portal when I click the link the browser URL updates but does not go anywhere. Any thoughts?

My assumption is that a page needs to be created to render the content (a page similar to the page requests use) but I don't know how to direct the link to render on a page if I built one. For clarity I'm including the URL slugs below of a request and an incident:

Request (working): ourinstance.service-now.com/portal/?sys_id=7adb2b9813cd2640e7d5ff82e144b041&id=sc_request&table=sc_request

Incident (now working): ourinstance.service-now.com/portal/?id=site_home&sl_sys_id=a38ac044139de6407b88345fd144b009&sl_table=incident&spa=1

In the incident link "site_home" is our index page for this portal. This page is not referenced in the Request link.

Thanks,

Isaac

[Community Alums]

Just to confirm- you created a widget instance (instance of simple list) which points to the Incident table? What value is populated in the 'Link to this page" field on on the form? I set mine to 'ticket', which opens the ticket form. Unless you need a custom view setup, the 'ticket' page should cover the basics.

Cheers,

Tim

[Isaac10]

Hi Tim,

Thanks I did create a widget instance of Simple list which points to the Incident table. Where is "Link to this page"? When click the pencil icon on the widget instance I do not have that option.

[Community Alums]

Navigate to Service Portal->Widget Instances. Find your widget instance in the list. You should see this tab:

Hope that helps!

Cheers,

Tim

[Isaac10]

That makes sense but I don't have that. To my knowledge we are on the initial Helsinki release, could this be an issue that was resolved in a patch? Any idea if this can be accomplished with code in the widget instance?

Thanks