The release notes provide information on the features and improvements in the specified version. The release dates that are related to the version of the release are published in the Curriculum/Workload Management release schedule.
Improvements
The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or 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 a department manager I want to approve ad-hoc absence requests - CUR-2034
(Un)availability management of staff members is standard supported in different means. The until this release supported (un)availability was based on generic setting steered with the weekly availability pattern or a number or percentage of unavailability hours in the context of workload.
The image below shows the user screen to define the weekly availability pattern.
In this release the option is added to support the request of 'ad-hoc' unavailability by a user and the approval by the HR manager.
A new screen is introduced called 'unavailability', that can be added to the user Tab settings as shown in the image below, but can also be added into a workflow to gather 'ad-hoc' unavailability prior to the semester start.
The user is shown an overview of the ad-hoc requests done and their status. The user can define additional ad-hoc unavailabilities by clicking the Add button.
The user can specify:
- Start and end date
- Start and end time
- Type, allowing to define if it should be set als unavailable, available or rather not
- Description to define the reason for the absence
The HR manager will have access to the Absence report (unavailability-report) that will show an overview of the the staff unavailability request.
The image below shows the standard view. The HR manager can filter on date to select only request that have been filed between specific dates, or on status to only see the 'open' requests (or the approved / rejected ones).
The HR manager can use the toggle buttons to 'select all' or 'select one/more' requests from the list. In the image below the HR manager selected one request. Once selected the Approve and Reject button appear to enable the HR manager to manage the request.
In case the HR manager approves the request, a pop-up appears that allows the further handling of the request. The HR manager can decide to just accept and without providing any additional information and handling, but can also decide the absence should both have effect on the availability in scheduling and in the availability of the person in relation to workload.
In the image below the latter is chosen. The HR manager has marked that for this request a 'task' should be created that will have effect on the total availability of the person. The request should be marked and saved as an ad-hoc absence task in the users profile. The amount of hours is calculated based on the request, but can be adjusted at this moment.
If we then look at the users profile, we notice a task has been added in the section 'Absence'. The task size is 16 hours and this 16 hours will be deducted from the total available hours for the person.
This means that an unavailability 'marked' as task will lead to an additional deduction of hours, next to the standard user availability hours that already has deducted the contract defined leave hours.
Buttons to manage activities in the activity-grid should be accessible - CUR-2164
The activity grid shows a visual representation of the desired teaching layout (activities). The activity-series and activities defined can be managed using the buttons shown in the tile. However, in case a long(er) activity name was used, the name was positioned on top of the buttons, making them inaccessible. A change is applied to truncate the activity name and not float over the button. The button is now always accessible and the full name of the activity is available using mouse-over.
As an administrator / implementation manager I want to brand the used product - CUR-1993
The Workload management and Curriculum product partly use the same configuration and administration interface. Using the administration interface the 'branding' of the product can be defined and differentiate between the Workload management or Curriculum branding.
Configuration:
Navigate to the Administration -> Config menu option
- Set the 'header.workload-product' to true to use the Workload management branding
- Set the 'header.workload-product' to false to use the Curriculum branding
- Optional set the 'header.product-switcher' to activate the TE product switcher including the branding selected
Security
An integral part of our development and build process 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. For more information on reported vulnerabilities, see the central database of vulnerabilities.
This release no vulnerabilities has been reported that require mitigation.
Refer to the Workload Management manual for configuration guidance.