Bug 1403603 - Service Provision form inputs not passed to notification email messages
Summary: Service Provision form inputs not passed to notification email messages
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.6.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Greg McCullough
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-11 20:17 UTC by Thomas Hennessy
Modified: 2020-01-17 16:19 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-11 21:50:18 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)
Five initial screen captures provided by customer (338.62 KB, application/zip)
2016-12-11 20:20 UTC, Thomas Hennessy
no flags Details

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.


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