Project

General

Profile

Bug #4618

First export of a run doesn't yield KAR with ROML

Added by Derik Barseghian over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Category:
workflow run manager
Target version:
Start date:
12/09/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4618

Description

I've introduce a bug in r22148:

For the case where no report is made: the first export of a run doesn't put a ROML in the kar, and subsequent exports get a ROML and a RIO. For this scenario you previously got ROMLs and no RIOs each time (which seems right).

History

#1 Updated by Derik Barseghian over 9 years ago

r22150 should fix this, but I want to test it a bit more.
One oddity currently is that if you export a run, export it again to a second kar, then tag the run and export to a third kar, the serialized workflowRun entityIds in kar2 and kar3 are the same. I think they should be different.

#2 Updated by ben leinfelder over 9 years ago

Would you just bump the run revision (entityId)? But then wouldn't that mean it's a different "run" rather than the same run with a new tag?

I found that if I don't layout a report (blank) I still get a ROML and a RIO for that run export. I think this should not happen for blank report layouts - fixed that.

#3 Updated by ben leinfelder over 9 years ago

in the name of upcoming code freeze, I'm thinking this can be closed.

#4 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 4618

Also available in: Atom PDF