Bug 1403603

Summary: Service Provision form inputs not passed to notification email messages
Product: Red Hat CloudForms Management Engine Reporter: Thomas Hennessy <thenness>
Component: ProvisioningAssignee: Greg McCullough <gmccullo>
Status: CLOSED NOTABUG QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: jdeubel, jhardy, jocarter, myoder, obarenbo, saali
Target Milestone: GA   
Target Release: cfme-future   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-11 21:50:18 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:
Attachments:
Description Flags
Five initial screen captures provided by customer none

Description Thomas Hennessy 2016-12-11 20:17:38 UTC 
Description of problem: Problem reported during Intuit migration


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
What problem/issue/behavior are you having trouble with?  What do you expect to see?

When a Catalog Service Provision Form is used to provision, there are inputs that are not being passed to notification email messages. these inputs were passed successfully before the upgrade to 4.1

Where are you experiencing the behavior?  What environment?

Production, Service Provisioning Form

When does the behavior occur? Frequently?  Repeatedly?   At certain times?

Every time the Catalog Service Provisioning Form is used

What information can you provide around timeframes and urgency?

Needs to be resolved during the upgrade windows which ends today
Comment 2 Thomas Hennessy 2016-12-11 20:20:39 UTC 
Created attachment 1230658 [details]
Five initial screen captures provided by customer
Comment 3 Thomas Hennessy 2016-12-11 21:50:18 UTC 
Closing at customer request.  problem was found in customer local automation.
Comment 4 Greg McCullough 2016-12-11 22:16:47 UTC 
The dialog field was defined with data_type of integer.  In 5.4 it was being passed as a string into the request.  That issue was resolve and the request now stores that value as an integer.  Custom automation logic was evaluating the value and no longer matching.  The custom automation logic was updated to process the integer values.