Comments on: Overriding the ess Checkout View for Catalog Requests

By: Eric Pace

Eric Pace — Wed, 29 Mar 2017 19:13:24 +0000

This works perfectly! Thank you!

By: Mark Stanger

Mark Stanger — Wed, 29 Mar 2017 00:11:50 +0000

In reply to Eric Pace. Good idea! I just updated the script above to do this. I also made it smart enough to detect whether or not there is only one item in the request. If there is only one it goes to the item view, if there are more it goes to the request view. Give it a test and let me know how it works!

By: Eric Pace

Eric Pace — Tue, 28 Mar 2017 23:06:28 +0000

How about redirecting them to the RITM record that is associated? I understand that many people use them as a one to many, our Request & Request Items are always a 1:1 (we just Catalog Tasks and Variables for our needs)

By: Kim

Kim — Wed, 06 Apr 2016 18:58:14 +0000

This is great — I’ve got it all working except 3/4. My ess page view is named “Self Service” but it seems my end users are being directed to the default view when checking the status of a sc_request ticket. I tried creating a view called “users” and updated the UI page code, but no effect.

By: Yvonne

Yvonne — Wed, 10 Dec 2014 21:15:42 +0000

In reply to Mark Stanger. yes. I did configure as described and when I go order, now it takes me directly to the request page not the order summary.

By: Mark Stanger

Mark Stanger — Wed, 10 Dec 2014 20:19:27 +0000

In reply to Yvonne. I think that's exactly what this solution describes. Have you configured the system as outlined in this article?

By: Yvonne

Yvonne — Wed, 10 Dec 2014 19:58:54 +0000

Hello Mark – I would like my client to see the order summary when they complete their order but when they go to “My Request” and open the request, I would like them to get an ess view of the request. OOTB, they are getting the order status page when they click on the request number and not the ess defined fields.

Thoughts?
~Yvonne

By: Mark Stanger

Mark Stanger — Wed, 09 Apr 2014 12:33:24 +0000

In reply to Simon.

Hey Simon, this should be pretty simple using a standard business rule and an information message that runs on insert of any record to the ‘sc_request’ table. This article may be helpful.
https://servicenowguru.com/scripting/ui-info-error-message-cheat-sheet/

By: Simon

Simon — Wed, 09 Apr 2014 08:12:00 +0000

Thanks Mark. Working great.

What would be a good option to let the users know their request has been submitted? Redirecting the users to the traditional ESS form is great but could sometime be confusing since there isn’t a true confirmation that the request has been submitted. Maybe some text on top of the ESS form or a notification popup stating “Your Request Has Been Submitted”? Can you share how to implement such a confirmation please?

Thanks.

By: Mark Stanger

Mark Stanger — Fri, 31 Jan 2014 13:56:50 +0000

In reply to Arindam Dutta. I haven't looked at that much so I don't know for sure. I don't use wizards as a general rule because I've found them to be buggy in the past. You might ask on the SN community and see if anybody has dealt with this problem already.