Skip to main content

A customer has copied their production database to a test database.  That includes all the Document Management basic data.  Their repositories are all FTP.

 

They want to ensure that new documents created in their  test environment do NOT get put into the repositories in which production documents are stored.  I thought we could just remove the repository entries in the test environment but it is not allowed as there are thousands of documents linked to that repository.

We created a new repository pointing to the test environment with all document classes going to it. Does anyone know a way to remove the other repository entries?

 

Thanks!!

Hi @Vernon Anderson ,

 

Instead of trying to remove the repositories why not just change them from Generating to Usable.

We do this in our test and development environments after we refresh them from the production database.

 

As you can see we’ve changed all our Shared repositories to Usable from Generating so no one accidently adds a document. 

 

 

Regards,

William Klotz

It sounds like they should just set them to Usable in Test. Then no new files will be stored there. Or even better change the password to a wrong one as well.

 

Reply


Terms & ConditionsCookie settings