Saving a record without populating all mandatory variables

[Jim Coyne]

We have a few mandatory workflow variables setup. The variables are mandatory to ensure the techs populate them before closing a task as the information is required in subsequent tasks. Unfortunately, we have been running into problems with the Catalog Task form.

The problem with mandatory variables is you cannot enter information in some of the fields and/or variables and save the record - the blank mandatory variables prevent the update of the record. This is a valid use case as you do not always get all the required information at the same time and it would be nice to update the task as you receive that information. Same thing if a tech wanted to enter some info in the work notes or comments field - cannot save unless the mandatory fields are filled in.

This has been bugging me for a while but I think I've come up with a pretty good solution. I've created 2 new UI Actions on the Catalog Task form to override the global OOB Save and Update actions.   Here is how the Save version is configured:

Name:                       Save

Table:                     Catalog Task [sc_task]

Action name:         sysverb_update_and_stay   (to override the OOB "Save" UI Action)

Client:                   checked

Form button:         checked

Onclick:                 u_saveRecordClient()

Condition:             current.canWrite()

Script:

//Client-side 'onclick' function
function u_saveRecordClient(){
     //ignore mandatory fields
     var state = g_form.getValue('state');

     //we can save without filling in all mandatory fields and variables if the task is not closed or closing
     if (g_form.getValue('state') != 3){
           g_form.checkMandatory = false;       //ignore mandatory fields
           try {
                 //now ignore any mandatory variables
                 var allVariables = document.getElementById('variable_map').getElementsByTagName('item');
                 for(var i = 0; i < allVariables.length; i++){
                       var item = allVariables[i];
                       g_form.setMandatory('variables.' + item.getAttribute('qname').toString(),false);
                 }
           } catch(err) {}
     }
   
     //Call the UI Action and skip the 'onclick' function
     //this will execute the code below
     gsftSubmit(null, g_form.getFormElement(), 'sysverb_update_and_stay'); //MUST call the 'Action name' set in this UI Action
}

//Code that runs on the server, without 'onclick'
//Ensure call to server-side function with no browser errors
if(typeof window == 'undefined')
     u_saveRecordServer();

function u_saveRecordServer() {
     action.setRedirectURL(current);     //come back to the same record
     current.update();
}

The Update version would be slightly different:

Name:                       Update

Table:                     Catalog Task [sc_task]

Action name:         sysverb_update   (to override the OOB "Update" UI Action)

Client:                   checked

Form button:         checked

Onclick:                 u_updateRecordClient()

Condition:             current.canWrite()

Script:

//Client-side 'onclick' function
function u_updateRecordClient(){
     //ignore mandatory fields
     var state = g_form.getValue('state');
     //we can update without filling in all mandatory fields and variables if the task is not closed or closing
     if (g_form.getValue('state') != 3){
           g_form.checkMandatory = false;       //ignore mandatory fields
           try {
                 //now ignore any mandatory variables
                 var allVariables = document.getElementById('variable_map').getElementsByTagName('item');
                 for(var i = 0; i < allVariables.length; i++){
                       var item = allVariables<i>;
                       g_form.setMandatory('variables.' + item.getAttribute('qname').toString(),false);
                 }
           } catch(err) {}
     }
     //Call the UI Action and skip the 'onclick' function
     //this will execute the code below
     gsftSubmit(null, g_form.getFormElement(), 'sysverb_update'); //MUST call the 'Action name' set in this UI Action
}
//Code that runs on the server, without 'onclick'
//Ensure call to server-side function with no browser errors
if(typeof window == 'undefined')
     u_updateRecordServer();
function u_updateRecordServer() {
     current.update();
}

The script sets "g_form.checkMandatory = false" in order to bypass the mandatory fields, but, unfortunately, it does not work with variables. So, I figured why not run through all the variables and remove their mandatory properties?

I'd like to get a few comments to see what people think.   It seems to work fine so far.   Now the real solution of course would be to have the "g_form.checkMandatory" property take variables into account as well.     🙂

To use them elsewhere, just change the Table field.

UPDATES:

- modified the code above to add a "try {} catch(err) {}" block to avoid problems when there are no variables on the form (thanks shill)

- added a missing "{" at the end of line 7 (thanks chucksimonds)

- added the separate settings for the Update UI Action

[vijay_kumar]

Hi Hardik,

Finally the solution which i implemented is checking the mandatory fields on the UI Action of request approval.If the user fills all the   mandatory fields on form and clicks the request approval then the form will get submitted or else it wont.

If you want the script let me know.

Thanks,

Vijay

[scottatah]

This is fantastic Jim!!

Curious, for the folks using this, are you naming your buttons any different from your normal save/update buttons?   i.e. are you using "Save 2.0"?

Part of me thinks, how will a user ever know if they need to fill in all required fields if the buttons are named the same??   Another part of me thinks that this is going to blow the minds of users if they see a "2.0".  

What'd everyone else do?

[Kalaiarasan Pus]

We actually make use of two buttons,  Save  and Update. Save works like the one mentioned here, allowing user to negate mandatory fields and save fields that they need.

[Jim Coyne]

As Kalai mentioned, I've used the normal "Save" and "Update" wording for the new buttons as well.   The "2.0" was really just meant to differentiate the new ones during testing.

[knowledgelearne]

Hey JIM,

I have seen a post on Ageing report. Now I do have the same requirement and I need your help very badly. Can you respond as soon as possible?

Thanks