Service Portal "Edit Item" doesn't have SAVE button

shuguang2
Kilo Expert

Hi all

On the Service Portal you have the option to Edit the item before Checkout. However if you click on the Edit item button (the Edit button is on several places, an UI page pops up showing the item options. User can edit the options. However there is no Save or Update button on this page, so that any changes are in vain. 

I have tried to look whether any properties is controlling this, but couldn't find.  Any suggestions appreciated.

See attached screenshots

Best regards

1 ACCEPTED SOLUTION

else, you could try to hide this button with CSS.
by overriding Widget CSS with CSS for this page.

Try to add something like this in the "Page specific CSS" area of your page:

button[name=save]{
   visibility: hidden; 
}

May need to clear cache or reload before becoming effective.

View solution in original post

8 REPLIES 8

denis hoffmann
Kilo Guru

Hi,

when you look at the ID of your "SC Shopping Cart" widget in Service Portal Configuration,
is it "sc-shopping-cart" or "sc-shopping-cart-v2" ?

if you are still using the old v1 widget, then it's calling "sp-variable-editor" widget that uses this condition in Client Script area :

if (parent_g_form)
		addSaveHandler();
	else
		c.showSave = true;

regards,
Denis

Yes, we still have the sp-variable-editor widget.

Actually I have commented out the footer section in the HTML area, because user are not allowed to edit the variables after item is submitted, therefore showing the SAVE button is confusing.  This had the unintended side-effect that the button is also gone before checkout 😞  

I guess I need to add some conditions to show the button before checkout, but don't show after checkout. Any hint which condition can be used?

After a checkout your cart is empty and your orders converted in Requested items (RITM)

Where are they able to edit variables from Service Portal after a checkout ?  from the "id=ticket" page ?

 Also, what is you ServiceNow instance version ? and do you enabled two step catalog checkout model or one step ?

 

yes, user is shown the ticket after submitting order. The variables are all controlled by role assignment in such way that they can't edit it anymore, so very confusing if the Variables section has a SAVE button

My instance is Jakarta patch 9 & I have 2-step  catalog checkout.

I am thinking to clone the widget sp-variable-editor & use that for the ticket page, I can then easily comment out the button section for that cloned widget. The OOB sp-variable-editor is then still in tact for the Edit Item UI page