• Type: Improvement
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 5.2.4
    • Fix Version/s: None
    • Component/s: Records Management
    • Labels:
    • Environment:
      Alfresco 5.2.4
    • Bug Priority:
      Category 4
    • ACT Numbers:



      The Export function with Records Management module currently, returns the generated .acp file directly in the HTTP response to the user. This causes us a serious practical problem in the environment. The instance of Alfresco is accessed by a proxy server that is configured (by policy) to return an HTTP 504 error if no response is sent to the user after 5 minutes. In practice, most of the exports will time out if a user ever tries to export more than a couple dozen results in a single export.

      The end users need to be able to reliably export the result sets that the Record Search returns for them. Some of our record users are supporting legal documentation processes where they need to provide copies of all records in our Alfresco server that match a particular set of criteria. This will sometimes return very large result sets. We understand that Alfresco does not allow users to run queries with unbounded result sets, but those result sets it does return, it needs to be able to export reliably to a user.

      We would propose an option for an "asynchronous Export", where the export would be generated after the HTTP query had returned, and would be placed at some location in the document library (and the user would be sent an email when the export was finished).





              • Assignee:
                jiball John Iball
                ajanjua Ahmad Janjua
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created:

                  Structure Helper Panel