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.
The usage of end-date and terminated in year copy and display should be clear and standardised - CUR-2062
Based on questions and feedback on the usage of the terminated flag and/or the start and end date on objects and the 'sometimes felt magic' we have standardised and streamlined the behaviour.
The standard (and implemented) behaviour is defined as:
- Terminated flag will be used for the 'roll-over exclusion'
- In case an object is marked as terminated, the object will be excluded from the year copy
- In case an object is marked as terminated, the object will be excluded from the year copy
- End date will be used for the ‘roll-over exclusion’.
- In case the end date is before the start date of the new year, the object will be excluded from the year copy.
- The object will only be visible in Curriculum if the end date is not yet passed, thus end date > start selected academic year. This use case supports ending objects that were not yet ended before the year copy, but still should not be offered.
- Consistent usage of start and end date on the relevant objects specification (data), study, module-group, module, subject
Based on the start date the functionality should be:- The object should always be visible in Curriculum
- The relevant pages (structure, list) will have a visual indicator to highlight objects with a start date in the future
- The relevant pages (structure, list) should have a filter option to only show objects with a start date in or prior to the active academic year, to support visualisation of the ‘this year active setup’.
- The integration should have a configuration option to filter out objects with a start date in the future.
- For integration with Core and Study Guide this filter should be applied.
- Filter for other integration depends on the use case of the customer.
- The integration should have a configuration option to filter out objects with an end date in the past.
- For integration with Core and Study Guide this filter should be applied.
- Filter for other integration depends on the use case of the customer.
- On the general tab show the terminated, start and end date information
The behaviour mentioned above is not yet 100% percent finished yet. The main focus was on getting the behaviour defined and implemented for the year copy.
The 'filter option in the pages to filter on end date in current year, the configuration option for integration to filter on end date also requires some more work to be done in the next sprint(s).
A terminated module-group should not be copied in the year copy - CUR-1873
Even if a terminated module-group was marked as 'terminated', the module-group was still copied to the next year. This has been fixed, so the terminated flag will prevent the object from copying over to the new year
As an administrator I want to configure access to the appraisal page based on assessment and/or activity-serie - CUR-2084
A long awaited feature is the option to limit the access to the appraisal page to the different types of information. In the current setup if a user has access to the appraisal page, the user was allowed to manipulate (add, update, delete) assessments and manipulate the activity-series (add, update, delete). There was no option to limit access to only the activity-series, allowing to have the definition of the assessments done earlier in process or by other stakeholders.
A change has been made to the authorisation and the behaviour of the authorisation on the appraisal page. This will support the limitation of access to all options, or only activity-series.
Configuration options:
- Page configuration: Read-only
All information is available in read-only mode only - Authorization: EDIT_APPRAISAL
- Allow access to manage the appraisal tree and the assessments
- Allow access to the activities owned by the 'you' - Authorization: EDIT_SCHEDULE
- Allow access to manage the activity-series and activities
So in order to define the authorization for a role that is NOT allowed to manage the assessment but SHOULD manage the activity series, this should be:
- EDIT_APPRAISAL (not allowed)
- EDIT_SCHEDULE (allowed)
The page template 'discussion' should show feedback, notes and advise - CUR-2090 (Hotfix)
The page template 'discussion' was broken, and didn't show any feedback, notes or advise that has been given. This has been fixed, so the information is shown again.
The description change overview should show changes in numeric lists correctly - CUR-1897
The historic changes overview of the description pages didn't show the changes applied to a numeric list correctly. This has been fixed, so the changes in lists are shown as expected.
Comments defined as while 'impersonating' should be defined under the impersonated person - CUR-1699
In case a user is logged in 'impersonating' another user, any changes or comments made should be registered as changed by X on behalf of. It was noted that not all comments applied this registration. This has been fixed, so all changes applied by an 'impersonating person' are registered with the relevant on behalf information.
Propagation of descriptions to next year should not fail - CUR-2053 (Hotfix)
Descriptions marked to propagated to the next year on change weren't always correctly propagated. In this context propagation is a configuration option to keep data multiple years in sync in case these years are already created.
The use case is that a new year is created based on a copy of the previous year. This means all changes for the new year should be made in that new year. There are however still changes in the current year that would be nice to be synchronised/copied to the new year (even after the year copy). The propagation option is used to configure which fields should follow this synchronisation pattern after a year copy has been done.
The read-only activity-grid should not be editable after reload - CUR-2102 (Hotfix)
In case the activity-grid was defined as a read-only page, the information was shown in read-only mode. However, in case the user did a refresh of the Browser (page), the page was reopened in edit mode. This has been fixed, so the read-only activity-grid will stay read-only even after Browser refresh.
The planboard should support retrieval of multiple offerings in same period - CUR-2086
Since the introduction of the support for multiple offerings in the same period, we now and then get a bug request for a page-template that was missed / not fully corrected changed to support this multiple-offering implementation. The planboard was one of them, and has been extended to deliver support for the multiple offerings in the same period.
Next to this extension, also some usability have been applied to provide an even better user experience.
The activity-grid should not duplicate the scheduled flag in case duplicate offerings in same period are defined - CUR-2015
In line with the above issue, the activity grid had a small issue when using multiple offerings in the same period. In case the 'schedule' flag was used, this was not only applied to the selected offering, but was also defined for the other offerings in the same period. This has been fixed, so the flag is set for the selected offering in period only.
New created module-group in structure should be added to the structure - CUR-2110 (Hotfix)
In case a new module-group is created within the structure tree, it should be added to the module-group / study it was created on. This was not always the case, and after some investigation the cause was identified. The authorisation to change the structure tree, e.g. add the just created module-group, was not correctly for module-group added to module-groups that were deeper than 2 in the hierarchy. This has been adjusted, so the proper authorisation rule is applied, allowing to add the module-group to the structure tree.
An authorised user should be able to remove a module from the structure tree - CUR-2098 (Hotfix)
In some cases an authorised user couldn't remove a module from the structure tree. The cause was the same to the issue above and was an incorrect validation of the authorisation rule on deeper nested module-groups. This is fixed for both issues.
The page template 'methods' should show the defined methods - CUR-2096 (Hotfix)
The page template methods was broken and didn't show the defined methods anymore. This has been fixed, so the methods page will show the defined methods again.
The validation on activity-series should be limited to the activity-series - CUR-2092
The method-tree page template supports the option to show any validation rules in the defined methods and activity-series. In case the validation was applied, with duration as an required field, the validation always gave an error / warning even if the duration was set. This has been fixed, and the error/warning is only shown if relevant.
The UI should align the columns correctly - CUR-1919, CUR-2070, CUR-2108, CUR-2113
A number of changes has been applied to the user experience / usability. Some small bugs, other to improve the visibility of data. Changes are made for:
- Subjects page columns should be correctly aligned
- Buttons in the structure tree should now exceed the page width
- Column headers in (all) reports should be correctly aligned
- @tag in comments should show the pop-up for user selection in the foreground, to enable user selection.
Bulk select of subjects should respect the configured subject category- CUR-1912
When using bulk select to add multiple learning outcomes (subjects) in one action to a study or module, the provided subject options should be limited to the subject category defined on the page configuration. E.g., only show subjects of category 'skill' or 'learning outcome'. The subject category wasn't used as a filter, so the user could select subjects of any type. This has been fixed, so the shown subject for bulk select adhere to the configured subject category.
The subject page-template should show the subject categories based on the defined sequence - CUR-1821
In case the subject page shows more subject categories, the order in which the categories were shown was more or less random. This has been changed, so the order will now use the sequence number as defined on the subject category
New page template subject-report launched - CUR-1877
A new report is launched that offers the option to report on all defined module subjects and its added custom-fields.
The report template is having the same options and behaviour as all other reports.
Configuration:
- Create a new custom-page of type subject-report (administration -> custom-pages)
- Add the page as a Tab (administration -> tabs) to for instance the study
- Define the root type to define the object type the subjects should be reported on
- Module: show subjects related to modules (report from faculty, study, module-group)
- Study: show subjects related to studies (report from faculty)
- Define the root type to define the object type the subjects should be reported on
- Open a study, select the tab to show all subjects defined for modules in context of that study
The filtering on the route-planner should filter correctly - CUR-2022
The route-planner filter options didn't work as it should be. Depending on order of selecting and deselecting the select options could even get stuck, requiring a page refresh. This has been fixed, so the filtering should work as expected, independent of previous actions.
Usage of elements and/or references should not give errors or numeric IDs - CUR-2060, CUR-2088
In the previous sprint (release) some performance optimisations were applied for elements and references. In some cases the created temporary cache was not populated correctly (internet speed, busy laptop, ...), which was not correctly flagged. This could cause that the 'cache' used was not properly setup, causing errors or showing numbers instead of names or codes. This has been fixed, so the cache will be populated, marked as correct and used, or re-populated till it's OK.
The activity-series page template should respect the field configuration - CUR-2072
The activity-series page template provides information on the fields configured for the activity-series. What fields to show is configurable, like with all other objects, but in this case the page template didn't partly follow the configuration and threw in some fields by itself. This has been fixed, so the activity-series template will only follow the configuration.
The offering info in the structure tree should provide a mouse-over - CUR-2048
The introduction of the option to define a pattern when showing offering information, e.g. period and location, the length of the information shown has grown. In the structure tree this could cause effects that the information was partial readable, or even information could be not visible when the column width was exceeded. In order to have access to all information a mouse-over is implemented.
The underlying workflow page should be refreshed in case the data is changed using a workflow popup - CUR-2066
In case a workflow page uses a 'popup' to define information that is shown on the workflow page, after saving the information and closing the pop-up the workflow page wasn't automatically refreshed. The user had to refresh of 'guess' that it was OK. From a usability perspective this could be improved, and in this sprint we've added an automatic refresh of the workflow page in case information has been added / changed for that page using a pop-up.
The changes to the cost calculation base details should only be accessible to the authorised user - CUR-1916
The cost calculation module annual settings on budget, cost division, student flow percentages, etc. were configurable at multiple places and by different roles. This has been standardised to only support configuration of the 'faculty / organisation' based settings at faculty level by the user (role) having access to this specific information.
The information could also (partly) be modified in the cost-structure page. This 'change' option is removed, and the information is only in read-only available.
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.
Extend the subject CSV to support related IDs - CUR-2015
The subject CSV is extended with support to define related ItDs. This allows when adding a subject to a module to define the study/studies the subject is related to.
Improve error handling and messages for the routes-step CSV import - CUR-2085
The CSV import of route-steps didn't provide a proper functional error message, but more a technical error. This has been changed so in case import fails a more functional message is shown to help the admin in finding the root cause of the failure.
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 has been reported that require mitigation.
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.