New functionalities have been released to our github repo.
- Reordered the portlets
- Added a new portlet for in progress and done session
- Added the field Age to a candidate so you do not have to use the birthdate. The birthdate is considered a special personal feature in some jurisdictions that may not be recorded for testing purposes.
- Added the possibility to change the narrative reports created by the ITR to tailor them for a specific candidate. The changes can be saved and will be included in the session result archive (see point immediately below here)
- Add option to download session results and reports in a ZIP file from the client. This allows for easy archiving of the session results.
- For all e-mails sent from the system a CC email address can now be set. You can set the address via Organisation – Customer settings or the regular organisations menu
- The master user can now set the invoice code and test costs before publishing the test
- Added more credit options on a customer to set specific costs for a test, set discount percentages for all tests, and set an amount charged per test.
- Added a personal credit pool for a consultant. The personal credit pool will be used primarily for this consultant. If the consultant is out of credits the session results that have not been invoiced yet can no longer be viewed. This under the assumption that the organisation has sufficient credits off course. The credit level can go below zero if the last test being invoiced is more expensive than the total amount of personal credits remaining. Invoicing will continue in that case.
- Fixes for texts that ended up wrongly in the translations file
- Improvements for handling of out of credit sessions
- A master user can now update the application from the webbrowser via the menu Server settings – button Install open source publics. This functionality will update all source code from the browser instead of from the server. The functionality is new and experimental, so use with care! Occasionally replacing the open files fails, meaning you will have to repeat the procedure multiple times. When you host on IIS the changes will be immediately available, on Linux the back end process will stop under the assumption that you are using docker and the container will automatically restart.