Red Hat Bugzilla – Bug 860845
Assets can not be restored when archiving "Global Area"
Last modified: 2013-11-07 17:14:12 EST
** Description of problem: The assets can not be restored when archiving the Global Area by selecting "File -> Archive" in JBoss BRMS 5.3.0 Guvnor. When trying to restore any asset, the following message is displayed on Guvnor UI: "400 The package [globalArea] that asset [teste1] belongs to is archived. You need to unarchive it first." However it is not possible to unarchive this since "Global Area" is not a package, then archival of "Global Area" should not be allowed. ** How reproducible: 1) Go to BRMS Guvnor UI 2) Archive the Global Area (File -> Archive) 3) Go to Administration -> Archive 4) Try to restore an asset from Global Area 5) The message will be displayed ** Workaround * Open the asset from Archive Area (Administration -> Archive -> Click on the Open button to an asset) * Click on Edit -> Copy (choose a different name) * Select a temporary package Note: that asset will not be (yet) on that temporary package, the copy will be still on archive area, but you can restore this new one. -> After restored, go to the temporary package, click on the restored asset and go to Edit -> Promote to global
Also, I would like to add that the proposed workaround does not solve all of the issues since when creating a new asset, directly under the global area, it always gets created as an archived asset. Then they can not create new assets for global area too.
The root cause of the problem is that the "Global area" should not be allowed to be achieved. Only the individual assets under the "Global area" can be achieved.
Fixed on 5.3.x branch
Jervis Liu <jliu@redhat.com> updated the status of jira GUVNOR-1944 to Resolved
Jervis Liu <jliu@redhat.com> made a comment on jira GUVNOR-1944 Fixed on 5.3.x, 5.4.x and 5.5.x branch.
Jervis, please review the doc text I have provided for the release notes for this issue, to ensure it is correct. Thanks Lee
The doc text is correct. Thanks
Although it is still possible to archive the global area using a little keyboard hack (bug 875732) I'm convinced that the chance a user would archive global area accidentally is insignificant, therefore I confirm the fix.