Red Hat Bugzilla – Bug 609456
Unset checkbox is non affective on Command line options and Environment variables text field
Last modified: 2013-08-05 20:37:42 EDT
Description of problem:
The Unset Checkbox that is present against Command line options in Alert Notification and the one present against Environment Variables under script is non affective. If I set a value and then click save and later try to unset by checking the check box, the old value is still retained and the check from the check box is not saved.
Version-Release number of selected component (if applicable):
jon-server-2.4.0.GA_QA Build# 43.
Steps to Reproduce:
1.Create a new alert definition.
2.Click on Edit for the Alert Notification.
3.On the Alert notification page, click on Add New. Select the Alert sender
type as Resource Operations.
4.Select the resource selection mode as Relative Resource.
6.Select Start search from as "JBoss AS Server"
8.Select Then Filter by as "Script"
9.Provide the name of the script that should be executed upon meeting the alert
10.Select operation name as "Execute Script"
12.Uncheck the Unset for Command line arguments and enter the value that needs
to be passed.
14.Now Check the Unset and click save.
Check the unset check box, the old value is still retained and the check from the check box is not saved.
Checking back the unset should unset the value.
This was actually two separate issues:
1) prepareInputsForSubmission() function in rhq.js was not including textarea elements (i.e. for longString props) in the inputs that it prepared for submission; this issue affected all textarea inputs on all config pages throughout RHQ
2) missing call to prepareInputsForSubmission() JS function upon submission of form on update alert sender config page (/rhq/common/alert/notification/details.xhtml).
Both issues are fixed by commit a3a6c3c, which has been pushed to the release-3.0.0 branch.
Verified the scenario with jon-server-2.4.0.GA_QA.zip build# 65. The unset is working as expected.
Marking this bug as verified.
This second bug meant that it was impossible to unset textarea fields in configuration components that occurred anywhere in the UI.
Mass-closure of verified bugs against JON.