Improvements

The issues mentioned under the section improvements are considered as new functionality, user experience improvements and bug fixes.

‍

Extended support for document management - CUR-1189

The management of document (upload, download, report) was supported for modules only. The document management functions and page templates have been extended and is now also supported on Specification, Study and Module-group level.

‍

Adding a document page gives an error with limited information on the reason - CUR-1220

When adding a document page an unexpected error was shown providing no information on the reason behind the error. It turned out that the error was caused by the fact the 'document name' was not provided. In the code the document name is considered required, but in the document custom-field configuration the document name is not set as a required field.

A fix is applied that will automatically set the document name custom field as required, so the user is aware and noted the document name should be provided.

‍

Enable support for custom (form) pages for method and assessment creation - CUR-1123, CUR-1252

When creating a new method or assessment a create page is created based on the configuration of the custom-fields. This could be considered as a 'hard-coded' page, since all configured fields are shown on the create page. A new option is added to allow definition of a custom form page for method / assessment and use that page as the create page for new methods / assessments.

In case no create page is defined, the fall-back is using the method / assessment custom field configuration, just like it always was. The new create page offers the option to define a more tailored create that may have limited fields in comparison to for instance the edit page.

The configuration consists of three steps:

• Define the new create page based on the Form page template
• Define the fields to be used to create a new method/assessment
• Configure the new page to be uses as the default create page

‍

Default user language should not get lost - CUR-1250

In some circumstances, e.g. process manager, close the browser and re-login, or just a re-login the default user languages was reset to the system default. The default behaviour should be that the user selected language is kept and should be selected automatically with login and during the entire session. This has been fixed, so the language will now correctly be kept.

‍

Process can be re-opened for a period in which it's not offered - CUR-1249

The option to enable re-opening of a process by a user, e.g. a lecturer or coordinator, was not correctly limiting the re-opening option to the objects for the configured process period. In case a module was offered in multiple periods and the process was only configured for one of the periods, an individual re-open for each period was offered, instead of just one re-open for the configured period.

This has been fixed, and now the re-open respects the configured period.

‍

Extended the 'expand' function for the subject matrix - CUR-1211

The subject matrix provides insight in the match-up of learning outcomes, learning goals, skills, competences between study program and its modules. Using the objects Subject (e.g. learning outcome, competence) and Objective (e.g. learning goal). The setup of the matrix page provides the structure of the study program, including modules. The modules can be expanded to show the defined objectives (learning goals) on the module and see the match-up with the defined subjects on the study program.

Looking to the explanation above, it means there are in fact two layers in the subject matrix:

• Matchup of module subjects to study program subjects
• Matchup of module objectives to study program subjects

To support the two layers and the specific insight it provides the option is added to expand the view in steps, using an expand structure and an expand all. This expand option is provided on top of the standard 'user expansion option' that enables expanding just one module-group (e.g. year 1) or module (to show the underlying objectives).

‍

Users access is restricted and their own information is not shown correctly - CUR-1241

Due to an issue with the authentication session using an incorrect data type, the logged in person information could not correctly be used. This causes for instance the following issues, which are all (hot)fixed:

• Users not able to edit their notes
• Users not able to edit their simulations
• Users not seeing their own person label highlighted
• Workflow assignee not properly shown if current user

‍

Improved alignment of the assessment overview (report) - CUR-1249

The alignment of the assessment overview didn't correctly align the header row with the data rows. A fix is applied to improve the readability and use the same alignment for both the header and data rows.

‍

Fixed visualisation of the planboard- CUR-1221

The planboard information mis-aligned the header periods and the modules in the different periods. This has been fixed, so the planboard is showing the information as it should be, clear and crisp.

‍

Phase 2 - support the same offering period multiple times for a module - CUR-1187

The first phase to support the same offering period multiple times in a single module is added in the previous release. It enabled to select the same period twice for a single module. In this release the second phase is implemented to allow the definition of the individual activities for each of the defined periods.

From a user perspective the functionality has limited / not changed, except that you can now define multiple offering periods that include twice the same offering period, instead of multiple offering periods that are all different. Behind the scenes this has been a more complex change, that could not be solved in a single sprint.

‍

Improve the readability of the welcome page process feedback information - CUR-1177

The welcome page provides the option to show the feedback and comments given in the process. The readability has been improved by providing more distinction between the different feedback and process statuses as shown in the image below.

‍

Restriction on Edit authorisation for methods doesn't respect the editing for HTML fields - CUR-1128

In case a restriction is added to limit the Edit rights on a methods / assessment page, text fields configured as HTML text are still (shown as) editable. In case the user navigates away, the question is asked if the changes should be saved. The save will fail with an unauthorised error, since the restriction to execute the operation is validated at save too.

A fix is applied to disable the editing of the HTML fields in case the restriction on the edit operation is set (and met).

‍

Enable a blocking error on duplicate values - CUR-1011

A few releases ago the functionality was added to inform the user with a warning in case a custom-field was marked as 'unique' and the user provide a value that already existed. This release the option is added to distinct between a warning or and error message, where:

• warning: user is informed, but can still choose to save the data and create for instance a second module with the same name as an already existing one
• error: user is informed, and has to adjust the information to a unique value in order to save.

Configuration

• Set the 'Unique value' for the custom-field to have a unique value within the system
• Unset the 'Block duplicates' to show a warning to the user and allow saving the duplicate value
• Set the 'Block duplicates' to show an error, and prevent the user from saving the duplicate value

‍

HTML editor should support <br/> - CUR-1129

The new HTML editor, which is the most used HTML editor, only supports <p> (paragraph) tags and doesn't support <br> (line-break) tags. A lot of discussion is going on around this lacking of <br> where the overall statement is that <br> should not be supported, since the paragraph <p> can be style appropriate. That having said as background doesn't help with the request to support <br> since it was supported in the old HTML editor.

The HTML editor is extended to support both <p> (paragraph): Enter and <br/> (line-break): Shift Enter.

‍

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.

‍

REST API - Added faculty field to Person endpoint- CUR-1217

The REST Person API is extended with the faculty field that has been added some releases ago to the standard person attributes set. This allows for the creating and updating of persons including their main faculty.

‍

SOAP API - Extended the (custom) SOAP API for Person creation with the utq field - CUR-1248

The (historic) SOAP API for Person creation is extended with the utq field.

Since the extension of the SOAP API, which is currently only used for person creation, requires development effort and a new release of the product we have decided to freeze the SOAP API for person creation. We advise customer still using this historic SOAP Person API to switch to the new REST API that automatically will support any field created as an additional field for a person, and doesn't require development effort and new releases.

‍

OOAPI - automatic conversion of HTML to markdown is incorrect for & - CUR-1235

When using the & character in HTML it is not correctly translated to markdown format, which is the only supported method for text exchange in the OOAPI. A fix is applied to correctly translate the & character to the respective markdown format.

‍

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 mitigates the following vulnerabilities:

After some releases with vulnerability fixes, during this Sprint no vulnerabilities were reported and thus no mitigation actions had to be taken.dd

‍

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.