Page Comparison

...

The system will mark the current Default Records Management Policy in Policy Managment as the DEFAULT policy

...

The system will mark the current Default Approval Policy in Policy Managment as the DEFAULT policy

...

The system will move the Default Synchronization Policy in Policy Managment to Connections under Settings in Vera Administration Web Portal

We introduced new containers to improve performance

...

. The deployment script (e.q. docker-compose-yml) needs to be updated to include the new images. Please see Upgrade the VERA Server Applications for more information.

1. tricentis/vera-api-connections-testconnection - Internal API to for connection tests

2. tricentis/vera-api-qtest-routeactions - Public API for Route Actions from qTest

3. tricentis/vera-api-routes-routeevents - Internal API for Approval Events (Task Approved, Task Rejected, Route Completed)

4. tricentis/vera-server-legacy - Legacy Vera Server components that have not migrated to microservices.

5. tricentis/vera-worker-qtest - Worker to handle qTest actions.We introduced new databases and collections

Vera 2023.2 introduced new Connection and Policy Managment features. Vera will automatically make the following updates when you upgrade to Vera 2022.3 to support these new features.

1. The system will mark the current Default Records Management Policy in Policy Managment as the DEFAULT policy

2. The system will mark the current Default Approval Policy in Policy Managment as the DEFAULT policy

3. The system will move the Default Synchronization Policy in Policy Managment to Connections under Settings in Vera Administration Web Portal

4. The system will add the following databases and collections:

   1. New Database: tx3-vera-connections:

      1. Collection: connections

   2. New Database: tx3-vera-webhooks

      1. Collection: webhook-callbacks

   3. New Database: vera-qtest-routeactions-sagas

      1. Collection: job-attempts

      2. Collection: job-types

      3. Collection: jobs