Bug 1598431

Summary: When editing a service dialog, the methods gets executed for the dynamic fields
Product: Red Hat CloudForms Management Engine Reporter: Raul Mahiques <rmahique>
Component: UI - OPSAssignee: Dan Clarizio <dclarizi>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: low    
Version: 5.9.0CC: cpelland, hkataria, lavenel, mpovolny, obarenbo, rmahique
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-05 16:20: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 Raul Mahiques 2018-07-05 12:48:18 UTC 
Description of problem:
When editing a service dialog if there is any dynamic field it will be executed, this is a problem because the method may not work and block you from editing, if you have not access to modify the method, it is also not right because you just want to edit the dialog.

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

How reproducible:
Always

Steps to Reproduce:
Automation -> Automate -> Customization
Service Dialogs -> select dialog -> Configuration -> Edit this dialog.


Actual results:
If there is any dynamic field it will be executed. 

Expected results:
No methods get executed. We just want to edit the dialog.

Additional info:
Comment 2 Dave Johnson 2018-07-05 13:02:07 UTC 
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
Comment 3 Chris Pelland 2018-07-05 16:20:39 UTC 

*** This bug has been marked as a duplicate of bug 1589837 ***