The 'Requested for' field is not cleared out if the user clicks on 'Cancel' from the Order Confirmation screen.Description<!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } table tr td { padding: 15px; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } hr{ border-top-width: 1px; border-top-style: solid; border-top-color: #cccccc; } ul { list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> In the case where the 'Requested for' field is not cleared out when the user clicks on 'Cancel' from the Order Confirmation screen. Example Scenario: As any user (User A), when you add an item to the cart and click on 'Proceed to checkout, it would give the Order Confirmation screen. At this point, if we click Cancel and add another item to the cart and do Proceed to Checkout, the requested for still shows User B. Release or EnvironmentAll ReleasesCauseThis is expected behavior because, when you change the requested for to User B, if we check for DEFAULT cart in sc_cart table for User A, the requested for gets updated to User B. Until to clear the cart or submit this request, requested for is User B.ResolutionExpected BehaviorAdditional InformationThe same behavior is seen even from Service Catalog.