ESF_reports_access party cannot access documents if setup in the package do not give permission

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a multi-document package with ESF_reports_access defined for one out 
of multiple documents in the package.
2. Create a transaction that uses that package.
3. Via a report, note that the reports access is limited to that one document.
4. Change the package so the reports access to access another document.
5. Via that same report, access the transaction again, but reports access 
remains limited to the original documents.

What is the expected output? What do you see instead?
Would like reports access to work on any document, not just those given access 
when the transaction was created.

The issue appears to be that if the transaction is created and the reports 
access party is defined, the corresponding transaction party access to the 
document objects are created and remain in place.  If more documents are added 
later, the old transaction is not constructed to provide access and so nothing 
is allowed.

When a package says the reports access is allowed for a given document, the 
associated transaction party document should be created automatically so access 
to older transactions will work the same way.  Of course, if an older 
transaction doesn't have the document, access cannot be provided, but this 
should not be the general case as packages should be versioned when documents 
are added/removed.

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

[OpenESignForms]

Now when accessing the transaction via the reports, if the ESF_reports_access party is defined to have access to a document which it previously did not, the associated transaction party document is created to allow access to the document.

This is added to the release after 17.8.4.