Feature Request: Control form buttons #921

New Issue

Open

opened 2022-06-27 21:43:58 +00:00 by cpaschen · 0 comments

cpaschen commented

2022-06-27 21:43:58 +00:00

(Migrated from github.com)

Feature: control form button display at the form level.

On a number of projects we need to completely disable form buttons on the front-end in a way that I don't think can be handled with just ACL alone.

Example:
A form that needs to NOT have the 'apply' button display, but does need the Save & Close.

I don't believe that there is an ACL way to do this as both buttons appear in an if clause related to the .create ACL setting.

Additionally, in cases where there should be no 'save & new' button displayed (ever), I believe it would be more 'efficient' to be able to just disable that, rather than testing against the .create ACL i.e. we wouldn't need to add yet more ACL entries/data for something that would never happen and we could potentially eliminate the if .create check complete - i.e. nobody would ever need to 'create' so why include that functionality?

Right now, it appears the only way to deal with the example above is to do a custom code replace modification (which is outside the 'norm' of JCB)

[Just sharing based on the comment in the JUG about instances where I'm needing to write custom code]

Feature: control form button display at the form level. On a number of projects we need to completely disable form buttons on the front-end in a way that I don't think can be handled with just ACL alone. Example: A form that needs to NOT have the 'apply' button display, but does need the Save & Close. I don't believe that there is an ACL way to do this as both buttons appear in an if clause related to the .create ACL setting. Additionally, in cases where there should be no 'save & new' button displayed (ever), I believe it would be more 'efficient' to be able to just disable that, rather than testing against the .create ACL i.e. we wouldn't need to add yet more ACL entries/data for something that would never happen and we could potentially eliminate the if .create check complete - i.e. nobody would ever need to 'create' so why include that functionality? Right now, it appears the only way to deal with the example above is to do a custom code replace modification (which is outside the 'norm' of JCB) [Just sharing based on the comment in the JUG about instances where I'm needing to write custom code]