Bug 1553767 - Visibility expression does not evaluated correctly on custom buttons for Generic Object
Summary: Visibility expression does not evaluated correctly on custom buttons for Gene...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.10.0
Assignee: Yuri Rudman
QA Contact: Angelina Vasileva
URL:
Whiteboard:
Depends On:
Blocks: 1553836
TreeView+ depends on / blocked
 
Reported: 2018-03-09 13:59 UTC by Yuri Rudman
Modified: 2019-08-01 13:06 UTC (History)
4 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1553836 (view as bug list)
Environment:
Last Closed: 2019-02-11 13:58:40 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yuri Rudman 2018-03-09 13:59:51 UTC
Description of problem:
  Visibility expression for custom buttons on Generic Object does not evaluate correctly


How reproducible: 100%


Steps to Reproduce:

1. Create Generic Object Definition  with name "ObjectDefinition":
Automation-> Automate->Generic Object->Configuration->Add New Generic Object Class

2. Create Custom Action for Generic Object with visibility expression:
Automation->Automate->Customization->Generic Object ->[Unassigned Buttons]->Add New 
Button. 
Visibility Expression: Generic Object : Name = "MyObject"

3. In Rails console create Generic Object and get list of buttons for that object: 
> obj_def = GenericObjectDefinition.where(:name => "ObjectDefinition").last
> obj = GenericObject.create(:generic_object_definition => obj_def, :name => "MyObject")
> actions = obj.custom_actions[:buttons]

Actual results:
 actions is empty array

Expected results:
 actions should have custom button created in step 2

Comment 2 Yuri Rudman 2018-03-09 14:28:00 UTC
PR: https://github.com/ManageIQ/manageiq/pull/16858

Comment 4 Angelina Vasileva 2018-12-10 15:38:29 UTC
Fixed and verified in 5.10.0.28.20181204160308_aa3b074


Note You need to log in before you can comment on or make changes to this bug.