Improvements

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

‍

Changing uploaded document fields should not give an error- CUR-1319

After uploading a document, fill out the document related fields gave an error. This has been (hot)fixed and it is again possible to add or modify and save fields for uploaded documents.

‍

Appraisal page should show the assessment plan with its objectives- CUR-1317

An appraisal page configured to show the assessments and their respective objects (assessment plan) didn't show this information, since the height was incorrectly calculated as 0. This has been (hot)fixed, so the height of the assessment plan is calculated correctly and the appraisal page with its assessments is fully visible again.

‍

Add support to welcome page to define the order of the shown comments - CUR-1228

A new configuration option is added to the welcome page to define the order of the shown comments. The default is comments being shown in historical order (oldest on top). By setting the added 'ordering' configuration, this can be changed to newest on top.

‍

Adding a new method should show the configured 'new method fields' - CUR-1334

When creating a new method the configured fields to define the method were not shown. This has been (hot)fixed to enable creating of methods with all configured fields available / visible.

‍

Users should be able to create new qualifications - CUR-1322

It was not possible for non-administration users to create qualifications. There was an error in assigning the given permissions correctly to the user to enable creation of a qualification. This has been (hot)fixed, allowing users with the appropriate permission to create qualifications.

‍

Creating (and editing) a new activity should respect defined conditions - CUR-1305

When creating a new activity with fields configured to only be shown on a specific (generic) condition, the validation of the condition was not respected at create. For instance only show a field if the activity is created for a module in a specific faculty. Only after save the condition was evaluated. This has been changed to enable the validation of (generic) conditions both at create and edit of activities.

Condition for the example above would then be:

• :moduleId.facultyId != 'XYZ'
• not(:moduleId.facultyId in ('ABC', 'DEF'))
• :root.facultyId != 'XYZ'
• :root.facultyId in ('ABC', 'DEF')

‍

Selecting an 'object' in a report should always work in the same way - CUR-1290

To improve usability the behaviour of clicking information lines in a report has been standardised. This to improve usability, where users now what to expect. All reports allow clicking on a line, that will open the selected object in a new tab. For instance selecting a specification from a specification list will open the selected specification in a new tab.

‍

Prevent accidental change of system relevant fields - CUR-1342

Curriculum is highly configurable and invites administrator to manipulate defined fields and add new fields to the system. Some standard configured fields have  related logic in the application, but could be changed. This change would affect the system behaviour and could even lead to errors since the expected field configuration had been changed. To prevent these accidental changes the fields with functional logic attached have been made read-only.

‍

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.

‍

Standard integration with Activity Manager - CUR-1029

As part of the AOP (academic operations platform) supporting the entire academic operations requirements from curriculum management via schedule preferences to scheduling to allocation and registration of students and finally the evaluation of the provided modules including feedback to curriculum management a new integration is standard available between Curriculum and the Activity Manager.

Via this new integration the module coordinator defined module delivery requirements (schedule preferences) can be sent from Curriculum to the Activity Manager. The standard process and integration options of Curriculum are supported, so the entered data can be sent from the process directly to Activity Manager after reaching a specific status.

The mapping configuration of the (custom) fields configured in Curriculum and activity objects and fields in Activity Manager is for the moment only available for the System Manager, but will be released as a System administrator function in the future.

‍

Descriptions using markdown lost the 'returns' in OOAPI services - CUR-1324

Descriptions written using the markdown editor lost the returns when transforming to the OOAPI format and sending the message. A fix has been applied that prevents losing the returns and exchange the (markdown) descriptions correctly to for instance eduXchange and RIO.

‍

Extend the method endpoint by providing extended period information - CUR-1272

The information on methods provided activity with a reference to the assigned offering period. To prevent from having to make an additional call to get the offering details, the response has been extended to not only provide the reference to the offering period, but also the start and end date of the offering period.

‍

Extend event based messaging to support method-events- CUR-1339, CUR-1340

Support has been added to use the event based messaging on method changes / approvals.

Export configuration and hooks can now be configured on Events to be used for automation of Method related events in processes. The relevant date fields (import date, publication date) have been added to the Method object with the same behaviour as the fields in the other objects, e.g. Module, Study, ...

‍

Extend message propagation using event based messaging - CUR-1275

Propagation can be used in event based messaging to extend the event being triggered to its children. For example in case a study is approved an event will be sent for this study. Using propagation this 'change to study' can also be configured to sent events for all of its module-group children. And by configuring the propagation for module-group this can also sent event for all of the module-groups children (module-group and/or modules).

The propagations supported are:

• * -> Specification
• Specification -> Study
• Study -> Module-group
• Module-group -> Module-group
• Module-group -> Module
• Module -> Method, Assessment
• Method -> Method
• Assessment -> Assessment

The propagations can be configured using the Export type in the custom field configuration.

‍

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.

‍

No vulnerabilities were reported during this sprint.

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.