When a party picks up a transaction, can get newer document versions than when the transaction was started

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a transaction that uses a given version of a document.  Note that the 
tran details will show the transaction document version in use at the time the 
transaction was created.  
2. Do not complete the transaction, but have it so you can resume it later 
(either with a pickup code or via the To Do if you start while logged in)
3. Make a new version of that document and ensure it's in the same 
Test/Production level of the one accessed in step 1, but make it obvious (such 
as a text change) that it's a modified version so it's easy to detect if you 
have the original document version in step 1 or are now getting this version.
4. Return to the document via the To Do list (or via the pickup code).

What is the expected output? What do you see instead?
You should see the same document version as was present when the transaction 
was created in step 1.  We noted that we see the new version.

Original issue reported on code.google.com by yoz...@gmail.com on 20 Feb 2015 at 9:42

[GoogleCodeExporter]

Note that getting the latest production/test version is how most of the 
elements in the library are resolved at runtime. But transaction->package 
version->document versions should be maintained as custom logic expects certain 
fields and capabilities that may not be present in subsequent versions.

Noted that the code appears to retrieve the correct documents, but the version 
is selected using "test/production" labels rather than getting the exact 
version that was present when the transaction was created.

Original comment by yoz...@gmail.com on 20 Feb 2015 at 9:44

• Changed state: Started

[GoogleCodeExporter]

Fixed in 15.3.7 release

Original comment by yoz...@gmail.com on 21 Feb 2015 at 2:40

• Changed state: Fixed