{"text_format":"1","workbook":"xlsx","n_sheets":1,"sheets":["Release notes"],"not_rendered":{"charts":0,"images":0,"macros":1,"external_links":0,"defined_names":0,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Release notes","index":0,"n_rows":315,"n_cols":8,"rows_kept":315,"cut":false,"hidden":false,"merged":[]}
[]
["Date Test&Internal","In production","Date in production","Type","Title","Description","Upgrade note","Item number"]
["2022-09-22","Yes","2022-10-07","Feature","Widen shift cells","This has been improved and the user will now see a proper error page with the ability to logout of their account.",null,4220]
["2022-09-22","Yes","2022-10-07","Feature","Show shift times in schedule","It is now possible to show the shift begin- and end times directly in the schedule view. This can be enabled by a new toggle that has been added to the schedule view settings (located in the top right of the schedule).\nAs the begin- and end times require a minimum cell width, enabling the toggle will automatically set the zoom level to 200%.",null,4221]
["2022-09-22","Yes","2022-10-07","Feature","Display subcontracted shifts in schedule","It is now possible to see and recognize subcontracted shifts in the schedule. They are visualized with a grey progress bar at the bottom  and the shift name will be displayed in italic. The shift keeps its original color (white/blue/yellow). The hint text of the shift is extended with the subcontract status. ","Only available with ORTEC WS update higher than 1505113",4160]
["2022-09-22","Yes","2022-10-07","Feature","Display subcontract info into shift details","Clicking on a subcontracted shift now shows additional subcontract information, such as the department it was subcontracted to and the subcontract status. In addition, some shift actions are limited based on the subcontract status. The following statuses are relevant.\n\nOpen - The receiving planner has not accepted the subcontracted shift yet. It is still possible to edit the shift.\nIn progress - The receiving planner has accepted the subcontracted shift (note: this status is a combination of the old accepted & concept planned statuses). It is not possible to edit the shift. \nFinal - The subcontracted shift was assigned to an employee and this employee is now visible in the schedule. It is possible to edit the shift again.\n\nA rejected subcontracted shift will be treated as a 'regular' shift. The user will not see that it is/was subcontracted.\nIn any status, it is not possible to delete a subcontracted shift from the schedule. First, the subcontract should be canceled.","Only available with ORTEC WS update higher than 1505113",4179]
["2022-09-22","Yes","2022-10-07","Feature","Subcontract shift to flexpool","It is now possible to subcontract a shift to a Flexpool department. For now, this can be done only in the \"Selection mode\" (multi-select mode). When selecting one or more vacant shift(s), an option is available in the \"Actions\" menu to subcontract the shift(s). Clicking on that action opens a popover menu where you can select a Flexpool department to subcontract to and, optionally, you can enter a remark for the Flexpool planner.","Only available with ORTEC WS update higher than 1505113",4180]
["2022-09-22","Yes","2022-10-07","Feature","Cancel subcontracts","It is now possible to cancel a subcontract on a shift. For now, this can be done only in the \"Selection mode\" (multi-select mode). When selecting one or multiple shifts that are subcontracted, an option appears in the \"Actions\" menu to cancel the subcontract(s). \nNote: It is only possible to cancel a subcontract that is in status \"Open\".","Only available with ORTEC WS update higher than 1505113",4161]
["2022-09-22","Yes","2022-10-07","Feature","Add permission + toggle for Optimizer functionality","A new Access Control permission has been added that allows the user to start an Optimizer in ORTEC WS for Team Schedulers. Previously, the Optimizer was always available for ORTEC WS for Team Scheduler users.\nThe new permission is located in the (new) permission category \"ORTEC WS for Team Schedulers\"","Only available with ORTEC WS update higher than 1505571",2206]
["2022-09-22","Yes","2022-10-07","Bug","Not possible to select night shifts on last day of schedule","It was not possible to select night shifts on the last day of a schedule. This has been fixed. ",null,3664]
["2022-09-22","Yes","2022-10-07","Bug","Strange hint text employee requests","When a shift was dragged and held over an employee request, an irrelevant tooltip was shown. This has been fixed.",null,4959]
["2022-09-22","Yes","2022-10-07","Bug","Incorrect  sorting if employee has >1 shifts","When a user would drag a shift into a cell that already contained other shifts, it would add the new shift at the end. Now all shifts are shown in order of start date and time, including new ones added.",null,4638]
["2022-09-22","Yes","2022-10-07","Bug","Error message when opening a schedule from the dashboard on 1st day of rosterperiod","When opening a schedule from the dashboard on the first day of that schedule, an error was shown and the schedule was not loaded. This has been fixed.",null,4495]
["2022-09-22","Yes","2022-10-07","Bug","It should not be possible to drag an outgoing subcontracted shift","Users were able to drag outoging subcontracted shifts into the schedule,. After the drop an error notification was shown and the shift was moved back to its original place. To prevent this, subcontracted shifts cannot be dragged anymore. ",null,5208]
["2022-11-11","Yes","2022-11-25","Feature","Workstations on activity level","It is now possible to view and edit workstations for an activity in a shift, if this functionality is turned on in ORTEC WS (with the general setting UseWorkstations). This feature also takes into account the activity type attributes \"Entering a workstation is required\" and \" Entering a workstation is not allowed\".","Only available with ORTEC WS update higher than 1516666",4304]
["2022-11-11","Yes","2022-11-25","Feature","Cost centers on activity level","It is now possible to view and edit cost centers for an activity in a shift, if this functionality is activated in ORTEC WS (with the general setting UseCostCenterActivityType). When editing the cost center for an activity, the cost centers will by default be displayed in a tree view as it is configured in ORTEC WS. There is no option to present the cost centers in a flat list. Note: If the tree is more than 5 layers deep (which is an exceptional case), the user might run into some small usability issues. ","Only available with ORTEC WS update higher than 1516666",4305]
["2022-11-11","Yes","2022-11-25","Language","Finnish language","The app is now available in the Finnish language. ",null,5297]
["2022-11-11","Yes","2022-11-25","Improvement","Shifts in other departments shown in italic","To distinguish shifts from other departments better, they are now shown with italic names.",null,6377]
["2022-11-11","Yes","2022-11-25","Bug","Error message for schedules without employees ","Opening a schedule for a department without employees doesn't show an error anymore.    ","Requires ORTEC WS update >= 1516666",5391]
["2022-11-11","Yes","2022-11-25","Bug","Horizontal calculations did not work","It was not possible to retrieve horizontal calculations when the general setting 'UseHideTransferredEmployeesOnRunningAccount' was activated. This has been fixed. ","Requires ORTEC WS update >= 1514209",5844]
["2022-11-11","Yes","2022-11-25","Bug","Shift counters incorrect in case of  identical shifts in other department","Shift counters in the Staffing tab now take into consideration only shifts belonging to your selected/current department. Previously, shifts with identical names from other departments were also counted.",null,6376]
["2022-11-11","Yes","2022-11-25","Bug","Incorrect violations for \"Daily rest after shift (labor period)\"","Violations caused by the labor rule \"Daily rest after shift (labor period)\" were visualized for every employee on the day of the violation. This has been fixed.",null,5950]
["2023-01-03","Yes","2023-01-17","Improvement","Performance improvement vacant shifts","The performance when dragging and dropping shifts from the vacant shift section to employees is significantly improved, mostly noticeable in cases with a lot of vacant shifts.\nNote: As a side effect, the vertical spacing between vacant shifts is slightly increased and is now equal to the vertical spacing between assigned shifts."]
["2023-01-03","Yes","2023-01-17","Improvement","Automatically lowering shift status when doing a realization","•\tA shift with a status higher than its corresponding schedule was previously treated the same as any other shift in ORTEC WS for Team Schedulers.\nThis could result in unforeseen situations, for example in which an (unapproved) pending shift update was created without the user noticing it.\n\nA well-known scenario for such a case is a schedule that was previously approved, but that was later lowered in status. For performance reasons, ORTEC WS does not lower the status of those shifts by default.\nUsers in the ORTEC WS Client first have to lower the status of the individual shift via the right-mouse menu before they can make changes.\n\nIn ORTEC WS for Team Schedulers, this has been made easier. Shifts that have a status higher than their schedule status will now automatically be lowered to the schedule status when a realization is made.\nHowever, the user does need one of the following (existing) permissions, depending on the shift/schedule status combination:\nSHIFT_PROC_AGREED_ForDepartment, SHIFT_AGREED_JUST_ForDepartment, SHIFT_JUST_PUBL\n\nIf the user does not have the correct permissions an error could occur.\nNote: The status of the shift will remain at the schedule status after the realization.","Requires ORTEC WS update >= 1525753 ",7095]
["2023-01-03","Yes","2023-01-17","Bug","Changing status not possible","Changing the status of a schedule was not possible in certain situations. This has been fixed.                                                                            ","Requires ORTEC WS update >= 1525753 ",6448]
["2023-01-03","Yes","2023-01-17","Bug","Employee requests multi-week patterns incorrect","Employee requests were sometimes not shown correctly in case they had multi-week patterns. This has been fixed.                                  ","Requires ORTEC WS update >= 1525753",6921]
["2023-01-03","Yes","2023-01-17","Bug","Stopping optimizer did not work","Stopping the optimizer was not possible in case Backend Domains API calls were handled by an interface worker. This has been fixed","Requires ORTEC WS update >= 1525753",6945]
["2023-01-03","Yes","2023-01-17","Bug","Employee realizations not shown as changed shifts","Shifts with an (approved) employee realization now also have the 'changed shift' icon visualized on the shift","Requires ORTEC WS update >= 1525753",7510]
["2023-01-03","Yes","2023-01-17","Bug","Shift counters not correct in case of identical names","Shifts with identical names but with different originating duty set duties were not counted correctly in the shift counters. This has been fixed. Shifts in the Staffing tab are now grouped by their originating duty set duty. \nNote: As a side effect, one-time shifts with identical names are not counted in the Staffing tab.",null,6861]
["2023-02-20","Yes","2023-02-27","Feature","Subcontract to any department                                                                                                                                                                                                          ","It is now possible to subcontract shifts to any department in the organization, instead of just Flexpool departments. This makes it possible to subcontract shifts to other planners in ORTEC WS for Team Schedulers.\nShifts that are subcontracted to you are now distinctly visible. This means they are visualized differently than shifts you subcontracted yourself to other departments.\n\nThe available departments to subcontract to are now determined by the existing Access Control permission SHIFT_SUBCONTRACT_TO, more specifically for the departments for which this permission is granted.\n","Requires ORTEC WS update >= 1533112\n\nUpgrade note for customers already using the subcontract functionality in ORTEC WS for Team Schedulers: After placing ORTEC WS update 1533112 (or higher) the list of available subcontract departments is empty until the SHIFT_SUBCONTRACT_TO permission is correctly granted.","4622/4623"]
["2023-02-20","Yes","2023-02-27","Feature","Handle subcontracted shifts","It is now possible to handle incoming subcontracted shifts from other departments with similar logic as used in the ORTEC WS Client. This means it is possible to (optionally) accept an incoming subcontracted shift, directly assign it to an employee in concept status and to finalize the subcontract. \nAfter finalizing, the employee will be visible in the sending party’s schedule as a borrowed employee (after a schedule refresh). It is also possible to set a finalized subcontract back to concept. \nNote: For now, these actions are only possible in the selection mode under the Actions menu. In the future it will also be possible to do these actions from the detail window of an individual shift.\n\nYou can now see that a subcontracted shift was declined by the receiving party. In this case the subcontract progress bar of the shift is colored red. This (red) bar disappears when the shift is assigned to an employee. ","Requires ORTEC WS update >= 1533112",4624]
["2023-02-20","Yes","2023-02-27","Language","French language","The app is now available in the French language. ",null,8636]
["2023-02-20","Yes","2023-02-27","Improvement","Not possible to edit shifts anymore in schedule with status Closed or higher","It is no longer possible to edit shifts in a Closed, Approved or Processed schedule. Note: This is done because we don’t support pending shift updates in Team Scheduler for the time being and it prevents the user changing a shift without seeing the effect of it.",null,7096]
["2023-02-20","Yes","2023-02-27","Improvement","Horizontal calculations available sooner","Due to the way horizontal calculations are pre-calculated and stored in Cosmos db, it could take up to 24 hours for horizontal calculations to appear when opening a new schedule or when applying a new horizontal calculation set. This has been changed. If calculations are not yet available in the Cosmos db when opening a schedule, an event is triggered to actively retrieve the calculations and store them directly.",null,8243]
["2023-02-20","Yes","2023-02-27","Bug","First day not directly visible with zoom level >100%","If the configured zoom level in the schedule was greater than 100%, a schedule would open without the first day being directly visible. This has been fixed. When opening a schedule, it now always starts on the first day, regardless of the zoom level.",null,6207]
["2023-02-20","Yes","2023-02-27","Bug","Errors when rapidly assigning shifts to same employee","Multiple rapid updates of the same employee schedule are now processed sequentially and therefore do not result in conflict errors anymore. This was most notable when assigning shifts to the same employee in rapid succession.",null,6737]
["2023-02-20","Yes","2023-02-27","Bug","Error when opening schedule in case of duplicate horizontal calculations","Opening a schedule could sometimes result in an error in case duplicate calculations for the same employee/schedule combination were found in the Cosmos db. This has been fixed by adding an extra check that prevents the insert of identical horizontal calculations in the Cosmos db.",null,8724]
["2023-03-16","Yes","2023-03-30","Feature","New permissions","New permissions have been added for ORTEC WS for Team Schedulers. They can be found in the ORTEC WS for Team Schedulers permission category in Access Control. The new available permissions are:\no\tApprove leave requests - Without this permission it is not possible to approve or decline leave requests in the leave requests dashboard tile. \no\tApprove swap requests - Without this permission it is not possible to approve or decline swap requests in the swap requests dashboard tile. \no\tReplace with sick leave shifts - Without this permission it is not possible to replace shifts with sick leave in the sick leave dashboard tile. \no\tPublish schedules - Without this permission it is not possible to set the status of a schedule to Published. \no\tClose schedules - Without this permission it is not possible to set the status of a schedule to Closed.\no\tEdit schedules - Without this permission it is not possible to do any mutations in the schedule view. \nNote: The existing Team Schedulers permission \"Allowed to start Optimizer\" now also needs the \"Edit schedules\" permission.","Requires ORTEC WS update >= 1537826\n\nTo prevent any backwards compatibility issues, Access Control user groups that had the general \"Team scheduler (departments)\" permission will automatically receive these new permissions when the Backend Domains API is updated.",5571]
["2023-03-16","Yes","2023-03-30","Feature","Subcontract remark","It is now possible to see the (optional) remark that was added when a subcontract was created. The subcontract remark is visible in both the shift details and edit shift windows. \nWhen a subcontract remark is present, the shift also gets the existing remark icon (asterisk) in the schedule view.",null,5996]
["2023-03-16","Yes","2023-03-30","Improvement","Decline subcontract from shift details","It is now possible to decline a subcontracted shift directly from the shift details window. \nNote: Other actions on a single subcontracted shift, such as accepting or finalizing the subcontract, will follow in a future release. For now, these other actions can be done in the selection mode.",null,6457]
["2023-03-16","Yes","2023-03-30","Improvement","Violations icon properly aligned","The violation icon is now properly aligned with the corner of a shift.",null,8785]
["2023-03-16","Yes","2023-03-30","Bug","Not possible to to change shift demands","When dutyset duties were not valid for the entire scheduling period, it was impossible to change shift demands in ORTEC WS for Team Schedulers for that period.       ","Requires ORTEC WS update >= 1535556",8736]
["2023-03-16","Yes","2023-03-30","Bug","Incorrect dates in confirmation message when publishing","When publishing a schedule, the confirmation notification sometimes did not show the correct dates. This has been fixed.",null,9261]
["2023-03-16","Yes","2023-03-30","Bug","Public holidays not always visible","Public holidays were sometimes not visible in the schedule. This has been fixed.",null,9292]
["2023-03-16","Yes","2023-03-30","Bug","Action menu counters not always correct","The counters in the Actions menu, which show for how many shifts a certain action will be performed based on the selected shifts, could be incorrect if another action was done previously. This has been fixed.",null,8428]
["2023-03-16","Yes","2023-03-30","Bug","Issue in schedules with daylight saving time change","When the start and end dates of a schedule were in different time zones due to daylight saving time, the schedule dates were displayed incorrectly and it was not possible to apply the cyclical schedule and demands for the entire period. This has been fixed.",null,8850]
["2023-04-13","Yes","2023-04-20","Feature","Handle subcontract from shift details","It is now possible to handle shift subcontracts directly from the shift details window. This makes it possible to handle individual shift subcontracts without having to use the selection mode.\nThe shift details window now provides the option to subcontract the shift, but also options to set the different subcontract statuses in case of an incoming subcontracted shift.",null,6361]
["2023-04-13","Yes","2023-04-20","Improvement","Title of schedule more explicit in case of non-full month periods","The title shown in the schedule header is now more explicit in case of non-full month schedules. It now shows the begin- and end date instead of only the month name.",null,8767]
["2023-04-13","Yes","2023-04-20","Language","\"Costs\" label for Optimizer changed to \"Score\"","Translation for the label showing the internal costs of the Optimizer changed from “Cost” to “Score”. This should be clearer for end users, e.g. it can no longer be confused with actual monetary costs of the schedule.",null,10163]
["2023-04-13","Yes","2023-04-20","Language","Updated German translation for applying cyclical schedule","German translation for “Apply cyclical schedule and shift demands” updated.",null,10151]
["2023-04-13","Yes","2023-04-20","Bug","Schedules won't open in case of many subcontracts in the database","Opening a schedule was very slow and could result in timeouts when there are a lot of subcontracts in the database. The query used for retrieving the schedule contents has been improved.\t\t      ","Requires ORTEC WS update >= 1543005",10181]
["2023-04-13","Yes","2023-04-20","Improvement","Extend refresh calculations functionality when opening schedule","When opening a schedule, horizontal calculations were only updated in case the schedule did not have any cached calculations at all. This has been improved.\nNow, all calculations for the employees are checked when opening a schedule. Recalculations are triggered for outdated (older than 24 hours) and missing calculations.",null,10261]
["2023-04-13","Yes","2023-04-20","Bug","Add shift functionality uses vacant subcontracted shifts ","The add shift functionality was mistakenly trying to use a subcontracted shift from the vacant shifts when adding a shift of that type, resulting in errors. This has been fixed. Now a vacant shift will only be used when it is actually allowed (e.g. no active subcontract).",null,10017]
["2023-04-13","Yes","2023-04-20","Bug","Processed swap requests details window has been improved","The details window for (automatically) processed swap requests has been improved. Error messages are no longer visible and the approve/decline buttons have been removed. \t\t","Requires ORTEC WS update >= 1525753",8079]
["2023-04-13","Yes","2023-04-20","Bug","Illness percentage sometimes not correct","Illness percentages were sometimes not shown correctly in the hint text of the absence. This has been fixed.",null,8152]
["2023-04-19","Yes","2023-04-20","Bug","Timeouts when opening schedule","Timeouts could occur when opening a schedule with many outdated or nonexistent calculations. This been fixed.",null,10439]
["2023-05-15","Yes","2023-05-31","Improvement","Schedule component upgrade","The main component used for the schedule view has been upgraded to its latest version. This provides several benefits to the user:\no\tThe overall performance of the schedule view has improved, most noticeable in large schedules with a lot of data. For example: scrolling through a large schedule should be more fluent. \nPlease note this only concerns the UI part of the schedule (rendering the schedule elements). The time needed to retrieve data through the API’s is not affected. \no\tThe grouping functionality (on sorting groups) no longer requires a refresh of the schedule. Instead, employees will be instantly grouped.",null,4575]
["2023-05-15","Yes","2023-05-31","Improvement","Cost center tree view dialog improvements","Several small styling and UX improvements to the activity cost center dropdown menu.",null,"6393, 7090, 10587"]
["2023-06-07","Yes","2023-06-21","Feature","Send shifts to central department                                                                                                                       ","Notes:\n-\tThis feature is only available when the central departments functionality is activated in ORTEC WS (UseCentralDepartments).\n-\tThis feature is meant to support the decentral side of the central departments functionality. The central department side is not supported and it is expected that central department planners use the ORTEC WS Client.\n•\tIt is now possible to send shifts to the central department. A new action has been added to the selection mode Actions menu. When used, all selected shifts will be sent to the central department of the department you are working in (there can be only one at a time).\n•\tShifts that are sent to a central department have a distinct visualization. The shift details dialog shows additional information when the shift is sent to a central department.\n•\tOnce a shift is sent to a central department, the user can no longer do any changes to this shift. However, a new Access Control permission has been added called “Edit shifts that are sent to a central department\". \nWith this permission it is possible to (only) edit the contents of the shift, even though it is currently in the central department. The permission is disabled by default.","Requires ORTEC WS update >= 1550417",4325]
["2023-06-07","Yes","2023-06-21","Permission","New permission for \"Apply cyclical schedule & shift demands","A new Access Control permission has been added called \"Apply cyclical schedule & shift demands\".  Without this permission it is not possible to apply a cyclical schedule or shift demands from the Actions menu in the schedule view. \nNote: The existing permission \"Edit Schedules\" is also needed to make the functionality available. For user groups that already had the Edit Schedules permission, the new permission is enabled by default to ensure backwards compatibility.","Requires ORTEC WS update >= 1550417",10063]
["2023-06-07","Yes","2023-06-21","Bug","Unexpected removal of overstaffed shifts when editing","When an overstaffed vacant shift was edited, it could happen that the shift was deleted right after saving the changes. This has been fixed. Now, changing the properties of an overstaffed shift will not lead to the removal of the shift.",null,11269]
["2023-06-23","Yes","2023-07-05","Feature","Offer shifts","•\tIt is now possible to offer shifts to employees, both from the shift details window for single shifts, as well as the selection mode for multiple shifts.\n•\tOffering a shift will make the shift available in ORTEC WS for Employees / ESS7 for picking or bidding (depending on the ESS configuration).\n•\tAn offered shift is visualized by a distinct icon on the shift in the schedule view. The shift details window and the shift hint text also provide information about the offered status.\n•\tAn offered shift can also be withdrawn. Withdrawing the offer means the shift is no longer available for picking or bidding in ORTEC WS for Employees / ESS7.\n\nNotes:  \n- This functionality is only active when the Bidding module is enabled in ORTEC WS\n- Because ORTEC WS for Team Schedulers does not show duty wishes yet, it is advised to only use this functionality in case employees can directly pick a shift. Showing and handling bidding requests / duty wishes is part of the ORTEC WS for Team Schedulers roadmap.","Requires ORTEC WS update >= 1553220","6003,6004,6005"]
["2023-06-23","Yes","2023-07-05","Bug","Could not start optimizer in French and Finnish language","In the languages Finnish and French the maximum duration for the Optimizer could not be set correctly, resulting in problems starting the Optimizer. This has been fixed. ",null,10182]
["2023-09-11","Yes","2023-09-25","Improvement","Upgraded Bryntum stylesheet to v5","Upgraded the Bryntum stylesheet that is used in the schedule view to version 5.",null,10026]
["2023-09-11","Yes","2023-09-25","Improvement","Several translations updated","Several translations for various languages have been updated.",null,"11990, 12990"]
["2023-09-11","Yes","2023-09-25","Improvement","Fix/unfix vacant shifts","It is now possible to fix or unfix vacant shifts. Previously it was only possible to fix/unfix assigned shifts.",null,13727]
["2023-09-11","Yes","2023-09-25","Improvement","Apply shift demands in published schedule","It is now possible to apply shift demands in a published schedule. Previously this was only possible in planned schedules.",null,13726]
["2023-09-11","Yes","2023-09-25","Improvement","Violations of custom violation types now shown ","Violations of custom violation types are now shown as regular labor rule violations. Previously they were not shown at all, as custom violation types were filtered out of the violations.           ","Requires ORTEC WS update >= 1561992",14039]
["2023-09-11","Yes","2023-09-25","Bug","Incorrect schedule overview when using scenario's","In case a scheduling period had scenario's, the number of schedules visible in the Dashboard was not correct. This has been fixed.                                                                                                                     ","Requires ORTEC WS update >= 1561992",14105]
["2023-09-11","Yes","2023-09-25","Bug","Original department removed from subcontract list","When subcontracting shifts to another department it was possible to select the original department. This has been fixed.",null,10464]
["2023-09-11","Yes","2023-09-25","Bug","Incorrect staffing counter when deleting vacant shifts","Fixed an issue where deleting vacant shifts would incorrectly lower the assigned shift counter in the Staffing tab.  ",null,10657]
["2023-09-11","Yes","2023-09-25","Bug","Not being able to edit shift that was subcontracted multiple times","When a shift was subcontracted multiple times (e.g. from department A to B and from B to C), it was not possible to open or edit the shift in ORTEC WS for Team Schedulers anymore. This has been fixed.\nNote that subcontracting a shift multiple times using ORTEC WS for Team Schedulers is not supported but could be done using the OWS Win32 Client.",null,13543]
["2023-09-11","Yes","2023-09-25","Bug","Bad performance with read-only permissions","Users with read-only schedule permissions experienced very slow performance in the schedule view, especially noticeable in larger departments. This has been fixed.",null,14108]
["2023-09-11","Yes","2023-09-25","Bug","Strange behaviour when dragging & dropping the same shift","Rapidly dragging and dropping the same shift could result in strange behavior because intermediate changes were not yet processed in the backend. This has been improved. The shift is now shortly blocked from dragging & dropping until the changes are processed.",null,8087]
["2023-09-28","Yes","2023-10-24","Improvement","Improved data infrastructure","Improved the data infrastructure of the various schedule components. This makes it easier to implement future changes and makes the code more maintainable.\nNote: By mistake this was included in the release notes of the previous deployment while it was actually not included. This time it is.",null,9432]
["2023-09-28","Yes","2023-10-24","Feature","Vertical calculations","•\tIt is now possible to use vertical calculations in ORTEC WS for Team Schedulers. For this purpose, a new tab “Counts” has been introduced in the bottom of the schedule view (next to the Vacant Shift and Staffing tabs). This tab is always visible.\n•\tThe calculations are configurable in the ORTEC WS Client by giving a daily calculation set the code “TEAMSCHEDULER”. It is only possible to use one calculation set for the entire organization.\n•\tThe following attributes are taken from the daily calculation set and used for visualization purposes:\nNote: It might take up to 15 minutes for changes in the daily calculation set are propagated to the Team Scheduler app.\no\tName of the calculation \no\tHours vs. decimals settings (for the calculation rules that support these)\no\tCurrency sign (for the calculation rules that support it)\no\tThe order of calculations\no\tThe parent / child relations between calculations. Please note that we only support one parent/child layer, meaning it is not possible for a child to have another child.\nNote: In this release the child calculations are always visible, indented to the parent calculation. In a future release we will make the parent collapsible so the child calculations are hidden by default.\no\tColor settings\nNote: We only support green, orange and red color ranges. If the configured color falls within their respective range, they are converted into a default green, orange and red color in ORTEC. This is done to keep the color palette consistent.\nColors that fall out of the preconfigured ranges of green, orange and red are shown as gray (“unknown”).\no\tThe master schedule status settings are not considered, unless all statuses are unmarked. In that case the calculation will be invisible in the Team Scheduler app.\n•\tA caching mechanism is used for vertical calculations, similar to how it is used for the employee calculations. This means that the results of calculations are stored in a Team Scheduler repository.\no\tThe first time a schedule is opened, the calculations are loaded and stored in the repository. This might result in a longer loading time of the schedule.\no\tWhen opening the same schedule later, the calculations are retrieved directly from the Team Scheduler repository. This results in a fast load time.\no\tTo make sure calculations are in sync with the Client there are update mechanisms in place:\n\tWhenever a scheduling action is done in Team Scheduler the calculations for that specific day are updated.\n\tA nightly update for all calculations. This is to make sure they are synchronized at least once every 24 hours in case of backend changes (e.g. import of an account category line, or import of an employee attributes that influences the calculation).\no\tBecause of this asynchronous update mechanism there is a slight delay visible after a plan action is done. The length of this delay depends on the configuration of the calculations and the size of the department.\n•\tPerformance note: Depending on the complexity of the vertical calculations, the number of simultaneous plan actions across the organization and the department sizes, there can be a significant load on the server process that is calculating/updating the calculations.\nThe server load per calculation update from the Team Scheduler app is bigger than a calculation update from the ORTEC WS Client planboard, because there is no buffer mechanism place. \nPlease consider this when implementing vertical calculations. In case of doubt please contact ORTEC Product Support. We will monitor the situation and work on performance improvements where necessary.","Requires ORTEC WS update >= 1565900",8890]
["2023-09-28","Yes","2023-10-24","Bug","Incorrect shift popover","When hovering shifts, sometimes the shift popover of the previous hovered shift was shown. This has been fixed.",null,10109]
["2023-10-04","Yes","2023-10-24","Bug","Slow and unresponsive app when no vertical calculations are configured","When no vertical calculations were configured in the ORTEC WS Client, the app would become very slow and sometimes unresponsive after the latest deployment because of vertical calculation calls that were retried many times. This has been fixed. When no calculations are configured, no unnecessary calls are done.",null,21752]
["2023-10-12","Yes","2023-10-24","Improvement","Several translations updated","Several improved translations for various languages.",null,21893]
["2023-10-12","Yes","2023-10-24","Improvement","Technical change in the user authentication flow","A technical change in the user authentication and authorization flow. Secrets are now stored on the server instead of the browser. This was needed as an alternative for to-be deprecated Auth0 functionality."]
["2023-10-19","Yes","2023-10-24","Improvement","Block drag & drop in selection mode","Dragging and dropping shifts is not possible anymore during selection mode. This was previously possible  but was never fully supported. In preparation for a new feature to unassign multiple shifts, we have now blocked this option.",null,11921]
["2023-10-19","Yes","2023-10-24","Bug","With read only permissions one was able to enter selection mode","A user without the \"Edit schedules\" permission could still enter the selection mode by ctrl+click on a shift (but wasn't able to do any actions). This has been fixed.",null,11607]
["2023-10-19","Yes","2023-10-24","Bug","Make apply cyclical schedule permission more strict","The user now needs both the \"Apply cyclical schedule & shift demands\" and \"Edit schedules\" permissions (instead of only the first one) for using the \"Apply cyclical schedule and shift demands\" option.",null,11607]
["2023-11-16","Yes","2023-11-30","Feature","Show shifts from other contracts\t","Added functionality to show shifts from other contracts in the schedule. Before, only shifts assigned to the contract itself were shown, but now, also shifts from other contracts of the same employee (in other departments) are shown. \nPlease note that, due to current technical limitations, unique shifts are only shown once. This means that, in case of multiple contracts in the same department, shifts from contract one are not shown at contract two and vice versa. ","Requires ORTEC WS update >= 1571075",26118]
["2023-11-16","Yes","2023-11-30","Improvement","Schedule zoom level slider made faster","The zoom level of the schedule now changes only after the user finishes dragging the zoom level slider from the settings menu, and not with every step in between. This makes the slider a lot faster.",null,13922]
["2023-11-16","Yes","2023-11-30","Improvement","Visibility of employee columns stored in browser","The selection of (in)visible employee columns in the schedule is now stored in the browser, so the user doesn’t have to re-apply it every time a schedule is opened. ",null,14297]
["2023-11-16","Yes","2023-11-30","Improvement","Employee calculations in other periods now also updated ","If a change is done in a certain schedule, employee calculations in other schedules are now also correctly updated. This did not happen previously.\nExample: A change done in schedule A that influences employee calculations in schedule B (e.g. with yearly calculations), will now refresh the calculations in schedule B once schedule B is opened. ",null,18176]
["2023-11-16","Yes","2023-11-30","Bug","Timeouts and errors because of many simultaneous backend domains API calls","Performing actions on many vacant shifts at once caused a large number of simultaneous calls towards the backend domains API, which could result in timeouts and errors for all users in a certain timeframe. This has been improved significantly.",null,27128]
["2023-11-16","Yes","2023-11-30","Bug","Incorrect special shift staffing counter when unassigning last shift","The counters for the special shift staffings are now correctly updated after unassigning the last shift of a special shift type.",null,13716]
["2023-11-16","Yes","2023-11-30","Bug","Incorrect height of staffing and counts rows when \"show shift times\" activated","In case “Show shift times” was activated in the schedule, the rows of the Staffing and Counts tabs were also heightened unnecessarily. This has been fixed.",null,21773]
["2023-11-16","Yes","2023-11-30","Bug","Vertical calculations were not updated  after changing shift demands","When updating the shift demands on a certain day, the vertical calculations were not updated for that day. This has been fixed. This is necessary for vertical calculations that depend on the shift demands.",null,21887]
["2023-11-16","Yes","2023-11-30","Bug","Incorrect absence popover","Sometimes the hint text of absences would show the text of the previous absence that a user hovered over. This has been fixed.",null,25918]
["2023-12-22","Yes","2024-01-18","Feature","Unassign multiple shifts","Added functionality to unassign multiple shifts in one action by using the selection mode. \nThis makes it possible to quickly unassign a large part of the schedule while previously this had to be done one shift at a time.","Requires ORTEC WS update >= 1577453",11912]
["2023-12-22","Yes","2024-01-18","Bug","Timezone issue applying cyclical schedule or shift demands","Fixed some timezone issues related to the rollout period dates when applying cyclical schedules or shift demands.",null,29413]
["2024-01-11","Yes","2024-01-18","Bug","Edit shifts no longer possible","Fixed a bug in the Edit shift screen that made it impossible to save the shift if an activity type was selected for which a workstation was required."]
["2024-02-15","Yes","2024-02-22","Feature","Employee proposal (part 1)","•\tIt is now possible to request an employee proposal for a (single) vacant shift and assign the shift to one of the listed employees. \nThe proposal will display a list of employees that are available for the shift. Available means: no overlapping shifts, not reported ill nor having an approved leave request that overlaps with the shift.\n•\tThe employee proposal contains the following columns:\no\tEmployee name\no\tEmployee phone number(s). Please note it is possible to call employees directly by clicking on the phone icon (if the user has a call app installed on the device, such as teams or skype). \no\tSkills. This column shows whether the employee has the required skill(s) for the shift.\no\tViolations. This column shows if the shift would cause additional violations for the employee, based on the configured labor rules in ORTEC WS.\no\tBalance. This column can be configured to show an account balance. The following configuration options are available in ORTEC System Configuration:\n\tThe displayed header name \n\tThe sorting order (ascending/descending)\n\tThe account & category used to retrieve the balance\nPlease note that the balance will always be calculated for the entire scheduling period of the vacant shift.\n•\tThe employees are sorted based on the order of the columns shown; first employees with the right skills, then employees without additional violations, and then employees with the highest/lowest balance (depending on its sorting setting).\n\nNote: The following enhancements will be done to the employee proposal in an upcoming release:   \n-\tMore criteria/columns, such as duty/work in interval requests, already planned non-overlapping shifts, self-scheduling points.\n-\tThe ability for users to turn on/off the visualized columns and to configure the priority (and thus sorting order) of the different columns.","Requires ORTEC WS update >= 1585598",4307]
["2024-02-15","Yes","2024-02-22","Improvement","Prefix and initials are now included in employee names.","Prefixes and initials are now included in employee names. Prefixes are added at the end of an employee name. Initials are shown when an employee does not have a registered first name.        ","Requires ORTEC WS update >= 1580730",10331]
["2024-02-15","Yes","2024-02-22","Improvement","Several improvements on available shift actions for subcontracted shifts","Several improvements on available shift actions for subcontracted shifts:\no\t(Un)Fixing shifts is no longer possible for the sender of a subcontracted shift.\no\tDeclining a subcontracted shift which is fixed is no longer possible.\no\tDeclining a subcontracted shift which is offered to employees is no longer possible.",null,11933]
["2024-02-15","Yes","2024-02-22","Improvement","Optimizer progress window improvements when initializing","When the external planner is starting, the optimizer progress window now shows \"Initializing\" instead of -1 and the unassigned shifts count reflects the proper number of vacant shifts instead of 0. ",null,30232]
["2024-02-15","Yes","2024-02-22","Improvement","Increased  employee calculations to max 5","The number of employee calculations that can be displayed in the schedule has been increased from 3 to 5. ",null,30973]
["2024-02-15","Yes","2024-02-22","Improvement","Performance improvement BDA","Technical changes to improve the performance of several API calls, by reducing unnecessary checks and wait time.     ","Requires ORTEC WS update >= 1585598",31675]
["2024-02-15","Yes","2024-02-22","Improvement","Removed duplicate or unnecessary frontend calls","Removed duplicate or unnecessary calls in several places in the frontend.",null,31216]
["2024-02-15","Yes","2024-02-22","Improvement","Today and Weekly tiles no longer load automatically when having 4 or more departments selected","When a user has 4 or more departments selected in the dashboard, the Today and Weekly tiles no longer load automatically. Instead, the user can request the information manually.\nThis should give a performance improvement to customers that have users with many department permissions.  ",null,31760]
["2024-02-15","Yes","2024-02-22","Improvement","Department selector behaviour changed","The dashboard data would refresh immediately once a user selected a new department in the department selector, even if the user was planning on selecting more departments. Now the dashboard data is only refreshed after the dropdown is exited.",null,31258]
["2024-02-15","Yes","2024-02-22","Bug","Employee schedules could get swapped in exceptional cases","If users would quickly drag multiple shifts from one employee to another and the backend would respond slowly, the employee schedules might end up being swapped. This has been fixed now.               \nNote: This bug was introduced in the previous release and is now fixed. ",null,31867]
["2024-02-15","Yes","2024-02-22","Bug","Editing required skills","Several small fixes for editing the required skills of a shift.",null,27269]
["2024-02-15","Yes","2024-02-22","Improvement","Technical & security improvements","Several technical & security improvements, such as package upgrades.",null,"Various"]
["2024-02-19","Yes","2024-02-22","Bug","Null shown as employee name prefix with older OWS versions","Employee prefix was shown as null in the displayed employee name, if an older Backend Domains API version was being used. This has now been fixed.",null,32071]
["2024-02-19","Yes","2024-02-22","Bug","More than 5 employee calculations are shown but without values","If more than 5 calculations were configured in OWS, those would have shown up as additional columns in the UI, but with empty or NaN values. This happens because the calculationlist call does return more than 5 calculations, but the kpi calls are hardcoded to return a maximum of 5 calculations. We've now limited the maximum number of calculation columns in the UI to 5.",null,32072]
["2024-03-15","Yes","2024-03-21","Improvement","Department badges no longer overflow in dashbaord","In case many departments are selected in the dashboard, the department badges would overflow into the dashboard tiles. This has been improved by placing them in a scrollable container.",null,31759]
["2024-03-15","Yes","2024-03-21","Performance","Package upgrades reverted","Reverted several package upgrades done in an earlier release due to suspected performance issues.",null,32829]
["2024-03-15","Yes","2024-03-21","Performance","Edit shift calls trigger too early","Certain calls needed for the edit shift functionality were triggered too early (when opening the shift details dialog). They are now done only when you click on Edit.",null,31794]
["2024-03-15","Yes","2024-03-21","Bug","Broken schedule view due to failing public holiday call","When quickly going back and forth between dashboard and schedule view, the schedule view could break due to a failing public holiday call. This has been fixed.",null,32790]
["2024-03-15","Yes","2024-03-21","Bug","Add new shifts to absent employees not possible","It was not possible to add new shifts to employees that were reported absent. This has been fixed.",null,32825]
["2024-03-15","Yes","2024-03-21","Feature","Employee proposal (part 2)","The employee proposal has been enhanced with the following 3 columns:\no\tShift wish: Displays the relevant shift wishes of an employee, including self-scheduling wildcards.\no\tPreference: Displays the relevant work/do not work requests of an employee.\no\tPlanned shifts: Displays shifts already assigned to the employee that overlap with the day of the shift proposal. ",null,22331]
["2024-03-29","Yes","2024-04-11","Improvement","Employee details no longer visible for users without edit permissions","Disabled the employee details dialog for users who do not have permission to edit the schedule.",null,32155]
["2024-03-29","Yes","2024-04-11","Feature","Show violations on wishes","In addition to skill and labor rule violations, the schedule now also includes violations on requests (such as leave requests, shift wishes etc.).\nPlease note that there is no differentiation between approved and unapproved requests. Violations on both are treated the same and are visualized with the same dark blue color.","Requires ORTEC WS update >= 1592068",11122]
["2024-03-29","Yes","2024-04-11","Improvement","Shift popover extended with employee schedule request information","The shift popover has been extended with employee schedule request information. This prevents the user having to hover over the narrow space between the shift and the cell borders.",null,30629]
["2024-03-29","Yes","2024-04-11","Feature","Shift wishes now visible in schedule","Along with releasing the self-scheduling features, shift (duty) wishes without wildcards are now also visualized in the schedule, both incidental and recurring ones.","Requires ORTEC WS update >= 1592068",30629]
["2024-03-29","Yes","2024-04-11","Feature","Self-scheduling support","Self-scheduling support has been added to Team Scheduler, consisting of several elements:\no\tIn the Schedules dashboard tile, it is now possible to change the following self-scheduling attributes; round number, number of wildcards and the self-scheduling remark (shown to ESS users).\no\tIn the Schedule view, self-scheduling points are visualized in a new employee column. This column is visible whenever there is an active scheduling round assigned to the scheduling period (the column can be made invisible by the user if desired).\nPlease note that these self-scheduling points are treated as regular employee calculations. This means they will be updated whenever a relevant action is performed in Team Scheduler, but not when changes are done in the backend/Client.\nIn the latter case, they will be updated in the nightly refresh of employee calculations.\no\tIn the Schedule view, wildcards are visible as shift wishes with an additional blue icon. This makes wildcards easily recognizable by planners.\no\tIn the Employee proposal, an additional column was added that shows the self-scheduling points of an employee. This column is visible whenever there is an active scheduling round assigned to the scheduling period.","Requires ORTEC WS update >= 1592068","30628, 30629, 22327. 2886"]
["2024-04-23","Yes","2024-05-21","Feature","Employee proposal configuration dialog","•\tA new configuration dialog has been added to the employee proposal, called “Set up table”.\nIn this dialog the user can change the order and visibility of columns. These settings are saved locally in the user’s browser.\n•\tThe configured order of columns determines the order of employees shown in the proposal.\ne.g. Dragging the ‘Shift wish’ column before the ‘Violations’ column, means that employees will first be sorted on their shift wishes and then on violations. ",null,22326]
["2024-04-23","Yes","2024-05-21","Feature","Tablet support","•\tDragging a shift from the vacant shifts to the assigned shifts - or vice versa - while hovering the edge wouldn't trigger scrolling on tablets. This has now been fixed.\n•\tThe dashboard is now more responsive to lower resolutions. On screens with a width of less than 1600 pixels, the tiles are now displayed in 2 columns x 3 rows instead of 3 columns x 2 rows.\n•\tThe shift edit screen is now more responsive to lower resolutions. Activity dropdowns (such as cost center and workstation) are now displayed on a new row if they don’t fit the screen.\n•\tThe selection mode menu options are made denser, so the complete menu fits lower resolution screens.",null,"30362,30952,30961,31018"]
["2024-04-23","Yes","2024-05-21","Improvement","Online user manual added","A link to the online user manual has been added to the user menu. Please note that there is an English and Dutch version. All other languages refer to the English version.  ",null,34062]
["2024-04-23","Yes","2024-05-21","Improvement","Spinner added to subcontract button","When subcontracting shifts, a spinner is now shown in the confirmation button until the shifts are successfully subcontracted.",null,8745]
["2024-04-23","Yes","2024-05-21","Improvement","Added hint text to selection mode","In the selection mode, a hint text is now shown telling the user that Control can be used to initiate the selection mode and to (multi) select shifts.",null,5207]
["2024-04-23","Yes","2024-05-21","Bug","Incorrect staffing when deleting assigned shift","Deleting an assigned shift resulted in an incorrect staffing number (it subtracted 2 instead of 1). This has been fixed.",null,33934]
["2024-05-07","Yes","2024-05-21","Feature","Tablet support","Improvements to the handling of various popovers for tablets.",null,"35676,35677,35747"]
["2024-05-07","Yes","2024-05-21","Feature","Tablet support","The maximum height for dialogs has been changed to 90% of the viewport height. This prevents certain elements to become invisible on lower resolutions (e.g. the approve/decline buttons for leave requests).",null,30363]
["2024-05-07","Yes","2024-05-21","Language","Swedish added","Swedish has been added as a new language.",null,36781]
["2024-05-30","Yes","2024-06-13","Bug","Dashboard didn’t render properly in Firefox","Since the previous release, the dashboard did not render properly in Firefox. This has been fixed.",null,37300]
["2024-05-30","Yes","2024-06-13","Bug","Preference hint text of previous day shown","When a shift was planned after a full day preference, the hint text of that shift showed the preference of the previous day. This has been fixed. We now only show the preference in the hint text when the preference overlaps with the day of the shift.",null,36856]
["2024-05-30","Yes","2024-06-13","Bug","Shift hint text not shown anymore","In some cases, the shift hint text did not show up anymore until the user refreshed the schedule. This has been fixed.",null,37215]
["2024-05-30","Yes","2024-06-13","Feature","Popovers accessible with long press on touch devices","Improvements to the handling of various popovers for tablets. These were the last improvements regarding popovers. On touch devices, all popovers are now accessible with a long press, and they don’t interfere with other functionalities.",null,"30364,35679,37140"]
["2024-07-03","Yes","2024-07-16","Feature","Reports","•\tIt is now possible to open MS Reports in ORTEC WS for Team Schedulers. An extra tab has been added to the dashboard page, which shows an overview of the available reports.\n•\tBoth system reports and custom reports are supported. A new setting called TeamScheduling\\Reports\\ReportNames dictates which reports are available in Team Scheduler.\nBy default, this setting is filled with all non-ESS system reports. Custom reports must be added to the setting.\n•\tThe reports feature is behind a new general Team Scheduler permission. Without this permission, the extra tab is not visible. Existing permissions on individual reports are used to determine what user can see which report.\n\nNote: In certain cases, generating a report will fail because the combined parameter size exceeds the configured maxQueryStringLength of the ReportServer. \nThis can happen when the user has a lot of department permissions (e.g. administrators) and/or when reports are opened for a large number of employees.\nIn that case it’s needed to increase the maxQueryStringLength parameter in the ReportServer configuration. Both the API logfiles and the browser console provide extra information about the query length used.","Requires ORTEC WS update >= 1605853",32618]
["2024-07-03","Yes","2024-07-16","Feature","Tablet support","On touch devices, the selection mode behavior has slightly changed to facilitate not having a keyboard nor a mouse available. Shifts can now be added to or removed from the selection by selecting individual shifts. \nPressing outside of the selection will not remove the selection (this can only be done with the “Deselect all shifts” option in the selection mode header).",null,37346]
["2024-07-03","Yes","2024-07-16","Improvement","Setting to disable old schedules ","A new setting called TeamScheduling\\Dashboard\\MaximumScheduleAgeInDays has been introduced. Schedules older than the configured number of days will no longer be shown in Team Scheduler. The default value is 365 days.            \nThis setting also makes sure that the nightly refresh of calculations will not refresh old periods, leading to potential memory issues.                            ","Requires ORTEC WS update >= 1605853",46093]
["2024-07-03","Yes","2024-07-16","Bug","Absences for all contracts did not always show","Absences marked as \"for all contracts\" are now shown in the schedule view for all contracts of an employee, instead of only the contract the absence was reported for.         ","Requires ORTEC WS update >= 1605853",46082]
["2024-07-03","Yes","2024-07-16","Bug","Publish and Close buttons not shown","The Publish and Close buttons were sometimes not shown in the schedule. This has been fixed.                                                                                                                                                            ","Requires ORTEC WS update >= 1605853",36884]
["2024-07-03","Yes","2024-07-16","Bug","Schedule opens in the middle of the schedule","If a schedule would not fit into one screen, it would open in the middle of the period. This has been fixed. Schedules now always open with the first day of the period visible.",null,37634]
["2024-07-25","Yes","2024-08-05","Feature","Create Sick leaves","•\tIt is now possible to create sick leaves in ORTEC WS for Team Schedulers. A user can add a sick leave via a new button in the sick leave dashboard tile.\n•\tThis functionality is behind a new general Team Scheduler permission to manage sick leaves. This permission will, in the future, also be used for editing and deleting sick leaves.\n•\tThe following attributes can be assigned/changed while creating a sick leave:\no\tEmployee\no\tSick leave type\no\tFor all contracts y/n\no\tBegin date and time\no\tEnd date and time\no\tRemark\n•\tSick leaves that start in the future are now also visible in the sick leave tile (previously they weren’t).\nNote: Editing and deleting a sick leave will be part of a (near) future release. Partial sick leave periods and custom sick leave properties are out of scope for now but might be added in the future.","Requires ORTEC WS update >= 1609523",37235]
["2024-07-25","Yes","2024-08-05","Improvement","Styling changes","Updated styling due to a Bolster upgrade, mainly noticeable in button, badge and font styling and some minor color scheme changes.",null,32990]
["2024-07-25","Yes","2024-08-05","Bug","Applying cyclical schedule did not work","Applying a cyclical schedule sometimes did not work. This has been fixed.                                        ","Requires ORTEC WS update >= 1607763",37391]
["2024-07-25","Yes","2024-08-05","Bug","Custom reports did not work","Custom reports without translations would not work correctly. This has been fixed.","Requires ORTEC WS update >= 1607763",46694]
["2024-07-25","Yes","2024-08-05","Bug","To-be-assigned shifts incorrect in optimizer progress screen","The number of to-be-assigned shifts in the optimizer progress screen was not always correct in case there were shifts that can not be moved in the schedule (e.g. fixed shifts, subcontracted shifts). This has been fixed.",null,45811]
["2024-08-15","Yes","2024-08-29","Feature","Show employee realizations","•\tORTEC WS for Team Schedulers now shows employee realizations in the schedule view. \n•\tOpen employee realizations (which includes the status concept approved) are visualized with a pink color in their original department (where the approval needs to take place). \nIn all other cases, the visualization does not change, but a popover text and a shift details callout have been added to indicate that there is an employee realization, along with a description of its approval status.\n•\tActions on a shift with an employee realization have been limited, depending on the approval status:\no\tOpen: No actions on the shift are possible. The employee realization must first be approved or declined.\no\tApproved: Editing and deleting the shift is possible. Deleting will also remove the approved employee realization. Moving the shift in the schedule is no longer possible.\no\tDeclined: Editing and deleting the shift is possible. In both cases the declined employee realization will be removed. Moving the shift in the schedule is no longer possible.\nPlease note that approval of employee realizations is not yet supported. This will be delivered in a future release.","Requires ORTEC WS update >= 1611779",46310]
["2024-08-15","Yes","2024-08-29","Feature","Tablet support","When a user would start dragging a shift on an iPad, sometimes the scheduler would also start scrolling in the same direction, making it impossible for the user to drop the shift in the correct spot. This has been fixed.",null,32236]
["2024-08-15","Yes","2024-08-29","Language","Danish added","Danish has been added as a new language.",null,46829]
["2024-08-15","Yes","2024-08-29","Bug","Unable to edit self scheduling for second department when there are two departments selected","Fixed an issue when multiple departments that use self-scheduling were selected in the dashboard. Changing self-scheduling for one of them would cause the other one to disappear and not be editable when the dashboard was reloaded. ",null,47177]
["2024-08-15","Yes","2024-08-29","Bug","Incorrect employee calculation value ","Employee calculations which had time values were incorrectly formatted if the value was between 0 and -1. The values were displayed as a positive time value, instead of a negative time value. This has been fixed.",null,47822]
["2024-08-15","Yes","2024-08-29","Bug","Leave request tile no longer scrollable","The leave requests list was no longer scrollable. This has now been fixed.",null,47882]
["2024-08-15","Yes","2024-08-29","Bug","Shift counter in sick leave tile incorrect","The shift counter in the sick leave tile was displaying the wrong number. This counter is meant to show all to-be-replaced shifts between now and +7 days in the future. Due to a recent change this was no longer the case and it showed shifts for a longer period. This has been fixed.","Requires ORTEC WS update >= 1611779",48041]
["2024-09-13","Yes","2024-09-26","Feature","Approve schedules","It is now possible to approve schedules in ORTEC WS for Team Schedulers, similar to how schedules can be published and closed. \n•\tThe new approval button is behind a new Access Control permission “Allowed to approve schedules”.\n•\tIn this feature, we also slightly improved the schedule status change flow:\no\tThe appropriate schedule change button is now always visible but is disabled if the schedule does not meet the necessary conditions. The following conditions apply:\n\tFor publishing: The status of the previous schedule should be published or higher (or it is the first schedule)\n\tFor closing: The status of the previous schedule should be closed or higher, there exist no subcontracts in status Concept in the schedule and the schedule end date is within 7 days from now.\n\tFor approving: The status of the previous schedule should be approved or higher and there exist no open employee realizations in the schedule.\no\tThe hint text of a disabled button now shows the condition(s) that have not yet been met.","Requires ORTEC WS update >= 1616090",46841]
["2024-09-13","Yes","2024-09-26","Improvement","Federated logout supported","When a user signed out, they remained logged into their identity provider. This is not very safe when multiple users use the same machine and has been improved. Now, when a user logs out, they are now also logged out of their identity provider. Please note this is only available for Auth0 - IdP connections that support federated logout.",null,48328]
["2024-09-13","Yes","2024-09-26","Bug","Tablet support","Long press interactions on events in the schedule were no longer working on touch devices after navigating back and forth between the dashboard and the schedule page. This has been fixed.",null,48302]
["2024-09-13","Yes","2024-09-26","Bug","Incorrect colors in dark theme ","Some UI elements were missing the correct color in dark theme. This has now been fixed.",null,48256]
["2024-10-14","Yes","2024-10-28","Feature","Approve employee realizations (in schedule)","•\tIt is now possible to approve employee realizations in ORTEC WS for Team Schedulers from the schedule view. \n•\tAny shift with an open employee realization will have a “View realization” button, which will open a new dialog with the realization information is shown and where the user can approve/decline.\n•\tThe “View realization” dialog will highlight differences between the original shift and the employee realization.\n•\tThe functionality is behind a new Access Control permission called “Approve and decline realizations”. If this permission is not granted, the user can still see the realization details but is unable to approve/decline.\nNote: In a future release, we will also add an option in the dashboard to approve open employee realizations.","Requires ORTEC WS update >= 1620658",46315]
["2024-10-14","Yes","2024-10-28","Feature","Edit sick leaves","•\tIt is now possible to edit sick leaves in ORTEC WS for Team Schedulers. \n•\tIn the sick leave details dialog (opened from the dashboard), an “Edit sick leave” button is available. This leads to a dialog in which the following properties of a sick leave can be changed: End date & time, remark.\n•\tThe functionality is behind the existing Access Control permission called “Create, edit and delete sick leaves”.\nNote: With this feature, we support the most common use case (changing the end date). We will monitor the need for changing other attributes of a sick leave. Deleting a sick leave will be in one of the next releases.","Requires ORTEC WS update >= 1620658",37238]
["2024-10-14","Yes","2024-10-28","Improvement","Exclude central departments from vertical calculations","Vertical calculations can now be skipped for central departments. In many cases vertical calculations for central departments will not return meaningful values (depending on the configuration) while still consuming memory and CPU power. In these cases, it is better to not do vertical calculations for central departments. This is now possible through a setting.                                         ","Requires ORTEC WS update >= 1614627",48669]
["2024-10-29","Yes","2024-10-30","Language","Updated French date & time formats","Date and time formats have been updated for the French language.",null,50213]
["2024-10-29","Yes","2024-10-30","Improvement","Improved failed login situation","When the Access Control department parameter was not configured for a user(group), the login failed without a clear indication why. This has been improved. The user is now shown a page that says, 'Signing in with this account is not allowed'. The backend domains API logging provides more details about the failed login.",null,46129]
["2024-10-29","Yes","2024-10-30","Improvement","Improved performance of retrieving shifts","Improved the performance of retrieving shifts. After the introduction of “show employee realizations” these queries could become slow in case of many employee realizations in the database. This has been improved.","Requires ORTEC WS update >= 1622079",50101]
["2024-10-29","Yes","2024-10-30","Improvement","Violation text now includes labor rule name.","The violation text in a shift popover now also shows the name of the labor rule that was violated. ","Requires ORTEC WS update >= 1622079",50030]
["2024-10-29","Yes","2024-10-30","Bug","Staffing information icon no longer visible","The staffing information icon was no longer visible in the leave request details dialog. This has been fixed.",null,48752]
["2024-10-29","Yes","2024-10-30","Bug","Schedule status change button now updates correctly in case of language change","The popover of the schedule status change button on the schedule page now updates translations correctly when the language is changed.",null,49016]
["2024-10-29","Yes","2024-10-30","Bug","Adding shifts to a sick leave was not possible in certain situations.","The mouse movement validation was not triggered when moving to a sick leave event. In case the previously hovered cell contained an overlapping shift, it was not possible to add a shift to the sick leave. This has now been fixed.",null,49827]
["2024-11-08","Yes","2024-11-20","Feature","Delete sick leaves","•\tIt is now possible to delete sick leaves in ORTEC WS for Team Schedulers.\n•\tDeleting a sick leave will automatically roll back all sick leave shifts that were created in the sick leave period.\n•\tTherefore, deleting a sick leave is only possible for sick leaves that don’t have sick leave shifts with status Closed or higher.\n•\tThe functionality is behind the existing Access Control permission called “Create, edit and delete sick leaves”.","Requires ORTEC WS update >= 1623707",34154]
["2024-11-08","Yes","2024-11-20","Improvement","Additional grouping options","It is now possible to group on additional employee attributes. Position, labor agreements, main department and rotation unit have been added as grouping options, next to the existing sorting group.\nPlease note that the values that are valid on the first day of the scheduling period are used.  ","Requires ORTEC WS update >= 1623707",50357]
["2024-11-08","Yes","2024-11-20","Bug","Balance column in employee proposal showed wrong numbers","The balance column of the employee proposal screen was showing incorrect duration numbers if the values had exponential notations (very small numbers). This has now been fixed.",null,50406]
["2024-11-08","Yes","2024-11-20","Bug","Parent cost centers without valid childs were visible","Parent cost centers without a valid child cost center were shown in the cost center list in the shift edit screen. This has been fixed.","Requires ORTEC WS update >= 1623707",50464]
["2024-11-08","Yes","2024-11-20","Bug","Added logging for changing shift demand issue","Added browser console logging for the “change shift demand” feature, to track an issue that doesn't allow users to change the shift demand.",null,50882]
["2024-11-08","Yes","2024-11-20","Bug","Next day indicator was not showing correctly for shifts ending in the next scheduiling period","The ‘next day’ time indicator (+1) was not displayed for shifts/activities that started in a month and ended in the next month. This has now been fixed.",null,49605]
["2024-12-04","Yes","2024-12-18","Feature","Change shift name","It is now possible to change a shift’s name in ORTEC WS for Team Schedulers. Please note that in case a shift based on a shift type (duty set duty) is renamed, it will still count as the original shift type in the staffing counters. ","Requires ORTEC WS update >= 1628312",10393]
["2024-12-04","Yes","2024-12-18","Improvement","Proper error shown when logging it with user that does not exist","In case a user was authenticated by Auth0 during login, but the corresponding user did not exist in Access Control, they would be redirected to the home/login page without any warning. This has been improved and the user will now see a proper error page with the ability to logout of their account.",null,51278]
["2024-12-04","Yes","2024-12-18","Improvement","Automatic browser translations disabled","Automatic browser translations have been turned off. These sometimes led to users seeing strange texts without knowing why. Please note that this does not work in Firefox yet and we are looking for a solution.",null,50662]
["2024-12-04","Yes","2024-12-18","Improvement","Angular 18 + Bolster 7 upgrade","Technical upgrade to Angular 18 and Bolster 7. Some visual elements received updates.",null,50468]
["2024-12-04","Yes","2024-12-18","Language","Added English (United Kingdom) language","English (United Kingdom) has been added as a new language.",null,50849]
["2024-12-04","Yes","2024-12-18","Bug","Employees no longer shown properly when grouped","Employees were not shown properly when opening a schedule in case a previously stored grouping option was used. This has now been fixed.",null,51164]
["2024-12-04","Yes","2024-12-18","Bug","Fixed issues with sorting employee groups","Several issues with the sorting of employee groups have been fixed.",null,51519]
["2024-12-04","Yes","2024-12-18","Bug","Employee realizations not available in schedule with status Closed or higher","Users were not able to open or process employee realizations in schedules with status Closed or higher. This has now been fixed.",null,51013]
["2024-12-04","Yes","2024-12-18","Bug","Reports didn't work for administrators","Users with permissions for a lot of departments (typically administrators), reports could throw an error when opened. This has been fixed. ","Requires ORTEC WS update >= 1628312",51272]
["2024-12-12","Yes","2024-12-18","Bug","Activity workstation appears empty","In some cases, the activity workstation dropdown in the edit shift screen was shown as empty while it had a workstation selected. This has been fixed.",null,52310]
["2024-12-12","Yes","2024-12-18","Bug","Shift details caching mechanism could shorty cause an incorrect shift state","Shift details were previously cached, causing the shift details dialog and the edit shift screen to potentially display older data until the details were refreshed. This could lead to users having access to action buttons that should not be there according to the latest shift state.\nSome of those actions could result in errors or, in specific cases, shifts being unscheduled. This has been fixed by removing the cache logic and implementing loading states that are displayed while the data is being retrieved.",null,52022]
["2024-12-18","Yes","2025-01-09","Feature","Employee realizations dashboard tile                                                      ","•\tA new tile has been added to the dashboard which shows all open employee realizations for the selected department(s).The dashboard tile is divided in two tabs, one for realized shifts and one for confirmed shifts. As ESS7 no longer supports the confirmation of shifts, the confirmed shifts tab might be removed at some point in the future. Please note that there is no filter on shift date, so all open employee realizations will show up, even if they are old. \n•\tClicking on one of the open employee realizations will open the approval window, where the realization can be approved or declined.  \n•\tTo make room for the new tile, the Today and Weekly staffing tiles have been merged into one tile and the Sick leave tile has changed position.\nThe user can switch between Today and Weekly staffing information by using the new button toggle in the tile. The last selected option is saved for the user for the next login.","Requires ORTEC WS update >= 1628312","46311,46312,46313"]
["2024-12-18","Yes","2025-01-09","Improvement","Employee number now shown when 'Show shift times' is enabled","In case the 'Show shift times' setting is enabled, we now display the employee number in the schedule’s employee section.",null,51156]
["2024-12-18","Yes","2025-01-09","Bug","Visibility self-scheduling points column not stored correctly","The (un)visibility of the self-scheduling points column in the schedule is now correctly stored for a user when switching between schedules with and without a self-scheduling round. Earlier, this could lead to the column being visible again.",null,52047]
["2025-01-10","Yes","2025-01-22","Improvement","New permissions for viewing employee details","A new Access Control permission has been created for viewing employee details. Previously, if you had the edit schedule permission you were also allowed to view employee details. This has now been split into separate permissions. To ensure backwards compatibility, the new permission is granted automatically for user groups that already had the edit schedule permission. ","Requires ORTEC WS update >= 1625278",50909]
["2025-01-10","Yes","2025-01-22","Improvement","Updated styling of some dashboard elements","Updated the styling of several dashboard elements to make them more consistent with the latest design guidelines.",null,"53108, 52348, 52349"]
["2025-01-16","Yes","2025-01-22","Bug","Add shifts feature could get stuck in case of error","When a user tried to add a new shift to an employee but that request failed, no other new shifts could be added to employees until the user would refresh the application. This has now been fixed.",null,53302]
["2025-01-24","Yes","2025-02-06","Feature","Sick leave properties","•\tIt is now possible to manage yes/no (boolean) sick leave properties in ORTEC WS for Team Schedulers. They are visible in the sick leave details and as toggles in the sick leave edit form.\n•\tA new setting TeamScheduling\\SickLeave\\Properties has been introduced in which the sick leave properties can be configured that need to be managed in Team Scheduler.\n•\tThe properties can be edited if the user has the existing “Allowed to manage sick leave” permission.","Requires ORTEC WS update >= 1631660",34207]
["2025-01-24","Yes","2025-02-06","Improvement","Improved navigation in prefilled cost center dropdown","When an activity already had a cost center and the user would open the dropdown menu, it was difficult to navigate to another (related) cost center due to all nodes being collapsed. This has now been changed. The parent nodes of the selected cost center are now expanded, and the dropdown automatically scrolls to the selected cost center. ",null,52019]
["2025-01-24","Yes","2025-02-06","Bug","Shifts without demand were not rolled out when applying cyclical schedule","Duties without a demand were not rolled out when applying a cyclical schedule. This has been fixed.                   ","Requires ORTEC WS update >= 1631660",53182]
["2025-01-24","Yes","2025-02-06","Bug","Monthly recurring duty requests not always shown correctly","Monthly recurring duty requests were in some cases not shown correctly. This has been fixed.","Requires ORTEC WS update >= 1631660",53401]
["2025-02-26","Yes","2025-03-11","Feature","Sick leave shifts based on contract hours                                                      ","•\tThe \"Replace with sick leave shifts\" functionality has been extended with the option to create contract-based sick leave shifts.Depending on an illness type's replace type settings in the ORTEC WS backend, Team Scheduler will now show different replacement options when opening a sick leave.\nPlease note that only the \"Planned shifts\" and \"Contract\" options are supported.\no\tWhen the replacement type is set to \"Planned shifts\", the behavior is the same as it was before. This means the user can select which shifts to replace with identical sick leave shifts.\no\tWhen the replacement type is set to \"Contract\", the user now has the option to create contract-based sick leave shifts up until the selected date (from the sick leave start date). Any shift still assigned to the employee in that period will be unassigned first.\n•\tThe new functionality also supports the use of two illness replace types, depending on the schedule status (in ORTEC WS: UseTwoReplaceTypesForIllnessType).\n•\tIt is clearly visualized to the user what replace type is active for which period and what will happen if they click the \"Create sick leave shifts\" button.\n•\tTo better reflect the new functionality, we made some small changes to the sick leave tile and dialog:\nBoth the \"Shifts (7d)\" column in the tile and the sick leave dialog itself, now show all non-closed shifts from the start of the sick leave until 7 days in the future. Previously it was from today until 7 days in the future.","Requires ORTEC WS update >= 1635163",34206]
["2025-02-26","Yes","2025-03-11","Feature","Plan contract hours for special shifts \t","Team Scheduler now uses the \"Plan contract hours\" option defined on Special shift types. This option can be set in the ORTEC WS backend on special duties. When set, adding a shift of this type will adjust the length of the shift to  the employee’s contract hours. Previously, this option was not considered in the \"Add shift\" functionality in Team Scheduler. ","Requires ORTEC WS update >= 1635163",7543]
["2025-02-26","Yes","2025-03-11","Improvement","Automatic browser translations disabled in Firefox","Automatic browser translations in Firefox have now also been turned off.",null,52036]
["2025-02-26","Yes","2025-03-11","Improvement","Improved behaviour of fast rescheduling actions ","Sometimes, when users were rescheduling shifts in quick succession, these actions would result in shifts jumping around, some shifts being unscheduled, and employee schedules that could no longer be updated until the user would refresh the screen. This has been improved.",null,52245]
["2025-03-26","Yes","2025-04-09","Feature","Using proposal departments in employee proposal                                          ","•\tIt is now possible to use proposal departments in the employee proposal, which means it is possible to find employees for your shift outside your own department.\n•\tA new toggle has been added in the proposal screen that lets the user switch to proposal departments.\nIn proposal department mode, a new column has been added that shows the department of the employee. Everything else works the same as in normal mode.\n•\tAfter selecting a suitable employee from another department, the shift can be assigned. The employee will automatically be borrowed for the day of the shift and shown in the schedule.\n•\tA new permission for this feature has been added called \"Borrow employee via the employee proposal (proposal departments)\".\nNote that there is a maximum number of resources that can be retrieved from proposal departments, depending on the ORTEC WS setting MAXNUMBEROFRESULTSINPROPOSAL.","Requires ORTEC WS update >= 1638158",34046]
["2025-03-26","Yes","2025-04-09","Feature","Schedule search & filter on employee names ","It is now possible to search & filter employees in the schedule by name. A new work bar has been introduced in the schedule view, which includes a search field.\nTyping a search phrase will automatically filter the schedule on employees whose names match the search phrase.",null,11125]
["2025-03-26","Yes","2025-04-09","Improvement","Duty description and position now visible","Two existing attributes of a shift in ORTEC WS are now also visible in Team Scheduler: The (duty) description and the position.                             ","Requires ORTEC WS update >= 1638158",46292]
["2025-04-09","Yes","2025-04-30","Bug","Optimization status could get stuck","The optimization process could get stuck or fail in case employees no longer exist in a schedule that they were previously a part of (e.g. due to a database restore). This has been fixed.      ",null,54589]
["2025-04-09","Yes","2025-04-30","Bug","Saving an edited shift not possible","Saving an edited shift was sometimes not possible due to skills that were not properly initiated. This has been fixed.",null,56449]
["2025-04-09","Yes","2025-04-30","Bug","Changing shift demand did not lead to updated vacant shift on last day of the schedule","Changing the shift demand on the last day of a schedule did not result in updated vacant shifts on that day. This has been fixed.",null,56198]
["2025-04-09","Yes","2025-04-30","Improvement","Added a shift hover state","A subtle visual hover state has been added to shifts in the schedule view",null,53174]
["2025-04-09","Yes","2025-04-30","Improvement","Approving a schedule with open realizations in another department now possible","It is now possible to approve a schedule with open realizations in another department. ",null,56409]
["2025-04-22","Yes","2025-04-30","Bug","Incorrect skill information in employee proposal when using proposal departments","The employee proposal did not always show the correct skill information when using proposal departments. This has been fixed.","Requires ORTEC WS update >= 1640539",56582]
["2025-04-22","Yes","2025-04-30","Improvement","Improved performance of schedule query","Improved performance of the main schedule query (most notable when central departments exist).","Requires ORTEC WS update >= 1640539",56049]
["2025-04-22","Yes","2025-04-30","Improvement","Improved permission checks for showing shift details","Authenticated users that were authorized for at least one department, were able to use a workaround to see shift details from other departments. This has been disabled.","Requires ORTEC WS update >= 1640539",51246]
["2025-04-30","Yes","2025-05-14","Feature","Easier navigation between schedules","•\tIt is now possible to navigate to other schedules for the same department directly from the schedule view, without having to go back to the dashboard.\n•\tThe header of the schedule view has been enhanced with two options:\no\tLeft and right arrows to move to the previous or next schedule\no\tA dropdown with all available schedules to move directly to a specific schedule",null,10387]
["2025-04-30","Yes","2025-05-14","Language","Updated Finnish & French translations","Several translations have been updated in the Finnish and French language.",null,59562]
["2025-06-19","Yes","2025-07-04","Feature","Horizontal/ diagonal drag & drop","•\tIt is now possible to drag and drop shifts horizontally and/or diagonally in the schedule.\n•\tThis functionality is behind a new permission. Only users with this permission are allowed to drag & drop horizontally / diagonally.\n•\tA new setting has been introduced in the schedule settings menu. A user can toggle this setting to allow for horizontal / diagonal movements in the schedule. \nThis setting can also be toggled using the keyboard shortcut Shift + D.\nNote: The following movements are not supported: moving a vacant shift to another day, unassigning a shift to another day.","Requires ORTEC WS update >= 1645673",54833]
["2025-06-19","Yes","2025-07-04","Improvement","Improved performance of schedule query","Improved performance of the main schedule/shift query.                           ","Requires ORTEC WS update >= 1643385",72040]
["2025-06-19","Yes","2025-07-04","Improvement","Correct sick leave percentage using UseIllnessAvailabilitiesExtended","The sick leave percentage value did not support setting UseIllnessAvailabilitiesExtended, which means it showed the wrong value if that setting was enabled. This has been improved.  ","Requires ORTEC WS update >= 1643385",54964]
["2025-06-19","Yes","2025-07-04","Bug","Wrong time picker format in certain languages","Formatting rules have been added for displaying date and time pickers. This fixed an issue where the wrong time format was displayed in certain languages.",null,72256]
["2025-06-19","Yes","2025-07-04","Bug","Balance column in employee proposal showed 0","The balance column in the employee proposal always showed '0' (introduced in a recent change). This has been fixed.       ","Requires ORTEC WS update >= 1643385",72470]
["2025-07-31","Yes","2025-08-12","Feature","Manage employee skills","•\tIt is now possible to manage the skills of employees. Clicking on an employee in the schedule will open a full-screen dialog, which has a separate tab for viewing and managing employee skills.\n•\tThe available skills depend on the assigned department(s) of the employee (in any point in time). Only skills valid for the assigned department(s) are visible/selectable.\n•\tIn case there are skills with identical names defined across the organization, the name of the organizational level is displayed behind the skill name.\n•\tIt is possible to make a skill valid for a specific department only, via a toggle in the add skill dialog. \no\tIf disabled, the skill is automatically valid for all departments (depending on where the skill is defined in the organization). \no\tIf enabled, only departments are selectable for which the user has permissions, and to which the employee is assigned to (in any point in time).\n The toggle value (enabled/disabled) is stored in the user settings, meaning the next time a skill is changed/added the toggle is set to the same value as it was the previous time.\n•\tThis functionality is behind a new permission. Only users with this permission are allowed to change the skills of an employee. ","Requires ORTEC WS update >= 1653626",53796]
["2025-07-31","Yes","2025-08-12","Feature","Manage employee properties","•\tIt is now possible to manage certain properties of employees. Clicking on an employee in the schedule will open a full-screen dialog, which has a separate tab for viewing and managing employee properties.\n•\tWhich property types are visible is managed by a setting in ORTEC System Configuration called TeamScheduling\\Employees\\Properties. \nThis is introduced to prevent all properties being visible by default, which is often undesired because some could contain sensitive information.\nNote: Only properties of type Yes/No and Text (with predefined values) are supported.\n•\tThe visible property types also depend on the assigned department(s) of the employee (in any point in time). Only properties valid for the assigned department(s) are visible/selectable.\n•\tIn contrast to the ORTEC WS Client, the default value of a property is always visible on employee level. \n•\tThis functionality is behind a new permission. Only users with this permission are allowed to change the properties of an employee. Note that users with the “view employee details” permission will be able to see the properties.","Requires ORTEC WS update >= 1653626",53797]
["2025-07-31","Yes","2025-08-12","Feature","Overrule sick leave replacement type","•\tIn an earlier feature we built support for creating sick leave shifts based on the contract hours of an employee. This was always based on predefined (and therefore fixed) sick leave type settings in the backend.\n•\tIt is now possible to overrule these default replacement types, meaning the user can switch to the other replacement type if needed.","Requires ORTEC WS update >= 1653626",80343]
["2025-07-31","Yes","2025-08-12","Bug","Fixed configuration check on sick leave replacement type","The configuration check on sick leave period replacement type was performed even when it was not relevant. This could result in an unnecessary error when opening a sick leave. This has been fixed.\t","Requires ORTEC WS update >= 1653626",84269]
["2025-08-14","Yes","2025-08-27","Feature","Extended Shift Offering flow / integration","•\tIt is now possible to use Shift Offering data (originally available in the Ad Hoc Planner) in ORTEC WS for Team Schedulers. \n•\tThe following functionalities have been added based on the data retrieved from Shift Offering (most notably the employee requests):\no\tShifts opened for bidding now show if there are employee requests via a distinct visualization in the schedule. \no\tA callout in the shift details window shows the number of employee requests for the shift. \no\tA link in the callout opens a dialog with information about the employees that requested the shift. This information is coming from Shift Offering and includes the employee name, department, contract hours, balance and violations.\no\tIn the same dialog it is possible to assign the shift to one of the employees. This includes assigning employees from proposal departments.\n•\tAssigning a shift in this way starts the same post processing as if the shift would be assigned in the Ad Hoc Planner / Shift Offering (e.g. set duty request statuses, send notifications).\n•\tTo enable this feature, both the Shift Bidding module and a Shift Offering tenant are required. The feature must be activated on individual basis. Please contact your ORTEC representative.",null,56418]
["2025-08-14","Yes","2025-08-27","Bug","Rounding issue in employee calculations","Fixed a rounding issue in the employee calculations when using the hh:mm format. ",null,80916]
["2025-08-14","Yes","2025-08-27","Bug","Incorrect month label shown in report date picker","In some cases, date and month labels in the reporting date picker were not displayed properly. This has now been fixed.",null,71173]
["2025-09-01","Yes","2025-09-10","Technical","Cloudflare preparations","Technical preparations for implementing Cloudflare."]
["2025-09-01","Yes","2025-09-10","Improvement","Department search field in dashboard","The department selector on the dashboard now has the option to search for specific departments if the list contains more than 10 departments.",null,84818]
["2025-09-01","Yes","2025-09-10","Bug","Shift staffing counters not updated","Sometimes the shift staffing counters were not updated correctly when unassigning shifts. This has been fixed.",null,80462]
["2025-09-01","Yes","2025-09-10","Bug","Vertical calculations (counts) not calculated","Vertical calculations were not calculated when the ORTEC WS server time zone was set to “FLE Standard Time”. This has been fixed.",null,85548]
["2025-09-24","Yes","2025-10-08","Technical","References removed from API","Removed the references to protected API end points from a publicly accessible file.",null,84592]
["2025-09-24","Yes","2025-10-08","Improvement","Employee row highlighted when dragging","Dragging a vacant shift to the employee grid will now highlight the hovered employee.",null,94887]
["2025-09-24","Yes","2025-10-08","Improvement","Shifts without demand were not rolled out when applying cyclical schedule","Shifts planned on top of an absence now show the absence information in their popover.",null,85088]
["2025-09-24","Yes","2025-10-08","Improvement","Sick leave end date now used for creat sick leave dialog","If a sick leave has an end date, this date will now be used as the end date in the create sick leave shifts dialog (instead of today + 7). ",null,85090]
["2025-09-24","Yes","2025-10-08","Bug","Creating or updating sick leave not possible","Creating or updating sick leaves was not possible when a sick leave property was configured that required permissions. This has been fixed","Requires ORTEC WS update >= 1665354",85444]
["2025-09-24","Yes","2025-10-08","Bug","Error when retrieving staffing information ","Daily and weekly staffing could not always be retrieved when a large amount of shift types was involved. This has been fixed. \t","Requires ORTEC WS update >= 1662311",85326]
["2025-09-24","Yes","2025-10-08","Bug","Error when adding shifts","The add shifts functionality sometimes resulted in errors due to (query) timing issues. This has been improved.\t","Requires ORTEC WS update >= 1662311",85106]
["2025-09-24","Yes","2025-10-08","Bug","Number of schedules not correct","The number of schedules shown in the past or future was not correct in case proposal departments were configured on parent departments. This has been fixed. ","Requires ORTEC WS update >= 1662311",84580]
["2025-10-08","Yes","2025-10-22","Improvement","Improved performance in large schedules","Drastically improved performance in schedules with many shifts (or shift types), during or right after shift scheduling actions. Hiccups should no longer occur.",null,99230]
["2025-10-22","Yes","2025-11-09","Feature","Manage older sick leaves","•\tIt is now possible to view and manage older sick leaves. The sick leave dashboard tile has been split into two tabs, one for current and one for past sick leaves.\n•\tPast sick leaves are limited to those having an end date beyond the first day of the previous month.","only available with ORTEC WS update >= 1669618",51096]
["2025-10-22","Yes","2025-11-09","Improvement","Show shifts from all departments in sick leave dialog","The list of to-be-replaced shifts in the sick leave details only included shifts for the selected departments in the dashboard. This has been changed.\nIt now includes all shifts in all departments, regardless of the selected departments nor user permissions. This means that a planner that has access to the sick leave can replace all shifts at once (for all departments).\nA setting has been added to revert to the old functionality TeamScheduling\\SickLeave\\ShowShiftsForAllDepartments.","only available with ORTEC WS update >= 1672637",105405]
["2025-10-22","Yes","2025-11-09","Bugfix","Reports with special characters didn't work","Reports with special characters could not be used in ORTEC WS for Team Schedulers","only available with ORTEC WS update >= 1672637",86048]
["2025-11-26","Yes","2025-12-10","Improvement","Workstation and cost center no longer shown in employee realization when features are turned off","In the employee realization dialog, the activity cost center and workstation fields are no longer shown when these features are not used within ORTEC WS (their general settings turned off).",null,131210]
["2025-11-26","Yes","2025-12-10","Improvement","Increased number of employee calculations to 8","It is now possible to have up to 8 configurable employee calculations, instead of 5. Please note that:\no\tIf more than 5 calculations were already configured in the calculation set, they will be visible immediately.\no\tThe newly visible calculations will initially show 0. They are (re)calculated whenever the employee calculation is updated (e.g. due to a shift assignment or realization).\no\tOn smaller resolution screens, having 8 visible calculations might lead to usability issues.",null,131316.13131699999]
["2025-11-26","Yes","2025-12-10","Improvement","Scroll to current day in schedule","When the current day is within the opened scheduling period, the scheduler will automatically scroll so that today is visible.",null,130849]
["2025-11-26","Yes","2025-12-10","Improvement","Minor visual changes","Some minor visual changes such as more rounded corners in certain elements, according to ORTEC’s latest design guidelines.",null,129696]
["2025-11-26","Yes","2025-12-10","Bugfix","An error could occur when saving edited shift","Editing the properties of a shift could sometimes result in an error when saving the shift. This has been improved.                          ","only available with ORTEC WS update >= 1680681",131201]
["2025-11-26","Yes","2025-12-10","Bugfix","Error when opening sick leave that starts before a department assignment","When opening an employee’s sick leave that starts before the employee had a department assignment, an error could occur. This has been fixed.  ","only available with ORTEC WS update >= 1680681",130650]
["2025-11-26","Yes","2025-12-10","Bugfix","Schedule popovers could get stuck","Sometimes schedule popovers were stuck even when a user would move away from the event. This has been fixed.",null,130247]
["2025-11-26","Yes","2025-12-10","Bugfix","Error when replacing sick leave shifts in period without schedule","Replacing shifts with sick leave shifts for a period where there is no schedule (but a calendar) could result in errors. This has been fixed.        ","only available with ORTEC WS update >= 1676040",85094]
["2025-12-17","Yes","2026-01-14","Feature","Vacant shifts department filter","A department filter option has been added to the vacant shift section, allowing the user to quickly filter the vacant shifts on specific departments. \nThis is helpful when shifts are subcontracted from multiple departments (e.g. in a Flexpool).",null,54679]
["2025-12-17","Yes","2026-01-14","Improvement","Week number added","The schedule view now displays week numbers on the first day of the week.",null,130108]
["2025-12-17","Yes","2026-01-14","Improvement","Improved query performance sick leave dialog","Improved query performance when retrieving shifts to be replaced by sick leave.            ","only available with ORTEC WS update >= 1688654",132132]
["2025-12-17","Yes","2026-01-14","Improvement","Vertical calculations skipped for large departments","Vertical calculations could result in performance or memory problems in departments with a lot of employees. A new setting has been introduced in TeamScheduling\\VerticalCalculations\\MaxNrOfEmployeesInDepartment, with a default value of 500.\nIn case a department contains more employees than this configurable value, the vertical calculations will be skipped","only available with ORTEC WS update >= 1688654",131801]
["2025-12-17","Yes","2026-01-14","Bugfix","Violation still in hint text when unassigning","When unassigning a shift with a violation, the violation text still appeared when hovering over that shift. This has been fixed.",null,130904]
["2025-12-17","Yes","2026-01-14","Bugfix","Visual artifacts when scrolling in tables","Fixed some visual artifacts where the content of tables would be rendered underneath the table header when scrolling.",null,132515]
["2025-12-17","Yes","2026-01-14","Bugfix","Sick leave were missing","Sick leaves were sometimes missing from the dashboard in case trial scenarios were present. This has been fixed. ","only available with ORTEC WS update >= 1688654",132316]
["2025-12-17","Yes","2026-01-14","Bugfix","Sick leave shown of employee not in department anymore","The dashboard sometimes showed sick leaves of an employee that was no longer part of the department (but was in the past or future). This has been fixed. Now only sick leaves are shown that overlap with the department assignment. ","only available with ORTEC WS update >= 1688654",132689]
["2026-02-03","Yes","2026-02-18","Improvement","Employee realization dialog improved for smaller resolutions","The employee realization dialog has been improved for smaller resolutions.",null,131952]
["2026-02-03","Yes","2026-02-18","Improvement","Assigned employees shown in shift counter hint text","Hovering over a shift counter in the Staffing tab now shows the employees that are assigned to that shift. ",null,132487]
["2026-02-03","Yes","2026-02-18","Improvement","Removed restriction for activities smaller than 15 minutes","The restriction that an activity should be at least 15 minutes has been removed when editing shifts. ",null,134214]
["2026-02-03","Yes","2026-02-18","Improvement","All existing shifts selected by default in sick leave replacement dialog","In the sick leave replacement dialog, all existing shifts are now selected by default.",null,134374]
["2026-02-03","Yes","2026-02-18","Improvement","Remark of employee request shown in hint text","The remark of an employee request is now shown in the hint text of the request.","only available with ORTEC WS update >= 1698566","132469, 132470"]
["2026-02-03","Yes","2026-02-18","Bugfix","Employee calculations in other departments did not update","In case of a planning change in a certain department, the employee calculations were not updated for other departments of the employee. This has been fixed.",null,134330]
["2026-02-03","Yes","2026-02-18","Bugfix","Special duties were not shown","The special duties were not shown in the Staffing tab in case the root department Id was changed from its default. This has been fixed.                      ","only available with ORTEC WS update >= 1698566",134174]
["2026-02-03","Yes","2026-02-18","Bugfix","Vertical calculations sometimes not executed","Vertical calculations sometimes did not update when assigning a shift. This has been fixed. A new setting StartSnapshotTransaction_WaitForDtcCommits_BDA was added to OWSSettingsManager, with default value 'Y'.                                                           ","only available with ORTEC WS update >= 1694250",133610]
["2026-02-03","Yes","2026-02-18","Bugfix","Number of shift in sick leave tile wrong","The number of shifts in the sick leave tile could be wrong in case an employee was working for multiple departments. This has been fixed. ","only available with ORTEC WS update >= 1698566",133097]
["2026-02-10","Yes","2026-02-18","Improvement","Employee counters last updated in hint text","The employee counters now have a hint text which says when the calculations were last updated.",null,134621]
["2026-02-20","Yes","2026-03-04","Improvement","Changing shift demands now only updates vacant shifts for that specific date.","Updating a date specific shift demand would previously sync the vacant shifts for the entire period. This has been improved and is now done only for the changed date.",null,135237]
["2026-02-20","Yes","2026-03-04","Bugfix","Error for new users","New users could get an error the very first time they logged in. This has been fixed.",null,135024]
["2026-02-20","Yes","2026-03-04","Bugfix","Incorrect vertical calculations when changing shift demands","When updating shift demands, the vertical calculations were updated before the vacant shifts were synced, which could result in incorrect values in case vacant shifts are part of the calculation. This has been fixed.",null,135237]
["2026-02-25","Yes","2026-03-04","Bugfix","Default language changed","In the previous Team Scheduler update an issue was introduced that caused the default language to no longer be taken from the user's browser language. It would always default to English. This was relevant for users that didn't have a language stored in their user settings (for example because this is turned off in the browser).",null,135818]
["2026-02-25","Yes","2026-03-04","Improvement","Login page language selection not stored","When a user would select a different language on the login page, the selected language would not be stored for that user. It was only stored when the user changed the language in the user menu (after login). This has been improved",null,135608]
["2026-02-25","Yes","2026-03-04","Improvement","Vertical calculations updated when self scheduling round changes","Previously only horizontal calculations were updated whenever a self-scheduling round changed. Now the vertical calculations in that schedule are also recalculated.",null,134604]
["2026-02-25","Yes","2026-03-04","Bugfix","Error when opening schedule","In ORTEC WS update 1702119 an issue was introduced resulting in an error when opening a schedule that has a leave request with an empty leave type. This has been fixed.","only available with ORTEC WS update >= 1703292",135775]
["2026-03-13","Yes","2026-03-25","Improvement","Performance improvement in schedule","Performance improvement in schedule queries ","only available with ORTEC WS update >= 1704031",134723]
["2026-03-13","Yes","2026-03-25","Improvement","Performance improvement in sickness tile","Performance improvement in the sickness tile query.                                   ","only available with ORTEC WS update >= 1704031",136151]
["2026-03-13","Yes","2026-03-25","Bugfix","Vertical calculation skipped when adding shift","A vertical (re)calculation could be skipped after assigning a new shift in case an internal demand check failed. This has been fixed.",null,136365]
["2026-03-13","Yes","2026-03-25","Bugfix","Night refresh of calcutions triggered at app restart","The refresh of calculations that runs during the night hours was also triggered when the application was restarted during the day (e.g. after a deployment). This has been fixed.",null,135173]
["2026-03-30","Yes","2026-04-08","Feature","Multilanguage module support","•\tORTEC WS for Team Schedulers now supports the Multilanguage module. This means that if this module is activated, all user entered (master)data will be shown in the correct translation depending on the selected language.\n•\tThis feature has been released in stages in ORTEC WS. To have all entities translated correctly ORTEC WS update >= 1704521 is needed.","only available with ORTEC WS update >= 1704521",56065]
["2026-03-30","Yes","2026-04-08","Improvement","Address & activity properties shown in employee realization","Address and activity property information is now shown in the employee realization details.\nNote: only activity properties without defined permissions are shown. In a future (ORTEC WS) update also properties with permissions are added.","only available with ORTEC WS update >= 1704521",84280]
["2026-03-30","Yes","2026-04-08","Improvement","Vertical calculations now always done in sequence","Triggering many vertical calculations in parallel could lead to memory spikes in the interface worker. This has been improved. Large batches of vertical calculations are now processed in sequence.",null,134368]
["2026-03-30","Yes","2026-04-08","Bugfix","Error when editing a special shift","Editing a special shift would sometimes result in an error if there were duty properties defined on lower departments. This has been fixed.","only available with ORTEC WS update >= 1704521",136364]
["2026-04-13","Yes","2026-04-22","Feature","Calculations are updated more frequently                                            ","•\tHorizontal and vertical calculations are now refreshed more often. \n•\tBefore, calculations would be marked as outdated after 24 hours. This was relevant for changes that occur outside Team Scheduler that influence calculations (e.g. changes in the OWS Client). \n•\tThis has now been made configurable, with a new default of 6 hours (360 minutes). \n•\tIn addition, it is now possible to offload horizontal calculations to another worker, similar to how vertical calculations can already be offloaded.\n•\tNew settings have been introduced to support this feature:\no\tTeamScheduling\\VerticalCalculations\\RecalculateAfterXMinutes (default 360)\no\tTeamScheduling\\HorizontalCalculations\\RecalculateAfterXMinutes (default 360)\no\tTeamScheduling\\HorizontalCalculations\\ServerNumber (default 0  - no offloading)\n•\tIn case these settings do not yet exist, the old default of 24 hours will be used.\nNote: Increasing the calculation frequency will increase the load on the backend. Please lower these settings with care, especially in situations of heavy Team Scheduler usage or in case of demanding calculations.\nIt is advised to offload both horizontal and vertical calculations to another worker process. This makes sure the calculations do not interfere with other Team Scheduler actions.","only available with ORTEC WS update >= 1705035","51137, 51140"]
["2026-04-13","Yes","2026-04-22","Improvement","Employees with multiple sort categories were grouped randomly","Employees with multiple active sort categories were grouped randomly in one of the sort categories instead of the most recent one. This has been improved. Now the most recent sort category (latest begin date) is used. ","only available with ORTEC WS update >= 1705035",134600]
["2026-04-13","Yes","2026-04-22","Bugfix","Vertical calculations could be skipped for departments with many historic assignments","Vertical calculations were skipped in certain departments. This relates to an earlier introduced setting TeamScheduling\\VerticalCalculations\\MaxNrOfEmployeesInDepartment. If the total number of employee assignments (incl. historic ones), was higher than this setting, the calculations would be skipped. This has been fixed. Now only the current employee assignments ","only available with ORTEC WS update >= 1705035",134898]
["2026-04-13","Yes","2026-04-22","Bugfix","Vertical calculations not refreshed in original department when changing subcontract status","When a subcontracted shift was changed from `Concept` to `Final` or vice versa, the counts in the original department were not refreshed. This has been fixed.",null,135322]
["2026-04-17","Yes","2026-04-22","Bugfix","Dashboard failed to load ater permission changes","If a user no longer has permissions for a department which was used previously as a selected department in the dashboard, then the dashboard failed to load. This has been fixed.",null,137909]
["2026-04-17","Yes","2026-04-22","Bugfix","No longer possible to see child nodes when searching for a cost center","When searching for a string in the cost centers tree dropdown, it was no longer possible to see non-matching child nodes of a matching parent node. This has been fixed. \nUsers can now expand a matching parent node to see its non-matching child nodes. Non-matching ancestor nodes are no longer shown.",null,138449]
["2026-04-29","Yes","2026-05-06","Improvement","Longer sick leave history","Users can now add and view sick leaves up to 2 months in the past (from the start of the current month). Previously, this was only 1 month.",null,138442]
["2026-04-29","Yes","2026-05-06","Improvement","Sick leave end date option saved ","The 'I want to specify an end date' option in the add sick leave dialog is now saved for the next time a user uses this dialog.",null,135408]
["2026-05-08","Yes","2026-05-19","Feature","Rollout shift patterns in Team Scheduler","•\tIt is now possible to rollout shift patterns that were created in ORTEC Workforce Shift Patterns.\n•\tThe existing \"Apply cyclical schedule and shift demands\" window did not change visually, but when applying the cyclical schedule Team Scheduler will either apply:\no\tThe cyclical schedule in ORTEC WS (default), or\no\tThe shift patterns created in ORTEC Workforce Shift Patterns if both of the following are true:\n\tShift Patterns is deployed and activated for the Team Scheduler tenant.\n\tIn ORTEC WS, the department property \"UseShiftPatternRollout\" (fixed name) is set to true for the department you are applying it for.\n•\tRolling out shift patterns uses the same logic as applying a cyclical schedule. The same checkboxes for public holidays, sick leave and approved requests are active and used.","only available with ORTEC WS update >= 1706196",130933]
["2026-05-08","Yes","2026-05-19","Improvement","Improvement to potentially solve issue with adding shifts","An improvement was done to the add shift functionality, to potentially solve an issue that sometimes blocks users from adding shifts. We've also added additional logging in case the improvement doesn't fix the problem.",null,139397]
["2026-05-20","Yes","2026-05-26","Technical","Technical preparations for the integration of Team Scheduler into ORTEC Workforce","Technical preparations for the integration of Team Scheduler into ORTEC Workforce. This affects various Team Scheduler components and user authentication. Other than an updated login screen, there are no changes for end users.",null,84285]
["2026-05-21","Yes","2026-05-26","Bugfix","Error when adding shifts","When navigating back and forth between scheduling periods, the shift wish hover popover would break and no longer show up. As a cascading effect, users were no longer able to add shifts on top of the affected shift wishes. This has now been fixed.",null,140039]
["2026-06-10","Yes","2026-06-23","Feature","Export reports to Excel","It is now possible to export Reports to Excel. The Open Report button now has an option to “Export to Excel”. This will generate an Excel file which will be downloaded to the user’s browser.",null,130543]
["2026-06-10","Yes","2026-06-23","Feature","Extend duty property types","•\tAll duty property types are now available, except for free text fields without predefined values.\n•\tWhen read/write permissions are active on a duty property, these are now also considered.","only available with ORTEC WS update >= 1707207",139365]
["2026-06-10","Yes","2026-06-23","Bugfix","Setting subcontract status could fail","Setting the status of a subcontract to/from Final could unexpectedly fail for users who only manage their own department. This has been fixed.",null,140124]
["2026-06-10","Yes","2026-06-23","Bugfix","Logout issues","Fixed several logout issues that were introduced in the previous release.",null,140094]
["2026-06-10","Yes","2026-06-23","Technical","Removed release toggles","Several release toggles have been removed for features that were introduced over a year ago. For these features we now assume that the backend is up to date.",null,139364.13936500001]
["2026-06-25","Yes","2026-07-07","Improvement","Parent calculations can now be expanded and collapsed","Parent calculations can now be expanded and collapsed in the counts tab. Parents are collapsed by default.",null,14665]
["2026-06-25","Yes","2026-07-07","Improvement","Student shifts excluded from staffing","Student shifts are now excluded from overstaffing and understaffing counters. ","only available with ORTEC WS update >= 1707590",140911]
["2026-07-07","Yes","2026-07-21","Feature","Set status for a part of the schedule","•\tIt is now possible to set the status of schedule partially, e.g. only publish/close/approve a part of the schedule.\n•\tThis functionality is behind a new permission called \"Apply status to part of a schedule period\". Without this permission, the user is only able to change the status of a full schedule (like it was).\n•\tTo facilitate this change, the checks on concept planned shifts (to close a schedule) and employee realizations (to approve a schedule) have been moved inside the action dialog and no longer show in the hint text of the action button.","only available with ORTEC WS update >= 1707976",141146]
["2026-07-07","Yes","2026-07-21","Bugfix","Wrong duration for shifts >= 24 hours","The total duration of shifts that are 24 hours or longer was not displayed correctly in the employee realization dialog. This has been fixed.",null,141146]
["2026-07-07","Yes","2026-07-21","Improvement","Sorting in sick leave tile","It is now possible to sort on the columns in the sick leave tile in the dashboard.",null,141146]
["2026-07-07","Yes","2026-07-21","Improvement","Changed notification after creating sick leave shifts","The temporary notification shown in the top right of the screen after successful sick leave shifts creation has been replaced with a success message inside the dialog that stays visible until the dialog is closed or the end date is changed.",null,139544]
["2026-07-07","Yes","2026-07-21","Improvement","Show all employees in employee proposal","Changed the “show 10 more employees” option in the employee proposal to “show all employees” to make it easier to see all proposed employees.",null,138287]
["2026-07-07","Yes","2026-07-21","Improvement","Improved queries for sick leave and leave request tiles","The queries used in the sick leave and leave request tiles have been rebuilt to improve performance. Added feature toggle: TeamScheduling\\FeatureToggles\\LeaveRequestsTileQueryImprovedPerformance which is enabled by default.","only available with ORTEC WS update >= 1707976",141008]
["2026-07-28","Yes","2026-08-04","Feature","Dashboard tiles configurable with permissions                                                             ","•\tIt is now possible to set permissions for individual dashboard tiles. This makes it possible to hide specific tiles for users, for example if they are not allowed to see sick leaves or if swap requests are never used.\n•\tNew Access Control permissions have been created for each tile. When revoked, the tile is no longer shown for the user. \n•\tUsers with existing Team Scheduler access will receive the permissions automatically.\nNote: Depending on which tiles are disabled, the remaining tiles may be displayed in a different place than before.","only available with ORTEC WS update >= 1708625",134568]
["2026-07-28","Yes","2026-08-04","Improvement","Effective work time added to shift","The effective working time is now shown in the shift details, shift edit and employee proposal screens. It contains the sum time of the activities that are considered work in ORTEC WS.                 ","only available with ORTEC WS update >= 1708625",134376]
["2026-07-28","Yes","2026-08-04","Improvement","New permission for editing a subcontracted shift as the receiving department","A new Access Control permission has been added that allows the receiver of a subcontracted shift to edit the shift. This permission is revoked by default.       ","only available with ORTEC WS update >= 1707590",135400]
["2026-07-28","Yes","2026-08-04","Improvement","Added search field to activity type dropdown","Added a search field in the activity type dropdown in the edit shift dialog to quickly search for a specific activity type.",null,140391]
["2026-07-28","Yes","2026-08-04","Improvement","Changed absence visualizations","Changed the visualization of absences to improve visual distinction between leave requests and sick leaves: \no\tSick leaves are now colored pink\no\tLeave requests are now colored blue\no\tIn addition, an icon has been added to sick leaves, leave requests and department unavailabilities",null,140919]
["2026-07-28","Yes","2026-08-04","Bugfix","Missing parameters when exporting to Excel not highlighted","Missing parameters when exporting a report to Excel were not highlighted. This has been fixed.",null,140890]
["2026-07-28","Yes","2026-08-04","Bugfix","Rollout out demanded duties created Requested exchanges","Rolling out demanded duties in a published schedule created exchanges of type Requested instead of Required. This has been fixed.                  ","only available with ORTEC WS update >= 1707976",140346]
["2026-07-28","Yes","2026-08-04","Bugfix","\"Apply cyclical schedule and shift demands option\" gone when navigating between periods","Fixed an issue where the \"Apply cyclical schedule and shift demands\" button would disappear when navigating between scheduling periods using the period navigation arrows.",null,141443]
["2026-07-28","Yes","2026-08-04","Bugfix","Description of a leave request with indefinite end date is confusing","The description of a leave request with an indefinite end date was showing a confusing end date. This has been fixed.",null,142208]
["2026-07-28","Yes","2026-08-04","Translation","Dutch translation for \"Approved\" changed","Dutch translation for the schedule status \"Approved\" has been changed to \"Goedgekeurd\" instead of \"Geaccordeerd\"."]
["2026-08-04","No","2026-08-25","Feature","Support for forbidden violations","•\tForbidden violations can now be checked when performing certain plan actions. A new CSCS setting was added called TeamScheduling\\PlanActions\\CheckForbiddenViolations, which is False by default.\n•\tWhen the setting is enabled, the system checks whether the performing user has permissions to create a violation that would occur from the action (if permissions are enabled on the violation type). \nIf not, the action is blocked and the user will receive a message that it is not allowed to perform this action, including the violation information.\n•\tThe following plan actions are affected:\n•\tEditing a shift\n•\tAdding a shift\n•\tMoving a shift\n•\tApproving an employee realization\n•\tAssigning a shift through the employee proposal\nImportant note: When the new setting is enabled, the user needs additional ORTEC WS permissions to continue to use certain plan actions. For editing shifts, the permission SHIFT_REALISATION_PLAN_WRITE, SHIFT_REALISATION_PUBLISHED_WRITE are needed. For diagonal shift movements their respective ORTEC WS permissions are needed. If these are not granted when the setting is enabled, users will no longer be able to perform these actions in Team Scheduler.","only available with ORTEC WS update >= 1708625",143220]
["2026-08-04","No","2026-08-25","Other","Styling changes","We've updated the styling of the application to match our latest design guidelines. Users will notice changes in rounding, colors and fonts used by some of the interface elements. ",null,9618.5958699999992]