API 1.4.1
Software version: API 1.4.1
Publication date: 23 JUL 2020
This file provides information about the VERA API Server
- Resolved Issues
- Docker Image Information
- Known Issues and Limitations
Resolved Issues
| Key | Summary | Notes |
|---|---|---|
| VS-802 | qTest Run with large attachment(s) does not return an Approval Route to qTest | Fixed an issue in which VERA was limited data transfer to 30MB. This limit is now configurable with the VERA_MAXREQUESTBODYSIZE and the VERA_MULTIPARTBODYLENGTHLIMIT variable. See Supported Environment Variables for more information. |
Docker
| Repository | veraserver20190209075900.azurecr.io/tx3/vera-server |
|---|---|
| Tags |
|
Known Issues and Limitations
Key | Summary | Known Issue Details |
|---|---|---|
| VS-629 | qTest webhook errors are not recorded in the error log. | If a qTest callback action results in a HTTP 500 status code, the error will not be recorded in the VERA API Server error log. |
| VS-610 | Cannot add large number of users to a domain at once | (Preview Feature Only) Admins are not able to add more than 999 users to a VERA domain in a single operation. |
| VS-383 | Tester(s) not included in Execution Log in VERA | qTest Tester name is not displayed in VERA web portal. The VERA Record Management Policy can be updated to include the Tester field in VERA. |
VS-323 | VERA Server needs a reboot to fully read new Sync Policy entries | Changes to the VERA Synchronization Policy will not take affect until the VERA Application service is restarted. |
VS-222 | Tasks show Not Started instead of Cancelled after rejection | Approval Tasks are set to Not Started when an approval task in the same approval route is Rejected. The approval tasks should be set to Cancelled when an approval task in the same approval route is Rejected. |