Record producer submitted within an Order Guide via Service Portal redirects to a page with no information about the submitted requestIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms After submitting a record producer with the SC Order Guide widget, the user is redirected to: https://[instance-name].service-now.com/sp?id=requests However, this page does not contain info about the newly submitted request, and thus the user does not know whether the ticket was submitted successfully or not Release All Cause One of the causes may be that the record producer(s) in the order guide is linked to a custom table or any other table besides the OOB Incident table. After submitting an order with the OOB SC Order Guide widget, there are only two possible scenarios in which information about the newly submitted items will be displayed. The first one is if submitted items came from sc_cat_item table. The second is if the order guide is used in a record producer linked to the OOB Incident table. Resolution While this may fall outside of scope of technical support to assist with, customers can code new logic in the SC Order Guide widget controller to redirect to a page containing information about the newly submitted record from a custom table.