How to enable save as draft for catalog items

[MohammedYaseen]

Hi All,

I want to know how to save a catalog form in draft. I am using a customised portal so its not enabled by default.

I saw the post by Robert, but need some more details

Thanks

[Mark Roethof · Accepted solution]

Hi there,

When on Washington DC release, this is out-of-the-box functionality. If you have a portal with a custom suffix, you do need to add a system property for this yourself.

"- System Property "glide.sc.enable.save_as_draft.portal." followed by the URL suffix of the Service Portal the user is on."

I've described this in this article of mine:
https://www.servicenow.com/community/developer-articles/save-catalog-items-as-draft/ta-p/2855484

A common blocker for new functionality like this is... when customers have cloned widgets and are not updating there widgets with upgrades. You might be working with widgets of years and years back, which don't have the newer functionality, like in this save as draft. Thats one the things with cloning widgets: you clone it, you own it! So you need to merge the updates, or manually update your widgets. A thing I see at customers, hardly being done 😢

[ChanakyaMekala]

May I know the version of your instance? Because in Washington DC release, this requirement has been addressed.

https://www.servicenow.com/community/developer-articles/save-catalog-items-as-draft/ta-p/2855484

If you are using totally custom portal, in that case try to create a new button using a widget in the catalog item page, the button retrieves all the details provided on the form, then you can do things:

1. If you don't want to have custom table, create a record on the sc_req_item table in a new state called draft and make sure all your flows kick start only after draft state.

2. Else you can make use of OOB table sc_cart_item, as per your version and render the draft version whenever the user wants to continue with the draft.


Please mark Helpful or Answered appropriately, if it had done so.

[Myk]

Hi Chanakya

I'm using custom portal and it's upgraded to Washington DC release recently

I don't see this system property in my custom portal

[Mark Roethof · Accepted solution]

Hi there,

When on Washington DC release, this is out-of-the-box functionality. If you have a portal with a custom suffix, you do need to add a system property for this yourself.

"- System Property "glide.sc.enable.save_as_draft.portal." followed by the URL suffix of the Service Portal the user is on."

I've described this in this article of mine:
https://www.servicenow.com/community/developer-articles/save-catalog-items-as-draft/ta-p/2855484

A common blocker for new functionality like this is... when customers have cloned widgets and are not updating there widgets with upgrades. You might be working with widgets of years and years back, which don't have the newer functionality, like in this save as draft. Thats one the things with cloning widgets: you clone it, you own it! So you need to merge the updates, or manually update your widgets. A thing I see at customers, hardly being done 😢

[MohammedYaseen]

Thank you Mark.  After creating a new system property for the custom portal, should i update the Server side script of widget with this new system property?

[Mark Roethof · Accepted solution]

No.

Its about the widget code itself. Is that the same as the out-of-the-box widget, does it include the new save as draft functionality.