Bug 1297951

Summary:	[RFE] Support dynamic fields in service dialogs
Product:	Red Hat CloudForms Management Engine	Reporter:	Greg McCullough <gmccullo>
Component:	UI - OPS	Assignee:	eclarizi
Status:	CLOSED ERRATA	QA Contact:	Shveta <sshveta>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.5.0	CC:	cpelland, dajohnso, hkataria, jhardy, jprause, mfeifer, mpovolny, nachandr, obarenbo
Target Milestone:	GA	Keywords:	FutureFeature, ZStream
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.6.0.0	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1297953 (view as bug list)		Environment:
Last Closed:	2016-06-29 15:28:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1297953

Description Greg McCullough 2016-01-12 20:24:15 UTC

Description of problem: Service with dynamic fields cannot be ordered through the Self Service UI.

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


How reproducible: Always


Steps to Reproduce:
1. Create a Service Dialog that uses dynamic dialog fields and connect it to a Catalog Item.
2. Order the catalog item from the self-service UI
3.

Actual results:
Self-Service UI reports "Service Template Contains Unsupported Provision Dialog Types."

Expected results:
Self-Service UI supports ordering service with dynamic dialog fields

Additional info:

Comment 2 Greg McCullough 2016-01-12 20:27:11 UTC

Related PRs:
https://github.com/ManageIQ/manageiq/pull/5872
https://github.com/ManageIQ/manageiq/pull/6097
https://github.com/ManageIQ/manageiq/pull/6157

Related trello cards:
https://trello.com/c/ADumkyh5
https://trello.com/c/MTuUkoKS

Comment 3 Shveta 2016-05-13 20:31:39 UTC

Fixed.
Verified in 5.6.0.6-beta2.5.20160511140943_ff75fb2

Comment 5 errata-xmlrpc 2016-06-29 15:28:12 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1348