Hide/Show Update button when certain condition is met

[beryllium]

I have an Update page where I want to disallow users from updating the form when the CurrentProcess != 00 or 05

I have the following script placed in the footer, it works when there is only one condition [("[@field:CurrentProcess]" != "00")] but does not work when I include [|| ("[@field:CurrentProcess]" != "05")]. 

Is there anything wrong with the script?

Thanks!

<script>
document.addEventListener('DataPageReady', function (event) {
  if (("[@field:CurrentProcess]" != "00") || ("[@field:CurrentProcess]" != "05")) {
    document.getElementsByName("Mod0EditRecord").forEach(function(elem) {
      elem.style.display= 'none';
    });
  }

});
</script>

 

[PotatoMato]

Hi @beryllium, you may check this forum post for reference: 

 

[BaySunshine]

Hi @beryllium,

A standard way of achieving this without using JavaScript is below:

• Add a Header/Footer to your page.
• Enter following code to hide the existing Update button:

               <style>

              .cbUpdateButton {
                    display: none !important;
               }

             </style>

• Add a new section and in it add an HTML Block.
• Enter following code to add a custom Update button:

               <div id="update" align="center">
                         <input type="submit" class="cbSubmitButton" value="Update" />
               </div>

               

 

• Now add a Rule. It should look like below:

              

 

                Replace "Value" with your field name.

                I hope this helps.

 

                 Regards,

 

 

[GrumpyRick]

Excellent option. Thanks.

[KG360]

On 6/17/2022 at 1:28 AM, BaySunshine said:

Hi @beryllium,

A standard way of achieving this without using JavaScript is below:

• Add a Header/Footer to your page.
• Enter following code to hide the existing Update button:

               <style>

              .cbUpdateButton {
                    display: none !important;
               }

             </style>

• Add a new section and in it add an HTML Block.
• Enter following code to add a custom Update button:

               <div id="update" align="center">
                         <input type="submit" class="cbSubmitButton" value="Update" />
               </div>

               

 

• Now add a Rule. It should look like below:

              

 

                Replace "Value" with your field name.

                I hope this helps.

 

                 Regards,

 

 

Very nice solution. I tried it, and it works, but I could not do the same with the Delete button. I used a similar script, but it might be the wrong syntax. <div id="delete" align="center">
                         <input type="delete" class="cbDeleteButton" value="Delete" />
               </div>

I tried it in the same HTML block as the Update button and in a separate HTML block; neither worked for the Delete button. 

any further guidance is much appreciated! Also: How 'safe' is hiding the button, the Delete in particular. Is it sufficient to Hide or must one also disable?

 

KG

[SushiPizza]

2 hours ago, KG360 said:

Very nice solution. I tried it, and it works, but I could not do the same with the Delete button. I used a similar script, but it might be the wrong syntax. <div id="delete" align="center">
                         <input type="delete" class="cbDeleteButton" value="Delete" />
               </div>

I tried it in the same HTML block as the Update button and in a separate HTML block; neither worked for the Delete button. 

any further guidance is much appreciated! Also: How 'safe' is hiding the button, the Delete in particular. Is it sufficient to Hide or must one also disable?

 

KG

Hi @KG360,

Please check this forum post for a custom delete button. A custom delete button will not work without additional scripting. Also, you need to have the type attribute as type="button" instead of type="submit" in the button code from this post.

 

Regards,
SP

[KG360]

These solution from @CoopperBackpack work perfekt! I liked that it was not necessary to involve any other elements than the authentication field and the record creator ID. When they are the same the user have editing rights, if not user can only view the content. I also disabled the fields that could otherwise be edited.