Hide Forgot
Date of First Response: 2009-09-25 05:30:20 Workaround: Workaround Exists Workaround Description: restart the app server securitylevel_name: Public
Link: Added: This issue depends GUVNOR-345
Workaround Description: Added: restart the app server Workaround: Added: [Workaround Exists]
Verified in 5.0.1 CR1
added to the 5.0 CP01 release notes as resolved: GUVNOR-345 A rule that was imported again after already having been imported previously was not having its disabled attributes recreated. This was because the cache was not being cleared after the import process had occurred. This has now been fixed and these attributes are recreated correctly when a rule is re-imported.