Applies to QAComplete 12.21 SaaS, last modified on July 15, 2019
||Fixed: It was impossible to download a file using the GET method, if its name included the
||Fixed: It was impossible to work with custom fields of test sets using REST API.
||Fixed: When adding a new user to a custom security group with the restricted access to QAComplete functionality, they could still perform unallowed actions.
||Fixed: QAComplete displayed an inappropriate error message when the identity provider did not return the X.509 certificate.
||Fixed: When trying to add a child item to the release, it caused an internal server error due to the ID assignment issues.
||Fixed: Custom fields name mapping caused lags on test runs with multiple similar requests involved.
||Fixed: In test cases with multiple steps, statuses of the steps did not update if only the first and last step had been run.
||Fixed: Sometimes it was impossible to work with QAComplete REST API using the Active Directory user credentials.
||Fixed: The password reset links in QAComplete service emails used the HTTP protocol, even if the server used HTTPS.
Features Added to QAComplete 11.4, April 2017