Bug 1548523 - Correct values are not loaded on dynamic refresh
Summary: Correct values are not loaded on dynamic refresh
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: eclarizi
QA Contact: Shveta
URL:
Whiteboard: service
Depends On:
Blocks: 1553486
TreeView+ depends on / blocked
 
Reported: 2018-02-23 18:19 UTC by Shveta
Modified: 2019-02-11 14:03 UTC (History)
10 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1553486 (view as bug list)
Environment:
Last Closed: 2019-02-11 14:03:04 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
dialog (3.58 KB, text/x-vhdl)
2018-02-23 18:19 UTC, Shveta
no flags Details
domain (4.82 KB, application/zip)
2018-02-23 18:20 UTC, Shveta
no flags Details

Description Shveta 2018-02-23 18:19:45 UTC
Created attachment 1399975 [details]
dialog

Description of problem:


Version-Release number of selected component (if applicable):
5.9.0.22.20180221205805_f93a675

How reproducible:


Steps to Reproduce:
1. Import the dialog and domain attached.
2. Create a catalog item that uses this dialog.
3. Order service catalog. Select "Contract A" in Contract dropdown , location shows "Ohio and Alaska" . Select Contract B , Location does not change even after refresh .
Location should display : " Florida and Oregon" as in below method.

Actual results:


Expected results:


Additional info:

Method 
=============
contract = $evm.root['dialog_contract']

locations = if contract == 'a'
              {'ak' => 'Alaska', 'oh' => 'Ohio' }
            else
              {'fl' => 'Florida', 'or' => 'Oregon'}
            end

$evm.object['values'] = locations


Appliance : https://10.8.197.128
Service catalog : generic.

Comment 2 Shveta 2018-02-23 18:20:15 UTC
Created attachment 1399976 [details]
domain

Comment 3 eclarizi 2018-02-27 21:01:56 UTC
I believe the root cause of this is the same as what is happening in https://bugzilla.redhat.com/show_bug.cgi?id=1548562 and 
https://bugzilla.redhat.com/show_bug.cgi?id=1548568.

When you choose from the drop-down, that value isn't being propagated through, so when it runs through the automate method, it still thinks the contract is A.

This is resolved by https://github.com/ManageIQ/ui-components/pull/258, which currently has two supporting PRs out to be backported:
classic ui: https://github.com/ManageIQ/manageiq-ui-classic/pull/3451
service ui: https://github.com/ManageIQ/manageiq-ui-service/pull/1389

Comment 6 Shveta 2018-07-10 01:03:30 UTC
Fixed in 5.10.0.2.20180626170006_40dc459


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