Test system retrieves documents from Squeeze

A test system that is connected to the same SQUEEZE instance as the production system – for example because it was created as a copy of production – retrieves documents from there as well.

A retrieved document is marked as processed in SQUEEZE. Documents retrieved by the test system are then missing in the production system.

Deactivate SQUEEZE in the test system

If the test system should not communicate with SQUEEZE at all, deactivate SQUEEZE there:

1. In the test system, open the Squeeze Setup page.
2. Clear the Activated field.

The Active field of the DEXPRO SQUEEZE app in the DEXPRO Apps part of the Core Setup page does the same. The two fields are kept in sync.

The test system then no longer retrieves documents – neither through the job queue nor through the Download Documents now action. If the action is run anyway, it shows the message App DEXPRO SQUEEZE not activated.

No function that calls SQUEEZE is available in the test system then. Because the setup is copied along with every new copy of production, SQUEEZE is activated again afterwards. Repeat the deactivation after every copy – or have it done automatically (see the next section).

Automatically or only for certain documents

If the test system should detect and prevent the retrieval by itself, or if only certain documents should be held back, a developer can implement this with two integration events, available from SQUEEZE version 2.54.0.0. Description and example: Events before retrieving and creating SQUEEZE documents.