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.
Using a formula hook to update specification fields should work - CUR-2703 (Hotfix)
The formula hook can be used for bulk change of information, e.g. codes, based on a formula. Then applying this hook with a formula including the academic year on a specification, this fails. This has been fixed by enabling the usage of the academic year in code generation for specifications.
Configuration should be respected - CUR-3278, CUR-3259, CUR-3264, CUR-2606
In this release some issued with fields not respecting the configured behaviour have been fixed:
- Activity type should not be editable, in case it is defined as read-only
- Duration marked as required, should behave as required (and not optional)
- Reference and Element fields in select options should show both code and name when configured
The end date of reference type should be respected and only show reference values that are still active
Reporting should support 'separate' fields to be selected - CUR-2282
The reporting offers the option to select for instance the modules offered by a program. The module in the report was shown as a combination of the module code and the module name (one column). In case only the module code was needed, in Excel a macro should be defined to separate both values.
To improve the usability, separate values are made available for code, externalId and name.
Correctable should be honoured when configured - CUR-3277 (Hotfix)
A task configured to be correctable should follow to configured calculation rule and allow the user to correct the calculated value. The option to correct the calculated value was not shown. This has been fixed, to enable correcting calculated values based on the configuration setting.
The cost calculation should not adjust the original costs - CUR-3268 (Hotfix)
In case an additional offering period was added to a module, the calculation not only changed the 'new costs' (upcoming year costs), but also changed the 'original costs' (previous years costs). The original costs should not be changed by a change for the upcoming year. This has been fixed.
Delete button should be available on activity-grid, list and card (acceptance only) - CUR-3274 (Hotfix)
In the previous release a bug was found where the delete button was only shown in case the activity-grid was empty. As soon there was data, the delete button was no longer available. This has been hotfixed prior to the release to production.
The behaviour of availability-preferences should be improved - CUR-3273
In case a user is requested to enter their availability preferences, the default configuration (everything set to available) or their last saved preferences are shown. In case the users navigates away (e.g. next button in workflow), the data is not saved since no 'changes' were made. And thus the preferences from last year were not saved to this year.
A fix is applied to improve / correct the behaviour:
- If the preference data is never changed in the context of the requested period, it will be marked as 'new' and when preceding in the workflow it will be saved.
- If the preference data is already saved and no changes were made the user can continue the workflow, and no data will be saved.
The Next button in the workflow should be available when using the HTML editor - CUR-3269 (Hotfix)
The Next button was not always shown in the workflow when using the HTML editor, but showing an error 'invalid' data. This was a 'nice' issue, with a root cause being a combination of configuration settings combined with a longer text. A fix is applied to properly work with the configuration combination causing the issue.
Team members should not receive tasks when they have been end dated - CUR-3260
Team members no longer member of a team based on a set end-date were still getting tasks assigned in a new year. This has been fixed, and the end-date of the team membership assignment will be respected.
General page behaviour should be more consistent and show correct data - CUR-2596, CUR-3258, CUR-2603, CUR-3238
Some issues were reported concerning the general page not being consistent and label and corresponding value data not showing correctly. Some fixes are applied to the general page to solve these issues:
- Only show fields that are configured to be shown on the page
- Use the labels of the fields, instead of 'fixed' labels
- Show the label and its value next to each other
- Respect 'visible' condition settings
- Support display of team email address in case roles are assigned a team
Administrator configuration:
Since fields are no longer 'automagically' shown on the general page, but only based on configuration the configuration for fields to be shown should have the checkbox 'Display on general' set.
Fields with formulas should work on form pages - CUR-3253 (Hotfix)
In case a field with a formula on a form page was changed, the data was not save. When changing the same field on the standard 'additional' page the data was saved. The cause was found and has been hotfixed, and fields can be changed when used on additional and form pages.
Long (reference) text should be fully readable in read-only mode - CUR-3255
Long texts, considered to be displayed on a single line, where cut-off when showing in read-only mode. In fact it also happens when not in read-only mode, but then the text was fully accessible moving the cursor.
A fix is applied where single line texts and reference list values exceeding the page size are cut-off, but will have a mouse-over option that will fully expand the text. This is not only applied on read-only values, but also for select boxes with values that exceed the select box width.
As a user I want to define a note - CUR-3247, CUR-2937
In case a user selected the option to create a note, e.g. add a note for a specific assignment, the screen freezed. Only after refresh the user could continue without having the option to specify the note. This has been fixed, and it is again possible to create notes.
Fix usability issues - CUR-3242, CUR-3231
Two small, but annoying usability issues introduced in the previous release, are fixed:
- Improve contrast in select boxes where the highlight and text color were (almost) the same
- Prevent admin pages to require two clicks to open the page
As a user I want to print the advice defined in a report page - CUR-2604
Using the rows template a report page can be configured based on existing pages. When adding the Advice page to the report, it was shown on screen. However, when selecting the print button it was not printed to the generated PDF. This has been fixed, and the advice will not only be shown on screen, but is also printed.
Extend study-modules report with study-module relation fields - CUR-2704
A few releases ago the option has been added to define relationship information between a module and a study. This to support the definition of study context specific information to a module.
In this version support is added to the study-module report to select (and display) the configured study-> module relationship fields.
The activity-groups-report functionality is extended - CUR-2697
The first release of the activity-groups-report, providing an overview of the user groups assigned to activities, is delivered a few releases ago. Based on the backlog and feedback some improvements are added:
- Add support for the configuration of the method type (e.g., teaching, exam) to be shown
- Add additional fields, such as method type, to the report to provide a better and more useful overview
- Add/improve filter options with support for filter on period, faculty and study. For a study the 'owned' modules and their activities will be reported.
The schedule weeks on teacher page should respect the configuration - CUR-2523
When creating activities, the schedule weeks are displayed according to the configuration settings in both the activity-grid and list. However, on the page of type 'teacher' the week number shown is always the academic year week number. In case for instance the schedule week is configured, a difference occurred in the display on the activity-grid/list and the teacher assign page. This has been fixed, and all week numbers shown will follow the generic configured week-display configuration.
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.
API documentation should show the correct response page - CUR-3281
It was noted the API documentation didn't show the correct response page (message format) in all cases. This has been fixed.
API users should be informed when open changes are reapplied to their import - CUR-3261
The standard behaviour using the API so update information in Curriculum is that the API will not overwrite / override any pending manual applied changes. This behaviour was implemented silently, sometimes raising questions why updates via the API were not processed.
To improve a better understanding of the above use case, the logging is extended with an information message informing the object is 'updated', but not all fields due to pending manual changes. This helps in not being puzzled why it seems the API doesn't work, but understand it works, but the result is different due to the pending change.
API calendar service extended - CUR-2944
The API calendar service is extended with the start and end date of the academic year. The underlying periods already provided the dates, but the year itself not.
API documentation using the Broker should be available
The Curriculum Broker provides a dedicated read-only database optimised for querying Curriculum information. The API documentation is published.
Offering code should be saved using the API - CUR-3271
When using the API is was noted the offering code was not saved. This has been fixed.
It should be visible if an activity is offered more than once a week - CUR-3270
In Curriculum it is supported to defined an activity is delivered more than once a week. Integrating to other systems may cause issues in case multiple activities per week is not supported. In those cases errors are raised, rejecting the activity.
In order to get more insight if (accidentally) activities are defined with multiple occurrences in a single week the activity report has been extended with the field 'duplicate weeks'. This will not solve the integration issue, but will help identifying the failing activity and the option to adjust it.
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 release no security vulnerabilities were reported requiring a fix.
Refer to the Curriculum manual for configuration guidance.