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
New functionality, user experience improvements and bug fixes. Issues marked as Hotfix were developed in this sprint but applied to the previous release or directly to production, depending on impact.
The availability report should be accessible via the organisation - CUR-3774
In case availability-preference is collected on person level, and the person has a relation with an organisation, there was no option to report the person availability from organisation perspective. This has been added and the person availability can be reported from organisation level. In case an organisation has sub-organisation, the persons from the sub-organisations are also in the report.
A user requires the permission to view the schedule preference report, else an unauthorized message will be shown.
Assessments from a terminated module should not be rolled-over to a new year - CUR-4161
In case a module is terminated, the assessments were still copied to the new year. Since the assessments were actively filtered in the active year based on the 'terminated flag' of their owning module the didn't show up in that year. Since the owning module was not copied over and the assessments were, they suddenly popped up in the new year, because there was no owning module anymore,
A fix is applied to the roll-over and not only filter the terminated module, but also its assessments. Next to that the assessment report is extended with two new columns, the assessment's own Terminated and its (owning) module Terminated. This will allow in the active year to report the assessments from terminated modules and if needed move them to a new owning module.
Assessment matrix sorting should be consistent with other matrix reports - CUR-4421
The standard sorting order for the matrix reports should be first sorting on phase, then period, like in the other matrix reports. Next to that it was found the sorting of the structure (study -> group) was not equal to the default sorting used in structure view.
Both have been changed and all matrix reports will follow the standard phase, period sorting and the study->module-group ordering
Extend the usage of faculty fields in person related formulas - CUR-4201
There was no support for using formulas in person fields based on fields (and their values) defined on the person-related faculty. This has been added, and person fields can use faculty fields in their formulas.
Improve usability of the version-based module-group and module creation - CUR-4143
When creating a new module-group or module the context the 'create' was initiated was not used. The changes made are:
- Copy from an selected object prefills the version as the source and the definition as both the source and destination.
- Create a new module/module-group will also show the option 'copy of', to not only allow to create one from scratch, but also use an existing module/module-group and version combination.
The advised route-planner overview should show the time blocks - CUR-4201, CUR-4445
The migration to the new look and feel had accidentally removed the display of the advised route with the relevant time-blocks. In this release this view has been added and the display shows the modules again in a grid-view using the time-blocks.
Modules without an active offering should not be shown strike-through - CUR-4374
The strike-through of modules in the structure view was used both for terminated modules and modules with no active offering. This causes issues for users to distinct the two variations. A change is made to use the strikethrough only for terminated modules. The module with no offering in the selected year are shown without strike-through and can be identified since they have no offering information.
In case there is a requirement to show both strike-through, the configuration option to show modules without offering as strike-through can be set.
Specification subjects page should filter on specification related categories - CUR-4218
The filter for specification subjects was incorrect and has been adjusted to only retrieve the specification own subject categories, instead of every subject category in the environment.
As a user I want an overview of unused offerings - CUR-4346
There was no option to get an overview of all unused offerings in the offering report. This option has been added with the following underlying logic to determine if the offering is unused:
- Is the module linked to a study, if not the offering is considered unused.
- If linked, does it have the setting 'no alternative offering' (default) or 'alternative offering AND the offering is selected as alternative). If one of the two settings is matched, the module is considered used.
As a user I want to see the changes made on form pages (experimental) - CUR-2140
As part of the improvements on the audit trail, and an outstanding feature request, a new option for form pages is introduced.
This option adds support to configure a form page to show 'read-only', 'edit' and/or 'history' information. In case multiple options are selected, the 'default' option can be defined and the other selected options will be shown as buttons to switch between the views.
The added option is the 'history' option. In this case the new value and the old value are shown in the form, so the user can easily identify the changed information. E.g. in a validation process. The way of working is more or less similar to the description pages that already offer support for visualising the 'changes' in context of the description page.
The image below shows the different options as buttons, with the Change view selected. The new values are highlighted. In case an 'old' value is replaced, both the old and new value are shown.
An additional change is made to the form page where fields were shown as 'read-only'. During save these read-only fields were validated, and in case the field was filled incorrect the save would fail with no reference to the incorrect field. The save is adjusted to only validate and save the 'editable' fields on the pag.
Configuration:
- Use the modes option to define the supported mode(s) offered to the user
- Use the default mode to specify the standard selected mode in case multiple modes are selected.
Experimental feature:
This change is for the upcoming 2 releases marked as 'experimental feature'. This means that the standard used form pages are using the 'old' way of working. When toggling the 'experimental feature', the new way of working is used. This choice is made, since it's not only an extension of the options but also a complete technical rebuild of the form page. This allow admins to test specific form pages and play around with the options.
As a user I want to export a program changes report to PDF - CUR-2692
As part of the audit trail related changes, the reports in the user interface have been changed and extended with new options. In this release the function the Download menu of the reports is extended with a PDF option, next to CSV and Excel.
The PDF holds the selected rows in landscape, with the column headings repeated on every page, the page title and object at the top, your logo, and the print date and page numbers in the footer.
Moved to the next release
A PDF of a report that has textual changes other than Western-European script, e.g. Chinese, are not yet displayed correctly. This will be picked up as a remaining issue.
As a user I want to enter the Other duration without fallback to preset options - CUR-3474
After choosing Other in a duration dropdown, typing a value considered a preset option, the duration switched the field back to this preset option. This has been adjusted and typing 1 will no longer switch back to the preset option, but allow the user to continue typing and define for instance12 hours. This defined value in Other will save 12 hours.
A preset is only matched against the value when the field first loads, until the user picks an option or types a duration. Clearing both hours and minutes on a required field also no longer refills the default preset.
As an administrator I want to exclude method and assessment types per faculty - CUR-1893
Via method-parameter page, an administrator can already exclude certain method-types within a faculty. However, the defined value were not respected in all pages offering a 'method selection'. The following changes are made to improve and extend the support:
- Next to the method type, also the excluded assessment type(s) can be defined per faculty
- The assessment and method type restrictions are applied to all pages offering a select option. This covers adding a method via the method tree or the methods list, the method and assessment forms, editing an activity, and adding an activity.
As an administrator I want to use hook to set values based on reference lists - CUR-4224
A hook has been added to enable setting a field value based on a reference list. The Set field value hook can set both reference-list and element fields using the code or external id. It also support usage of expressions that read another reference field, such as :studyId.city.
As a user I want to report on specifications from organisation and faculty - CUR-4340
With the change in previous release to support to define the relation between a specification an the organisation, the option was opened to report the specifications for a specific organisation. In this release a new report page is added 'specification-report' that can be used both from a faculty and organisation perspective. The report will list the related specifications to the selected faculty / organisation with similar options to all other report pages (filter, add fields to report, export, etc.).
Time fields should be displayed as time (hh:mm) in reports - CUR-4356
The report pages showed time fields as a date-time instead of only the time. This has been adjusted and time fields are displayed as time in the format hh:mm.
As a user I want an organisation report - CUR-4208
It was found that there was no organisation report, something we completely missed. Luckily the question was asked, to make us realise and add the organisation report to the system. The organisation report has similar options to all other report pages (filter, add fields to report, export, etc.).
Integration
Extensions, improvements and fixes to the integrations: the Curriculum API, OOAPI, CSV import, and the data exchange with Data Manager, Core and the broker.
Asset CSV import should import unit cost columns- CUR-4446
In case the asset CSV was used to upload the unit cost columns (amount, duration, occurrences), these were not saved. This has been fixed and the uploaded fields are now correctly stored.
CSV should support definition of start and end date for version based objects - CUR-4378
The CSV upload doesn't provide the option to specify start and/or end date for versions objects. This causes the objects to appear in every defined year.
The change made is to add optional start_date / end_date columns (yyyy-mm-dd) to the method, assessment, module, module group, study, qualification, organisation and faculty CSVs, directly after version (or after the names where there is no version).
The method and assessment importers now store the dates similar to the other objects. A blank cell will keep the existing date.
Specification already had support for start and end date, and is therefor not mentioned in the objects that are extended.
CSV import of specification and organisation should show errors - CUR-4436
When importing specifications or organisations using the CSV import, they always show a success. In case rows in the import fail, they are not shown as error / warning in the result report. The change applied makes sure specification and organisation CSV imports now report row errors. A row with an invalid value, such as two values in a single-valued field or an unknown reference, is counted as failed. The errors are shown as import result to the user and logged in the job log, similar to the other imports.
Security
Our build process scans continuously for known vulnerabilities. Fixes are prioritised by impact: some go out as an immediate hotfix, others in the current or next sprint. See the central database of vulnerabilities for details.
Overarching roles should not be able to proceed the workflow - CUR-4275
Maybe not really a security issue, but it's different then a functional change. It was found that a user that is in a role against a workflow but is not the owner was able to send the workflow to the next step. A typical use case could be a “teacher” and “coordinator” that both perform a data collection task for a module. The teachers can put in their data but are not allowed to submit the module, only the coordinator is.
This has been fixed and only a participant who holds the owner role on the object the workflow runs for, can now send it to the next step.
See the Curriculum manual for configuration guidance.