Onclick UI action should be grayed out

coolsaurabh
Tera Contributor

I have created a UI action Locked. I want when user click on it , it should   be grayed out . Screenshot attached (UI Action encircled in red) :-

Qt.jpg

Thanks,

Saurabh

1 ACCEPTED SOLUTION

ark6
Mega Guru

Hi Sourav,



Here you go. The below procedure works for me



1. Create a custom checkbox on your form(for me its flag)


find_real_file.png



2. Write the below code on the locked out UI action



function hello()


{



  document.getElementById("159c99bb4f303200b5d50ab18110c747").disabled = true;


  var ga = new GlideAjax("hello");


    ga.addParam("sysparm_name","hello2");


    ga.addParam("sysparm_parent",g_form.getValue('number'));


    ga.getXML(test2);


function test2(response){


var answer = response.responseXML.documentElement.getAttribute("answer");


}


  }


find_real_file.png



3. And the script include



var hello = Class.create();


hello.prototype = Object.extendsObject(AbstractAjaxProcessor, {


hello2: function() {


var groupID=this.getParameter('sysparm_parent');


  gs.log('testing1'+groupID);


  var gr=new GlideRecord("incident");


gr.addQuery('number',groupID);


gr.query();


if(gr.next())


{


gr.u_flag='true';


gr.update();


}




},


      type: 'hello'


});



find_real_file.png



4. To control the reloading issue, write the below onload client script



function onLoad() {


    //Type appropriate comment here, and begin script below


    if(g_form.getValue('u_flag')=='true')


  {


  document.getElementById("159c99bb4f303200b5d50ab18110c747").disabled = true;


  }


}




Please note: I haven't used the try/catch statements, but you need to use it in your code while playing with DOM.


Also you need to hide the flag button from the form through UI policy or ACL(dont remove it from form layout or else it will not work).



Please hit LIKE or mark HELPFUL if found appropriate


View solution in original post

27 REPLIES 27

Yes, just a flag like a custom field(a check box) just to check if the button is clicked.


coolsaurabh
Tera Contributor

I am not able to do this. Could you please give me an example for this.


coolsaurabh
Tera Contributor

Can anyone let me know how can I restrict that on reload form UI action remain and fields remain grayed out.


Hi Sourav,



Here you go. The below procedure works for me



1. Create a custom checkbox on your form(for me its flag)


find_real_file.png



2. Write the below code on the locked out UI action



function hello()


{



  document.getElementById("159c99bb4f303200b5d50ab18110c747").disabled = true;


  var ga = new GlideAjax("hello");


    ga.addParam("sysparm_name","hello2");


    ga.addParam("sysparm_parent",g_form.getValue('number'));


    ga.getXML(test2);


function test2(response){


var answer = response.responseXML.documentElement.getAttribute("answer");


}


  }


find_real_file.png



3. And the script include



var hello = Class.create();


hello.prototype = Object.extendsObject(AbstractAjaxProcessor, {


hello2: function() {


var groupID=this.getParameter('sysparm_parent');


  gs.log('testing1'+groupID);


  var gr=new GlideRecord("incident");


gr.addQuery('number',groupID);


gr.query();


if(gr.next())


{


gr.u_flag='true';


gr.update();


}  




},


      type: 'hello'


});



find_real_file.png



4. To control the reloading issue, write the below onload client script



function onLoad() {


    //Type appropriate comment here, and begin script below


    if(g_form.getValue('u_flag')=='true')


  {


  document.getElementById("159c99bb4f303200b5d50ab18110c747").disabled = true;


  }


}




Please note: I haven't used the try/catch statements, but you need to use it in your code while playing with DOM.


Also you need to hide the flag button from the form through UI policy or ACL(dont remove it from form layout or else it will not work).



Please hit LIKE or mark HELPFUL if found appropriate


The SN Nerd
Giga Sage
Giga Sage

You are trying to enforce Business Logic via the Presentation layer (client side).


There are a few issues with this approach:


  1. Takes more time to implement
  2. Is difficult to test
  3. Can be easily bypassed by a crafty end user (via DOM manipulation)
  4. Is not supported by the vendor
  5. Will not work in Service Portal
  6. Will probably break in the next platform UI change, which may also stop other client side code from running


This should be done via ACL's and State (server side) as suggested by davidsmith



ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022