| Summary: | Javascript error after removing a global from test scenario configuration and accesing it in the expect part | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jiri Locker <jlocker> |
| Component: | BRM (Guvnor), User Interface | Assignee: | manstis |
| Status: | MODIFIED --- | QA Contact: | Jiri Locker <jlocker> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0.2, 5.1.0.CR1 | CC: | atangrin, manstis |
| Target Milestone: | --- | ||
| Target Release: | 5.1.0.PostGA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/BRMS-300 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
If a global asset is removed from a test scenario and the user tries to access the asset in the expect section a Javascript error occurs. <!-- This has been resolved by preventing the removal of global assets from the test scenario before they are removed from the expectation section. -->
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-12-08 03:32:11 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: | |
| Bug Depends On: | 724507 | ||
| Bug Blocks: | |||
|
Description
Jiri Locker
2010-04-09 17:56:53 UTC
Link: Added: This issue depends GUVNOR-524 Release Notes Text: Added: test Release Notes Text: Removed: test Release Notes Docs Status: Added: Not Yet Documented Writer: Added: Darrin Link: Added: This issue depends BRMS-453 Cannot be verified until BRMS-453 is resolved. It means that I cannot verify the JavaScript error if I cannot remove the global. Labels: Removed: rn-dmison rn-open Added: rn-dlesage rn-done-resolved Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Writer: Removed: Darrin Added: dlesage Release Notes Text: Added: https://jira.jboss.org/browse/GUVNOR-254 If the user removed a global from a test scenario and then tried to access it from the expectation by clicking on the green triangle icon, a Javascript error would occur. To fix this problem, the code has been changed so that the user can no longer remove the global from the scenario before it is removed from the expectation. As a result, the Javascript error is no longer encountered. Not fixed, the issue is still present in BRMS 5.1.0 CR1. The feature implemented in GUVNOR-524 probably has not made it into BRMS branch, the global can still be removed even if it is used in the EXPECT section. Should be documented as known issue for BRMS 5.1.0. Labels: Removed: rn-dlesage rn-done-resolved Added: rn-dlesage rn-done-known-issue Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Documented as Known Issue Release Notes Text: Removed: https://jira.jboss.org/browse/GUVNOR-254 If the user removed a global from a test scenario and then tried to access it from the expectation by clicking on the green triangle icon, a Javascript error would occur. To fix this problem, the code has been changed so that the user can no longer remove the global from the scenario before it is removed from the expectation. As a result, the Javascript error is no longer encountered. Added: https://jira.jboss.org/browse/GUVNOR-254 If the user removes a global from a test scenario and then tries to access it from the expectation by clicking on the green triangle icon, a Javascript error will occur. This should be fixed as of Drools 5.1. Retest to verify.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
If a global asset was removed from a test scenario and the user tried to access the asset in the expectation section, a Javascript error would occur. This has been resolved by preventing the removal of global assets from the test scenario before they are removed from the expectation section.
I am still able to remove global from test scenario even though it is being used in the "EXPECT" section. The project issue is https://issues.jboss.org/browse/GUVNOR-524.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-If a global asset was removed from a test scenario and the user tried to access the asset in the expectation section, a Javascript error would occur. This has been resolved by preventing the removal of global assets from the test scenario before they are removed from the expectation section.+If a global asset is removed from a test scenario and the user tries to access the asset in the expect section, a Javascript error occurs. <!-- This has been resolved by preventing the removal of global assets from the test scenario before they are removed from the expectation section. -->
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-If a global asset is removed from a test scenario and the user tries to access the asset in the expect section, a Javascript error occurs. <!-- This has been resolved by preventing the removal of global assets from the test scenario before they are removed from the expectation section. -->+If a global asset is removed from a test scenario and the user tries to access the asset in the expect section a Javascript error occurs. <!-- This has been resolved by preventing the removal of global assets from the test scenario before they are removed from the expectation section. -->
Fixed in master. |