Improvements

The issues mentioned under the section improvements are considered as new functionality, user experience improvements and 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.

‍

As an administrator I want to configure additional columns in the qualifications-award template - CUR-1439

The qualifications-award template provides the option to specify different qualification awards within a program. The information shown was considered limited and was not extensible.

A configuration option is added to the qualification-award template to enable configuring additional columns to be shown next to the module-group / module name. In total 4 additional columns can be added both for module-groups and modules

Person name should be shown - CUR-1701 (Hotfix)

In various reports showing user information the name of the person was not properly displayed. This has been fixed, so the name is again shown correctly.

‍

In case multiple teachers are assigned they should be shown in the teacher template - CUR-1670 (Hotfix)

The templates teacher and teacher-assign provide insight in the assigned persons to teaching and exam activities. The teacher template only showed one teacher even in case multiple were assigned. The teacher-assign showed correctly all assigned persons. The teacher template is corrected and will now also show all assigned persons.

‍

Workload calculation on activities that are 0 should not use a fallback to activity hours - CUR-1651 (Hotfix)

In case a workload calculation configured at teaching methods ended with a 0 (zero) value, the value was substituted with the activity hours. For example the case if a method calculation was based on expectedStudents and duration where the students were not filled, the calculated value is 0 (empty). This was then replaced by the activity hours.
This has been fixed, so in case a calculation is 0, this value is used as the calculated value.

‍

Workload calculation should respect the configured category- CUR-1710, CUR-1711, CUR-1717 (Hotfix)

In case a workload calculation configured to be based on activity-series and method type with a specific method category, the calculation didn't respect the category. This has been fixed, so the calculated hours will only be based on the configured category.
Furthermore, in case no category is defined, the calculation will use the calculated hours for all methods to define the total of the calculated hours.

‍

The order of subjects should be configurable - CUR-1661

The various pages to define / report subjects showed the subjects based on creation date. A new option is added to define a sequence on subjects that will enable steering the order the subjects are shown.

‍

When a module is terminated, I would like to provide a comment - CUR-810

When a module is terminated, the option is shown to select the termination model (only offering, only in program, fully), but there was no option to provide a comment to provide background on the termination. A change has been applied that will automatically show the comment prompt if a module is terminated, to allow the user to define background information.

‍

Relations with a condition on faculty should be selectable in reports - CUR-1627

In case a relation that would restrict the usage of the relation with a condition on faculty, e.g. :facultyId in ('ABC'), the relation was not selectable in reports. This has been solved, so relations with a condition will be selectable in reports.

‍

Adding subjects using Bulk Edit should respect the default level - CUR-1712

In case a subject is added to a study, the configured default level is automatically set. In case the subject would be added using the bulk select option to multiple studies, the configured default level was not set. This has been fixed, so the configured default level will be set both using individual updates and bulk edit.

‍

The subjects overview should allow to display the assigned level - CUR-1675

The subjects template extended to support display of the assigned subject level.

‍

The changes made to Faculty should be visible in the change history - CUR-1696

Not all changes made to a Faculty were added to the change history. This has been fixed, so all changes at Faculty level will be added to the change history.

‍

Workload calculation on activities bound to method/assessment not assigned to module - CUR-1718

In case activities are not defined as a relation to a module, but only have a relation to a method or assessment, the calculated hours were not added up to the module level. This has been fixed, so both activities directly attached to the module and attached to the method or assessment will be correctly added up and assigned to the module hours.

‍

Read-only reports should show no checkboxes - CUR-1662

Pages configured as read-only showed the different 'selectable functions' (button, dropdown) as a read-only form in the report. A change is made to show the actual defined value in plain text instead of the read-only visual representation. This will improve the readability of the reports.

‍

Activity-serie details not opened from search or reports - CUR-1655

When performing a search for activity-series and select the found one, or click in a report on a activity-serie the selected activity-serie was not opened. This has been fixed, so after search or select from reports the activity-serie details are opened again.

‍

Dashboard active role should always be shown - CUR-1673

In the situation where a user has two roles on an educational object (e.g. module), and one of these roles was deleted or ended, both roles were no longer shown on the dashboard. This has been fixed, so in the sketched situation the role still active will be shown on the dashboard.

‍

HTML editor should show ordered list similar in edit and preview mode - CUR-1667

The HTML editor didn't show the numeric values of an ordered list similar in the edit and preview mode. This has been fixed, so both view will show the ordered list properly and similar.

‍

In case the workload changes, the new remaining hours should be calculated and shown - CUR-1652

In case a change is made to a persons assignments or tasks, the new total is calculated. An addition is made to this functionality, where the total remaining hours base will be calculated and both the newly calculated and remaining hours values will be shown directly on screen.

‍‍

A label should support the usage of a . (period) - CUR-1639

If a label was defined with a . (period) in it, the label was not shown. This has been fixed, so labels with a . will be shown properly.

‍

Improve the loading of the activity report- CUR-1669

The activity-series-report didn't respond as expected with lots of data. The retrieval of the report is changed to support paginated data retrieval and the underlying data retrieval and filtering mechanism is changed.

‍

As an admin I want to search in the relation/role management page - CUR-49

The relation/role administration page provided a list with limited filtering. This has been extended with a search option to quickly find and select the relation to be managed.

‍

The method category should be respected when editing an activity - CUR-1699

In case a method is added, the method category is selected and the user is offered the option to select from the defined method types in this category. In case the method is edited, the restriction on the selected category is not followed, allowing the user to select any of the system defined method types. This has been fixed, so both on create and edit the method category is respected when showing the selectable method types.

‍

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.

‍

CSV uploads fail with a technical error - CUR-1708 (Hotfix)

In case (larger) CSV files were uploaded the import failed with an error. Any consecutive upload attempts would then also fail with a technical error. The cause of the error is identified and has been fixed.

‍

Extend the activity CSV with the assignment percentage - CUR-1681

In the previous sprint the option has been added to define an assignment division (percentage) for persons delivering one activity. In this sprint the activity CSV is extended with support for the definition of this assignment percentage.

The CSV information is provided in the CSV upload function, but the columns relevant for this change are:

• persons: John; Maria
• persons-percentage: 30;70

Both persons and persons-percentage support configuring multiple persons/percentages.

The similar option is added to support vacancies, using the columns vacancies and vacancies-percentage.

‍

Extend a manually executed hook on an object with result information - CUR-1713

A hook executed from an education object admin page only showed a success or failure message with no further information. The returned information is extended with the result message to get direct feedback on a possible cause.

For detailed logging on messages exchanged the Request log can be used.

‍

Enable relations in Core using year information - CUR-1689

In scheduling it might be required to keep students starting on a different moment (e.g. January or April start instead of September start) together when scheduling. To support this in Core relations are used.

For this specific situation an option is added to the Core mapping to support definition of these relations that can use year (cohort) information. E.g. a student starting in september will do the modules from the first period (September till January) in this period, where a student starting in January will do these modules as the third period from start and thus in the next academic year.

‍

Security

An integral part of our develop and build processes 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.

This release no vulnerabilities were reported, so a quit sprint on that area

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Curriculum, use the relevant Curriculum manual.