Bug 1391683 - "Application Name" in Objects section does not get resolved properly, displays "${APPLICATION_NAME}" instead
Summary: "Application Name" in Objects section does not get resolved properly, display...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: zakiva
QA Contact: Dafna Ron
URL:
Whiteboard: ui:container
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-03 18:42 UTC by Ramesh A
Modified: 2016-11-18 22:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-15 20:43:17 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Application Name issue (140.51 KB, image/png)
2016-11-03 18:42 UTC, Ramesh A
no flags Details

Description Ramesh A 2016-11-03 18:42:40 UTC
Created attachment 1217116 [details]
Application Name issue

Description of problem:
"Application Name" in Objects section does not get resolved properly, displays "${APPLICATION_NAME}" instead

Version-Release number of selected component (if applicable):
5.7.0.9-beta2.1.20161101182054_eb0afaa

How reproducible:
Very

Steps to Reproduce:
1. Manage a Container (say Openshift)
2. Navigate to Compute ==> Containers ==> Container Template ==> Click on any Template
3. Observe the Application name in "Name" column under "Objects" section

Actual results:
Displays "${APPLICATION_NAME}" instead of resolving to application name. Refer to the screenshot for further information

Expected results:
Should resolve to the appropriate application name

Additional info:

Comment 2 zakiva 2016-11-13 09:29:05 UTC
From my point of view the current behavior is the expected one because:
1. "${APPLICATION_NAME}" is a template parameter, by displaying it this way the user is notified regarding the use of a parameter in this field. So one can know that the parameter value can be changed, used in other fields, etc. 
Also, the value of the parameter can found at the parameters table below.  
2. In case that the parameter does not have a value (hasn't been set yet or auto-generated by openshift), we can't "resolve" it and display a value instead. 

This of course can be changed if another way is preferred. Barak, Federico what do you think?

Comment 3 Federico Simoncelli 2016-11-15 20:43:17 UTC
Current output is correct. What the user should see is the variable names. The values are filled in at instantiation time.

Closing.


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