I am trying to pull the documents associated to a TRIRIGA record using a custom interface (web app). The objective is to convert the document to PDF format using OpenOffice, and have it downloaded to the user local machine when the end-user clicks on a particular document from the web app. This functionality worked well in TRIRIGA 126.96.36.199. When we migrated to 3.5.0, we found issues retrieving the documents. Unlike in earlier platforms where the docs are stored in the network share, in the new platform, the docs are stored in the database.
In the code side, we defined a TRIRIGA client object using TRIRIGA client factory (by providing app URL, username, and password). Then, a content object is created (com.tririga.ws.dto.content.Content), and the document ID (spec_id of the respective document, collected using JSON) is set as the record_id. After this, we invoked the download() method of the TRIRIGA client by passing the content. The result is assigned to a response object (com.tririga.ws.dto.content.Response). With the not-null response object, we are doing the conversion.
Where is the change needed to make this work in the new platform? In the TRIRIGA side or external code side?