New release Curriculum 10.9
New location documentation, release notes and release schedule
As part of the integration in the TimeEdit way of working we've moved our documentation and release notes to the TimeEdit Academy (https://academy.timeedit.com/).
Release notes
The release notes will be available, where the latest will be shown on the academy home. If you want to navigate to older release notes, you can use the button 'See all release notes' or use the direct link to: https://academy.timeedit.com/product-news/release-notes
In order to get an overview of all Release notes for TE Curriculum, use the filter on the left.
Release schedule
The release schedule is listed as part of the Release notes and is accessible via the direct link: https://academy.timeedit.com/whats-new/release-schedule-te-curriculum
Documentation
The documentation will be available via the section Guides & Tutorials.
You can use the button 'Explore all Guides & Tutorials' or use the direct link to: https://academy.timeedit.com/learn/guides-tutorials. Use the filter to select the TE Curriculum documentation.
Call to action
In case you're using references to the AscMe documentation it is advised to change these links to the new documentation at the TimeEdit Academy. The references are defined via the Administration/Label menu, and you're advised to change the following labels:
- Static.Label.Manual.Url - https://academy.timeedit.com/learn/guides-tutorials
- Static.Page.Admin.Help.Url - https://academy.timeedit.com/learn/guides-tutorials
Search by Types directly in Navigation Bar
USABILITY, CONFIGURATION- Enable (virtual and physical) delete of an academic year and its data - CUR-167
An option to delete an academic year and its data is introduced.
Virtual delete
- The administrator can mark an academic year as deleted (thus a virtual delete), the administrator can also unmark the academic year as deleted (thus undelete a deleted marked year)
- The academic year will be hidden from the year list for the normal users
Physical delete
- The script 'Clear deleted years' is added to physical delete a 'delete marked' academic year, 30 days after it has been marked as deleted.
- The administrator can schedule the script to run weekly (or at other intervals), or execute the script once needed.
- The academic year and its data will be deleted by the script 30 days after it has been marked as deleted.
This function will mainly be used to enable virtual deletion (hide) of years only. E.g. hide the older years for the users.
The physical delete should be handled with care and is advised only to use on test / acceptance environments.
Configuration additional 'report' fields
USABILITY, CONFIGURATION- Improve and standardise configuration of column orders in custom (workflow) pages - CUR-35
Different visualisation and configuration options were used to configure additional columns to be shown in different reports. This has been standardised by offering a tab to the different pages supporting configuration of the additional columns.
Improvements
- Moved 'search for available columns' under its header for clarity.
- Moved the tooltips to a label in between drag-and-drop columns.
- Fixed a bug that caused not the first x columns to be shown if the max was exceeded.
- Fixed a bug that caused the max amount of columns (3) of the method-list not to be respected.
- All column configuration now consistently use drag-and-drop in tab.
- Changed ‘structure’ page to to offer the same configuration setup as offered in the the subject matrix. The hard limit on 2 additional attributes per module / module group is still guaranteed.
- Added a visual indicator that shows the amount of selected columns. If the max selected columns is set/exceeded, a tooltip is shown to inform that the limit is exceeded and only the first X will be shown.
- Existing column selections are unaffected (same selection, different view)
Affected pages are: activity-list, appraisals, objectives, method-list, method-tree, offerings, document, subject-report and structure.
The planboard configuration remains unchanged and is still using the existing configuration option.
More improvements and bug fixes
USABILITY - The subject category should always be shown when adding a subject. - CUR-131
The subject category used to filter the selection on subjects added to a study or module was only shown in case it was set to 'required'. Since this field is used for the initial filtering on the available subjects when adding a new subject to f.i. a module this field should always be available.
CONFIGURATION, BUG- Adding persons to a role doesn't work. - CUR-238
The option to select roles (e.g. when assigning persons a role) sometimes didn't load correctly, this has now been fixed.
USABILITY - Fixed: Reporting of modules and offerings on faculty level. - CUR-235
In case a module has no offerings, the report of modules and offering on faculty level failed in case a module has been defined with no offerings. A change is applied to not break the report in case a module has no offerings.
USABILITY, BUG - TE Curriculum automatically exports approved data without active clicking the export submit. - CUR-233
The 'area of the submit export' was defined incorrectly and included expanding the of the changes. So in case the changes were expanded the 'export was automatically triggered.The 'area of the submit export', and thus the export, has been set correctly to only be triggered by clicking the export submit.
USABILITY - Sequence of offering and appraisals. - CUR-232
There are two ways to define the order of columns for pages:
- On the page, using the columns options e.g. weighting, remark vs remark, weighting
- On the custom field, by setting sequence values
Option 1 is the default in case option 2 is not configured. The sequence wasn't respected correctly.
The offerings and appraisal will now be sorted and displayed via the defined sequence order.
USABILITY, BUG - Change messages not showing changed values. - CUR-225
Some change messages showed the field names to be filled in with the 'technical to be replaced value' instead of the actual values, e.g. The method {changedEntity} ... instead of The method Lecture ...
This has been fixed.
USABILITY, CONFIGURATION - Edit and create of qualifications doesn't respect the configuration. - CUR-223
The create button for the qualifications report will use the defined create page and action as defined on qualification custom type.
Clicking on Create will open the create page. If no create page has been defined a popup with only code, localName and englishName fields will be displayed. Otherwise clicking on a report row will open the edit workflow defined on qualification custom type. If no edit workflow is defined a warning will be displayed.
The qualification contains a studyId field which depends on the selected faculty. This can be configured on the qualification studyId field by adding the filter: ':facultyId' = :facultyId
USABILITY, CONFIGURATION - Limit the selectable search objects in the basis search based on the configuration. - CUR-222
The basic search was extended with an option to specify the object-type the search will apply to, e.g. search for studies or modules. The selection didn't take the configuration into account that specifies if a specific object is available for search, and therefor showed objects that may not be in use for a specific implementation.The select option to specify the object to be searched will respect the configuration.
USABILITY, CONFIGURATION - The advice page should be usable and distinct between different roles and allow roles in the curriculum hierarchy. - CUR-220
Per object, e.g. study, only one advice page was available. This meant that all advices, irrespective of the role of the person in the process where on the same page. So an advice of an exam committee was mixed with the advice of an education committee.Furthermore only roles on the object itself could be selected as 'advice role'. This meant that on a study only roles defined on the study could be used, instead of also roles defined on the faculty.
The role selection is extend to enable both selection of roles on the object and up in the hierarchy.The advice page is now configurable by defining the 'role' it will support. By defining multiple advice pages, one for each role that will use the advice page in the process, distinct advices can be created and reported based on the role.
USABILITY, BUG - Sequence not respected on capacity page. - CUR-306
Fields on the standard capacity page will be sorted on the defined sequence order.
USABILITY - Select of assessments when adding to an objective should not always default to a page size of 5. - CUR-84
The assessment/method search components, also used when adding an assessment to an objective, had a fixed page size of '5'. This fixed value has been removed, so it will respect the user settings.
The default used in TE Curriculum had different default sizes (5, 20, 25). With this change all default sizes have been standardised to 20.
Integration
INTEGRATION, OOAPI - Extend OOAPI v5 to support eduXchange v2.1. - CUR-195
The OOAPI v5 implementation support for the eduXchange v2.1 consumer, supporting the extended information exchange with the eduXchange and EuroTeq alliance.
The specification is available at: https://openonderwijsapi.nl/#/technical/consumers-and-profiles/eduxchange
INTEGRATION - Extend TE Curriculum API for study and module-group with objective object - CUR-240
The TE Curriculum API for study and module-group is extended to also the provide the defined objectives at study and group level.
Security improvements
SECURITY - Failed logins should be logged and marked as failed. - CUR-92
Based on the OWASP #9 Security Logging and Monitoring Failures advice the failed logins will now be logged and marked as failed.
SECURITY, BUG- Credits page doesn't validate permissions to edit. - CUR-215
Fixed a bug that caused the standard credits page not to check properly if a user is allowed to edit the credit values.
SECURITY - The subject category should always be shown when adding a subject. - CUR-131
Addressed various OWASP security vulnerabilities and upgraded the Spring Boot and Spring Cloud dependencies.
- Spring Boot 3.2.0
- Spring Cloud 2023.0.0
- Spring Cloud GCP 5.0.0
- logback 1.4.14
Detailed information for each of the CVE’s can be found at the central database of vulnerabilities: https://nvd.dist.gov
Customer unique training
