Bug 1344627

Summary: Default type of TexBox is not set up
Product: Red Hat CloudForms Management Engine Reporter: Jiri Stefanisin <jistefan>
Component: ProvisioningAssignee: eclarizi
Status: CLOSED WONTFIX QA Contact: Jiri Stefanisin <jistefan>
Severity: low Docs Contact:
Priority: low    
Version: 5.6.0CC: dajohnso, jhardy, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:automate
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-21 13:06:39 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:

Description Jiri Stefanisin 2016-06-10 08:28:38 UTC 
Description of problem:
When creating new TextBox in Dialog, type is set to Integer by default in type selectbox. However, TextBox type is not set.


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


How reproducible:
100%

Steps to Reproduce:
1. Create Dialog with dialog field TextBox and set data type as integer for this field
2. Create a Catalog Item and assign the Dialog created in step 1
3. Go Service Catalog and order a service, when submitting the dialog, it should do default validation on data type for Textbox fields.

Actual results:
Validation is done after pressing submit.

Expected results:


Additional info:
Found while testing https://bugzilla.redhat.com/show_bug.cgi?id=1278170
Comment 2 Chris Pelland 2017-08-21 13:06:39 UTC 
This bug has been open for more than a year and is assigned to an older release of CloudForms. 

If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.
Comment 3 Chris Pelland 2017-08-21 13:09:07 UTC 
This bug has been open for more than a year and is assigned to an older release of CloudForms. 

If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.