With the release of CLEVR Dev Suite 3.1 or in short CDS 3.1, we are introducing some new features and several fixes.
Forbidden words
In security we have introduced a feature we call ‘forbidden words’. The idea is that you setup your data with string attributes saying something about the security. So admin data get called ‘Name admin’, ‘Location admin’, ‘Organisation admin’ and so forth. When performing a security scan as user the forbidden word is then ‘admin’.
The advantage of this is that the test data on the test environment is easily maintained. Before you had to have a fixed database, probably restored from a backup, to be sure that any change in the security scan is either caused by a deliberate change in the model or a side effect/security issue.
Now with the forbidden words feature you can make changes to the test environment, easily add new data and still run the security check!
API v2 for CI/CD and security
We had already release a nice new version of our API for code review. This version 2 includes nice swagger files and better error handling.
A small addition is a dialog when you click on the revision number in the revisions overview of code review.
This dialog gives you information needed in API calls, like the commit id for GIT.
New features
- Drag-and-drop for CI/CD jobs.
Bug smash
- Our app store compare feature needed an upgrade to be able to link widgets to widgets of an app store module. This solves the issue that some widgets could not be linked to an app store item.
- Fix showing commit message on revisions that have no model.
- Updated terms and condition and privacy policy links as shown during on boarding
- Fix permission error for enterprise admins
- Fix clicking on number in revisions overview did not change the current selected model, but showed violations of the current selected model. So clicking on another row did not do what was expected.
- Fix for checkboxes on violations in combination with chunking. Selecting all in a single chunk should not mean select all in all chunks.
- Make responses of the v2 REST API consistent by always returning application/json unless explicitly requested XML via the Accept request header. (Request body is JSON, so repond in JSON)
- Updated error responses in case of maintenance mode or authentication failed to return the proper HTTP Error Status code and Status reason.
- Fix for retrieving custom runtime settings in CI/CD