Show buttons in Panel Operations or Operations w/Record as Disabled

Jhstephenson

Is it possible to have a button show as disabled, not completely disappear, from Panel Operations or the column it is on for each record?

I want the appearance on some screens to be very consistent, but just block the use of a button if it is not applicable to a user or some condition.

PointsWell

I was unable to achieve this and if you have buttons after the one hidden then these move all the other buttons over one space which makes for a random UX.

What I did to work around this was to use a non functioning operation (on forms I use wizard page next which does nothing on a non wizard form) coupled with a deliberately incorrect Font Awesome glyph misspelled in case they make one called Gibberish

I thens set the opposite visibility rule to the button it replaces

Eg
Edit hide when Contact.Status="Dormant"
EditSpacer hide when Contact.Status<>"Dormant"

I have asked Vlad for an option to add a spacer button that doesn't require a fake operation and fake glyph, but I obviously didn't make a strong enough case for it.

A better option would be a Disabled when function to allow the button to be greyed out (or with a null glyph) and inoperative based on hide when conditions as this would leave the UI unaltered and consistent for every BO state

Jhstephenson

Thanks PointsWell. That last option is what I am hoping for.

Jaymer

In the event you have an HTML cell where you place buttons, you can modify the default class to make it appear dimmed (ie. disabled).

You can see the conditional code that either displays the valid button, OR a "disabled" button.
I also call a process named "dummy" as a placeholder.
Inspecting the Log shows that the dummy process IS NOT actually called - apparently NOTHING is happening when you click the button. Other combinations of Classes that I tested still called the process, but this was the combination I came up with to get what I needed.

Given this info (and until Aware has a better option built in for Panel Operations) perhaps this strategy could be used on those buttons also.

-->JaymerTip Show button as disabled in HTML cell on Form

Screen Shot 2021-02-15 at 9.31.49 PM.png

Jaymer

Rather than mess with a SECTION_START (and a 2nd SECTION for the dimmed button),
it seems like it would be easier/cleaner to use the Script field.

Then the cell contains simpler code (ie. just the default Button code),
and the Script has code to alter the CSS class of the cell.

Something like: IF (data("ClosedYN") eq 1) {document.getElementById("btn1").className = "k-button k-state-disabled"; }

(this doesn't actually work - i didn't want to put time into figuring out the exact JS needed. But, once that is solved, then it would be easy to conditionally disable buttons. AND THIS METHOD WOULD WORK on Panel Operations)

Jhstephenson

Thanks Jaymer, I will have to play with that.

edvwruhs

Jaymer wrote
In the event you have an HTML cell where you place buttons, you can modify the default class to make it appear dimmed (ie. disabled).

You can see the conditional code that either displays the valid button, OR a "disabled" button.
I also call a process named "dummy" as a placeholder.
Inspecting the Log shows that the dummy process IS NOT actually called - apparently NOTHING is happening when you click the button. Other combinations of Classes that I tested still called the process, but this was the combination I came up with to get what I needed.

Given this info (and until Aware has a better option built in for Panel Operations) perhaps this strategy could be used on those buttons also.

-->JaymerTip Show button as disabled in HTML cell on Form

Hey Jaymer, just a quick question how did you position the button next to the field? When I try to drag and drop the button next to the field the field gets just replaced with the button.

Any idea how I can solve this?

Best Regards

Jaymer

Had to add a column just to contain that. That’s why it’s wayyyyy over there.
But it could be done with css tinkering too.

Also, see this
Form design with multiple columns, unwanted rowspans fix