Anyone know of an easy way to remove the Post button for Work notes?

[DrewW]

Anyone know of an easy way to remove the Post button for Work notes?   We are having issues with people entering SSN's on occasion into the work notes.   I built an onSubmit script that just removes them but what I found is that if the use clicks the "Post" button that the system does not run any of the onSubmit scripts.   I'm hoping I will not have to write a client script to find and remove it, that will just cause all kinds of issues I'm sure.

Thoughts anyone?

[shloke04]

Hi,

Except a Client Side Scripting the only other way is to set the below property as false.

"glide.ui16.live_forms.enabled" to false.

Navigate to sys_properties.LIST from Application Navigator search and set the above Property as false as shown below:

Other than these two methods there are no other way to disable the Post Button.

Hope this helps.Mark the answer as correct/helpful based on impact.

Regards,

Shloke

[cgedney]

Not sure why I'm getting this when I implemented this code...

onChange script error: TypeError: Cannot read properties of null (reading 'getElementsByClassName') function () { [native code] }

[Harsh Vardhan]

Hi Drew,

I had same requirement so i used ui policy and used DOM manipulation to hide the button.

shloke04 last suggestion. it might be possible if you make the value false in that property it will give you some other trouble.

Please check the below thread.

Issue in Sys Property - glide.ui16.live_forms.enabled

Thanks,

Harshvardhan

[DrewW]

I'm going to use an onLoad script because I want the button gone no matter what.   I just try and avoid DOM manipulation if I can because it adds a lot to the testing of an upgrade and we have occasions where they stop working and people do not notice until its to late.

[shloke04]

By setting the above Property as false the only concern would be that the Activity   Log would be reverted back to the Old Activity UI as it was in UI 15 and would also disable User presence Option as all these are controlled together.

So I would suggest to use either a UI Policy or a Client script using DOM Manipulation only.

Regards,

Shloke