Bug 860845

Summary: Assets can not be restored when archiving "Global Area"
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Amana <ajuricic>
Component: BRM (Guvnor)Assignee: Mark Proctor <mproctor>
Status: CLOSED UPSTREAM QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: BRMS 5.3.0.GACC: alazarot, manstis
Target Milestone: ER4   
Target Release: BRMS 5.3.1 GA   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
It was previously not possible to restore assets from an archived global area. This issued was caused because it should not have been possible to archive the global area, it should only have been possible to archive individual assets in the global. This has been resolved by preventing users from archiving the global area.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:20:52 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 Amana 2012-09-26 20:47:48 UTC 
** 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
Comment 1 Amana 2012-09-27 16:18:58 UTC 
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.
Comment 3 Jervis Liu 2012-10-29 15:18:15 UTC 
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.
Comment 4 Jervis Liu 2012-10-30 03:19:42 UTC 
Fixed on 5.3.x branch
Comment 5 JBoss JIRA Server 2012-10-30 04:59:32 UTC 
Jervis Liu <jliu> updated the status of jira GUVNOR-1944 to Resolved
Comment 6 JBoss JIRA Server 2012-10-30 04:59:32 UTC 
Jervis Liu <jliu> made a comment on jira GUVNOR-1944

Fixed on 5.3.x, 5.4.x and 5.5.x branch.
Comment 7 lcarlon 2012-11-09 01:12:12 UTC 
Jervis, please review the doc text I have provided for the release notes for this issue, to ensure it is correct.

Thanks
Lee
Comment 8 Jervis Liu 2012-11-09 02:38:18 UTC 
The doc text is correct. Thanks
Comment 9 Jiri Locker 2012-11-12 13:50:17 UTC 
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.
Comment 17 Red Hat Bugzilla 2025-02-10 03:20:52 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.