Enhanced flexibility for displaying/hiding action buttons in the Maintenance (Building Operations) Console.
It should possible to « manage » the buttons individually. For instance some roles could see and update all requests, just the way supervisors can do, but cannot complete requests. Or it should be possible to allow some specific roles to be supervisor but not use the « complete » button.
In previous versions, this could be done using classic buttons in AXVW files that could be enabled or hidden using security groups or roles.
But in the maintenance console, this seems to be done on a global way, merely depending on few parameters (essentially the craftsperson's attributes, e.g. "is supervisor?", "can estimate?"...).
Enzo
shared this idea
-
Peter Vanderheiden
commented
I think this is related to this request to better << manage >> the actions buttons individually, so will add it here...... I agree with this post with the additional request that the labels in the action buttons should also be programmatically variable (through the SLA?). For example, We have used the VERIFY action button to be sure a WR undergoes certain gating (pending) steps. Unfortunately, the button always says VERIFY no matter the specific verification action that is necessary. It would be very helpful to be able to see on the console (by the label in the button) the specific action (or verification step) that needs to be done. In general, having the ability to more flexibly name the action buttons can allow us to add more clarity to the console by allowing the SLA definer to indicate specifically what (and even what role) is gating or holding up a work request. I believe this is part of being able to better manage the buttons individually.
-
Alisse Wasser commented
I know for our Organization, we would like to be able to restrict a specific group of craftspeople (which have a dedicated role) from having the ability to place work requests on Hold for Labor. The approach that you have outlined would be useful for us.