Actions
Bug #4969
closedExported run-kar puts a roml at root of Components tree
Status:
Resolved
Priority:
Normal
Assignee:
Category:
reporting
Target version:
Start date:
04/30/2010
Due date:
% Done:
0%
Estimated time:
Bugzilla-Id:
4969
Description
If you create a workflow and a report, run, export the run, you end up with a roml at the root level of your Components tree. It goes away on Kepler restart.
Updated by Derik Barseghian over 14 years ago
Also the RIO.1.xml and RIO.1.pdf don't show up in the gui inside the KAR. This is a regression.
Also I'm not sure why the ROML shows up in the tree as "roml" when the filename is: Unnamed1_ROML.xml
Updated by Derik Barseghian over 14 years ago
fixed in r24213 (trunk) and r24214 (2.0)
Updated by Derik Barseghian over 14 years ago
This can happen again, though the replication procedure is different now (and i'm not sure what it is yet).
Updated by Derik Barseghian over 14 years ago
I can't find the replication procedure for this, or it's no longer happening. Please reopen if you see this.
Actions