How do I create two custom Save & Submit buttons that bypass the global UI Actions?

ChuanYanF · ‎04-08-2025

Dear experts,

For my risk event form, I want to create a custom save button when clicked it will erase the assigned_to field in the risk event form, where the submit button will proceed with the risk event form submission that will prompt to the defined user in the assigned_to field. Currently, the submit button will only appear in the first submission of the form, so if we submit for the first time even though there is no assigned_to defined, when we log back in to the risk event record, the submit button is gone and it will be replaced with the update button. To make sure the submit button is always present before the assigned_to is defined, how do we make it happen? So my requirement now is to have two buttons at the first creation of the risk event record, Save and Submit buttons. I have created an onLoad script, where when user creates a new risk event form, the system will autopopulate the assigned_to field. Both of this state of the risk event will still remain as "New". So after I save and I go back to the record, the risk event form should still has the two save and submit button still and their function still the same as mentioned above until it is submitted to the defined user in the assigned_to field. Currently, the submit and update buttons are using the global one that is in the screenshots below, if I create new ui actions will it bypass the Global Ui Action or should I add in my conditions in the global ui actions script or what can I do in this case? Please advise, thank you.

ChuanYanF · ‎04-09-2025

Hi Shivalika, thanks for the reply but I managed to solve the issue using my approach as below:

So I have created two new button one is Save as Draft and one is Submit to Assigned and also a new flag field in the risk event form called u_submitted.
Save as Draft code and condition:
Condition:

current.state == 1 && !current.u_submitted

Script:

current.assigned_to = '';
current.update(); // Use update so record isn't considered "submitted"
action.setRedirectURL(current); // Stay on the same record after save

Submit to Assigned:
Condition:

(current.assigned_to != null || !gs.nil(current.assigned_to)) && current.state == 1 && !current.u_submitted

Script:

current.u_submitted = true;

if (current.isNewRecord()) {
    current.insert();
} else {
    current.update();
}

action.setRedirectURL(current);

And for the global Ui action I did not delete or remove but added in one condition which is to exclude the sn_risk_advanced_event table only which is this condition:

current.getTableName() != 'sn_risk_advanced_event'

View solution in original post

Ankur Bawiskar · ‎04-08-2025

@ChuanYanF

simply override those 2 buttons by changing the table to your table and click Insert and Stay on Right Click -> Form Header

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

Shivalika · ‎04-08-2025

Hello @ChuanYanF

I don't think you should modify this global submit update and save buttons - they are used at way tooo large scale and modifying them can have cascading effect.

Instead create custom button and add appropriate conditions.

Can you break down precisely - when do you want submit button - from when till when ?

And when do you want update button - from when till when ?

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.

Regards,

Shivalika

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY

ChuanYanF · ‎04-09-2025

Thks for the clarification Shivalika, so to break it down more granularly as you can see the screenshot here is how the risk event form initially looks like when users are creating a new risk event record.

So instead of just the Submit button, I wish to add in another button called Save as Draft button next to the Submit button. Currently the risk event form will autopopulate the assigned_to field based on the opened_by user's manager. So the function of the Save as Draft button should be erasing the assigned_to field values and saves the risk event record to not assigned the risk event to anyone, whereas the Submit button will work normally to submit the risk event form as well as making sure the assigned_to field has values inside it and submit the risk event form and assigned to destinate owners. So this two button will appear until the event is successfully assigned to a user, both Save as Draft and Submit button.

Shivalika · ‎04-09-2025

Okehh @ChuanYanF

Got it !! So just one more save as draft button is required and it will be visible when record is new. And Submit button will just make sure that assigned to is not empty.

So here, create a new Save as Draft button and for Submit button just do "Insert and stay" and apart from that add another condition that assigned to is not empty.

in the save as draft , just create in the table uo action as usual - check the form button, client checked and function on client side below 👇

function onClick() {

g_form.setValue('assigned_to', '');

g_form.save();

}

Now for the submit button just add another condition, if(g_form.getValue('assigned_to')=='')

{//g_form.addErrormessage();

return; //IMPortant so that nothing saves. }

Please make these modifications and share screenshot of stuck.

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.

Regards,

Shivalika

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY