Custom Button Expression Visibility Causing 500 Internal Server Error when Submitting Button

Solution Verified - Updated -


  • When adding an expression visibility filter to a custom button, users are only allowed to put in two expressions like so:
(expression 1) AND (expression 2)
  • If a user tries to add a third expression, the UI never saves this information, and insteadd the third expressions is ??? like so:
(expression 1) AND ((expression 2) OR (???))
  • However, if a user saves this custom button, the third expression is still saved in a malformed state, which causes issues in the Web UI. The main symptom is that a 500 Server Error is thrown when users try to use a custom button and submit it.


  • Red Hat CloudForms (CFME

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content