[kepler-dev] [Bug 5017] ReportLayout LSID and referral list should be maintained

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5017

--- Comment #12 from debi staggs <staggs at nceas.ucsb.edu> 2010-06-14 12:21:25 PDT ---
(In reply to comment #11)
> Sounds good. Can you poke around looking for any other similar problems -- e.g.
> what happens when you have multiple copies of the same report open (same LSID),
> make changes to one, but switch to the original window and execute that
> workflow? There exist in the system at that moment two report layouts with the
> same LSID. Hopefully the right report is used and has its LSID incremented, and
> hopefully the other report doesn't lose its changes, will have it's LSID
> incremented and be saved to prov when that wf is run, etc.

After testing I have found that what happens in this case, is that when you
open two copies of the same workflow, select one of them, make changes to one,
then switch to the original window and execute that workflow, then the LSID for
the report layout is incremented at that point.  There are no longer 'two'
report layouts. There is one current layout, and one layout that has (in
essence) been changed (by running the workflow) but not saved.  If you switch
to the workflow in either window they will both show the same LSID for the
report layout.  If you go to that window where the first change was made it
will always reload the layout from the workflow no matter what.  This is
something that we chose not to address for this release and can be referenced
in Bug #5009 (i.e. Opening two KARS that have the same Workflow, but that have
different report layouts, will make the first layout refresh itself with the
layout from the KAR that was opened most recently.) which still applies.

Can I suggest that this is satisfactory for now and that we should close this
bug ?

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.