is there a way to disable the hover function of the a!recordActionField ?

Is this really a "requirement"?  It sounds more like a design preference.  I'm not sure this is controllable on the design side, though if it is, I'd check your Related Action configuration first.

hi Mike, yes its a requirement the client is complaining that the hover is blocking the other buttons and uppon checking there is not option to disable it.

Unknown said:

hi Mike, yes its a requirement the client is complaining that the hover is blocking the other buttons

Technically this is still a design preference, rather than a requirement.  They are not being prevented from accomplishing any use cases if you are unable to fulfill this design preference, unlike a requirement.

I only add this because if expectations are not managed very carefully with clients, they will eventually (most likely pretty soon and/or often) request design preference changes that you can't control, even if you can in this case.  Of course it's always good to accomodate client design preferences where it's within our ability as designers, but this won't always be possible since so many UI style decisions are controlled by the Appian base product.

Unknown said:

hi Mike, yes its a requirement the client is complaining that the hover is blocking the other buttons

Technically this is still a design preference, rather than a requirement.  They are not being prevented from accomplishing any use cases if you are unable to fulfill this design preference, unlike a requirement.

I only add this because if expectations are not managed very carefully with clients, they will eventually (most likely pretty soon and/or often) request design preference changes that you can't control, even if you can in this case.  Of course it's always good to accomodate client design preferences where it's within our ability as designers, but this won't always be possible since so many UI style decisions are controlled by the Appian base product.