The release notes provide information on the features and improvements in the specified version. The release dates that are related to the version of the release are published in the Curriculum/Workload Management release schedule.
Improvements
The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes. Issues marked as Hotfix have been developed during this Sprint release, but are hotfixed and technically added to the previous release or direct to production based on the impact of the issue.
Reports should support search on date fields - CUR-1938
The search option in the standard reporting option didn't support search on full dates. This has been fixed, to add support for searching on dates in the different reports.
A condition defined on the method category should be respected - CUR-2263
The method category offers an option to configure a condition, e.g. only show the method category in the context of one faculty. The configuration option was there, but the evaluation of the condition wasn't. This has been fixed, so in case a condition has been defined on the method category it will be respected.
Vacancies should be manageable from the vacancy list - CUR-2295 (Hotfix)
The option to view and/or edit a vacancy from the vacancy list was broken and didn't open the expected form, but showed a technical error. This has been fixed, so management of vacancies from the vacancy report is working again as expected.
As an organisation (department) manager I want to see my contribution to programs - CUR-1937
A new report-template has been added named 'hour-contribution' that enable reporting from an organisation perspective, displaying all studies and hours per study the organisation contributes to.
The hours per study is the sum of the hours on modules, groups, activities for all staff members of the department (and its children).
As an administrator I want to configure custom-fields on educational tasks, that can be used by users - CUR-2243
In order to support better management, allocation and reporting of tasks outside the context of the curriculum structure, support has been added to define custom-fields on educational tasks. This will support adding additional attributes on tasks that can be used for the different overview. A practical example could be to get an overview of all tasks that are related to the project 'A brand new day'.
The administrator will add a custom-field to the Task object definition. Any custom-field can be added, e.g. a list of all projects, including the standard options to steer display, apply conditions, add info labels, etc.
The user will have access to the field when creating or managing a Task. Based on the example provided, the user can search and select the list from the defined list
The user can report on tasks, and using the standard reporting options can add the 'project' field to the report, filter on the project 'A brand new day' to get an overview of all tasks defined in the context of this project. The user can save the report as a template, or export to CSV or Excel.
Integration
The issues mentioned under the section integration are considered as extension, improvements or bug fixes related to the Curriculum API, OOAPI and/or CSV import functionality.
Extend the API to support retrieval and update of non-educational tasks - CUR-1976
To enable better management of the non-educational tasks a number of changes have been made that allow importing non-educational tasks using CSV import.
The CSV support is provided by using the 'TASK' import and provide the fields:
- year - the year the tasks should be applied to
- task_id - unique identifier of the task as present in an external system, e.g. the HR system
- assignment_id - unique identifier of the assignment/contract
- template_id - type of task , e.g. admission committee
- description - text to provide textual context
- correction - decimal value to define if more or less hours are applicable
In the next release API support will be added to the standard API.
Security
An integral part of our development and build process is automatic scanning for known security vulnerabilities. The vulnerabilities will be fixed based on their impact, which means that in some cases an immediate hot-fix will be applied, and in other cases the vulnerability will be fixed in the current or next Sprint (release). The security section provides an overview of the vulnerabilities mitigated. For more information on reported vulnerabilities, see the central database of vulnerabilities.
This release no vulnerabilities has been reported that require mitigation.
Refer to the Workload Management manual for configuration guidance.