de-activating Draft on request

Jack62
Giga Guru

Morning all

 

We are in the process of upgrading to Washington and a requirement is to disable the ability for a user to save a request in draft mode on the ESC.

 

Could anyone confirm how we would do this?

 

Thanks

 

Jack

1 ACCEPTED SOLUTION

Sandeep Kumar13
Tera Guru

Hi,

You can disable below system property for esc portal.

System Property name: glide.sc.enable.save_as_draft.portal.esc

Just change the value to false.

View solution in original post

5 REPLIES 5

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @Jack62 

 

You need to disable at catalog item level:

 

AGLearnNGrow_0-1710928009243.png

 

 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Sandeep Kumar13
Tera Guru

Hi,

You can disable below system property for esc portal.

System Property name: glide.sc.enable.save_as_draft.portal.esc

Just change the value to false.

Jack62
Giga Guru

Thanks for the quick response guys. for the moment we have disabled via the sys_property.

Adam43
Tera Contributor

use case: it looks like in WashDC if you save to draft an item from an order guide- it 'breaks' the order guide up.  If your item was meant to be tied to other items in the order guide, it no longer is, and can be submitted on it's own once in draft.  Our process owner now wants to disable the draft option across the platform 100%.  Can anyone help with a process-owner-friendly explanation of why the impact is only on the 'mandatory' items in the 2 or 3 order guides we have, and has no impact on the 100 or so other items in our service portal that are all single items for the cart?  I've tried and failed to convince that we only need to hide the 'save to draft' on the few items in the onboarding/offboarding order guide that are not available outside the order guide itself.