Skip to main content

We are aware of the limitation of which if the documents are created in the repo via a report rule, if the repo type is not the database, the document will not be available. After reading all the suggested solutions, it seems that we need to transfer these documents time to time between database to a different repo.

However the major problem is, in order to allow the report rule process working, we need to keep the repository as database and in generating state. In IFS document move solution, we can only transfer data from usable state repository to a generating state repository. That means if I want to take the documents out from the database, I have to set it to usable, and if my understanding is correct, during this time, the repository cannot be used to generate new documents. This essentially introduce a downtime for the application.


My question is, is it possible to transfer documents out of database in generating state, to a usable state repository? As far as I can see, you can only transfer from usable to generating which will not help here. We cannot keep the documents in the DB due to rapid increase in size, and we cannot have frequent downtimes. Given the volume of documents generated weekly, it’s impossible to have downtimes without interrupting the business. What could be a possible solution for this?

Some ideas:

- Can the downtime be planned to evenings or early mornings? If you move documents often, there will not be many and the downtime should be short.
- Can you create more than one Database repository? Then you can keep one in Generating status while the other is Usable. Perhaps switch between two in that way.
 


Reply