Issue in Order Guide - Two Step Checkbox (Portal view)

[amit170]

I want to have my order guide as two step in service portal instead of 3 steps. So I have checked The "Two Step" CheckBox in the Order Guide. System Properties Updated : "glide.sc.checkout.twostep" - true; "glide.sc.sp.twostep": false. It is working in Native View, however, in Portal, not working.

[pavani_paluri]

Hi @amit170 ,

glide.sc.checkout.twostep = true → this makes the native Service Catalog use the 2‑step checkout.
glide.sc.sp.twostep = false → this tells the Service Portal to keep using the 3‑step checkout.
That’s why it works in native view but not in the portal.
Set system property glide.sc.sp.twostep to true.
Clear the cache (cache.do) or test in a fresh browser session.
Make sure the “Two Step” checkbox is also enabled on your Order Guide.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[amit170]

Tried with the same, still not working. 

[pavani_paluri]

Hi @amit170 ,

Check the widget on your Service Portal catalog item page
Go to the portal page that displays your catalog item.
Confirm whether it’s using SC Catalog Item or SC Catalog Item Deprecated.
Replace the deprecated widget
If you see “SC Catalog Item Deprecated,” switch it to SC Catalog Item.
This widget supports the two‑step checkout flow.
Clear cache and retest
Run cache.do or test in a fresh browser session.
Open the catalog item in Service Portal, click Order Now, and you should see the two‑step confirmation popup.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[amit170]

For this Order Guide, the system is utilizing the standard Service Catalog SC Order Guide, not the deprecated version. Each individual catalog item is also using the out-of-box (OOB) SC Catalog Item widget. No customizations have been applied; however, the functionality is not working as expected in the baseline system. I have tested this in my Personal Developer Instance (PDI) as well and encountered the same issue.