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.
Personal plan should not give an error upon opening the task list - CUR-3642 (Hotfix)
When viewing a personal plan and expanding the tasks section for study related tasks, an error could be thrown (undefined property ...). This was caused by the fact the study relation was not defined for the task. A hotfix is applied and the study related tasks are shown.
The personal overview of relations should be responsive - CUR-3665
- A loader is show to inform the user the page is being loaded
- The page is paginated, and the first page is shown. The user can navigate to the next pages.
- Sorting is performed in the back-end, reducing the load on the browser
As an administrator I want to use 'if ... then ... else ...' in conditions - CUR-3578
The support for conditions is extended with an 'if ... then ... else ...' construction, supporting nested condition. E.g. If (x=1) then 'set value X' else (if (x=2) then 'set value Y' else 'set Value X').
The used convention is: (condition) ? 'value if true' `: 'value if false'.
Examples:
- (:age < 40) ? 'this is true' : 'this is false'
- (:age > 40) ? ( (:age > 60) ? 'this is old' : 'this is middle-aged') : 'this is young'
The column search in reports should work - CUR-3593
The column search in reports allowed the user to enter a search value, but the search was not executed. This has been fixed and using the column search with a value will return the matching rows.
The process behaviour of 'wait for last participant' should help the users more - CUR-2540
In case a process is defined with multiple participants, including the 'wait for last participant', the process will only continue of each of the participants is finished. However, in case a team is assigned as a relation (participant), the team should be handled as 'one participant'. Which means the process can continue if one of the team members has finished the task.
To support this, the following change is applied to the behaviour:
- When in a team, and a team member has assigned the task, the task will be greyed out for each team member. This will actively inform the other team members the task is being handled, including who (assignee) is handling the task. This will inform only, and not restrict other users from picking up the task.
- When completing the task as a team member, it will be done on behalf of the entire team. The task will disappear for all other team members dashboard.
As a user I want to see the description of a subject - CUR-1874
Subjects can be defined on a higher hierarchical level (system-wide, faculty, study) including a description. When using the subject on a lower level, the option is provided to define a 'overriding' description. In case this is not defined, no description will be shown in the subject list.
A change is applied to fall-back to the hierarchical defined description, to always show the relevant (own or hierarchical) description to the users.
A successful deleted activity-serie should not show an error - CUR-3507
When deleting an activity-serie on a method/assessment an error message pops up, even if the activity-serie is successful deleted. This has been fixed and the activity-serie is deleted without error message.
Authorisation to edit a route in a workflow should be supported - CUR-3501
Automatic login not shown to users - CUR-3510
It should be able to force delete a module without error - CUR-3660
Creating and working with a new report template has strange effects - CUR-3484
As an administrator I want to see where a reference list is used - CUR-1864
Reference list can be used on different fields, and the system didn't provide an easy way to find those fields. A change is made to show the fields using a reference list, similar to other configurations that show where the specific object (e.g. page, workflow, ...) is used.
The admin can click the field, to jump direct to the field configuration.
Conditional reference lists should be respected - CUR-3596
When using a reference list with configured conditional lists the conditional list was not correctly shown based on the defined configuration. This has been fixed, conditions will be respected and the correct list is shown.
AI translated descriptions should be shown immediately - CUR-3578
Some description translations were not shown immediately after translate, but required a save and manual refresh to show them. This has been fixed and the translated value will be shown immediately (without save and refresh).
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.
Extended support activity mapping to Data Manager (DM) - CUR-2715
The exchange of activities to data manager didn't support the option to define a set order. The mapping is extended with support for the sequence.
The localName of an activity was already available in the mapping, but in case the localName was empty a fallback was implemented to provide a default value. This fallback is removed to enable distinction between no value defined and value defined.
Support multi-value data exchange to Data Manager (DM) - CUR-2715
Support is added to exchange multi-select values to Data Manager. The values sent are in a single field, separated with a | (pipe) to meet the DM standards.
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.
In this version no vulnerabilities needed to be addressed.
Refer to the Curriculum manual for configuration guidance.