{"text_format":"1","workbook":"xlsx","n_sheets":2,"sheets":["Release notes","Blad1"],"not_rendered":{"charts":0,"images":0,"macros":1,"external_links":0,"defined_names":1,"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":1787,"n_cols":15,"rows_kept":1787,"cut":false,"hidden":false,"merged":[[0,0,0,9]]}
["P = Push this update and C = Client install mandatory (in first 2 columns)"]
["Pushpatch","Client mandatory","Update","Build date","Relevant for customer","Module","Issue Type","Release category","Release domain","Title","Release note","Upgrade note","Issue","Incident"]
[null,null,1074079,null,null,null,"Bug","Technical","Utilities","The ORTEC Patch Configuration now also allows updates with name Update*.zip","The ORTEC Pach Configuration will now allow both Patch*.zip and Update*.zip files as a format for updates.\n\nTest hints:\n1. Verify that updates can be installed with ORTEC Patch Configuration or ORTEC System Configuration.","Rename Update_1074079_CLib.zip to Patch_1074079_CLib.zip if you used the first installer and do not see the updates. Restart the patch util","OSDCOMMAIN-11351"]
[null,null,1076203,null,null,null,"Bug","Reliability","Service","ESS role unexpectedly removed with user import","When importing the same user record twice, no user group would remain for users when using the updateStrategy \"overwrite\". \nThis has been fixed. \n\nTest hints: \n1. Verify that an (ESS) user group of a user can be changed using ExtraXMLCreator 'TUserImport'.","","OSDCOMMAIN-11331","9532303"]
[null,null,1076203,null,null,null,"New Feature","Functionality","Service","Created new labor rule to check that a cost center is filled in for all activities with certain activity types","For some customers, filling in the cost center of an activity is mandatory for certain activity types. A new labor rule has been added to check this and give a violation in the planboard when the cost center is not filled in an activity that has one of the selected activity types.\nAdded global setting ActivityCostCenterCheckReq which is turned off by default. \n\nTest hints:\nPrecondition: the new labor rule is enabled in settings manager.\n1. Verify that the labor rule can be added to the labor rules set of the employment conditions.\n2. Verify that the rule gives a violation when no cost center is filled in an activity with one of the selected activity types.","","OSDOWSD-618",""]
[null,null,1076203,null,null,null,"New Feature","Functionality","Win32 User Interface","Added functionality to automatically remove shifts when changing validity period of a duty","When filling the valid until date of a duty in the duty set, it is possible that an error occurs that the duty is still used in shifts after the new valid until date. The planner has to remove these shifts manually.\n\nAdded Server setting: Duty\\RemoveShiftsOnShorteningValidPeriod with default value N. When this setting is enabled, the shifts after the valid until date will be removed automatically. In case there are shifts to be removed after setting the valid until date of the duty, the planner will receive a question in a dialog and has to answer yes to actually remove the shifts.\n\nAdded permission DUTY_UPDATEVALIDPERIOD_REMOVESHIFTS which is granted for users having permission DUTYSET_WRITE. \n\nTest hints:\nPrecondition: the new server setting is set to N\n1. Verify that setting the end date of a duty in the duty set is possible. \n2. Verify that when there are still shifts after the end date for this duty, an error message will be shown.","For this solution to become available, the win32 client must be installed.","OSDOWSD-621",""]
[null,null,1078922,null,null,"","New Feature","Technical","Employee self-service","Approving a swap request should not be dependent on a permission for the users in Employee Self Service","In Employee Self Service, the permission SWAP_SHIFT_WRITE was incorrectly considered when approving a swap request by an employee.\nThis has been fixed.\nThe permission SWAP_SHIFT_WRITE is no longer considered for the users in Employee Self Service because this permission should be considered only for the planners in OWS Client.\n\nTest hints:\n1) Swap a shift in OWS Client.\nExpected result : Shift can be swapped if the above permission is granted for the planner","","OOBA-296",""]
[null,null,1078922,null,null,"","New Feature","Security","Employee self-service","Make sure endpoint to retrieve token with username/password is not available on production environment","The BackendAPI provides an authorization mechanism that is only used during development. This authorization method via a URI endpoint is available in production and remotely accessible.\nTo improve security it is no longer allowed to request an authorization token using the URI endpoint on a production environment from remote hosts\n\nTest hint:\n- login and use ORTEC WS for Employees","","OOBA-334",""]
[null,null,1078922,null,null,"","New Feature","Reliability","Employee self-service","Creating a swap request can give a 'Sequence contains no elements' error","Sometimes, the exception 'Sequence contains no elements' is shown to the ORTEC WS for Employees user when he tries to swap a shift. If that happens, the request is created, but the swap request icon is not shown in the schedule.\nThis has been fixed. Now, the exception is not shown anymore, and the icon is shown.\n\nTest hints:\n1. In ORTEC WS for Employees, create a swap request. ","","OOBA-342",""]
[null,null,1078922,null,null,"","Bug","Reliability","Win32 User Interface","Changing the end date contract of an employee does not recalculate account entries","When changing the 'end date contract' of an employee, the saved account entries in the changed period were not recalculated. \nThis has been fixed. \n\nTest hints: \n1. Change the end date contract of an employee and check the account entries in the changed period are recalculated.","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-11324","9525505"]
[null,null,1078922,null,null,"","Bug","Reliability","Win32 User Interface","Warning to recalculate account entries sometimes shown when not needed","When the begin date of the first contract of an employee is not the first day of the scheduling period, a false warning message about recalculating account entries could be shown when opening the scheduling period.\nThis has been fixed.\n\nTest hints:\n1. Verify that adding an employee to a department half way the scheduling period will not lead to a warning about recalculating account entries","For this solution to become available, the win32 must be installed","OSDCOMMAIN-11347","9554360"]
[null,null,1078922,null,null,"","Bug","Performance","Win32 User Interface","Improved performance when opening employee management window","When opening the employee management window for the first time, selecting  '(All departments)' could be slow. \nThis has been improved. \n\nTest hints:\n1. Verify that selecting 'All departments' will show the expected employees.","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-11361","9585588"]
[null,null,1078922,null,null,"","Bug","Reliability","DataWarehouse","Memo days are seen as holidays in BI Support","When getting the holidays for BI Support, also memo days were taken into account. \nThis has been fixed.\n\nTest hints:\n1. Run an incremental load and verify the results","In order to correct the current data, all holidays will be removed by the dbupdate. In order to return holiday info to BI, a BI run (incremental load) should be scheduled.","OSDCOMMAIN-11362","9585592"]
[null,null,1078922,null,null,"","Bug","Security","Core Framework","Improved security of login sessions for ESS and MSS","Improved the security against session hijacking in combination with load balancing systems. \n\nTest hints:\n1. Verify that it is possible to log in to ESS or MSS","","OSDCOMMAIN-11363","9586145"]
[null,null,1078922,null,null,"","New Feature","Security","Service","Certain private information is logged in Windows event viewer","Several error messages that are logged into the Windows event viewer could contain the name and employee number of the employee. This is private information that should not be shown according to the General Data Protection Regulation (GDPR).\nThis has been fixed. Now the database ID of the employee is shown.\n\nTest hints:\nNone","","OSDOWSD-623",""]
[null,null,1078922,null,null,"CMHS","New Feature","Security","Utilities","XSDProcessor writes entire file to event viewer","The XSDProcessor component in the System Configuration Network Editor was writing the entire xml file to the event viewer if the xml could not be validated. This is private information that should not be shown according to the General Data Protection Regulation (GDPR). \nThis has been fixed.\nNow the XSDProcessor does not write the contents of xml files to the event viewer anymore. \n\nTest hints:\nNone","","OSDOWSD-624",""]
[null,null,1078922,null,null,"","New Feature","Security","Service","Username is logged to event viewer when an error occurs in a plan board","Error messages related to a plan board could contain the username of the user that opened this plan board. This is private information that should not be shown according to the General Data Protection Regulation (GDPR).\nThis has been fixed.\n\nTest hints:\nNone","","OSDOWSD-625",""]
[null,null,1078922,null,null,"","New Feature","Security","Core Framework","Username is sometimes shown in ORTEC Identity Gateway log entries","Error messages logged into the Windows event viewer by ORTEC Identity Gateway could contain the user name. This is private information that should not be shown if not needed according to the General Data Protection Regulation (GDPR).\nThis has been fixed. \n\nTest hints:\nNone","","OSDOWSD-629",""]
[null,null,1078922,null,null,"","New Feature","Configuration","Utilities","CSCS does not have to be started as admin","When starting Ortec System Configuration, a User Account Control window used to be shown that asks for elevated rights. When the user did not grant these rights, the application would not start. \nThis has been improved.\nOrtec System Configuration no longer asks for the elevated rights. When started normally, the text '(No administrator)' is added to the caption of the application and some functionality like creating environments and uploading configuration files is not possible. If the user still wants to use that functionality, the process has to be started using 'Run as administrator'\n\nTest hints:\n1. Start Ortec System Configuration","From now on, use 'Run as administrator' for CSCS.exe if you need to use the small set of functionalities that need elevated rights.","OSDOWSD-630",""]
[null,null,1078922,null,null,"","Bug","Functionality","Security","OIG installer: the connection in connectionstring.config is not encrypted","When installing the Ortec Identity Gateway, the file containing the database connection string is now encrypted.\nThis means a user has to be an administrator to be able to read the current configuration using the tool.\n\nTest hints:\n1. Start IdentityGatewayConfigurator.exe","","OSDOWSD-636",""]
[null,null,1081014,null,null,"","New Feature","Functionality","Employee self-service","Confirming an actual without any changes should be only dependent on the \"gui.ess.realizeshift.submit\" permission.","In ORTEC WS for Employees, confirming a shift without changes should depend on the permission to confirm shifts, but it depends on the permission to realize a shift.\nThis has been fixed.\nNow, it is possible to confirm a shift without changes if the user only has the permission 'Confirm' (and not the permission: 'Update shift with status xxx (ESS)').\n\nTest hints:\n1. In ORTEC WS for Employees, confirm a shift without changing it","","OOBA-336",""]
[null,null,1081014,null,null,"","New Feature","Reliability","Installer","Remove dependency of UrlRewrite from backendAPI install script","During installation of the backendAPI, a message was shown that the UrlRewrite module should be installed for the redirect to https to work. Installing UrlRewrite is not necessary, so the warning has been removed.\n\nTest hints:\n1. Install the backendAPI and see that it is started","","OOBA-345",""]
[null,null,1081014,null,null,"","Bug","Stability","Service","Deleting a pending update outside buffer history from the interface worker can cause an error on server one","When the status of a scheduling period is set to approved, the shifts that are not needed anymore are deleted from the database. This happens for instance for shifts that are not planned. When setting the status is applied via an import and one of the shifts that are deleted used to have a pending realization, an error could be raised on the main server when deleting the pending realization. \nThis has been fixed. \n\nAdded feature toggle Server setting: FeatureToggles\\AllowLoadingOfDutyWhenApplyingDutyChanges which is by default enabled.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hints: \n1. Verify that the status of a scheduling period can be updated with an import.","","OSDCOMMAIN-11221",""]
[null,null,1081014,null,null,"","Bug","Reliability","Interfaces","No message created when employee import fails","For employee imports, in some cases there was no message created when the import failed.\nThis has been fixed.\n\nTesthints:\n1. Subscribe to 'XML-interface failed' messages. Verify that a message is created if the employee import fails.","","OSDCOMMAIN-11290","9511134"]
[null,null,1081014,null,null,"","Bug","Reliability","Win32 Userinterface","Incorrect cell selected after mouse click in a workstation plan board with multiple days","When selecting a cell that requires scrolling in the workstation plan board, the cursor would not jump to the correct cell. \nThis has been fixed.\n\nTest hints:\n1. Verify the correct cell in the workstation plan board can be selected.\n2. Verify that clicking on a cell selects the correct cells in the adjoining grids","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-11341","9547462"]
[null,null,1081014,null,null,"","Bug","Functionality","Win32 Userinterface","Several translations added for German and Finnish","Several translations have been added for German and Finnish for recent functional changes.\n\nTest hints:\nNone","","OSDCOMMAIN-11375",""]
[null,null,1081014,null,null,"","Bug","Reliability","Calculation","Criterion 'Avoid over qualification' calculates penalty per occurence of skill in a shift","Scheduling criterion 'Avoid over qualification' gave a penalty per occurence of a skill for which the employee is over qualified.\nThis has been improved. \nAn option is added to the criterion to indicate whether there should be a penalty for every occurence of the skill, or only for unique ones. \n\nNOTE: When the same skill is used twice with a different level or workstation, they are regarded as different occurences\n\nTesthints:\n1. Create a shift with two activities with the same activity type that has a skill for which the employee is over qualified. \n - When setting the new option to 'all', the shift should have 2 penalties\n - When setting the new option to 'unique', the shift should have 1 penalty","","OSDCOMMAIN-11383","9608815"]
[null,null,1081014,null,null,"","New Feature","Functionality","Interfaces","New command handler to update duration of activities percentually","A new command handler CAdjustDurationOfActivitiesPercentually has been added. This command handler can be used to extend or shorten activities percentually. Only non-removed shifts and shifts in a regular schedule are supported by this command handler. Extending a shift outside the buffered history is not possible, because it cannot be checked whether overlap with other shifts is caused by adjusting the shift.\n\nExample input for the new command handler:\n<CAdjustDurationOfActivitiesPercentually>\n  <parameters>\n    <shifts>\n     <shift id=\"123\"/>\n     <shift id=\"124\"/>\n    </shifts>\n    <option value=\"extend\" />  \n    <percentage value=\"50\" />\n    <activityType id=\"125\" />\n    <timeToAdjust value=\"beginOfActivity\" /> \n  </parameters>\n</CAdjustDurationOfActivitiesPercentually>\n\nParameters of the command handler:\nshifts: Here shift id's are specified of shifts that will be adjusted.\noption: This parameter can be set to either \"extend\" or \"shorten\" to extend or shorten the activities with activity type.\npercentage: The percentage by which an activity is extended/shortened. This must be greater than 0.\nactivityType: Only the activities with the specified activity type are extended/shortened.\ntimeToAdjust: This parameter can be set to either \"beginOfActivity\" or \"endOfActivity\". When it is set to beginOfActivity the activity begin time is adjusted in order to extend/shorten the activity. When it is set to endOfActivity the activity end time is adjusted in order to extend/shorten the activity.\n\nTest hints:\nNone","When running the interface handler on an interface server. Parameter ReadHistoryForAllDepartments must be set to 'Y' and the shifts to adjust must be in the buffered history. Otherwise, extending a shift is not possible as overlap cannot be determined outside the buffered history. Shortening a shift is possible outside the buffered history.","OSDOWSD-580",""]
[null,null,1081014,null,null,"","Bug","","","In ORTEC WS for Employees the team schedule sometimes shows shifts of the previous day","In case a shift ended between 23:00 and 00:00 the shift was shown in the team schedule/workstation assignment popup on the next day.\nThis has been fixed.\nNow, the team schedule or workstation assignment popup only shows shifts of the opened period.\n\nTest hints:\n1. Verify in ORTEC WS for Employees that in team schedule or workstation assignment popup only shifts of the selected day are shown.\n","","OSDOWSESS-724",""]
[null,null,1082782,null,null,null,"Bug","Reliability","Database","Possible duplicate entries in BI database for SQL Server 2012","The FACT package for assigned activities used an incorrect end date for gathering data when comparing with the availability of the employee. This caused duplicate entries in the HDM database for BI. \nThis has been fixed.\n\nNote that this was incorrect for the package for SQL Server 2012 only. The other packages have not been changed.\n\nTest hints:\n1. Run an incremental load and verify the results","","OSDCOMMAIN-11384","9608817"]
[null,null,1082782,null,null,null,"Bug","Reliability","Service","Date of account entries could be changed when transferring booking per entry","The compensation rule 'Transfer booking based upon an expression' booked account entries on the day of the shift in case 'per entry' was selected. This caused the following case to fail:\n- Global setting UseBookOnDayOfShift is on\n- Rule 'Allowances per time interval' is set up to book on the day of the activity - for night shifts the 2nd part of the shift is booked on a different date than the first part\n- Rule 'Transferbooking based upon expression' is set up 'per entry'.\nIn this case, the bookings belonging to the 2nd part of the night shift would be moved to the date of the begin time of the shift.\nThis has been fixed.\nBookings no longer switch dates when using the 'per entry' option.\n\nAdded feature toggle DoNotBookOnDayOfShiftForAccountUsingExpressionsRem: FeatureToggles\\DoNotBookOnDayOfShiftForAccountUsingExpressionsRem and is by default enabled.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hints:\n1. Only relevant in case UseBookOnDayOfShift is on\n2. Verify that bookings for the 2nd part of night shifts created by rules of type 'Transferbooking based upon expression' which book 'per entry' are shown on the correct day.","","OSDCOMMAIN-11390",""]
[null,null,1082782,null,null,null,"Bug","Reliability","Optimization","Automatic planner 'Generate master schedule' misses improvements for employees with 0 hour contract","The automatic planner 'Generate master schedule' had a check if an employee was already planned for all of his contract hours with fixed shifts. These employees were not considered in the local optimization phase, to speed up this phase. However, in many cases employees are allowed to have more working time than their contract hours, for instance for employees with a 0 hour contract.\nThis has been fixed.\nThe check has been removed, so the schedule of employees with a 0 hour contract is optimized as well. For the cases where the labor-time rule 'Working hours and availability' is used to prevent that employees are planned more than their contract hours, there was already another mechanism in place to filter out the employees that are already 'fully' planned to guarantee performance.\n\nTest hints:\n1. Run 'Generate master schedule' and verify the results.","","OSDCOMMAIN-11391","9610220"]
[null,null,1082782,null,null,null,"Bug","Reliability","Employee self-service","In ESS Find Address overview, the house number and extension are not included in the columns that are shown by default.","In the ESS find address window, the 'housenumber' and 'housenumber ext.' columns are not shown by default if a user logs on for the first time.\nThis has been improved.\nNow also the 'housenumber' and 'housenumber ext.' are shown by default.\n\nTest hints:\n1. Login to ESS with a new user and verify the default columns of the address search window.","If a user has logged on before, he still keeps his own column configuration. To use the new default, remove the file 'transientconfig.xml' for this user (In folder ...Ortec\\ORTEC Workforce Scheduling\\CWGS\\default\\CWGSESSCONFIG\\Users). The file will be regenerated when the settings are saved on next logout.","OSDCOMMAIN-11419","9636296"]
[null,null,1084864,null,null,null,"Bug","Stability","Service","In case the import of a shift fails because the shift was already changed, the import is not always reverted correctly","If the CWSS process is very busy, there is a chance that an action creates a realization on a shift that is also changed by an import. This causes the import to fail, which is correct, but the import action is not reverted correctly. A retry of the import will not succeed and the CWSS process has to be restarted to resolve the problem.\nThis has been fixed.\nAfter a failure of the import due to changes to the same shift, the import action will be reverted to make a retry possible.\n\nTest hints:\n1. Verify a shift realization can be imported","","OSDCOMMAIN-11399",""]
[null,null,1084864,null,null,null,"Bug","Performance","Service","Improve performance of displayer Understaffed/Overstaffed by running less queries","When the shift counters also take into account nonrecurring duties, updating the counters is slow, because queries are run on the database. This has been improved. The amount of queries required has been greatly reduced. \n\nTest hints: \n0. Precondition: your shift counters also count nonrecurring duties \n1. Verify the amount of nonrecurring duties is counted correctly towards the demand","","OSDCOMMAIN-11418","9635454"]
[null,null,1084864,null,null,null,"Bug","","","Cumulative clocking total shows very small number instead of 0 after the decimal separator","In the clock times window, the amount and cumulative amount booked on selected account categories is shown unrounded.\nThis has been improved. \nNow the amount shown is rounded to the nearest minute for accounts with Time entries, and rounded to two decimals for accounts with Payment or Amount entries.\n\nTest hints:\n1. Check the amount for a selected category in the clock times window is rounded.","","OSDCOMMAIN-11422","9638938"]
[null,null,1086845,null,null,null,"Bug","Configuration","Utilities","ORTEC Patch Utility must be run as an administrator","Ortec System Configuration needs elevated right for certain tasks. One of these task is applying updates through the Ortec Patch Utility as changes to the system have to be made. Ortec Patch Utility must therefore always be started as administrator.\nThis was a manual task that has been improved.\nStarting the Ortec Patch Utility will now ask if it needs to be started as administrator and shows the User Account Control window to asks for elevated rights.\nNext to that, Ortec System Configuration will now show for which tab elevated rights are always needed by adding the text 'Admin required'.\n\nTest hints:\n1. Start Ortec Patch Utility\n2. Start Ortec System Configuration","Note: in case CSCS has already been run on the machine, some configuration files are already saved on disk for user admin. This will prevent CSCS from being able to read and write these files in case it is started for a different user.\nIf you do not want to start CSCS as admin and do want to update the configuration, you should remove these configuration files.","OSDCOMMAIN-11427","9652903"]
[null,null,1089040,null,null,null,"Bug","Reliability","Reporting","Report 'Overview shifts' ('Dienstenoverzicht') incorrectly displays a shift for lended employees","When the option in the report 'Overview shifts' to 'Show employees from other departments' is selected these employees will be shown in 'italic', otherwise they are hidden. If the employee worked for another department and had been lended to the current department in the past, the shift would sometimes be incorrectly hidden or shown 'italic'. \nThis has been fixed. \nThe report will now correctly handle lending and borrowing. \n\nTest hints: \n1. Verify that the report 'Overview shifts' only shows employees from other departments as 'italic'.\n2. Verify that the report 'Overview shifts' shows shifts of employees who previously worked in another department in a normal font.","","OSDCOMMAIN-11435","9662768"]
[null,null,1089040,null,null,null,"Bug","Reliability","Service","Cleanup unused employee realization information was not done correctly","Cleaning unnecessary information about employee realizations from memory could cause an exception. This has been fixed.\n\nTest hints:\n1. Decline and close an employee realization.","","OSDCOMMAIN-11440",""]
[null,null,1089040,null,null,null,"Bug","Reliability","Reporting","Master schedule report cannot handle hexadecimal color setting values","The Master schedule report for the planner was unable to handle hexadecimal values for the settings 'COLOR\\SHIFTILLNESSCOLORDISPLAYCOMPONENT(ISDEFINITELYILLONDAY)'\n'COLOR\\SHIFTILLNESSCOLORDISPLAYCOMPONENT(HASILLNESSAVAILABILITIESONTIME)'. This has been fixed.\n\nTest hints:\n1. Verify colors of illnesses and work therapy is shown correctly in the report.","","OSDCOMMAIN-11445","9666274"]
[null,null,1089040,null,null,null,"Bug","","","FIRSTDAYOFILLNESS expression returns incorrect results in case illness starts after midnight","For the compensation rule 'Transferbooking based upon an expression', the expression 'FIRSTDAYOFILLNESS' results in an incorrect value if the illness on the calculated day starts at a later time on that day.\nThis has been fixed. \nNow if we calculate account entries for today, and the illness start later today, still today is returned. \n\nAdded feature toggle Server setting: FeatureToggles\\CheckWholeDayForFirstDayOfIllnessExpression and is by default enabled. \nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department. \n\nTest hints:\n1. Verify that the expression returns the start date of the illness in case an illness starts halfway the day: \n\t- Create an illness that starts somewhere halfway the day. \n\t- Create compensation rule 'Transferbooking based upon an expression' and add a 'FIRSTDAYOFILLNESS' expression. \n\t- Verify that the expression returns the correct starting date of the illness.","","OSDCOMMAIN-11448","9668212"]
[null,null,1089040,null,null,null,"Bug","Reliability","Service","Dragging a shift from the history part of a plan board shows an empty message","It is not allowed to drag a shift from the history part of the plan board to another day. The message to show this to the user was missing, which resulted in an empty message dialog. \nThis has been fixed. \nA message will be shown: 'It is not allowed to make changes in the history part of the plan board.' \n\nTest hints: \n1. Verify that a shift can be moved horizontally and vertically within a plan board. \n2. Verify that a message is shown when a shift is moved from the history into the plan board.","","OSDCOMMAIN-11458","9674287"]
[null,null,1089040,null,null,null,"Bug","","","Several translations added for German, Finnish and French","Several translations have been added for German, Finnish and French for recent functional changes. \n\nTest hints: None","","OSDCOMMAIN-11478",""]
[null,null,1089040,null,null,null,"New Feature","Configuration","-","SSL certificate not found during install of BackendAPI","When installing the BackendAPI, the script failed to bind the correct certificate when it was located in certificate store \"Web Hosting\". Only certificates from certificate store \"Personal\" were considered. \nThis has been fixed.\nCertificates in certificate store \"Web Hosting\" are now also considered. \n\nTest hints:\nNone","","OSDOWSD-670",""]
[null,null,1091085,null,null,null,"New Feature","","","In Shift picking page, KPI values with a decimal are not shown correctly","In ORTEC WS for Employees, the values of the Shift picking KPI's were printed wrongly in case of decimal values. For example, a value 7,12 was shown as 712.\nThis has been fixed.\nNow, the KPI values in Shift picking are shown correctly.\n\nTest hints\n1. Go to ORTEC WS for Employees > Schedule on Shift picking mode -> verify the values for the Shift picking KPI's are correct","","OOBA-273",""]
[null,null,1091085,null,null,null,"Bug","Stability","Service","Deleting work therapy  might halt the CWSS export server process in case IllnessAvailabilitiesCollector is used","In rare cases, deleting multiple work therapy lines for the same illness within a short time span causes the export server to halt. \nThis has been fixed. \n\nAdded feature toggle Server setting: FeatureToggles\\ALWAYSQUERYTRANSACTIONDATAOBJECT and is by default disabled. \nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hints:\n1. Verify that work therapy can be deleted.","","OSDCOMMAIN-11459",""]
[null,null,1091085,null,null,null,"New Feature","","","Permission managerOfDepartments is not visible in access control category \"ORTEC WS for Managers\"","Permission managerOfDepartments is only located in permission category \"Manager Self Service (deprecated)\" while it should also be shown in the category \"ORTEC WS for Managers\". \nThis has been fixed.\nIt is now shown in both categories.\n\nTest hints:\n1. Verify in Access control that permission managerOfDepartments is visible in categories \"Manager Self Service (deprecated)\" and \"ORTEC WS for Managers\". ","","OSDCOMMAIN-11460","9674824"]
[null,null,1091085,null,null,null,"Bug","Reliability","Web User Interface","ORTEC WS for Web: not possible to roll out a cyclical schedule or change the roster status","An error is raised in ORTEC WS for Web when trying to roll out a cyclical schedule or change the roster status.\nThis has been fixed.\n\nTest hints:\n1. Verify that it is possible to roll out a cyclical schedule\n2. Verify that it is possible to change the roster status","","OSDCOMMAIN-11480","9684933"]
[null,null,1091085,null,null,null,"Bug","Reliability","Service","Question to update shifts is shown while not needed when updating the validity period of a duty","Note: Question to update shifts is only shown when server setting Duty\\RemoveShiftsOnShorteningValidPeriod is ON (default OFF).\n\nWhen entering the valid until date of a duty in the duty set, a question is shown whether the shifts for this duty after the valid until date have to be removed or if they have to be replaced by an equivalent duty. This question is shown, even if there is no equivalent duty that can be used.\nThis has been improved.\nNow, the question to remove or replace will only be shown if there is an equivalent duty that can be used as replacement.\n\nTest hints:\n1. Verify that setting the end date of a duty in the duty set is possible. ","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-11491","9689597"]
[null,null,1091085,null,null,null,"Bug","Technical","Service","Add French translations","Several translations have been added for French for recent functional changes. \n\nTest hints: None","","OSDCOMMAIN-11493",""]
[null,null,1091085,null,null,null,"Task","","","Partial leave is automatically checked","The checkbox 'Partial leave' is selected by default based on the corresponding server setting.\nNote: this functionality requires an app update.\nNote2: this was already done for win32 and ESS frontends.\n\nTest hints:\n1. Verify it is possible to create a leave request from the app.","","OSDGMSSRV-1320",""]
[null,null,1091085,null,null,null,"New Feature","Reliability","Service","Improve information about shifts that will be deleted when setting new valid until date of a duty","Note: The question to update shifts is only shown when server setting Duty\\RemoveShiftsOnShorteningValidPeriod is ON (default OFF). \n\nWhen changing the valid from date of a duty set duty, a message could appear that informs the user which shifts will be removed. The depicted shifts were not in a logical order. This has been fixed. The shifts are now ordered by begin time, resource and department.\n\nTest hints:\n1. Change the valid to date of a duty set duty such that shifts will be removed. Verify that the shifts in the message are ordered correctly.","","OSDOWSD-747",""]
[null,null,1091085,null,null,null,"New Feature","Reliability","Employee self-service","In ORTEC WS for Employees, it is possible to select a department period for a central department","In ORTEC Workforce scheduling for Employees, a user which is assigned to a central department can also select scheduling periods of the central department.\nThis has been fixed.\nNow, a user can only see the available scheduling periods of non-central departments.\n\nTest hints:\n1. Verify that a user in ORTEC WS for Employees can open scheduling periods.","","OSDOWSESS-730",""]
[null,null,1094638,null,null,null,"New Feature","Technical","Tools","Information on used sessions for ORTEC Workforce scheduling for Employees and Managers is missing","For analysis purposes, the number of sessions in use and/or created by the ORTEC Workforce Scheduling for Employees and Managers applications is recorded in the logging.\n\nAdded feature toggle Server setting: FeatureToggles\\LOGLOGINSESSIONOWSAPPLICATIONFORFRONTENDS and is by default enabled. \nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department. \n\nTest hints:\n1. Verify a user can log in to ORTEC Workforce Scheduling for Employees.\n2. Verify a user can log in to ORTEC Workforce Scheduling for Managers.","","OOBA-368",""]
[null,null,1094638,null,null,null,"Bug","Reliability","Employee self-service","Employee Self Service: Opening Personal information after updating a shift update shows error messages","Error messages are shown when opening Personal information after adding or updating a shift update in Employee Self Service (ESS).\nThis has been fixed.\nNow, Personal information can always be seen.\n\nTest hints:\n1. Verify that a shift update can be created and updated in ESS.\n2. Verify that the Personal information can be shown after updating a realization.","","OSDCOMMAIN-11483","9685684"]
[null,null,1094638,null,null,null,"New Feature","Technical","Miscellaneous","Adjust backend API install script for changing tables in ORTEC WS database","Added a new table to the database: ROS_SELFSCHEDULING_REMARKS. This table is added to the OWS database when the backend api is updated or installed. The table is not yet used, it is needed for future changes.\n\nTesthints:\n1. Test that the backend API can be installed or updated.","NOT NECESSARY IF VERSION 1096948 OR HIGHER! - When installing or updating the backend API, also fill in the new parameter \"owsDatabase\" in the file InstallPortal.xml (see Readme.txt):\nconnection string used for ows database connection; it should contain Data Source, Initial Catalog, Integrated Security. Note that Integrated Security can be replaced by User Id and Password (that must be valid in the database), but that is not advised for security reasons.","OSDOWSD-753",""]
[null,null,1094638,null,null,null,"Bug","Reliability","Win32 Userinterface","Information message about shifts to be removed is shown without any shifts","When a user changes the validity period of a duty in a duty set and selects to remove all existing shifts in the period, a message is shown in case the adjusted period already contains removed shifts. When there are 0 shifts to be removed, the message shows that 0 shifts will be removed. \nThis has been fixed. \nNo message is shown when 0 shifts will be removed. \n\nTest hints: \nPrecondition: setting Duty/RemoveShiftsOnShorteningValidPeriod is turned on \n1. Change the validity period of a duty in the duty set. Verify no message is shown when no shifts will be unplanned.","For this solution to become available, the win32 client must be installed.","OSDOWSD-765",""]
[null,null,1094638,null,null,null,"New Feature","Technical","Database","Removed obsolete table ROS_EMPLOYEES_USERNAMES","The table ROS_EMPLOYEES_USERNAMES and view HMY_EMPLOYEES_USERNAMES are removed from the database, because they are not used by ORTEC Workforce Scheduling. \n\nTest hints: \nNone","Table ROS_EMPLOYEES_USERNAMES and view HMY_EMPLOYEES_USERNAMES should not contain any data. So you should not have to update anything.","OSDOWSD-809",""]
[null,null,1094638,null,null,null,"New Feature","Functionality","Win32 Userinterface","Employee form does not show entire ESS username","When hovering the mouse over the 'User name' field in the 'Employee management' form, the hint will show the user name. This is helpful in case the user name is longer than the field is able to show.\nThis change also makes it possible to copy the user name directly from the 'Employee management' form.\n\nTest hints:\n1. Hover mouse over 'User name' field. Verify hint is shown in case field is filled.\n2. Copy the user name from 'User name' field.","For this solution to become available, the win32 client must be installed.","OSDOWSD-810",""]
[null,null,1094638,null,null,null,"New Feature","Functionality","Service","New command handler to move a shift to a different time on the same day","A new shift is always created when moving a shift with the commandhandler CAssignShift. This is not needed when the shift is only moved to another time on the same day. Therefor a new commandhandler CMoveShiftOnDay is added. This commandhandler moves the shift to a different time on the current begin date by creating a realization on the shift. \n\nExample of the input xml:\n<CMoveShiftOnDay>\n  <parameters>\n    <shift id=\"123\" />\n    <newBeginTime value=\"2018-05-31T15:25:00.000+02:00\" />\n   </parameters>\n</CMoveShiftOnDay>\n\nNote that this command handler does not allow moving shifts with pending updates.\n\nTest hints:\n1) Verify that the shift can be moved to a different time on the same day with the new commandhandler CMoveShiftOnDay\n2) Verify that the shift can not be moved to a different day with the new commandhandler CMoveShiftOnDay","","OSDOWSD-818",""]
[null,null,1094638,null,null,null,"New Feature","Reliability","Database","A user with a long user name cannot be linked to a user group in Access control","Linking a user with a long user name (maximum of 200 characters) to a user group failed, because of an error.\nThis has been fixed.\nIt is now possible to link a user with a user name of length 200 to a user group. \n\nTest hints: \n1. Verify in Access control that a user can be linked to a user group.","","OSDOWSD-823",""]
[null,null,1096948,null,null,"","Bug","","","The color of violations in an old schedule is missing","When calculating violations of a schedule ending before 'AUTOMATICCALCULATEVIOLATIONAGE', the shifts with violations are not marked. \nThis has been fixed.\n\nTest hints:\n1. Verify that when calculating violation in a schedule ending before 'AUTOMATICCALCULATEVIOLATIONAGE', violations are shown on the relevant shifts","","OSDCOMMAIN-11514","9733919"]
[null,null,1096948,null,null,"","Bug","Reliability","Reporting","Master schedule ESS report cannot handle hexadecimal color setting values ","The Master schedule report for the planner cannot handle hexadecimal values for the settings 'COLOR\\SHIFTILLNESSCOLORDISPLAYCOMPONENT(ISDEFINITELYILLONDAY)'\n'COLOR\\SHIFTILLNESSCOLORDISPLAYCOMPONENT(HASILLNESSAVAILABILITIESONTIME)'. \nThis has been fixed.\n\nTest hints:\n1. Verify colors of illnesses and work therapy is shown correctly in the report.","","OSDCOMMAIN-11515","9733920"]
[null,null,1096948,null,null,"","Bug","Reliability","Reporting","Report 'Overview shifts' groups shifts without considering the actual shift begin time","Report 'Overview shifts' groups shifts using the relative begin and end times of the activities, without considering the actual shift begin time. This results in shift and employees grouped together when the (realized) actual begin time of the shift are not the same. \nThis has been fixed. \nThe shifts are grouped taking into account (realized) actual begin time of the shift. \n\nTest hints: \n1. Run the shift overview report ","","OSDCOMMAIN-11516","9733951"]
[null,null,1096948,null,null,"","Bug","Security","Service","Employee name and number in eventlog when calculating compensation rules fails","When calculating bookings fails, the name and number of the employee were written to the event log. This has been fixed.\nNote that the information to the end user has not changed.\n\nTest hints:\nNone","","OSDCOMMAIN-11524","9745593"]
[null,null,1096948,null,null,"","Bug","Reliability","Win32 Userinterface","Entering a value for a 'Yes/No' activity property is case sensitive","When using activity properties, entering a value for a Yes/No property does not always select Yes. \nThis has been fixed.\n\nTest hints:\n1. Set the 'Yes/No' activity property to 'Yes' when 'No' is the default value.","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-11527","9747255"]
[null,null,1096948,null,null,"","New Feature","Reliability","Service","It is not possible to log on with a user name longer than 50 characters","It is not possible to log on to the different applications with a user name longer than 50 characters.\nThis has been fixed.\nFor ORTEC WS client, ORTEC WS for Employees, ORTEC WS for Managers, ORTEC system Configuration, (ORTEC) ESS Mobile App, it is now possible to log on with a user name of 200 characters.\nFor Employee Self Service, Manager Self Service and Access Control websites it is now possible to log on with a user name of 100 characters.\n\nTest hints:\n1. Verify it is possible to log on to above mentioned applications and websites.","","OSDOWSD-806",""]
[null,null,1096948,null,null,"","New Feature","Reliability","Self scheduling","It is not possible to use pending updates with a user that has a user name longer than 50 characters","It is not possible to use pending updates with a user that has a user name longer than 50 characters\nThis has been fixed.\nFor ORTEC WS client, ORTEC WS for Employees, ORTEC WS for Managers, (ORTEC) ESS Mobile App, it is now possible to use pending updates on with a user name of 200 characters.\nFor Employee Self Service, Manager Self Service it is now possible use pending updates on with a user name of 100 characters.\n\nIt is not possible to use pending updates with a user that has a user name longer than 50 characters\nThis has been fixed.\nFor ORTEC WS client, ORTEC WS for Employees, ORTEC WS for Managers, (ORTEC) ESS Mobile App, it is now possible to use pending updates on with a user name of 200 characters.\nFor Employee Self Service, Manager Self Service it is now possible use pending updates on with a user name of 100 characters.\n\nTest hints:\n1. Verify it is possible to use pending updates in to above mentioned applications and websites. ","","OSDOWSD-808",""]
[null,null,1096948,null,null,"","New Feature","Technical","Service","Be able to import users with username of 200 characters","There was a maximum of 50 characters for a username when importing.\nThis has been changed.\nNow, a username with at most 200 characters is accepted.\n\nTesthints:\n1: Verify that an import with a username between 51 and 200 characters succeeds","","OSDOWSD-811",""]
[null,null,1096948,null,null,"","New Feature","Technical","Logging","Superfluous event viewer messages are added when a Backend API route is invoked","A message containing \"Required properties not provided for\" was logged in the event viewer of the web server when ORTEC WS for Employees invoked a route on the Backend API. This was caused by an incorrect configuration of the logging system in the Backend.\nThis has been fixed.\nNow, only the exceptions/errors on the Backend are logged in event viewer. \n\nTest hints:\nNone","","OSDOWSD-826",""]
[null,null,1096948,null,null,"","New Feature","Technical","Miscellaneous","Revert adjusted backend API install script for changing tables in ORTEC WS database","The project to add remarks in ESS self scheduling has been postponed. Some preparations have already been delivered through Issue OSDOWSD-753. This involved changing the deployment of the backend API to make it possible to add a new table to the OWS database to store self scheduling remarks. \nThese changes have been reverted.\n\nTest hints:\n1. Test that the backend API can be installed or updated.","","OSDOWSD-831",""]
[null,null,1098758,null,null,"","Bug","Reliability","Self scheduling","Using shift proposal criterion 'Balance of account category' in Employee Self Service can give an empty self scheduling plan board","Using shift proposal criterion 'Balance of account category' in Employee Self Service configured to be calculated from 'first day of the year' can give an empty self scheduling plan board. \nIn addition a event log message is visible showing 'TProposalParams.GetFirstShiftTime: no shifts...' message. \nWhen shifts were planned before starting self scheduling on a day no demand was configured this error can occur because the start of the year could not be determined. \nThis has been fixed. \nThe start of the year to be used in the shift proposal criterion 'Balance of account category' is now determined correctly; so the self scheduling planboard is displayed correctly. \n\nTest hints: \n1. use shift proposal criterion 'Balance of account category' and use self scheduling to plan/unplan shifts ","","OSDCOMMAIN-11517","9733989"]
[null,null,1098758,null,null,"","Bug","Reliability","Planboard","Workstation demand overnight is split into two parts, except on public holidays","Recurring and holiday demands are handled differently in the workstation plan board. Recurring demands are split at 0:00, on public holidays they are not. \nThis has been fixed.\nNow demands are not split at midnight.\n\nAdded feature toggle Server setting: FeatureToggles\\DoNotSplitOvernightWorkstationDemand and is by default disabled.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hints:\n1. Verify that recurring workstation demand overlapping with midnight are shown as a single block in the workstation plan board. ","","OSDCOMMAIN-11529",""]
[null,null,1098758,null,null,"","Bug","Reliability","Reporting","Report 'Overview shifts' groups shifts with different activity types together","Two issues are solved for the report 'Overview shifts'.\n\nShifts and employees are grouped together when the (realized) actual activity types are not the same. \nThis is fixed. \nThe shifts are grouped taking into account (realized) activity types. \n\nShifts that are the same except for activity names are grouped separately. This is confusing since the visible data on the report does not reflect this. \nThis has been improved.\nThe activity names are no longer considered for grouping. \n\nTest hints: \n1. Run the 'Overview shifts' report. ","","OSDCOMMAIN-11539",""]
[null,null,1098758,null,null,"","Bug","Reliability","Logging","Failed to write' error dialog is shown after successful export","After an export finishes that started from the win32 client an exception message 'Write Failed' might be shown.\nThe source/reason of this error can not be found in any logging we have right now. \nThis has been improved. The error is now logged to the server log.\n\nTest hints\n1. None","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-11542","9763169"]
[null,null,1098758,null,null,"","New Feature","Functionality","Service","New labor rule that checks the amount of on call periods","A new labor rule \"Number of on call periods\" has been added that checks if there are not too many on call periods in a certain time frame. To check this labor rule, a new definition is added: \"Definition on call period\".\n\nAdded global setting MaxNumberOfOnCallPeriodsReq which is turned off by default.\n\nTest hints:\n1. Enable the global setting and see that the new labor rule can be added to the labor rule set.","","OSDOWSD-696",""]
[null,null,1098758,null,null,"","New Feature","Functionality","Service","New labor rule that checks the Maximum Number of Special Periods","A new labor rule \"Maximum Number of special periods\" has been added that checks if there are not too many special periods in a certain time frame. Presence, on call and consignation periods are considered special periods. To check this labor rule, a new definition is added: \"Definition consignation period\".\n\nAdded global setting MaxNumberOfSpecialPeriodsReq which is turned off by default.\n\nTest hints:\n1. Enable the global setting and see that the new labor rule can be added to the labor rule set.","","OSDOWSD-697",""]
[null,null,1100007,null,null,"CLTS","Bug","Stability","Logging","CLTS stops working while service still running","Fixed an issue where CLTS would stop logging.\n\nTest hints:\nNone","","OSDCOMMAIN-11533","9749766"]
[null,null,1100007,null,null,"","Bug","Reliability","Win32 User Interface","Incorrect scroll-into-view movement of grids after mouse click in a workstation plan board","Incorrect scroll-into-view movement after mouse click in a workstation plan board.\nThis has been improved.\nThe synchronisation of the selected column in the shift and classification of workstations grid is no longer done when clicking on a cell in either grid.\nWhen using the arrow keys or selecting cells at the edges of the grids, synchronisation the grids is done to scroll those edge cells into view.\n\nTest hints:\n1. Verify the correct cell in the workstation plan board can be selected.\n2. Verify that clicking on a cell selects the correct cells in the adjoining grids","","OSDCOMMAIN-11541","9760596"]
[null,null,1102388,null,null,"","Bug","Reliability","Service","Message about violation in future is shown for shift in current schedule","In case 'future schedules' with status planning are checked for violations when making plan actions, a message would pop up in case a violation was made for an employee working in two departments in case the other department would not have a roster period yet. \nThis has been fixed.\n\nTest hints:\n1. Add a shift to an employee so a violation will occur in a future schedule. Verify that a popup comes up notifying you about this.","","OSDCOMMAIN-11544","9770172"]
[null,null,1102388,null,null,"","Bug","Performance","Service","Do not calculate bookings after approving an employee realization","When approving an employee realization, the approved until date of the employee was always set to the maximum date. This has been fixed. \nNote: the problem was caused by the functionality that recalculates saved bookings and violations when employee realizations are approved in an already Approved period. That functionality is unaffected.\n\nTest hints:\n1. Approve a pending employee realization. Verify that the approved until date of the employee has not changed.","","OSDCOMMAIN-11561","9797654"]
[null,null,1106135,null,null,"","Bug","","","Incorrect handling of time zone information when entering wishes via mobile app","A wish entered in the mobile app with a begintime of 00:00 was shown in the OWS Client with a begintime of 01:00, because time zone differences were not taken into account correctly. \nThis has been fixed. \n\nTest hints:\n1. Verify that entering a wish in the mobile app is shown with the correct begin time in the OWS Client","","OSDCOMMAIN-11167","9377234"]
[null,null,1106135,null,null,"","Bug","Configuration","Self scheduling","Scheduling rounds are department specific and cannot be used by other departments","Scheduling rounds can only be used by one leaf department. This means that scheduling rounds must be created for every single department that wants to use Self scheduling functionality, while the scheduling rounds itself are not department specific.\nThis has been changed.\nNow, scheduling rounds could also be created for non-leaf departments. This means that scheduling rounds defined at a parent department can be assigned to all the scheduling periods of its leaf departments.\n\nTest hints:\n1. Verify that existing scheduling rounds are still assigned to scheduling periods in its own department.\n2. Verify that a scheduling round can be created for a non-leaf department and assigned to scheduling periods of its leaf departments.","","OSDCOMMAIN-11577",""]
[null,null,1106135,null,null,"","New Feature","Functionality","Service","ESS: A user can pick shifts from a non-proposal department","In Employee Self Service, a user can see and pick shifts from other departments that are not proposal departments.\nThis has been fixed.\nNow, a user can only pick shifts from his own department or shifts from proposal departments.\nThis is consistent with the 'Candidates for shift' functionality in the OWS Client.\n\nTest hints:\n1. Verify that a user can only see/pick shifts that are from own department or from a proposal department.","This issue changes the way proposal departments are handled in shift picking. Please read the release notes carefully to see how it should be setup.","OSDOWSD-908",""]
[null,null,1110714,null,null,null,"Bug","","","Reports were not visible in ORTEC WS for Employees in English language","The reports were not visible in ORTEC WS for Employees when they were uploaded using en-US language in System Configuration (CSCS)\nThis has been fixed.\n\nTest hint:\n1. Verify the report in the Insights page","","OOBA-398",""]
[null,null,1110714,null,null,null,"Bug","","","Unloading of shift pending updates caused locking and interface failures","Unloading shift pending updates while they are exported caused locking problems.\nThis has been fixed.\nNow the shift pending updates are not unloaded when they are also exported.\n\nTest hints:\n1. Approve an employee realization.","","OSDCOMMAIN-11551","9773759"]
[null,null,1110714,null,null,null,"Bug","Performance","Service","Error occurred when multiple CWSS server processes are started","When starting multiple processes at the same time caused some of these processes to stop on an error. This is because the CWSS processes loads many shifts with activities. This caused the performance of the database server to decrease, which resulted in an error. \nThis has been improved. \nLoading of the activities of shifts has been changed to avoid this error.\n\nAdded Feature Toggle: \nFEATURETOGGLES\\DONOTSORTACTIVITIESWHENLOADING, possible values 'Y', 'N', 'True', 'False'. Default value set to Y. \n\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department. \n\nTest hints: \n1. Verify CWSS processes start successfully \n2. Verify for any shift with a realization in OWS win32 client that it contains the desired activities","","OSDCOMMAIN-11557","9778641"]
[null,null,1110714,null,null,null,"Bug","Functionality","Optimization","The shift sequence planner does complete parts that started before the planner period","The shift sequence planner does not use assigned shifts on days before the planning interval to complete shift sequences.\nThis has been fixed. Now, the shift sequence planner can use the assigned shifts before the planning interval to complete shift sequences. \n\nTest hints:\n1. Run the shift sequence planner and verify that shifts are assigned to employees.","","OSDCOMMAIN-11572","9811492"]
[null,null,1110714,null,null,null,"Bug","","","Increase in memory as loading of account category lines happened always when changing the status of scheduling period","Account category lines were always loaded when changing the status of a scheduling period to status Closed or from status Closed to Published.Loading these lines could cause an unnecessary memory increase.\nThis has been improved.\nLoading is now only done, when there are compensation rules for which the lines are saved (the option 'Save entries' is checked).  \n\nTest hints:\n1) Verify that no errors are raised when changing the status of a scheduling period to Closed","","OSDCOMMAIN-11598","9822900"]
[null,null,1110714,null,null,null,"Bug","Stability","Import / Export","Repeating a duty import caused an error","Importing a duty with demand was not working correctly if a similar duty with demand already existed.\nThis has been fixed.\n\nTest hints: repeatedly import duties with demand","","OSDCOMMAIN-11608","9834577"]
[null,null,1110714,null,null,null,"Bug","Reliability","Service","The laborrule \"Maximum labor-time based on account balance\" could gave incorrect violations in special cases","When an employee was linked to a department halfway through its department period, the rule \"Maximum labor-time based on account balance\" did not work correctly in special cases when it checked per department period. \nThis has been fixed.\n\nTest hints:\n1. Link an employee to a department halfway its department period. Verify that the rule \"Maximum labor-time based on account balance\" works as expected.","","OSDCOMMAIN-11613","9837659"]
[null,null,1110714,null,null,null,"Bug","Reliability","Service","Approved leave requests could not be changed back to 'Open'  status \n","Approved leave requests cannot be changed back to 'Open' status.This happened when the original shift corresponding to the leave shift had some realisations in the scenario that cannot be deleted.\nThis has been fixed.\nNow replacing the leave shifts only considers shifts from the master schedule and not from the scenario.\n\nTest hints:\nNone","","OSDCOMMAIN-11631","9867285"]
[null,null,1110714,null,null,null,"New Feature","Functionality","Interfaces","Create queue interface that triggers when shifts are opened for bidding","Preparation change for showing notifications in the app when a shift is opened for bidding.\nNote: please only turn on the 'Shift open for bidding queue' when the app side has been delivered (expected October 2018).\n\nTest hints:\n1. None","","OSDOWSD-843",""]
[null,null,1110714,null,null,null,"New Feature","Functionality","Service","Added functionality to determine which employees gets the notifications about the shifts that are open for picking","A new command handler 'CGetEmployeesThatCanBidOnShift' is added. This command handler returns information about which employees gets notification about the shifts that are open for bidding. This change is a preparation change that is required to be able to send notifications to the ESS Mobile app when shifts are opened for bidding. \nNote: this notification functionality is not available yet in ESS MobileApp.\n\nTest hints:\nNone ","","OSDOWSD-845",""]
[null,null,1110714,null,null,null,"New Feature","Functionality","Service","New queue filter to filter shifts based on 'Opened for bidding' flag","A new filter type was added that can be used in queues. To use it, add the tag <ShiftOpenedForBiddingQueueFilter/> to your filters.\nThis filter will make sure the queue only triggers an export in case the flag 'Open for bidding' is turned on for a shift. It will not trigger in any other case.\nNote: this filter does not require a shift queue so UseShiftQueue can be false.\n\nTest hints:\n1. Use filter in queue definition and verify that exports are only written in case the shift is set 'Open for bidding'.","","OSDOWSD-892",""]
[null,null,1110714,null,null,null,"New Feature","Functionality","Service","New queue filter to filter shift based on their begin time","A new filter type has been added that can be used in queues. To use it, add the tag <ShiftOpenedForBiddingQueueFilter> to your filters. \nThis filter will make sure the queue only triggers an export in case the begin time is in the interval defined by the parameters (in days). \nNote: this filter does not require a shift queue so UseShiftQueue can be false. \n\nExample: <ShiftBeginTimeQueueFilter relativebegintime=\"-1\" relativeendtime=\"14\" includetime=\"Y\">\n\nTest hints: \n 1. Use filter in queue definition and verify that exports are only written in case the changed shifts start in the interval Now + RelativeBeginTime - Now + RelativeEndTime","","OSDOWSD-893",""]
[null,null,1110714,null,null,null,"New Feature","Functionality","Tools","Make deploying ESS_App_Definitions a manual update for OWS 7","The interface definitions that are used to create notifications for the ESS Mobile app should now be updated manually. The consultant should specify location of files and which notifications to send.\n\nTest hints:\nNone","","OSDOWSD-904",""]
[null,null,1110714,null,null,null,"New Feature","Functionality","Service","ESS: A user can pick shifts from a non-proposal department","In Employee Self Service, a user can see and pick shifts from other departments that are not proposal departments.\nThis has been fixed.\nNow, a user can only pick shifts from his own department or shifts from proposal departments.\nThis is consistent with the 'Candidates for shift' functionality in the OWS Client.\n\nTest hints:\n1. Verify that a user can only see/pick shifts that are from own department or from a proposal department.","This issue changes the way proposal departments are handled in shift picking. Please read the release notes carefully to see how it should be setup.","OSDOWSD-908",""]
[null,null,1110714,null,null,null,"New Feature","Configuration","Import/Export","Update ESS_App_XMLDefinitions to use one export path for shift bidding and exchange requests","The default export paths of both configurations in ESSAppNotifications are changed to one path to D:\\OrtecData\\OWSMobileAppNotifications. \n\nTest hints: verify that notifications on swap request are still received on mobile devices.","When configuring at the customer, both these exports should write to the same folder. Do not change the configured filename, as based on the filename the app server knows which notification to send.","OSDOWSD-931",""]
[null,null,1112251,null,null,null,"Bug","Functionality","Employee self-service","Shift exchange was not created when a shift was picked","Picking a shift in ESS did not result in a shift exchange.\nThis has been fixed.\n\nTest hints:\n1. Pick a shift in ESS and check in OWS Client that a shift exchange of type 'Requested' appears in the 'Shift assignment overview' of the shift.","","OSDCOMMAIN-11582","9815359"]
[null,null,1112251,null,null,null,"Bug","Reliability","Service","The employees' availability for the central department was not updated correctly","When updating the availability period of an employee for a decentral department, the availability for the central department is updated as well. This caused an error if the updated period fell outside the valid period of the central department.\nThis has been fixed.\nNow updating the availability period for the decentral department does not cause an error for this case.\n\nTest hints:\n1. Update the availability period of an employee for an employee in a decentral department.","","OSDCOMMAIN-11602","9831042"]
[null,null,1112251,null,null,null,"Bug","Reliability","DataWarehouse","Update Default BI CONFIG template to handle special characters in password","The declaration of connection strings in the default BI config template have been updated: the double quotes are replaced with the singe ones. This allows to use special characters in these strings without any errors.\n\nTest hints in case of usage of BI Config :\nRun an Incremental load on an environment that has BI configured already.\n\nTest hints otherwise: \nNone.","","OSDCOMMAIN-11632","9868441"]
[null,null,1112251,null,null,null,"New Feature","Functionality","Utilities","Make CSCS plugins elevated permissions aware","In Ortec System Configuration (CSCS), mark additional plugins that need elevated permissions. If CSCS is started without elevated permissions, these plugins will show an indication to the user that elevated permissions are required.\nThe following plugins are marked:\n- CRBS Publisher Test\n- CRBS Subscriber Test\n- Custom Actions Manager (Web)\n- CMHS Network Editor\n- Export configuration\n- CRBS Designer\n- Configure logging and tracking service","","OSDORDODPT-630",""]
[null,null,1112251,null,null,null,"New Feature","Functionality","Utilities","CSCS should report if started with administrator rights not the other way around","When starting Ortec System Configuration (CSCS) as administrator, the text '(Administrator)' is added to the caption of the application. Otherwise, no text is added.","","OSDORDODPT-631",""]
[null,null,1114373,null,null,"","New Feature","Stability","Service","Add logging to detect array parameters for web api actions that have a length that can cause issues when proxys or loadbalancer have restrictions on lengths in the URI's","Some network devices, like firewalls, cannot handle long URL's very well. Such long URL's should not exist in our back end, but if they do we log them.\n\nTest hints:\nNone","Added setting 'maxNumberOfActionsArgumentsInUrl' in Web.Config.Template. This number indicates how many elements can be in an single parameter before we log it","OOBA-347",""]
[null,null,1114373,null,null,"","New Feature","Security","Security","Exceptions occurring in backend api when getting the user name showed too much information","When showing the user name in ORTEC WS For Employees / Managers, the stack trace would be shown in case an error occurred.\nThis has been fixed.\nThe stack trace from the backend API is not shown anymore to the user.\n\nTest hints:\n1. Verify that the user name is visible in ORTEC WS for Employees / Managers.",null,"OOBA-362",""]
[null,null,1114373,null,null,"","Bug","Reliability","Reporting","Reports were not visible in ORTEC WS for Employees in English language","The reports were not visible in ORTEC WS for Employees when they were uploaded using en-US language in System Configuration (CSCS)\nThis has been fixed.\n\nTest hint:\n1. Verify the report in the Insights page","","OOBA-398",""]
[null,null,1114373,null,null,"","Bug","Reliability","Service","Compensation rule 'Travel distance' creates duplicate bookings when exporting for employees with multiple contracts","Travel distances rule created bookings on each contract of an employee. This resulted in creating double bookings for an employee having 2 contracts. \nThis has been fixed. \n\nTest hints:\n1. Verify the travel distance bookings for employees with one and for employees with multiple contracts","","OSDCOMMAIN-11652",""]
[null,null,1116175,null,null,"","New Feature","Functionality","Security","Added support for outgoing proxy server when ORTEC WS is configured as Resource Server for OIDC authentication","When ORTEC WS has been configured as Resource Server for OIDC authentication it not possible to use an outgoing proxy server to reach the URL of the OIDC provider for verifying the user's identity, for granting access to users and to clients and for creating tokens.\nThis has been improved.\nIn ORTEC System Configuration - Settings Management - CUASFW\\OIDC a proxy server settings page is available to configure and enable/disable a proxy server.\nIf enabled the configured outgoing proxy server is used to contact the OIDC provider for verifying the user's identity, for granting access to users and to clients and for creating tokens.\n\nIf changes are applied to this proxy server configuration, processes that rely on the OIDC provider for token validation should be restarted.\n\nNOTE: ORTEC WS depends on the ORTEC License Server and this server should not be blocked by the configured proxy server.  \n\nTest hints\n1. Verify ORTEC System Configuration can be started.\n2. Verify user can logon to ORTEC Workforce Scheduling for Employees when ORTEC WS has been configured as Resource Server for OIDC","","OOBA-403",""]
[null,null,1116175,null,null,"","Bug","Reliability","Reporting","When selecting a period in some reports in ORTEC Workforce Scheduling for Employees a warning about a too large selected period is not being translated","When selecting a period in some reports in ORTEC Workforce Scheduling for Employees a warning about a too large selected period is not being translated.\nThis has been fixed for the following reports:\nMaster schedule ESS\nPersonal schedule\nSelfscheduling ESS","","OSDCOMMAIN-11650","9898598"]
[null,null,1116175,null,null,"","Bug","","Database","Added detect corrupt duties script to DBUpdate","Previously new checks were added to detect corrupt data during the starting of the server. These could prevent the server from starting when the data in the database is corrupt. \nThis has been improved.\nWe added detection scripts to DBUpdate to find this data.\n\nTesthints:\nNone","","OSDCOMMAIN-11656","9901511"]
[null,null,1116175,null,null,"","Bug","Reliability","Service","Inconsistent duties or activities can cause server halts","CWSS server halted if there were inconsistent duties and activities.\nThis has been fixed.\nNow the server gets started but the information about the inconsistent data is logged for further analysis.\nTest hints\n1. Start up the CWSS Server process and verify that a user can log into OWS Client","","OSDCOMMAIN-11677",""]
[null,null,1116175,null,null,"","Bug","Reliability","Service","Added new Finnish and German translations","Several translations have been added for German and Finnish for recent functional changes. \n\nTest hints: \nNone","","OSDCOMMAIN-11681",""]
[null,null,1118159,null,null,null,"Bug",null,null,"A required availability entered via 'Employee Self Service' was not interpreted as required","The properties 'Weight' and 'Required' of the request '(No) work during a period' created in 'Employee Self Service' were not copied as in the template requests.\nThis has been fixed.\n\nTest hints: \n1. Create a template work request '(No) work during a period' in OWS Client\n2. Check the option 'Required'\n3. Log in ESS and enter the availability on a day for an employee\n4. Open OWS Client and verify that the request created on that day has the 'Required' option selected",null,"OSDCOMMAIN-11666",9911074]
[null,null,1118159,null,null,null,"Bug","Reliability","Planning","An error was shown when determining candidates for shift when Use proposal departments option is enabled","An error was shown when determining candidates for shift when Use proposal departments option is enabled.\nWhen ordering the active shift proposal criteria to determine the candidates for shift the read permission on the criteria in the criteria set was not taken into account correctly.\nThis could show an error like 'Could not convert variant of type (Unicode string) into type (Double)'\nThis has been fixed for the following shift proposal criteria:\n- Duty property\n- Employee property\n- Balance of account category\n\nTest hints:\n1. Verify that the options in a candidates for shift proposal are ordered as expected, while using the following criteria:\n a. Duty property\n b. Employee property\n c. Balance of account category",null,"OSDCOMMAIN-11684",9926159]
[null,null,1118159,null,null,null,"Bug","Stability","Tools","Removing a CMHS network without selecting a component resulted in an error message","In ORTEC System Configuration, an access violation could occur when removing a CMHS network. This would only happen if no component was selected. \nThis has been fixed. \n\nTest hints:\n1. Open the network editor in ORTEC System Configuration. Download the configuration and remove a network. Verify that no error message is shown.",null,"OSDCOMMAIN-11696"]
[null,null,1118159,null,null,null,"New Feature","Functionality","Optimization","Extended criterion 'Remaining work times' with options to only consider positive or negative deviations","The scheduling criterion 'Remaining work times' used to give a penalty if the employee worked less than his contract, but also if the employee worked more than his contract.\nThis has been improved.\nIn the criterion can be configured when the penalty should be given (in case of positive deviation, negative deviation or in both cases).\n\nTest hints:\n1. Verify that for an existing criterion the new options 'Avoid too much working time' and 'Avoid too little working time' are checked.\n2. Verify that the automatic planner takes the criterion into account.",null,"OSDOWSD-627"]
[null,null,1119861,null,null,"","Bug","Reliability","Planboard","Sometimes an error was shown in a plan board when the penalty was calculated for the scheduling criteria \"Shift length series (crit)\"","An error was shown sometimes when opening a plan board. This could happen when the employee calculation \"Planning penalty of employee\" calculated the penalty for the criteria \"Shift length series (crit)\" and when there was a shift series of more than 9 days long and when the series was on different scheduling periods.\nThis has been fixed.\n\nTest hints: \n1. Verify that the employee calculation \"Planning penalty for employee\" shows values without any errors when opening a plan board. ","","OSDCOMMAIN-11694",""]
[null,null,1119861,null,null,"","Bug","Reliability","Employee self-service","ESS: Button 'Confirm' was not available in shift update window while user was allowed to create an employee realization","In Employee Self Service (ESS) the 'Confirm' button in shift update window was not active in case the user has the permission to update a shift and has not the permission to 'Confirm' (permission \"gui.ess.realizeshift.submit\"). However, the permission \"gui.ess.realizeshift.submit\" should not be taken into account when the user wants to confirm his shift update.\nThis has been fixed.\nThe user can now confirm a shift update without the permission \"gui.ess.realizeshift.submit\" and global setting 'UseApproveRealisations' is turned on.\n\nTest hints: \nPreconditions: global setting UseApproveRealisations is turned on and the permission \"gui.ess.realizeshift.submit\" is revoked.\n1. Verify that the button \"Confirm\" in the shift update window becomes active after changing a value.","","OSDCOMMAIN-11697","9950305"]
[null,null,1119861,null,null,"","Bug","Technical","Reporting","OWS System report \"Attendance List per Department\" was not aligned with ORTEC Branding","Improved the look and feel of the report \"Attendance List per Department\". The 'header' table appears only on the first page now. This will allow the report to show more data.\n\nTest hints: \n- Verify that report \"Attendance List per Department\" can be opened and display data.","","OSDCOMMAIN-11716","9957693"]
[null,null,1119861,null,null,"","Bug","Technical","Reporting","OWS System report \"Master schedule ESS\" was not aligned with ORTEC Branding","Improved the look and feel of the report \"Master schedule ESS\". The 'header' table appears only on the first page now. This will allow the report to show more data.\n\nTest hints: \n- Verify in Employee Self Service (ESS) that report \"Master schedule ESS\" can be opened and display data.","","OSDCOMMAIN-11719","9958513"]
[null,null,1119861,null,null,"","Bug","Technical","Reporting","OWS System report \"Violations\" was not aligned with ORTEC Branding","Improved the look and feel of the report \"Violations\". The 'header' table appears only on the first page now. This will allow the report to show more data.\n\nTest hints: \n- Verify in Employee Self Service (ESS) that report \"Violations\" can be opened and display data.","","OSDCOMMAIN-11720","9958515"]
[null,null,1119861,null,null,"","Bug","Technical","Reporting","OWS System report \"Master schedule\" was not aligned with ORTEC Branding\n ","Improved the look and feel of the report \"Master schedule\". The 'header' table appears only on the first page now. This will allow the report to show more data.\n\nTest hints: \n- Verify in Employee Self Service (ESS) that report \"Master schedule\" can be opened and display data.","","OSDCOMMAIN-11721","9958521"]
[null,null,1119861,null,null,"","Bug","Technical","Reporting","OWS System report \"Workstation planning\" was not aligned with ORTEC Branding","Improved the look and feel of the report \"Workstation planning\". The 'header' table appears only on the first page now. This will allow the report to show more data.\n\nTest hints: \n- Verify in Employee Self Service (ESS) that report \"Workstation planning\" can be opened and display data.","","OSDCOMMAIN-11722","9958523"]
[null,null,1119861,null,null,"CMHS","Bug","Reliability","Core Framework","CSV2XMLProcess columheader parameter only accepts , separator","Fixed bug as when using ColumnHeaders parameter in the CSV2XML CMHS plugin, the separator used in there should be the same as the separator of the data ","","OSDGF-905",""]
[null,null,1119861,null,null,"","New Feature","Functionality","Service","New labor rule that checks the rest after a series of night labor periods","A new labor rule 'Rest after night shift series (labor period)' has been added which checks whether there is enough rest after a night shift series.\n\nAdded global setting RestAfterNightShiftSeriesLaborPeriodReq which is turned off by default. \n\nTest hints: \n1. Enable the global setting and verify that the labor rule 'Rest after night shift series (labor period)' can be added to a Labor-time set. ","","OSDOWSD-709",""]
[null,null,1119861,null,null,"","New Feature","Functionality","Service","New labor rule that checks the length of series of labor periods","A new labor rule \"Shift series (labor period)\" has been added. This labor rule checks that there is a maximum number of shifts in a series.\n\nAdded global setting ShiftSeriesLaborPeriodReq which is turned off by default. \n\nTest hints: \n1. Enable the global setting and verify that the labor rule \"Shift series (labor period)\" can be added to a Labor-time set.","","OSDOWSD-733",""]
[null,null,1122459,null,null,"","Bug","Stability","Tools","BI run could fail in case of large values for address data, e.g. a large street name","The column size for address data in the BI database was smaller than the column size of the OWS database.\nIn case the values in one of the columns STREET, CITY, STATE, or COUNTRY was too large then the conversion to the BI database failed.\nThis has been fixed.\nNow the column sizes in the BI database match the sizes in OWS database.\n\nTest hints:\n1. Verify that a BI conversion can be done successfully","","OSDCOMMAIN-11736","9968599"]
[null,null,1122459,null,null,"","Bug","Reliability","Reporting","Report 'Master schedule' did not take global setting UseLastAssignedGroupLabelAsCurrentForSorting into account","The reports 'Master schedule' and 'Master schedule ESS' did not sort employees correctly in case they were sorted on Grouplabel and global setting 'UseLastAssignedGroupLabelAsCurrentForSorting' was on.\nThis has been fixed.\nNow the report shows the employees in the same order as the master schedule plan board.\n\nTest hints:\n1. Verify in the report  'Master schedule' or 'Master schedule ESS' that employees are shown in the correct order when sorted employees on Grouplabel.","","OSDCOMMAIN-11737","9968611"]
[null,null,1122459,null,null,"","Bug","Reliability","Calculation","No warning message is logged when the expressions using dates on running accounts resulted in a value less than or equal to zero","A warning is logged in the event viewer and server log when the begin date and/or end date of the calculation period used in the expression evaluates to a value <= 0, and that causes the calculation interval being used for the calculation which might be unexpected.\nThis is done for the following expressions:\nTOTALAMOUNT\nTOTALRELATIVEAMOUNT\nILLNESSPERCENTAGE\nDATEOFLASTBOOKING\nVALUE\nVALUEFORSHIFTSBETWEEN\n\nTest hints:\nNone.","","OSDCOMMAIN-11739",""]
[null,null,1123989,null,null,"","Bug","Reliability","Planboard","In Workstation planning board the grids were not well aligned when selecting a cell","Incorrect scroll-into-view movement after mouse click in a workstation plan board.\nThis has been improved.\nThe planning grid and 'Classification of workstations' grid are now synchronized by the time column when using left mouse click on a cell in either grid.\n\nTest hints:\n1. Verify the correct cell in the workstation plan board can be selected.\n2. Verify that clicking on a cell selects the correct cells in the adjoining grids","For this solution to become available the win32 client must be installed.","OSDCOMMAIN-11733","9964066"]
[null,null,1123989,null,null,"","Bug","Stability","Optimization","The automatic planner did sometimes crash with InvalidPointer error","The automatic planner did sometimes crash when it ran for a long time (more than 1 hour).\nThis has been fixed.\n\nTest hints:\n1. Verify that the automatic planner can run without errors.","","OSDCOMMAIN-11753",""]
[null,null,1123989,null,null,"","Bug","Reliability","Planboard","Saved planboard vacant shift filters were not taken into account after reopening a planboard.","Upon opening a scheduling period, the saved vacant shifts filter was not applied. \nThis has been fixed.\n\nTest hints:\n1. Verify that stored vacant shifts filter is taken into account after planboard is opened.","For this solution to become available the win32 client must be installed.","OSDCOMMAIN-11760","9979042"]
[null,null,1123989,null,null,"","Bug","Reliability","Service","Address columns of BI (Physical) Location table had smaller size than the columns in OWS table","After the previous update, there was another table (DIM_LOCATION) for which the column size for address data in the BI database was smaller than the column size of the OWS database.\nIn case the values in one of the columns STREET, CITY, STATE, or COUNTRY was too large then the conversion to the BI database failed.\nThis has been fixed.\nNow the column sizes of the location table in the BI database match the sizes in the OWS database.\n\nTest hints:\n1. Verify that a BI conversion can be done successfully.","","OSDCOMMAIN-11761",""]
[null,null,1123989,null,null,"","New Feature","Functionality","Service","Added new labor rule 'Maximum non-presence time in presence shift (labor period)'","A new labor rule 'Maximum non-presence time in presence shift (labor period)' has been added. This labor rule checks if there is not too much non-presence time in presence period.\n\nAdded global setting NonPresenceTimeInPresenceShiftLaborPeriodReq which is turned off by default. \n\nTest hints: \n1. Enable the global setting and verify that the labor rule  'Maximum non-presence time in presence shift (labor period)' can be added to a Labor-time set. ","","OSDOWSD-939",""]
[null,null,1123989,null,null,"","New Feature","Functionality","Service","Added new labor rule 'Duration of Work (stand by) activities (on call period)'","A new labor rule 'Duration of work(stand by) activities (on call period)' has been added. This labor rule checks if there is not too much work(standby) time in an on call period. \n\nAdded global setting DurationWorkStandByInOnCallPeriodReq which is turned off by default. \n\nTest hints: \n1. Enable the global setting and verify that the labor rule 'Maximum non-presence time in presence shift (labor period)' can be added to a Labor-time set. ","","OSDOWSD-940",""]
[null,null,1123989,null,null,"","Bug","Technical","Utilities","Removed unnecessary checks for inconsistent activities in DBUpdateWizard","Previously a script for detecting corrupt data was added to DBUpdate. Upon detecting corrupt data the DBUpdate process stopped and showed what was incorrect. \nThe idea was that a consultant could repair this 'corrupt' data. However, the CWSS Server process can handle this 'corrupt' data correctly. Which means there is no need to stop the DBUpdate process for this specific situation. \nTherefore, these check scripts are removed. \nIn the case this kind of corrupt data occur it will be detected by System monitoring. \n\nTest hints: \nNone","","OSDOWSD-983",""]
[null,null,1126448,null,null,"","Bug","Reliability","Service","Rule 'Availability for a shift' did not check subcontracted shifts","Planning a subcontracted shift to an employee which was not available for the department didn't show a violation.\nThis has been fixed.\n\nTest hints:\n1. Verify that the rule 'Availability for a shift' shows a violation in the planboard when the rule is violated.","","OSDCOMMAIN-11740",""]
[null,null,1126448,null,null,"","Bug","Reliability","Service","Candidates for shift did not check if violations are created in future schedules","Candidates for shift did not check if violations are created in future schedules. The violation becomes visible when the shift is planned.\nThis has been fixed.\nWhen retrieving candidates for a shift, violations that will occur in future schedules are taken into account and this is made visible in the Candidates for shift window.\n\nTest hints:\n1. Verify that candidates for a shift take future violations into account.","","OSDCOMMAIN-11742",""]
[null,null,1126448,null,null,"","Bug","Reliability","Service","Approving a leave request in the middle of non working time could lead to inconsistent data","Approving a leave request that starts or ends during an activity that does not count as work could lead to inconsistent data. \nThis has been fixed.\n\nTest hints:\n1. Approve a leave request halfway a break. Verify that the start and end times of the activities equal the start and end time of the shift.","","OSDCOMMAIN-11778",""]
[null,null,1126448,null,null,"","Bug","Reliability","Win32 Userinterface","Shift counters did not get filtered when filtered on skills","The skill filter only filtered vacant shifts, and not the shift counters grid.\nThis has been improved.\nNow, the shift counters grid is also filtered when using the skill filter and the option 'Filter shift counters'.\n\nTest hints:\n1. Use skill filter to filter vacant shifts and verify the shift counters are also filtered when 'Filter shift counters' is checked","","OSDCOMMAIN-11780",""]
[null,null,1126448,null,null,"","Bug","Stability","Service","BI run did fail in case of demanded duties overlapping the end date of the conversion period","A BI run could fail in case duty demands for a night duty with activities starting on the next day exist in the BI database and the conversion period is extended.\nThis has been fixed.\nNow, the activities of night duty demands can be loaded even if they are after the end date of the conversion period.\n\nTest hints\n1. Verify that BI conversion succeeds without errors.","","OSDCOMMAIN-11789","9996959"]
[null,null,1128462,null,null,"Labor rules","New Feature","Functionality","Service","Break rules: Pause activities were not ignored at the begin or the end of a block of shifts","According to the law, a break in a shift should be in between the labor of the shift. A break activity at the begin or end of the shift is not between the labor but was still considered as a break by the 'Break rules' labor rule.\nThis has been fixed.\n\nTest hints:\nPrecondition: the 'Break rules' labor rule is using the default values for the parameters\n1. Add an 8 hour labor shift, starting with a 45 minutes break activity. Verify this shift gets a violation.","","OSDOWSD-726",""]
[null,null,1131028,null,null,"","Bug","Reliability","Win32 User Interface","Recalculation of bookings is not done when changing the contract hours","When changing the properties of an existing employment conditions line that overlapped with the period for which bookings and violations are saved, no recalculation was done. \nThis has been fixed.\n\nTest hints:\n1. Change the properties of an existing line; verify the changes have been applied correctly\n2. Also verify if the recalculation is done when necassary","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-11818","10038632"]
[null,null,1131028,null,null,"","Bug","Performance","Self scheduling","Improved the performance of approving the first scheduling period of a central department","When approving the first scheduling period of a central department, shifts were loaded more than needed.\nThis has been improved.\nNow only the relevant shifts are loaded.\n\nTest hints:\n1. Verify that the status of scheduling periods of Central departments can be changed.","","OSDCOMMAIN-11819","10038776"]
[null,null,1131028,null,null,"Clocking","Bug","Technical","Win32 Userinterface","Changed default cumulative period for a new calculation used in the clock times window from year to week","When selecting categories which will be shown in the clock times window, the default cumulative period is changed from Year to Week. For customers not using the cumulative calculations, this minimizes the performance and memory impact of using this functionality.\n\nTest hints:\n1. Open the window via Overview -> Clock times -> Select categories and verify that the Cumulative period settings are still correct","For customers using calculations in the clock times window we advise to check the cumulative period that is currently configured. ","OSDCOMMAIN-11825","10039860"]
[null,null,1131028,null,null,"","Bug","Performance","Calculation","Account category calculation in Clock times window is improved","When configuring or refreshing calculations in the Clock times window all categories from a running account were calculated. This might influence the performance significantly depending on the configuration of the accounts.\nThis has been improved.\nNow, only the selected categories are calculated.\n\nTest hints:\n1. Verify in Clock times window that the values are shown correctly. ","","OSDCOMMAIN-11826","10039876"]
[null,null,1131028,null,null,"Automatic planner","Bug","Performance","Optimization","Performance improvement for optimizer 'Generate master schedule' when using tight availability constraints","The optimizer 'Generate master schedule' has several phases. In the phase 'local optimization' the schedule is improved by either moving 1 shift or swapping 2 shifts. In situations where there are tight availability constraints (for instance by requiring that a shift should overlap with the times according to the cyclical schedule), moving 1 shift will most probably not help. However, in a customer environment that also had both tight availability constraints and too many shifts for the available employees, we saw that most calculation time was spent trying those moves. We made it possible to force the optimizer to spend more time trying to swap shifts and less time trying to move shifts. In the tested case for this customer, this caused the optimizer to find its goal more than 10 times faster.\n\nAdded server setting 'PLANNER\\SHIFTPLANNER\\SWITCHTOONEOPTAFTERSUCCESSFULTWOOPTMOVE' with default value Y to keep the old behaviour.\nNOTE: Be careful with this setting. In other configurations, it might make the optimization slower.\n\nTest hints:\nNone","","OSDOWSD-1013",""]
[null,null,1131028,null,null,"","New Feature","Functionality","Service","Split the existing rule 'Duration of a shift(labor period)' to separate the night shifts functionality","The labor rule 'Duration of a shift (labor period)' has been split into: \n- Duration of a shift (labor period) \n- Duration of a night shift (labor period) \nThis has been done to be able to extend the functionality of the night part of the rule in a future change. \n\nBecause of this change, extra violations will be shown for long night shifts. \n\nAdded global setting MaxDurationLaborPeriodNightReq which is turned on by default in case global setting MaxDurationLaborPeriodReq is turned on. \n\nTest hints: \n1. Verify in Labor-time set for every 'Duration of a shift (labor period)' labor rule, now a 'Duration of a night shift (labor period)' rule also exists. \n2. Verify in a plan board that the rules can show a violation. \nNote: A longer night shift could be violated by both rules.","","OSDOWSD-716",""]
[null,null,1131028,null,null,"","New Feature","Functionality","Service","Added an option to the labor rule 'Duration of a night shift (labor period)' to allow longer shifts","The labor rule 'Duration of a night shift (labor period)' has been extended with the option to allow a longer night shift a number of times within a configured period, to comply with the labor times regulation.\n\nTest hints:\n- Enable the new exception. Schedule night shifts longer than allowed by the 'normal' duration but shorter than the duration allowed by exception. Verify that when you schedule more than allowed of these shifts, they get a violation.","","OSDOWSD-719",""]
[null,null,1132438,null,null,"CCDS","Bug","Stability","Core Framework","Reenable timeout on createClientSession","Timeout on create session decreased to 15 seconds.","","OSDCOMMAIN-11618",""]
[null,null,1132438,null,null,"","Bug","Reliability","Planboard","A stored violation in a calendar could cause CWSSServer process to halt","When for a department all schedules are approved and in the past, then violations in the calendar could be stored in the database. When adding an additional schedule for this department the stored violations will still be associated to the calendar. When doing a restart of the CWSSServer process this caused the error 'Violation not in interval of schedule' that halted the server.\nThis has been fixed.\nThe error is logged but does not halt the server.\n\nTest hints:\nNone","","OSDCOMMAIN-11833",""]
[null,null,1132438,null,null,"","Bug","Performance","Service","Using \"Text shifts\" displayer \"Non default duty properties of type yes/no\" causes performance issues","The performance of the displayer \"Non default duty properties of type yes/no\" has been improved.\n\nTest hints:\n1. Verify the displayer is showing only the abbreviation of Boolean user properties for which the shift has a non default value","","OSDCOMMAIN-11845","10052661"]
[null,null,1132438,null,null,"","Bug","Functionality","Service","Added French translations for labor rules","Several translations have been added for French for recent functional changes. \n\nTest hints:\nNone","","OSDCOMMAIN-11849",""]
[null,null,1132438,null,null,"","New Feature","Functionality","Optimization","Added option to call Shift Generation module from OWS interface","It has been made possible to call the ORTEC Shift Generation cloud service from an OWS environment. For this, a new proces type 'ShiftGeneration' has been added that can be configured in CSCS. By default it is disabled to save resources when not used. \nOnce active, two new handlers /shiftGeneration/CSendShiftGenerationRequest and /shiftGeneration/CGetRequestStatusses become available. The first handler transfers a call to the Shift Generation cloud service. As it might contain considerable time to do the calculations (depending on the input), this handler only starts the Shift Generation optimizer and exits immediately. One can use the second handler to view the status of all shift generation calls.","","OSDOWSD-1015",""]
[null,null,1132438,null,null,"","New Feature","Stability","Import / Export","Added information about department when a department import fails","When importing a non-adjacent scheduling period, the import failed and an error message was included into the interface log. However, it was not clear for which department the import failed.\nThis has been improved.\nNow, the department name and department code are added to the error message.\n\nTest hint:\n1. Verify that importing a non-adjacent scheduling period shows a clear error message.","","OSDOWSD-1028",""]
[null,null,1132438,null,null,"","New Feature","Functionality","Interfaces","A new command handler was made to send shifts back to decentral department","A new command handler CSendShiftsBackToDecentralDepartment was added to be able to send shifts from a central department back to a decentral department from an interface.\n\nExample input:\n<CSendShiftsBackToDecentralDepartment>\n  <parameters>\n    <shift id=\"1\"/>\n    <shift id=\"2\"/>\n  </parameters>\n</CSendShiftsBackToDecentralDepartment>\n\nTest hints:\n0. Precondition: central departments have been configured and a shift with id X is sent to the central department\n1. Call the command handler for shift with id X and verify that the shift is now sent back to the original decentral department.","","OSDOWSD-1032",""]
[null,null,1132438,null,null,"","New Feature","Functionality","Interfaces","Added functionality to import proposal departments","Now, it is possible to import proposal departments when running an import of departments.\n\nHere is a sample for importing data:\n\n<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n<TABLES>\n<TDepartments>\n<TDepartment>\n<NAME>Department</NAME>\n<CODE>4321</CODE>\n<PROPOSAL_DEPARTMENTS>\n   <PROPOSAL_DEPARTMENT>\n      <PROPOSAL_DPT_ID>1234</PROPOSAL_DPT_ID>\n      <PROPOSAL_DPT_INDEX>0</PROPOSAL_DPT_INDEX>\n   </PROPOSAL_DEPARTMENT>\n</PROPOSAL_DEPARTMENTS>\n</TDepartment>\n</TDepartments>\n</TABLES> \n\nTest hints:\n1. Verify that current department imports (that do not include proposal departments) in use at the customer import correctly without changing the proposal departments.","","OSDOWSD-1039",""]
[null,null,1134185,null,null,"","Bug","Stability","Database","Large number of changes to existing user groups and its related permissions could cause overflow error","The number of records in the acPolicyUserGroupVersion (used for authorisations and permission) could increase rapidly when a lot of usergroups already existed and when updating their related permissions. This could lead to the overflow error in the database.\nThis has been improved. \nThe maximum size of the column in the database has been increased to handle this large data. \nA monitoring query has also been added to monitor the growth of this column.  \n\nTest hints:\nNone\n","","OSDCOMMAIN-11853",""]
[null,null,1134185,null,null,"","New Feature","Reliability","Reporting","Upgraded report viewer to support date pickers in the frontends","The Microsoft Report Viewer 2015 Runtime libraries are distributed with the Backend API binaries to make the date pickers visible in the reports of the frontends OWS for Employees and OWS for Managers.\n\nTest hints:\nNone","","OSDOWSD-1007",""]
[null,null,1134185,null,null,"","New Feature","Functionality","Service","Added department information to error message in case of failing organisation import","When importing a subdepartment to a deparment that is not allowed to have one, the import failed and an error message was included into the interface log. However, it was not clear for which department and subdepartment the import failed. \nThis has been improved. \nNow, the (sub)department name and code are added to the error message. \n\nTest hints: \n1. Verify that importing a subdepartment for a department that is not allowed to have one gives a clear error message","","OSDOWSD-1027",""]
[null,null,1134185,null,null,"","New Feature","Functionality","Tools","Added additional command line parameters for adjusting job scheduler configurations with ComtecConfig utility","It was not possible to edit the existing tasks and overwrite existing variables options when using the ComtecConfig command line utility to import job scheduler configurations. This has been fixed.\n\nThere are two parameters added to the ComtecConfig\n- /jscoverwritevariables=true or false.\n- /jscexistingtasks=add, skip or overwrite. \n\nTest hints:\nNone",null,"OSDOWSD-1046",""]
[null,null,1134185,null,null,"","New Feature","Functionality","Tools","Added the possibility to add or update a single message hub network using the ComtecConfig commandline tool","It was not possible to update an existing message hub configuration in the ComtecConfig commandline import, only to replace it entirely.\nThis has been improved.\nNow it is possible to add a parameter '/include' to the commandline import, so that the current configuration is updated with the new configuration.\n\nTest hints:\n1. Run 'comtecconfig /e=default /verbose /import /mh /include' and check in ORTEC System Configuration that the current message hub configuration is updated correctly.","","OSDOWSD-1048",""]
[null,null,1134185,null,null,"","New Feature","Reliability","Interfaces","Improved the feedback of the import interface with employee information ","For imports where we have information about the resource in the context of the import, we added information to the import feedback.\n\nThis has been done for \n- importing changes in employee availability\n- importing of clockings\n- importing using the ExtraXMLCreator TFillFieldsOfCOMTECShift\n- importing using the ExtraXMLCreator TFillFieldsOfShift\n\nTest hints\n1. Verify imports as described above work as before.",null,"OSDOWSD-1059",""]
[null,null,1134185,null,null,"","New Feature","Functionality","Optimization","Added a window that shows the details of the planning costs for an employee","A new window 'Details of planning costs' has been added that shows the details of the planning costs for an employee. The window can be opened from the plan board by using the right-click context menu in the Employee calculations grid, and is only available when that grid contains a calculation of the type 'Planning penalty for employee'.\n\nThe information in this window can be used to analyze the configuration of the soft constraints for the optimizer (automatic planner). \n\nTest hints: \n1. Verify that the new window 'Details of planning costs' can be opened in case a calculation of the type 'Planning penalty for employee' is available in the Employee calculations grid.","For this solution to become available, the win32 client must be installed ","OSDOWSD-1062",""]
[null,null,1136340,null,null,"","Bug","Performance","Reporting","Loading the ESS report 'Overview Shift Reassignments' can be slow ","The ESS report 'Overview Shift Reassignments' could be slow when a lot of data was queried. Side effect of such a long query could be observed in a rise in used memory during the query.\nThis has been improved. \nThe query loading the data has been improved, and is significantly faster.\n\nTest hint(s):\n1. Verify the report 'Overview Shift Reassignments' displays the correct data.","","OSDCOMMAIN-11900","10117369"]
[null,null,1136340,null,null,"","New Feature","Functionality","Import / Export","Improved error message when importing address data failed","Importing address data produced an error \"String or binary data would be truncated \" in case of providing too long values for address parameters, eg. importing employee data.\nThis has been improved.\nNow the error specifies the exact parameter and maximum length for this parameter. \n\nTest hint(s):\nNone","","OSDOWSD-1025",""]
[null,null,1136340,null,null,"","New Feature","Reliability","Import / Export","Improved error message when importing shift realisation failed when using TActivitiesXMLCreator","When an error occurred during a shift realisation import, the returned error message didn't contain enough information to identify the record that causes the failure. \nThe error message has been improved. \nNow, the related shift (name, begin date + time) and employee (employee number + name) are added to the message. \n\nThis has been done for: \n- import interfaces using the ExtraXMLCreator TActivitiesXMLCreator \n\nTest hint(s): \n1. Verify that the shift realisation import interface still works when using correct data. ","","OSDOWSD-1026",""]
[null,null,1136340,null,null,"Interfaces","New Feature","Functionality","Interfaces","Added department and workstation information to error message when workstation import fails","When updating the department of a workstation via the import was not possible, the error message was not very informative.\nThis has been improved.\nNow the name and code of the old department, new department and workstation are added to the error message, together with the number of activities that already use the workstation.\n\nTest hints:\n1. Verify that it is possible to update the department of a workstation when the workstation is not used in any duties or workstation demands.","","OSDOWSD-1029",""]
[null,null,1136340,null,null,"","New Feature","Functionality","Import / Export","Added wish information to error message when wish import fails","When using the import to delete a wish with a status higher than 'open' an error occurs. This error was missing information about which wish caused the error. \nThis has been improved.\nThe message now contains wish id and wish code.\n\nTest hints:\nNone.","","OSDOWSD-1030",""]
[null,null,1136340,null,null,"","New Feature","Functionality","Reporting","Made BI Settings configurable in ORTEC System Configuration (CSCS) Settings Manager","Currently, the BI Settings are configured per customer in database view HMY_BISettings. However, this is not desired, because people need access to the database.\nInstead, these settings are made configurable in CSCS/Configuration/Settingsmanager/CBIS/Dataloads and the view is now dependent on these settings. \n\nTest hint(s):\n1. Verify that a BI run (incremental load) is executed using the configured account(s) and period.","In case of a rolling horizon for the incremental load of BI, the settings in CSCS need to be reconfigured manually.","OSDOWSD-1031",""]
[null,null,1136340,null,null,"","New Feature","Functionality","Import / Export","Added commandhandler for changing duty property values of a shift","The command handler CChangeDutyPropertyValuesForShift for changing duty property values for a shift is added, to avoid importing unnecessary data.\n\nExample input: \n  <CChangeDutyPropertyValuesForShift>\n    <parameters>\n        <shift id=\"2102\" />\n        <dutyPropertyValues>\n            <dutyPropertyValue dutyPropertyId=\"123\" value=\"Sample Text\" />\n        </dutyPropertyValues>\n    </parameters>\n  </CChangeDutyPropertyValuesForShift>\n\nTest hints: \nNone","","OSDOWSD-1042",""]
[null,null,1136340,null,null,"ComtecConfig tool","New Feature","Functionality","Tools","Added the possibility to export the Process Configuration (CPMS) using the ComtecConfig commandline tool ","It was not possible to export the Process Configuration (CPMS) with the ComtecConfig tool.\nThis has been improved.\nThe parameter '/pc' can be used to the commandline export for exporting the CPMS configuration.\n\nTest hints:\n1. Verify that 'comtecconfig /e=<environmentname> /export /pc' exports the CPMS configuration. ","","OSDOWSD-1049",""]
[null,null,1136340,null,null,"ComtecConfig tool","New Feature","Functionality","Tools","Added the possibility to import or export configurations from or to a specified path using the ComtecConfig commandline tool ","It is now possible to specify a path to import or export configurations from or to when the ComtecConfig utility is used. If the parameter /path is specified, the CONFIGDIR setting in the registry will be ignored.","","OSDOWSD-1052",""]
[null,null,1136340,null,null,"","New Feature","Functionality","Tools","Added possibility to import the fields 'Comment' and 'WindowsUsername' in Process configuration import","For each process, a comment and user can be imported via process configuration import.\n\nTest hint(s):\n1. Verify a comment and windowsusername for a process can be imported. ","","OSDOWSD-1053",""]
[null,null,1136340,null,null,"","New Feature","Functionality","Tools","Made 'Process code' editable in Process configuration of ORTEC System Configuration (CSCS)","Now it is possible to view and edit the code of a process.\n\nTest hint(s):\nNone","","OSDOWSD-1055",""]
[null,null,1136340,null,null,"","New Feature","Configuration","Optimization","Improvements in text and calculation for scheduling criteron 'Duty type'","The scheduling criterion 'Duty type' had a inexplicable way of calculating costs. It gave quadratic cost per interval, so that the same shift could cause multiple penalties.\nThis has been improved.\nThe criterion now gives cost per shift (when needed), and the cost equals the number of other duty types in the preceeding shifts.\nFurthermore, the text of the rule has been changed. It no longer incorrectly suggests that this rule only works for some selected duties.\n\nTest hints:\nUse the 'Details of details cost' form (from the planboard) to check the cost when using this rule.","","OSDOWSD-1065",""]
[null,null,1136340,null,null,"","New Feature","Stability","Optimization","The 'Plan shift sequences' optimizer did halt in certain circumstances","In very special cases, the optimizer 'Plan shift sequences' ran into an error, which caused the optimization to stop prematurely. With this improvement, the search continues potentially leading to better solutions.\n\nTest hint: \n1. Run the optimizer 'Plan shift sequences' and verify that the result is good enough.","","OSDOWSD-1066",""]
[null,null,1136340,null,null,"ComtecConfig tool","New Feature","Functionality","Tools","Added the possibility to export full configurations using the ComtecConfig commandline tool ","It was not possible to export the full configuration with the ComtecConfig tool.\nThis has been improved.\nThe parameter '/full' can be used next to command line /export option for ComtecConfig tool to export the full configuration (default + changed configuration)\nWhen the parameter '/full' is used, then the parameter /path is required to be used to avoid exporting the configuration to the default CONFIG folder used by Postinstall.\n\nTest hints: \n1. Verify that 'comtecconfig /e=<environmentname> /export /all/full' exports the full configuration.","","OSDOWSD-1075",""]
[null,null,1136340,null,null,"Command handlers","New Feature","Functionality","Service","Added a commandhandler for changing activity property values of a shift","The command handler CChangeActivityPropertyValuesForShift for changing activity property values for a shift is added, to avoid importing unnecessary data.\n\nAn example of the input is:\n<CChangeActivityPropertyValuesForShift>\n <parameters>\n  <shift id=\"123\"/>\n  <activities>\n   <activity index=\"0\">\n    <activityPropertyValues>\n     <activityPropertyValue activityPropertyId=\"456\" value=\"Sample Text\" />\n     <activityPropertyValue activityPropertyId=\"789\" value=\"1234\" />\n    </activityPropertyValues>\n   </activity>\n  </activities>\n </parameters>\n</CChangeActivityPropertyValuesForShift>\n\nTest hints:\nNone","","OSDOWSD-948",""]
[null,null,1138317,null,null,"","Bug","Reliability","Core Framework","Starting service COMTEC CRBS Distributor took too long","The service 'COMTEC CRBS Distributor' sometimes took too long to start, causing the other COMTEC services to be stopped.\nThis has been improved.\nThe other COMTEC services will start, regardless of whether the 'COMTEC CRBS Distributor' succeeds to start\n\nTest hint(s):\n1. Verify that the COMTEC services can be started correctly by using the COMTEC CPMS Starter service.","","OSDCOMMAIN-11891","10101322"]
[null,null,1138317,null,null,"","Bug","Reliability","Reporting","In view HMY_Requirements the violation type was incorrectly filled in when labor rule \"Skills\" was used","The violation type of some requirements where not correct in the HMY_Requirements view. This could lead to incorrect customer reports.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that in a customer report, a skill requirement has violation type Skills","","OSDCOMMAIN-11905","10125507"]
[null,null,1138317,null,null,"","New Feature","Functionality","GUI","Several translations added for German","Several translations have been added for German for recent functional changes. \nTest hint(s):\n None","","OSDOWSD-1083",""]
[null,null,1140418,null,null,"","Bug","","","Error when finding candidates for shift","When the check box 'Use proposal departments' was checked in the 'Candidates for shift' window, it was not saved properly. This caused unwanted behavior when reopening the window. This has been fixed.\n\nTest hint:\n1. Verify that after selecting the box 'Use proposal departments' in the 'Candidates for shift' window, reopening the window and selecting a candidate from a proposal department does not lead to a warning.","For this solution to become available, the win32 client must be installed","OSDCOMMAIN-11937","10144489"]
[null,null,1140418,null,null,"","Bug","Functionality","Service","Several translations added for French","Several translations have been added for French for recent functional changes. \n\nTest hints: None ","","OSDCOMMAIN-11944",""]
[null,null,1140418,null,null,"","Bug","Stability","Reporting","For reports in 'OWS for Employees' and 'OWS for Managers' the language selected was not taken into account correctly","The selected language is not correctly taken into account when loading reports to fill the date pickers by default.\nViewing reports could fail or data of wrong period was returned.\nThis has been fixed.\n\nTest hints:\n1. Verify a report in the OWS for Employees opens with the correct date.\n2. Verify a report in the OWS for Managers opens with the correct date.","","OSDCOMMAIN-11947",""]
[null,null,1140418,null,null,"","New Feature","Functionality","Interfaces","Added a retry option for a failing export","A failed export stopped if there was an error.\nThis has been improved.\nNow a retry mechanism is in place that depends on the following settings in OWS Settings Manager:\n1. INTERFACES/XMLEXP/LOCKING/MAXRETRYCOUNT: the maximum number of retries, default value 0.\n2. INTERFACES/XMLEXP/LOCKING/RETRYMAXSLEEP: the time between retries in milliseconds, default value 1000.\nThe use of the retry mechanism can be configured with an optional <CanRetryLocking>Y</CanRetryLocking> tag in the export xml definition, by default it is off.\nUnless these settings are configured, the interfaces work the same as before.\n\nTest hint:\n1. Verify that an export can be executed.","","OSDOWSD-1068",""]
[null,null,1140418,null,null,"","Bug","Reliability","Reporting","Opening a report in 'ORTEC WS for Employees' and 'ORTEC WS for Managers' could result in an error","When a report in 'ORTEC WS for Employees' and 'ORTEC WS for Managers' was opened this sometimes resulted in an error due to unexpected data. After clicking 'View Report' this was resolved.\nThis has been fixed.\nThe reports are no longer automatically run when all parameters are set (or when no parameters are available). \nThe user always has to click 'View report'.\n\nTest hint:\n1. Verify reports show the correct data when running a report after clicking 'View Report' button.","","OSDOWSD-1192",""]
[null,null,1143070,null,null,"","Bug","Reliability","Installer","Removed installation of obsolete BackendAPI database from installation script","The BackendAPI database was not used in production environments.\nTo improve the installation of the BackendAPI the BackendAPI database installation step has been removed.\n\nTest hint(s):\n1. Verify on a clean machine that BackendAPI can be installed, no database is installed and it can be used by the front ends.\n2. Verify for an existing BackendAPI installation that the BackendAPI still can be used by the front ends when the BackendAPI database is deleted.","For existing environments keep the following topics in mind:\n1. The BackendAPI database needs to be deleted manually.\n2. In InstallPortal.xml the database connection string can be removed.","OOBA-417",""]
[null,null,1143070,null,null,"","Bug","Reliability","Import / Export","It was not possible to update the description of an illness availability in an illness update import","The description of illness availability was not updated when importing an update of an illness with an illness availability\nThis has been improved.\nWhen updating an illness availability the description is always imported.\nWhen illness availabilities are provided in the import they are always imported.\n\nTest hint(s):\n1. Verify illness availabilities can be imported.","With this change the functionality to import updates of illness availabilities has changed.\nBefore this change illness availabilities were only updated when\n- 1 or more illness availabilities existed with the updated illness in the import\n- or any of the imported illness availabilities with the updated illness had a percentage <>  0\n\nAn external parameter has been introduced: AlwaysUpdateIllnessAvailabilities. \nBy default this parameter is enabled.\nTo fall back on the old functionality as described above, it can be disabled in the import definition.\n\nExample:\n<Param>\n    <Name>AlwaysUpdateIllnessAvailabilities</Name>\n    <Show>N</Show>\n    <Type>boolean</Type>\n    <Value>N</Value>\n</Param>","OSDCOMMAIN-11877","10082997"]
[null,null,1143070,null,null,"","Bug","","","Shift reassignments were deleted when replacing illness shift by another illness shift","The shift reassignments of an illness shift were deleted when it was replaced by another illness shift.\nThis has been fixed.\nNow the reassignments are kept if a new illness shift is created.\n\nTest hints:\n1. Verify after an illness shift is replaced by an illness shift, the shift reassignment overview shows the correct reassignments.","","OSDCOMMAIN-11957",""]
[null,null,1143070,null,null,"","Bug","Functionality","Reporting"," SQL Reports update was missing the new logofile","The new ORTEC logo has been added to the Microsoft SQL Reports update.\n\nTest hints:\nNone","","OSDCOMMAIN-11959","10161777"]
[null,null,1143070,null,null,"","New Feature","","","Shifts are more fairly distributed across employees in optimizers","In our shift optimizers, we frequently search the best employee for a shift. When the score was a tie, it was quite possible that the same employee was selected every time. \nThis was not seen as a fair strategy and has been solved. \nIn case of a tie, now a random employee is selected. This randomness depends on the begin time of the period that is being scheduled, so that the result of the 'Plan vacant shifts' algorithm is still reproducible, but also gives different results for different periods. \n\nTest hint(s): \n1. Run the optimizers 'Plan vacant shifts' or 'Generate master schedule' with few or none scheduling criteria and verify that the result is more fairly distributed across the employees.","","OSDOWSD-1096",""]
[null,null,1143070,null,null,"","New Feature","Performance","Calculation","Improved the performance of updating the 'Clock times' window","The 'Clock times' window refreshed the clocking information for all employees when updating a single clocking for an employee. \nThis has been improved. \nNow only the clocking information for the selected employee(s) are refreshed.\n\nTest hints:\n1. Verify in the 'Clock Times' window clock times can be created, updated and deleted.","","OSDOWSD-1102",""]
[null,null,1143070,null,null,"","New Feature","Functionality","User Interface","Several translations added for French","Several translations have been added for French for recent functional changes. \nTest hints: None","","OSDOWSD-1163",""]
[null,null,1143070,null,null,"","New Feature","","","Added new compensation rule 'Variable entry for all activity types'","A new compensation rule 'Variable entry for all activity types' has been added. This rule will calculate per shift the amount spend per activity type.\n\nAdded global setting AllActivityTypesRem which is turned off by default. \n\nTest hints: \n1. Enable the global setting and verify that the compensation rule 'Variable entry for all activity types' can be added to a 'Compensation rules' set. ","","OSDOWSD-1164",""]
[null,null,1143070,null,null,"","New Feature","Functionality","Service","Added two database tables as preparation for new functionality","Added the following tables to the database:\n- ROS_ACTIVITYTYPE_DISTRIBUTIONPERIOD\n- ROS_ACTIVITYTYPE_DISTRIBUTIONPERIOD_COSTCENTERS\nThese tables are added as a preparation for the new functionality to distribute worked hours for a certain activity type over multiple cost centers.\n\nTest hint(s):\nNone ","","OSDOWSD-1169",""]
[null,null,1145390,null,null,"","Bug","","","Shifbidding in app requires extra permissions","- Fixed shiftbidding needs extra permissions for mobile app","","OSDCOMMAIN-11388","9609938"]
[null,null,1145390,null,null,"CUAS","Bug","Configuration","Utilities","User group permissions are not sorted when exporting","When exporting 'User Group Permissions', make sure the permissions are sorted on ObjectCode and then on AccessMode, to give every XML a consistent ordering.","","OSDCOMMAIN-11851","10056703"]
[null,null,1145390,null,null,"","Task","","","[ESS App] [Server] If user logs in with two iOS devices, no notifications are received","- Fixed notifications in case a user uses multiple iOS devices in parallel","","OSDGMSSRV-1405",""]
[null,null,1145390,null,null,"","New Feature","","","Configure server to allow to add an address of an activity in a shift","Is requested for ESS mobile app to open a navigation app showing the route to the activity location. In order to add this functionality, mobile app handler needs to send location details of activity to mobile device. \nWe added server side changes for adding address details on shift activity, and sending them to the mobile devices\n\nSettings\nAdded setting \"OWSMobileApp\\Address\\EnableSendingAddress\" to turn functionality on/off; is turned Off by default.","","OSDGMSSRV-1413",""]
[null,null,1145390,null,null,"","New Feature","Functionality","Service","Added functionality to distribute values for an activity type over one or multiple cost centers","New functionality is added to be able to distribute values for an activity type over one or multiple cost centers with a specified percentage within a validity period.\n\nA new menu item with name 'Activity type cost center distribution' has been added which opens a new window. In this new window the user can specify the cost centers and percentages for the activity types of the selected department.\n\nA new reporting remuneration rule 'Transferbooking based upon activity type cost center distribution' has been added. This rule will transfer bookings per department, and distribute them among cost centers, depending on activity type.\n\nAdded global setting FromAccountUsingActivityTypeCostCenterLinkRem which is turned off by default.\nAdded permissions ACTIVITY_TYPE_DISTRIBUTIONPERIOD_READ and ACTIVITY_TYPE_DISTRIBUTIONPERIOD_WRITE.\n\nTest hint(s):\nPrecondition: the global setting is turned on and the user has the new permissions. \n1. Verify that the rule 'Transferbooking based upon activity type cost center distribution' can be added to a 'Reporting remuneration' set.\n2. Verify that the rule 'Transferbooking based upon activity type cost center distribution' can be added to an 'Invoicing rules' set.\n3. Verify in 'Customize menu' that the new menu item can be added to the menu.","","OSDOWSD-1185",""]
[null,null,1145390,null,null,"","New Feature","Functionality","Win32 User Interface","Add planboard sorter for employee first name","It is now possible to sort employees in the plan board based on their first name.\nAdded global setting  ResourceFirstNameSorter which is turned off by default.\n\nTest hints:\n1. Open employee sorting from plan board and select First name as the sorter.","For this solution to become available, the win32 client must be installed before activating the new sorter.","OSDOWSD-1356",""]
[null,null,1145390,null,null,"","New Feature","Functionality","Win32 User Interface","Add rule set name in 'Overview configuration' window","The compensation rule name and also the rule set name are shown in the 'Overview configuration' window. This makes it possible to easily identify the compensation rules that are used in this configuration.\n\nTest hint:\n1. Verify that the correct rule name and rule set name of a compensation rule are shown when you select an account category in 'Overview Configuration'  window","For this solution to become available, the win32 client must be installed.","OSDOWSD-1357",""]
[null,null,1145390,null,null,"","New Feature","","","A request based on a template request added via Availability page did not show the right color","The color of a template request was not taken into account when adding a request via Availability page in ORTEC WS for Employees. \nThis has been fixed. \nNow the color set in Template request is displayed. \n\nTest hint(s): \n1. Verify that an entered request via Availability page has the same color as in OWS Client Master Schedule and is equal to the corresponding Template request.","For this solution to become available, the Backend API version must have at least 8.5.0-1139456.","OSDOWSESS-1001","10091671"]
[null,null,1147110,null,null,null,"Bug",null,"ESS App","ESS App - Address in navigation app was not correct, because the address coordinates were used in a reversed order ","The ESS App received the address (X and Y) coordinates in reversed order from CWSS Server when the OMR functionality is used. Therefore, the navigation app did not receive the right address.\nThis has been fixed. \n\nNote: The functionality for showing an address and navigation icon at an activity is available when enabling CSCS-setting OWSMobileApp\\Address\\EnableSendingAddress. The setting is disabled by default. \n\nTest hint(s): \n1. Verify the address of an activity can be seen. \n2. Verify that activities with an address show a navigation icon. \n3. Verify that after pressing the navigation icon the default navigation app is opened and the To-address is equal to the address of the activity. ",null,"OSDGMSSRV-1496"]
[null,null,1147110,null,null,null,"Bug","","","Only one team in ESS app after patch","ESS APP - Added ESS Departments to MyTeams. It is now possible to view schedules of ESS Departments assigned to department of the user. \n\nTest hint(s):\nVerify if departments selected as ESS Departments (under Maintenance/Organization/-current department- / ESS departments) are visible in MyTeams","","OSDCOMMAIN-11685","9927002"]
[null,null,1147110,null,null,null,"Bug","Stability","Utilities","It was not possible to configure system monitoring in case of multiple environments","When refreshing the data in the System Monitor Configurator in CSCS an error 'The combination of server name and service name must be unique for each service.' was shown in a multiple environments configuration.\nIt was not possible to configure system monitoring\nThis has been fixed.\nFor a multiple environments configuration, the server name and service name will be unique and the number of instances is increased given the configuration.\n\nTest hint(s):\n1. Verify that sections Processes and 'CPMS processes' are filled in after click on button 'Refresh Environment'.","","OSDCOMMAIN-11958",""]
[null,null,1147110,null,null,null,"New Feature","Reliability","Reporting","Employee Self Service 'Personal schedule' report showed planned shifts","For an employee with multiple departments the 'Personal schedule' report in Employee Self Service showed shifts in schedules with status plan when at least one of the departments had a schedule with status higher than plan. \nThis has been fixed. \nFrom now on only shifts of status published or higher will be visible in the report. \n\nTest hints: \n1. Verify report 'Personal schedule' in Employee Self Service shows no shifts with status plan. \n2. Verify report 'Personal schedule' in ORTEC WS for Employees shows no shifts with status plan.","","OSDCOMMAIN-11974","10175284"]
[null,null,1147110,null,null,null,"Bug","Functionality","Client","Printing 'Time and attendance' of an employee or 'Workstation demand' now shows 'ORTEC Workforce Scheduling'","When printing the 'Time and attendance' of an employee or 'Workstation demand' the title of the print showed 'HARMONY'. \nThis has been fixed. \nNow, the title shows 'ORTEC Workforce Scheduling'.\n\nTest hints:\n- Verify that when printing 'Workstation demand' the title shows 'ORTEC Workforce Scheduling' instead of HARMONY \n- Verify that when printing  'Time and attendance' the title shows 'ORTEC Workforce Scheduling' instead of HARMONY","","OSDCOMMAIN-11985","10210216"]
[null,null,1147110,null,null,null,"New Feature","Functionality","Service","Added functionality to distribute values for an activity type over one or multiple cost centers","New functionality is added to be able to distribute values for an activity type over one or multiple cost centers with a specified percentage within a validity period.\n\nA new menu item with name 'Activity type cost center distribution' has been added which opens a new window. In this new window the user can specify the cost centers and percentages for the activity types of the selected department.\n\nA new reporting remuneration rule 'Transferbooking based upon activity type cost center distribution' has been added. This rule will transfer bookings per department, and distribute them among cost centers, depending on activity type.\n\nAdded global setting FromAccountUsingActivityTypeCostCenterLinkRem which is turned off by default.\nAdded permissions ACTIVITY_TYPE_DISTRIBUTIONPERIOD_READ and ACTIVITY_TYPE_DISTRIBUTIONPERIOD_WRITE.\n\nTest hint(s):\nPrecondition: the global setting is turned on and the user has the new permissions. \n1. Verify that the rule 'Transferbooking based upon activity type cost center distribution' can be added to a 'Reporting remuneration' set.\n2. Verify that the rule 'Transferbooking based upon activity type cost center distribution' can be added to an 'Invoicing rules' set.\n3. Verify in 'Customize menu' that the new menu item can be added to the menu.","","OSDOWSD-1185",""]
[null,null,1147110,null,null,null,"New Feature","Functionality","DataWarehouse","Added illness description and type to BI database","Added illness description and illness type to the BI data load.\nAs this data is personal, this has been disabled by default.\nAdded CSCS Settings Manager setting: CBIS\\Dataloads\\LoadIllnessDescriptionAndIllnessType with default value false.\n\nTest hint(s):\n1. Verify that a BI load can run and whether the new columns are filled or left blank according to the value of the new setting LoadIllnessDescriptionAndIllnessType.","","OSDOWSD-1364",""]
[null,null,1147110,null,null,null,"Bug","","","Old translog files are now removed after a set time","Old translog log files located in the folder \"logfiles\\Translogs\" were not removed periodically. This took up hard disk space unnecessarily. \nThis has been fixed. \nThe translog files now will be removed together with the other log files after the number of days set in 'old_logfile_age' in the settings manager.","","OSDOWSD-1365",""]
[null,null,1147110,null,null,null,"New Feature","Technical","Tools","Removed feature toggle LOGLOGINSESSIONOWSAPPLICATIONFORFRONTENDS","For analysis purposes, the number of sessions in use and/or created by the ORTEC Workforce Scheduling for Employees and Managers applications is recorded in the logging.\n\nThe feature toggle Server setting: FeatureToggles\\LOGLOGINSESSIONOWSAPPLICATIONFORFRONTENDS has been removed and this functionality has become default.\n\nTest hints:\n1. Verify a user can log in to ORTEC Workforce Scheduling for Employees.\n2. Verify a user can log in to ORTEC Workforce Scheduling for Managers. ","","OSDOWSD-768",""]
[null,null,1116175,null,null,"","Bug","Performance","Database","OWS backend api route used for employee realisations was slow due to bad performance of view HMY_SUBCONTRACT_STATUS","The performance of view HMY_SUBCONTRACT_STATUS has been improved..\n\nTesthints:\n1. Verify that an employee realisation can be entered in ORTEC WS for employees","","OSDCOMMAIN-11997","10218669"]
[null,null,1116175,null,null,"","Bug","Reliability","Employee self-service","ESS: Error was shown in Self scheduling in case of a planned instructor shift in another department","An error was shown when opening Self scheduling for an employee with an instructor shift in another department.\nThis has been fixed. \n\nTest hint(s):\n1. Verify that Self scheduling in ESS shows the correct data. ","","OSDCOMMAIN-12000","10219257"]
[null,null,1116175,null,null,"","Bug","Stability","Interfaces","CSV2XMLProcessor does not handle configured column headers with ',' correctly","Due to a recent update a CMHS network with a CSV2XMLProcessor didn't work anymore when ',' was used as separator in the explicit column headers, while the configured separator was something else than ','.\nThis has been fixed for backwards compatibility.\nWhen having column headers with a ',' separator and without the configured separator, the column headers will be changed such that the configured separator is used and a warning will be logged to notify that the processor configuration needs to be fixed.\n\nTest hint(s):\n1. Verify that a CMHS network with a CSV2XMLProcessor is still working.","","OSDCOMMAIN-12005","10213857"]
[null,null,1116175,null,null,"","Bug","Performance","Interfaces","Improved performance of opening and showing the CMHS-configuration in CSCS","While showing opening/loading a CMHS network different network components were (re)aligned several times. This caused an unwanted delay. \nThis has been improved. \nThe different components are realigned only once. \n\nTest hints: \n1. Verify a (large) CMHS network can be downloaded. ","","OSDCOMMAIN-12009",""]
[null,null,1116175,null,null,"","Bug","","","Improved performance of 'Master Schedule ESS' and 'Master Schedule' reports","Queries used in 'Master Schedule ESS' and 'Master Schedule' have been adjusted. This improves the performance while using these reports with large amount of data.\n\nTest hint(s):\n1. Verify that reports show the correct data.","","OSDCOMMAIN-12010","10231251"]
[null,"Y",1152973,null,null,"","Bug","","","In ORTEC WS for Employees 'Save as draft' button is now visible when not using approve realisations (UseApproveRealisations is False)","In ORTEC WS for Employees 'Save as draft' button was not visible for shift with status 'published', when not using approve realizations (UseApproveRealisations is False). \nThis has been fixed.\nNow the 'Save as draft' button is visible when realizing a shift with status 'published'. \n\nTest hints:\n1. Verify 'Save as draft' button is visible for a shift with status 'published' in ORTEC WS for Employees.","","OOBA-419",""]
[null,"Y",1152973,null,null,"","New Feature","Functionality","Installer","Change default account for HTTP service to SVC account","The server installer has been updated. By default the HTTP service is now intalled under the service account, instead of under the application account.\n\nTest hints:\n- None","","OSDCOMMAIN-11844","10052174"]
[null,"Y",1152973,null,null,"","Bug","Stability","Mobile application","Remove setting EnableShiftPickingNotifications from app service","Mobile app setting EnableShiftPickingNotifications has been removed. This was introduced when the functionality was not yet ready for production. Now it is generally available and the setting is no longer required. Having these notifications can be configured by configuring the export definition.\n\nTest hints:\n- Configure shift picking notifications and verify a notification is received when opening a shift for shift picking.","","OSDCOMMAIN-12003",""]
[null,"Y",1152973,null,null,"","Bug","Reliability","Interfaces","Improved retry mechanism for illness importing","The retry mechanism for importing was not working when importing illnesses.\nThis has been fixed.\nNOTE: It is not possible to retry when running the import in a single transaction\n\nTest hint(s):\n1. Verify it is possible to import illnesses.","","OSDCOMMAIN-12007",""]
[null,"Y",1152973,null,null,"","Bug","Reliability","Reporting","Render format \"Excel\" or \"Word\" in MS reporting mail subscription did not work in SQL 2016","Since SQL version 2016 the OpenXML formats for Word and Excel have  become the default when rendering the reports for Word or Excel.\nWhen mailing or archiving reports this was not taken into account. \nThis has been improved. \nThe version of the MS SQL Server engine is used as reference to check if OpenXML rendering is supported and should be used when rendering reports for Word or Excel.\n\nNOTE: It is advised to use same SQL Server Reporting Services version as the used MS SQL Server engine version to be able to correctly render reports for Word and Excel\n\nTest hint(s)\n1. verify reports can be emailed using the available report render formats\n","","OSDCOMMAIN-12014",""]
[null,"Y",1152973,null,null,"","Bug","Stability","Service","Erroneous administration of locks can cause 'Cannot dec FCount below 0' error","In rare cases a panic exception and server halt could occur when administration of locks was corrupt. \nThis has been fixed by improving the locking mechanism.\n\nA feature toggle 'ImprovedLockingMechanism' has been added. It is by default on, meaning the improved locking mechanism is active.\n\nTest hints:\n- Precondition: have 2 clients open\n- Verify opening a planboard for a department in one client while manually planning shifts for the same department in another client is possible.","","OSDCOMMAIN-12019","10223553"]
[null,"Y",1152973,null,null,"","Bug","Reliability","Service","Removed eventlog message for \"No translations found for report\"","Retrieving the available reports in ORTEC Workforce Scheduling for Employees could show a warning in the event log about missing translations.\nThis line has been removed as it does not add any information when retrieving the reports.\n\nTest hint(s):\n1 - verify retrieving the available reports in ORTEC Workforce Scheduling for Employees","","OSDCOMMAIN-12021","10246400"]
[null,"Y",1152973,null,null,"","Bug","Performance","Win32 User Interface","Remove NumberOfFlexpoolshifts license check query","The first client that was started each day did an expensive query. The query is no longer necessary.\nThis query has been removed.\n\nTest hints:\n1. Verify that the client can be started","","OSDCOMMAIN-12023","10247664"]
[null,"Y",1152973,null,null,"","Bug","","","Approving a schedule could fail with the error message \"Cannot insert internal id into the database\".","When using labor rules based on labor periods and a labor period longer than 7 days existed in a schedule, it was not possible to approve the schedule. An error \"Cannot insert internal id into the database\" occurred when storing violations for that schedule. This has been fixed.\n\nTest hints:\n- When using labor rules based on labor periods, verify that it is possible to approve a scheduling period that has violations on these rules.","","OSDCOMMAIN-12024",""]
[null,"Y",1152973,null,null,"","Bug","Reliability","Planboard","Text of planned activity in workstation planboard was not visible","When a workstation name starts with one space (or more) this name was not always visible (when changing the zoomlevel) in the planned activity on the workstation planboard.\nThis has been fixed.\nPreceding and trailing spaces are removed from the workstation name when it is displayed in the planned activity on the workstation planboard.\n\nTest hint(s):\n1. Verify workstation names are visible in workstation planboard ","For this solution to become available, the win32 client must be installed","OSDCOMMAIN-12029","10255706"]
[null,"Y",1152973,null,null,"","Bug","Reliability","Reporting","Overview shifts shows shifts from other departments than the selected department","When the option in the report 'Overview shifts' to 'Show employees from other departments' is selected shifts were shown that do not belong to the selected department.\nThis has been fixed.\n\nTest hints:\n1. Verify that the report 'Overview shifts' only shows shifts belonging to the selected department.","","OSDCOMMAIN-12030","10255710"]
[null,"Y",1152973,null,null,"","Bug","Functionality","Service","Updated Finnish translations","Finnish translation for classes 'Consignation (no labor)' and  'On call (no labor)' were not correct. \nThis has been fixed. \nClass 'Consignation (no labor)' has been changed to 'Varallaolo' and class 'On call (no labor)' has been changed to 'Päivystys (ei työtä)'.\n\nTest hint(s):\n1. Verify that the translations of all classes are shown correct in the Activity type tab in the Organization window","","OSDCOMMAIN-12031","10257154"]
[null,"Y",1152973,null,null,"","Bug","","","HTTPServer could halt when it was not used for a long period after starting up. ","When HTPPServer started, but was not used for a while the database connection could get lost. When that happened the HTTPServer halted. \nThis has been fixed. \n\nTest hint(s): \n1. Verify that the HTTPServer still starts","","OSDCOMMAIN-12035",""]
[null,"Y",1152973,null,null,"","Bug","Configuration","Service","Export configuration CSCS does not include OIDC settings","It was not possible to export CUASFW/OIDC settings in CSCS. \nThis has been improved.\n\nTest hint(s):\n1. Verify that you can export the CUASFW/OIDC settings","","OSDCOMMAIN-12038","10279085"]
[null,"Y",1152973,null,null,"Utilities","New Feature","Functionality","Miscellaneous","Add option for configuring mail server port to ComtecSystemMonitorConfigurator","Added option to configure mail server port in ComtecSystemMonitorConfigurator","","OSDGF-919",""]
[null,"Y",1152973,null,null,"","New Feature","Functionality","Self scheduling","Add new shift in WS for Employees with UseApproveRealizations on will lead to a pending update that requires approval","New functionality has been added that when a user adds a new shift in WS for Employees in a published schedule and UseApproveRealizations is enabled, this new shift will be created with only day-off and the duty the user has selected will be added on top of that as a pending update. This way the planner will be able to approve or reject the extra work the user has added to the schedule.\n\nAlso a new subscription and message type have been added so the planner is informed when such a shift is added and he can approve / reject the pending update directly from the message.\n\nTest hints:\n- Verify adding a new shift in WS for Employees is still possible.\n- Verify that when UseApproveRealizations is on the added shift has a pending update awaiting approval.\n- Verify that the new type of message is received for the added shift by a user that has the subscription.","NOTE: this change may have an effect on customer interfaces, when these export the availability of employees based on the shifts (for example export to Outlook). Since at first a day-off shift is added to the schedule and the work duty is not active yet until it is approved.","OSDOWSD-1495",""]
[null,"Y",1152973,null,null,"","New Feature","Functionality","Service","Rescheduling optimizer","A new optimizer is available: the rescheduling proposal. This is an advanced proposal, intended for the following situations:\n1. There is a vacant shift that can not be planned directly at any employee (for instance, one employee already has a shift, another lacks the qualification and for the third one it will create a violation on the labor legislation). But by first moving some shifts to other employees, it will become possible to assign the shift to an employee without causing extra violations. In this case the rescheduling optimizer will make a proposal to move these shifts after which the vacant shift can be planned.\n2. There are a number of vacant shifts, of which several must be planned. When planning the first shift you could make the wrong choice, so that another shift can no longer be planned. The rescheduling optimizer considers all of the selected vacant shifts at the same time and finds a solution.\n\nThe rescheduling optimizer is available as a new action in the right-click context menu on the vacant shifs grid of the planboard.\nThe current functionality provides for the design and presentation of a solution. It is then up to the planner to contact the employees and to implement the solution in the planning.\n\nNo permission is needed (if you are allowed to plan the shift manually, the new functionality is available).\nA feature toggle has been created for this new functionality (UseReschedulingPlanner). Default it is turned off.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nMore documentation will follow later, after a pilot of this functionality.","","OSDOWSD-1505",""]
[null,"Y",1152973,null,null,"","New Feature","Functionality","Service","Created a new activity class 'Break (on call)'","A new class, 'Break (on call)' for an activity type is created. This class should be used when employees might need to work during their break, and can therefore not leave a certain area.\n\nTest hints:\n- Verify the new activity class can be selected for an activity type in the organisation window. ","","OSDOWSD-834",""]
[null,null,1155260,null,null,"","Bug","Reliability","Import / Export","Exporting bookings during a BI run could cause an out of memory error","When during a BI run a lot of account entries were exported, retrieving these entries via the HTTP Server could cause an out of memory error.\nRequesting these entries via HTTP server when using BI or reports has been improved.\nThe error received originated from the xml transformation used for the account enties export. This transformation has been eliminated. It is now possible to export a greater number of account entries. \n\nWith this solution a new parameter has been introduced that is to be used in the definitions for BI and report exports:\nWriteResultFileToInterfaceOutputOnly that is default set to 'N', for the definitions used by for BI and report exports, it is set to 'Y':\n\nThe data retrieved is stored in two ways: (1) on disk and (2) returned as a data stream from interfaceworker \nIf WriteResultFileToInterfaceOutputOnly on 'Y' staat, the data is only returned as stream (2).\nWhen WriteResultFileToInterfaceOutputOnly is set to 'N' staat, it reverts to storing/streaming as before.\n\nThe definitions that have this new parameter set to 'Y' are:\nGeneral_BI_XMLDefinitions.XML\nGeneral_XMLDefinitions.XML\n\nTest hint(s):\n1. verify the BI loads run\n2. verify exporting non-BI related data is possible\n3. verify reports with account entries show the correct data ","","OSDCOMMAIN-12028","10255577"]
[null,null,1155260,null,null,"","Bug","","","A copy of a one time shift with realization was not visible in scenario","A copied one time shift with realization was not showing up in scenario's. This has been fixed.\n\nTesthint(s):\n1. Copy a realized one time shift.\n2. Create a new scenario. Verify that both the original shift and the copy appear in the scenario.","","OSDCOMMAIN-12042","10285986"]
[null,null,1155260,null,null,"","Bug","","","Code field of the 'Settings' window was editable without the 'DEFAULT_CALCULATION' permission","It was possible to change the code of calculations in the 'Settings' window, without having 'DEFAULT_CALCULATIONS' permission.\nThis has been fixed\n\nTest hints:\n1. Verify that being able to change the code of a calculation depends on the permission 'DEFAULT_CALCULATIONS'","For this solution to become available, the win32 client must be installed","OSDCOMMAIN-12043","10286058"]
[null,null,1155260,null,null,"","New Feature","","Manager self-service","Illness on second contract not visible in dashboard","An illness, registered for all contracts, on a second contract of an employee was not visible when viewing the department with the first contract of the employee in ORTEC WS For Managers dashboard.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that illnesses are shown correct in ORTEC WS For Managers dashboard.","","OSDOMSSWEB-737","10266105"]
[null,null,1155260,null,null,"","New Feature","Functionality","Self Rostering","It is now possible to pick a duty with normal demand 0 and max demand greater than 0 in self scheduling in ORTEC WS for Employees, Employee Self Service and ESS mobile App","In self scheduling functionality it was not possible to pick a duty if the normal demand of a duty is zero and the maximum demand is greater than zero. \nThis has been fixed. \nIt is now possible to pick duties in self scheduling that have a regular demand of 0 and a maximum demand greater than 0.\n\nAdded Server setting: 'SelfRostering\\ALLOWDUTIESWITHONLYMAXIMUMDEMAND' with default value False. To change to new functionality change this setting to True.\n\nTest hint(s): \n1. Verify that a duty in the dutyset with a demand of 0 and a maximum demand greater than 0 can be selected in self scheduling. ","","OSDOWSD-1514",""]
[null,null,1155260,null,null,"","New Feature","Functionality","Self scheduling","Added a new hierarchic criterion 'Preferred workstation'","A new shift proposal criterion is added, 'Preferred workstation'. This criterion returns 'Yes' in case an employee has a preference for at least one workstation of the activities of the shift.\n\nFor this criterion to become available, the global setting 'PreferredWorkstationHCrit' must be turned on.\n\nTesthint(s):\nPrecondition: Turn on the global setting 'PreferredWorkstationHCrit'and add the new criterion to a shift proposal criteria set.\n1. Verify that 'candidates for shift' show the expected employees.\n2. Verify that self scheduling show the expected employees.","","OSDOWSD-1516",""]
[null,null,1155260,null,null,"","New Feature","","","Added script that cleans preferred locations of an employee with a valid until date older than one year.","For performance reasons of several calculations the number of preferred locations specified for an employee that are not relevant anymore for planning purposes should be cleaned. A cleaning script is added in DBUpdate that is executed when deploying an update of ORTEC WS. The script will only remove preferred locations of an employee that have a valid until date older than one year. \n\nTest hint(s):\n1. Verify that after running DBUpdate the preferred locations that are valid are still shown in the employee management in the client.","","OSDOWSD-1517",""]
[null,null,1155260,null,null,"","New Feature","","","Status of a realisation of a shift created in ORTEC WS for Employees based on existing duty changed from 'Draft' to 'Submitted'","In the previous update new functionality has been added that when a user can add new shift in WS for Employees in a published schedule when UseApproveRealizations is enabled. This new shift will be created with only day-off and the duty the user has selected will be added on top of that as a pending update. In this situation the status of the created realization was draft, meaning that the user has to submit a realization first before the planner can approve it. This has been improved. \n\nNow when user adds a shift in ORTEC WS for Employees in a published schedule the realization will have status 'submit', which allows planner to immediately approve or decline the realization in OWS win32 client. \n\nTest hints: \n1. Verify adding a new shift in WS for Employees is possible. \n2. Verify that when UseApproveRealizations is ON the added shift has a pending update awaiting approval with status 'Submitted'. ","","OSDOWSD-1542",""]
[null,null,1155260,null,null,"","New Feature","","","Added feature toggle for Planning Details Cost Form","Added feature toggle server setting: 'FeatureToggle\\UseDetailsPlanningCostForm' and is by default disabled. \nThis has been added for the recently released functionality available in the 'Details of planning costs' window (see issue OSDOWSD-1062). \nThis is to prevent a mandatory client install. \n\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department. ","When you want to keep using this functionality, activate the feature toggle UseDetailsPlanningCostForm.","OSDOWSD-1544",""]
[null,null,1157778,null,null,"","Bug","","","Shift properties were not set back correctly in case a leave request for a partial shift was set back to status Open.","When replacing a complete shift by an activity type with the action 'Replace by activity type' a new shift is created. This shift kept a link to the original shift. However this link is intended for leave request functionality to determine the original shift when the leave request status is set back from Approved to Open. In case a leave request was for a part of the shift, this has created a realization. When setting the status of the leave request to Open, the situation reverted to the original shift before the 'Replace by activity type' action.\n\nTo fix this situation, the new server setting OPTIONS/PLANBOARD/REPLACEWITHACTIVITYTYPE/SAVESHIFTBEFORELEAVEWHENREPLACEACTIVITYTYPEININTERVAL can be set to N. Then the link between the original shift and the created shift for action 'Replace by activity type' is not stored and it will thus not interfere with leave request functionality. Default value of the setting is Y to keep backward compatible.\n\nTest hints:\n- Verify the planboard action 'Replace by activity type' creates a new shift when replacing the complete shift by another activity type.","","OSDCOMMAIN-12046","10287963"]
[null,null,1157778,null,null,"ows-7","Bug","","","Labor periods that overlap with the end of a schedule could give an incorrect violation","If a labor period overlaps with the end of the schedule, it was falsely divided into two. This could lead to incorrect labor rule violations.\nThis has been fixed.\n\nTesthint(s):\nPrecondition: Have a labor rule using labor periods. \nPrecondition: Have a workshift ending at the end of the schedule and one at the begin of the next schedule.\n1.  Verify that the labor rule sees these two shifts as one labor period.","","OSDCOMMAIN-12047","10288157"]
[null,null,1157778,null,null,"","Bug","Stability","Interfaces","Exporting account entries could cause 'This class should not be added to any index classes' when feature toggle AlwaysQueryTransactionDataObject=Y","Exporting account entries could cause 'This class should not be added to any index classes' when feature toggle AlwaysQueryTransactionDataObject=Y and the export included calculated entries.\nThis has been fixed.\nExporting account entries will succeed when AlwaysQueryTransactionDataObject=Y.\n\nTest hint(s):\n1. verify reports with account entries show the correct data ","","OSDCOMMAIN-12063",""]
[null,null,1157778,null,null,"","New Feature","","","Planning Details Cost window does not use loaded setting","Added feature toggle server setting: 'FeatureToggle\\UseDetailsPlanningCostForm' and is by default disabled. \nThis has been added for the recently released functionality available in the 'Details of planning costs' window (see issue OSDOWSD-1062). \nThis is to prevent a mandatory client install. \n\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department. ","When you want to keep using this functionality, activate the feature toggle UseDetailsPlanningCostForm.","OSDOWSD-1568",""]
[null,null,1157778,null,null,"","New Feature","","","In ORTEC WS for Employees disturbance types were visible in the activity type picker for a realisation","It was possible to pick a disturbance type in ORTEC WS for Employees when doing an employee realization.\nThis has been fixed.\n\nTesthint(s):\n1. Verify that it is not possible to select a disturbance type when doing a realization in ORTEC WS for Employees.","","OSDOWSESS-1061","10218677"]
[null,null,1157778,null,null,"","New Feature","Reliability","Self scheduling","All activity types with \"Relevant to leave request\" checked for all departments were shown when entering a leave request","All activity types with \"Relevant to leave request\" checked for all departments were shown when entering a leave request in ORTEC WS for Employees.\nThis has been improved.\nNow when entering a leave request in ORTEC WS for Employees the department hierarchy for the employee is in taken into account when showing the activity types with \"Relevant to leave request\" checked.\n\nTest hint(s):\nPrecondition: Have activity types in different departments and the main department with \"Relevant to leave request\" checked\n1. Verify that when entering a leave request activity types of the department are shown\n1. Verify that when entering a leave request activity types of the main department are shown\n2. Verify that when entering a leave request activity types of departments of another branch are not shown ","","OSDOWSESS-1074","10268710"]
[null,null,1159551,null,null,"","New Feature","Reliability","Service","Data incorrect in HDM BRDG_DEPARTMENT_HIERARCHY]","When moving a department in the organisational structure but the number of levels from the HOE stayed the same, historical records were not set to inactive in the BRDG_DEPARTMENT_HIERARCHY table. This caused multiple records to be marked as active.\nThis has been fixed.\n\nNote this fix will partially correct existing corrupt records. The active flag is set to N, but the enddates are not correct.\n\nTest hints:\n- Move a department to another spot in the organizational tree while keeping the number of levels from the top the same as before.\nVerify that the old records in the BRDG_DEPARTMENT_HIERARCHY table have an enddate and the active_flag is set to 'N'","","OSDCOMMAIN-12064","10300820"]
[null,null,1159551,null,null,"","New Feature","Stability","Client","New treatment Break (on call) causes error on older clients","The recently added new activity class 'Break (on call)' (see issue OSDOWSD-834) causes an error 'Invald treatments found: BREAKONCALL' on older clients when opening the labor rules. To solve this a madatory client install would have been required.\nThis has been fixed.\nA feature toggle is now added to ignore the new treatment. To use the new treatment the client should be newer than the fourteenth of january 2019 and the feature toggle must be enabled. The feature toggle is automatically enabled if the new treatment is already in use.\n\nAdded feature toggle server setting: 'FeatureToggle\\UseBreakOnCall' and is by default disabled. \n\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department. \n\nTesthint(s):\n1. Verify the labor rules window opens.","","OSDCOMMAIN-12082",""]
[null,null,1159551,null,null,"","New Feature","Reliability","Interfaces","Added setting to skip check that could stop manual export when exporting data with inconsistencies","When doing a manual export, the error message \"There are inconsistencies with respect to the validity periode of activity types,.....\" was shown when there were inconsistencies. This also stopped the export. \nThis has been improved.\nA setting 'IgnoreValidPeriodInconsistencyCheck' has been added, that needs to be in a tag under Configurations/Configuration/Settings in the export definition. If the setting is not added, the checks are performed as before. When the setting is 'Y', the checks that cause the error message will be skipped. The manual export does not stop.\n\nTesthint(s):\n1. Verify running an xml export manually does succeed.","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12084","10308855"]
[null,null,1161831,null,null,"","New Feature","Reliability","Manager self-service","OWS for Managers: Final planned outsourced shifts were not taken into account in overview Staffing and Schedule","In OWS for Managers final planned outsourced shifts were not taken into account in overview Staffing and Schedule.\nThis has been improved.\nWhen subcontracted outsourced shifts are final they are taken into account in overview Staffing and Schedule.\n\nTest hint(s):\n1. Verify subcontracted final outsourced shifts with a demand are taken into account in overview Staffing and Schedule. \n2. Verify subcontracted concept/unassigned outsourced shifts with a demand are not considered in overview Staffing and Schedule. \n3. Verify non-subcontracted with a demand are taken into account in overview Staffing and Schedule. ","","OSDCOMMAIN-12087","10310334"]
[null,null,1161831,null,null,"","New Feature","Reliability","Service","BI hours with a loaned employee","In case an borrowed employee has a night shift on the transition date between departments (night shift ending on first day or beginning on last day of lending period) and bookings are grouped by department in the remuneration, the employee_department_key was not filled for boking of  the night part of the shift.\nThis has been fixed.","","OSDCOMMAIN-12088","10310711"]
[null,null,1161831,null,null,"","New Feature","Reliability","Reporting","Updated parameters of system reports to show translation","In some languages, boolean parameters of system reports were not translated in the all web applications of ORTEC Workforce Scheduling.\nThis has been fixed.\n\nTest hint(s)\n1. Verify that in a system report the boolean parameters are translated correctly.","","OSDCOMMAIN-12090",""]
[null,null,1161831,null,null,"","New Feature","Reliability","Reporting","Master schedule report does not handle outsourced employees correctly","Shifts of a lend employee were not shown when having the option 'show shifts from other department' checked in the 'Master Schedule' report when the borrowing department has no employees assigned.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that when option 'Shift of other departments' is unchecked in the Master Schedule report shows shifts of lend employees in the current department in both the Win32 Client and the ESS. ","","OSDCOMMAIN-12100",""]
[null,null,1163674,null,null,"","New Feature","Reliability","Manager self-service","OWS for Managers: Final planned outsourced shifts were not taken into account in overview Staffing and Schedule","In OWS for Managers final planned outsourced shifts were not taken into account in overview Staffing and Schedule.\nThis has been improved.\nWhen subcontracted outsourced shifts are final they are taken into account in overview Staffing and Schedule.\n\nTest hint(s):\n1. Verify subcontracted final outsources shifts with a demand are taken into account in overview Staffing and Schedule. \n2. Verify subcontracted concept/unassigned outsources shifts with a demand are not considered in overview Staffing and Schedule. \n3. Verify non-subcontracted with a demand are taken into account in overview Staffing and Schedule. ","","OSDCOMMAIN-12087","10310334"]
[null,null,1163674,null,null,"","Task","","","Renew notification certificates","The certificates required for sending notifications to iOS devices have been renewed. \n\nTest hints: \nNone ","","OSDGMSSRV-1515",""]
[null,null,1163674,null,null,"ows-7","New Feature","","","Added new permission for confirming all shifts in OWS for Employees","A new permission 'ConfirmAllShifts' which is revoked for all users is added. With this permission, an employee can confirm all shift in a period in OWS for Employees. \n\nThis new functionality will become available in OWS for Employees when improvement OSDOWSESS-1114 becomes available. ","","OSDOWSD-1607",""]
[null,null,1163674,null,null,"ows-7","New Feature","","","Created commandhandler to confirm all shifts and write employee log","A new command handler has been added as preparation for new functionality in OWS for Employees. This command handler will confirm all shifts in a given period for the employee and it will add a line in the employee log as proof that the employee has confirmed the period.\n\nTest hint(s):\n- None","For this solution to become available, the win32 client must be installed.","OSDOWSD-1609",""]
[null,null,1163674,null,null,"","Bug","","","Several translations added for German","Several translations have been added for German for recent functional changes. \n\nTest hint(s): \n1. None ","","OSDOWSD-1625",""]
[null,null,1163674,null,null,"","Bug","","","Introduce new mechanism for sending notifications to mobile app","A new process will be added to handle sending mobile app notifications through Firebase Cloud Messaging. This will replace the current notifications system that uses Google Cloud Messaging. The Google Cloud Messaging platform is deprecated and will go offline on April 11, 2019.\n\nThe new process has to be added as a website and can be added next to the existing installation of OWS (either OWS 7 or EP4). A full OWS upgrade is not required. It is required to configure additional queue export interfaces to write the files that will be picked up by the new process. An updated ESS_App_XMLDefinitions.xml file will be delivered with the template for these exports.\n\nNote: The process is activated after installation and after each restart but in case of a manual IIS reset or restart of the website the process needs to be activated manually by browsing the url from IIS. The expected result in browser is a 403.14 message, the process is activated.","","OSDGMSSRV-1511",""]
[null,null,1165894,null,null,"","New Feature","Reliability","Planboard","Some shifts in the personal schedule were not shown for employees in multiple departments","When opening a personal schedule of an employee that is in multiple departments, while the planner did not have permission on all departments, some shifts could have been incorrectly (not) shown. \nThis has been fixed.\n \nTest hint(s): \n1. Verify in the personal schedule that for an employee in multiple departments the shifts are shown according to the permissions of the planner. ","","OSDCOMMAIN-12096","10313754"]
[null,null,1165894,null,null,"","New Feature","Stability","Import/Export","CWSS Server process could halt with a panic exception","When the same data is changed and deleted within a very short period of time by another CWSS server processes, a CWSS server process could halt. \nThis has been fixed. \nThe chance of a panic exception for this specific situation has been reduced.\n\nTesthint(s): \n- None ","","OSDCOMMAIN-12130",""]
[null,null,1165894,null,null,"","New Feature","Reliability","Client","In OWS windows client it was not possible to create a leave requests outside an employee’s contract with a leave type of the highest organizational level ","It was not possible to create or change a leave request outside an employee’s contract with a leave type available from the highest organizational element.\nNow, leave types from the highest organization level can always be used for a leave request.\n\nTest hint(s):\n1. Verify that it is possible to enter a leave request outside an employee’s contract with leave type from the highest organizational element","","OSDCOMMAIN-12133","10400712"]
[null,null,1165894,null,null,"","New Feature","Reliability","Service","Processing clocking of adjacent shifts with realized times fails","When a shift was extended by a clocking rule, causing overlap with another shift, it was not possible to process the clocking of the other shift.\nThis has been fixed.\n\nTest hints(s):\n1. Verify that a clocking of a shift can be processed when the clocking of another shift overlaps with it.","","OSDCOMMAIN-12140",""]
[null,null,1165894,null,null,"","New Feature","Stability","Reporting","Mailing reports from OWS windows client showed 'Class not registered' error","When e-mailing a report from the OWS windows client an error message was shown with the text 'Class not registered'.\nThis has been fixed. \n\nThis was introduced recently by the fix for issue OSDCOMMAIN-12014 (Render format \"Excel\" or \"Word\" in MS reporting mail subscription did not work in SQL 2016).\n\nTest hint(s):\n1. Verify an \"Excel\" or a \"Word\" report can be emailed from the OWS windows client.","","OSDCOMMAIN-12141","10410702"]
[null,null,1165894,null,null,"","New Feature","Functionality","Planboard","Break rules: taking breaks at the start and end of combined shifts is now optional","The labor rule 'break rules' did take break at the start and end of combined shifts into account. \nThis has been improved.\nIt is now possible to not take the break at the start or end of combined shifts into account by using the checkbox \"Ignore break activity at the start and end of combined shifts\". By default this option is on. \n\nTest hint(s): \n1. Verify that the break at the start and end of a shift are taken into account when the checkbox in labor rule 'break rules' is not checked. \n2. Verify that the break at the start and end of a shift are not taken into account when the checkbox in labor rule 'break rules' is checked. ","","OSDCOMMAIN-12142","10411234"]
[null,null,1165894,null,null,"","New Feature","Reliability","Interfaces","It is now possible to import two different user properties with the same name ","When importing a user property (e.g. department property) while another property with the same name (e.g employee property) existed, it was possible that the existing property was overwritten.\nThis has been improved.\nNow a new property is created and the existing property of a different type is not touched.\n\nTest hint(s):\n1. Verify importing a new user property is possible. ","","OSDCOMMAIN-12143","10411353"]
[null,null,1165894,null,null,"","New Feature","Functionality","Optimization","New criterion for minimum or maximum working time based on account balance","A new scheduling criterion has been added, 'Min/max working time based on account balance'.\nThis criterion makes it possible to set a minimum or maximum to the number of working hours that the optimizer is allowed to plan per scheduling period.\nIt is also possible to use a duty property to make a correction on the working hours of a shift. This can be used to fill in the expected working time for an on call shift.\nThe account balance is calculated once, at the start of running the optimizer.\n\nTest hints: \n1. Use the new criterion, open a plan board with the employee calculation 'planning penalty for employee' and check the calculated penalties.","","OSDOWSD-1605",""]
[null,null,1165894,null,null,"","New Feature","Reliability","Self scheduling","OWS for Employees: Pending status of a shift is not visible after adding a new shift in a published schedule","After adding a shift when using approve realisations, the shift was not displayed with the pending status until the plan board was refreshed.\nThis has been fixed.\n\nTesthint(s):\n1. Verify when using approve realisations a newly added shift in OWS for Employees in status published has the pending status and needs approval.\n2. Verify when not using approve realisations a newly added shift in OWS for Employees in status published can be confirmed.","","OSDOWSESS-1077",""]
[null,null,1169674,null,null,"","Question","Reliability","Mobile application","ESS Mobile App: self-scheduling calculations calculations showed work hours in incorrect format","In ESS Mobile App the self-scheduling calculations showed work hours in incorrect format\nThis has been improved.\nSelf-scheduling calculations now show result in both decimals and hours when appropriate.\n\nTest hint(s):\n- Verify the result of self-scheduling calculations are shown in the expected format","","OSDCOMMAIN-11704","9955738"]
[null,null,1169674,null,null,"","New Feature","Reliability","Service","One of the parameters of the shift proposal criterion 'Balance of Account' was not copied correctly","When copying the shift proposal criteria \"Balance of account category\", one of the parameters was not copied correctly.\nThis has been fixed.\n\nTesthint(s):\n1. Verify that a copy of a \"Balance of account category\" has the same parameters as the original.","","OSDCOMMAIN-12149","10416180"]
[null,null,1169674,null,null,"","New Feature","Technical","Logging","The Environment used was not logged in eventlog messages originating from backendAPI ","The Environment used was not logged in eventlog messages originating from backendAPI.\nThis has been improved.\nIn addition to the information logged when entries are written to the Windows Logs (Event logs) the Environment and a Module name will be available.\n\nTest hint(s):\n1. Verify backend api works and logs information to Windows Log.","","OSDCOMMAIN-12159",""]
[null,null,1169674,null,null,null,"New Feature","","","Some old shifts were not shown in \"ORTEC WS for Employees\"","\"ORTEC WS for Employees\" did not show certain old shifts because of the way they were stored in the database. \nThis has been fixed.\nAfter running DBUpdate these shifts are shown again.\n\nTest hint(s):\nNone.","","OSDCOMMAIN-12166","10432362"]
[null,null,1169674,null,null,"","New Feature","Security","Win32 Userinterface","It was not possible for an user to view the 'Department Periods' in OWS client with department_periods_read permission ","It was not possible for a user to view the 'Department Periods' with department_periods_read permission.\nThis has been fixed. \nNow the user can view the 'Department Periods' tab in the 'organization' window if the permission 'department_periods_read' or 'department_periods_write_ForDepartment' is granted. \n\nTest hint(s):\n1. Verify that 'department periods' tab in the 'organization' window is visible if the user has the permission 'department_periods_read' granted","Updating the win-32 client is required for this change to become available. ","OSDCOMMAIN-12170","10440620"]
[null,null,1169674,null,null,null,"New Feature","Reliability","Miscellaneous","Updated text of compensation rule: \"Clocking entry with function key\"","The text of the compensation rule \"Clocking entry with function key\" lacked a remark which states that the rule only books when an activity type is found. This could lead to confusions while using the rule. \nThis has been improved.\nNow the rule contains the line: \"Note: This rule only makes account entries when the clock time overlaps with an activity.\"\n\nTest hint(s):\n1. None","","OSDCOMMAIN-12177","10467171"]
[null,null,1169674,null,null,"","New Feature","Performance","Logging","Added Server setting to limit the number of log warnings: \"TValueExpression: evaluating end date of expression resulted in a value <= 0\"","Incorrect configuration of account category expressions can lead to a large number of warnings: \"TValueExpression: evaluating end date of expression resulted in a value <= 0 \" in the event viewer and log files. \nThis has been improved. \nAdded Server setting \"Performance\\ACCOUNTCATEGORYEXPRESSIONMINUTESBETWEENLOGGING\" with default value 5. This is used to set the number of minutes between logging two such warnings. Possible values: an integer number between 0 and 60. To log all such warnings set the setting to 0. \nNote: This setting should be added manually to the settings manager, otherwise 5 minutes is used. \n\nTest hint(s):\n1. Verify that a compensation rule that uses an account category expression with a begin or end date works.","","OSDCOMMAIN-12180","10470687"]
[null,null,1169674,null,null,"","Task","Reliability","Mobile application","ESS Mobile App: Sending shift picking notifications added warnings to event log","Sending shift picking notifications added warnings to event log\nThis has been fixed.\n\nTest hints(s):\n- Verify shift picking notifications are send","","OSDGMSSRV-1406",""]
[null,null,1169674,null,null,null,"New Feature","Functionality","Service","Added new option for selecting employee property and value to clocking rules","All clocking rules have been expanded with the option to select an employee property and value. When also issue OSDOWSD-1087 is implemented, only the clocking rules for which the employee has the correct value for the employee property will be applied.\n\nTest hint(s):\n1. Verify the parameters of a clocking rule can be set.","","OSDOWSD-1086",""]
[null,null,1169674,null,null,"","New Feature","Functionality","Service","Added check to clocking rules so they only apply to employees with a certain employee property value ","In OSDOWSD-1086 all clocking rules have been expanded with the option to select an employee property and value. Now only the clocking rules for which the employee has the correct value for the employee property will be applied. Default the check is not executed, to ensure backwards compatibility.\n\nTest hint(s):\n1. Verify that the existing clocking rules are still executed.","","OSDOWSD-1087",""]
[null,null,1169674,null,null,"","New Feature","Functionality","Optimization","Added export for optimizer 'Generate master schedule'","It is now possible to write a file with the most important data for the optimizer 'Generate master schedule'. This file can be used by ORTEC to improve the optimizer. The file is written to a subfolder 'ShiftPlannerExport' of the folder where the server logfiles are written. \nAdded Server setting: Planner\\ShiftPlannerExport\\WriteShiftPlannerExport with default value N. Set this to 'Y' to activate the export. \nAdded Server setting: Planner\\ShiftPlannerExport\\HistoryLength with default value equal to the BufferedHistory setting. \nNote that the export contains no privacy data so it can be safely shipped to ORTEC. \n\nTest hint(s): \n1. Verify a file is written when the optimizer 'Generate master schedule' is run.\n2. Verify that this file contains valid JSON formatted data. ","","OSDOWSD-1667",""]
[null,null,1169674,null,null,"","New Feature","Reliability","Miscellaneous","Several translations added for German, French, Finnish and Danish","Several translations have been added for German, French, Finnish and Danish for recent functional changes.\nTest hints: None","","OSDOWSD-1674",""]
[null,null,1171806,null,null,"","New Feature","Reliability","Miscellaneous","Several translations added for German, French, Finnish and Danish","Several translations have been added for German, French, Finnish and Danish for recent functional changes.\nTest hints: None","","OSDOWSD-1674",""]
[null,null,1171806,null,null,"","New Feature","","","Small performance gain in optimizer 'Generate master schedule'","The optimizer 'generate master schedule' keeps a list of employee requests it has to check. This list also contained requests that are not valid in the period that is being generated.\nThis has been fixed. The optimizer will now be a bit faster.\n\nTest hints: Run 'generate master schedule' and see that it still takes requests into account.","","OSDOWSD-1688",""]
[null,null,1171806,null,null,"","New Feature","Functionality","Service","For the labor rule 'Cost center of activity' added check-box 'This rule only shows violations in the original department of the shift'","The labor rule \"Cost center of activity\" is used to verify that shifts with activity without cost center do not occur in a published schedule. If a shift was subcontracted from another department and the status of the subcontract is \"Final\" or higher then this rule produces violations in both schedules: in the schedule of the original department and the schedule where the work is actually done. \nThis has been improved. \nA check-box 'This rule only shows violations in the original department of the shift' has been added to the configuration page of the rule. If the checkbox is checked then the violation appears only in the schedule of the original department of the shift.\n\nTest hint(s):\n1. Verify the labor rule \"Cost center of activity\" produces a violation in both departments when the checkbox is unchecked.\n2. Verify the labor rule \"Cost center of activity\" produces a violation only in the original department when the checkbox is checked.","","OSDOWSD-1723",""]
[null,null,1171806,null,null,"","New Feature","Functionality","Service","Added new labor rule 'Rest after long night shift (labor period)'","A new labor rule 'Rest after long night shift (labor period)' has been added. This labor rule has been added to support an exceptional case in the labor regulations: sometimes a night shift longer than 10 hours is allowed, but this requires 12 hours rest after the night shift. \nAdded global setting RestAfterLongNightLaborPeriodReq. which is turned off by default.\n\nTest hint(s):\n1. Verify the new rule can be added to a labor rules set after it has been enabled.","","OSDOWSD-1724",""]
[null,null,1171806,null,null,"","New Feature","Reliability","Client","Several translations added for Danish, Finnish, French and German","Several translations have been added for Danish, Finnish, French and German for recent functional changes. \n\nTest hint(s): \n1. None.","","OSDOWSD-1733",""]
[null,null,1171806,null,null,"","New Feature","Reliability","Service","Now authorizations for department specific violation are only checked in the schedule where violation occurs","For a subcontracted shift the department-specific requirements produced violations only in one of the departments where the shift is shown. Meanwhile, the authorization mechanism for approving schedules checked all the departments where shift is visible. \nThis has been fixed. \nNow authorizations for department-specific violation are only checked in the schedule where the violation occurs.\n\nTest hint(s):\n1. Verify that it is not possible to approve a schedule where a department specific violation is shown for a subcontracted shift. \n2. Verify that it is possible to approve a schedule where a department specific violation is not shown for a subcontracted shift. ","","OSDOWSD-1756",""]
[null,null,1174816,null,null,"","New Feature","Reliability","Client","Several translations added for French","Several translations have been added for French for recent functional changes.\n\nTest hint(s):\n1. None. ","","OSDOWSD-1763",""]
[null,null,1176727,null,null,"","New Feature","","","Rolled out unassigned shifts caused unnecessary queries when running department cyclical schedule BI export","When exporting cyclical schedules for BI, the server did unnecessary queries to handle the request. This could have had a significant impact on performance.\nThis has been fixed.\n\nTesthint(s)\n1. Verify that a cyclical schedule still can be rolled out.\n2. Verify that a BI query concerning a cyclical schedule does contain shifts like before.","","OSDCOMMAIN-12192","10432391"]
[null,null,1176727,null,null,"","New Feature","Performance","Self scheduling","Improved performance of retrieving proposed shifts for an employee in self scheduling","Performance of retrieving proposed shifts for an employee in self scheduling in OWS for Employees has been improved.\n\nAdded feature toggle \\Featuretoggles\\USEIMPROVEDSELFROSTERGETSHIFTOPTIONS and is by default enabled.\n\nTest hint(s):\n1. Verify self scheduling in OWS for Employees.","","OSDCOMMAIN-12216",""]
[null,null,1176727,null,null,"","New Feature","Technical","Security","OIG: Less severe issues are logged to database instead of Identity Gateway application event log","When a user provided invalid credentials this was logged as a an error in Identity Gateway application log. \nThis has been improved.\nLess severe issues are no longer logged to the Identity Gateway application event log, but logged in the Log table of the Ortec Identity Gateway database.\n\nTest hint(s):\n- None","","OSDCOMMAIN-12217","10500985"]
[null,null,1176727,null,null,"","New Feature","Reliability","Planning","While shift queues are configured unnecessary data could be collected and stored when realizing an instructor shift","Realization of an instructor shift caused all shifts to be loaded for the duty set duty of the student shift when shift queues are configured.\nThis caused shifts to be loaded unnecessarily, which could prevent the action to finish.\nThis has been improved.\nThe shifts that are not needed are no longer included and the action can finish.\n\nTest hint(s):\n1. Verify instructor and student shifts can be realized in the OWS Win32 client.","","OSDCOMMAIN-12219","10484338"]
[null,null,1176727,null,null,"","Bug","Reliability","Service","When OMR was not running, 0 was stored as calculated distance","When OMR was not running, the distance calculation failed and a distance of 0 was kept in memory as calculated distance. To get the correct calculation a restart of CWSS was required. \nThis has been improved. \nUntil OMR is available again an exception will be shown that the calculation cannot be performed (similar to an exception in the configuration of rules). \n\nTest hint(s):\n1. Verify the distance calculation succeeds when OMR is available.","","OSDCOMMAIN-12228","10498745"]
[null,null,1179478,null,null,"","New Feature","Reliability","Planning","When GetFirstResourceAsRepresentativeForRotationLine is set to true for Personal rotation units the wrong resource is used","When Option\\Planboard\\Rotation\\GetFirstResourceAsRepresentativeForRotationLine = Y the 'Personal rotation unit' the wrong 'representative' resource was used to check violations against.\nThis has been improved.\nWhen Option\\Planboard\\Rotation\\GetFirstResourceAsRepresentativeForRotationLine = Y the 'Personal rotation unit' is checked the correct resource is used.\n\nTest hint(s):\n1. Verify when the rotation unit is a 'Personal rotation unit' only the resources of a rotation unit line is used to determine the representative which is used to check for violations. \n2. Verify when the rotation unit is a NOT a 'Personal rotation unit' all the resources of a rotation unit line are checked for violations.","","OSDCOMMAIN-12229","10483229"]
[null,null,1179478,null,null,"","New Feature","Reliability","Import / Export","User import: usergroup assignment is removed from the user instead of added","An usergroup assignment of a user was deleted when importing this usergroup with update strategy 'overwrite' and when the usergroup has a department group parameter assigned.\nThis has been fixed. \n\nAdded feature toggle \\Featuretoggles\\USEIMPROVEDUSERIMPORT\nThe feature toggle is by default enabled.\n\nTest hint(s):\n1. Verify that importing a usergroup for a user that is already assigned to the usergroup, where the usergroup has a department parameter assigned, doesn't delete the usergroup assignment.","","OSDCOMMAIN-12245","10533257"]
[null,null,1179478,null,null,"","New Feature","Stability","Calculation","Empty self schedule page in Employee Self Service and ORTEC WS for Employees","Unfortunately, an issue was introduced in a recent update (2019-01-24) for self scheduling in combination with labor rules based on labor periods. This issue caused the self scheduling page to remain empty. This has been fixed.\n\nTest hint(s):\nPrecondition: there is a self scheduling period with a demand for a night shift on the last day of the period. In the next scheduling period, the employee already has a shift that would be considered in the same labor period as the night shift, but does not overlap with the night shift.\n1. Open self scheduling page in in Employee Self Service or ORTEC WS for Employees and see that the shift options are shown.","","OSDCOMMAIN-12253",""]
[null,null,1179478,null,null,"","New Feature","Functionality","Service","Added new labor rule 'No activity kind between times'","A new labor rule 'No activity kind between times' has been added. This labor rule checks that there are no activity kinds between certain times.\nAdded global setting NoActivityKindBetweenTimesReq, which is turned off by default. \n\nTest hint(s): \n1. Verify the new rule can be added to a labor rules set after it has been enabled. ","","OSDOWSD-1778",""]
[null,null,1179478,null,null,"","New Feature","Reliability","Interfaces","When requesting day off duties in OWS for Employees on the day of the daylight saving time change, duties not valid on that day could be shown","On the day that the daylight saving time begins it was possible in OWS for employees to pick a day off duty that is only valid from the next day.\nThis has been fixed.\n\nTesthint(s):\n1. Verify that you can still request a day off in OWS for Employees.","","OSDOWSD-1850",""]
[null,null,1181643,null,null,null,"Bug","","","Some users were not able to select a duty in the 'Enter Duty Request' window","Some users were not able to select a duty in 'Enter Duty Request' window\nThis has been fixed.\n\nTest hint(s)\n1. Verify that a duty can be selected in 'Enter Duty Request' window","","OSDCOMMAIN-11338","9535832"]
[null,null,1181643,null,null,null,"New Feature","None","Reporting","Updated look and feel for several reports","Updated the look and feel of the following reports:\n- Auditing - Overview Status changes\n- Contractor Shift History\n- Flexpool statistics\n- Overview shift reassignments ESS\n- Requests\n- Self Scheduling ESS\n\nFor all these reports we changed the layout to be consistent with the new ORTEC style.The logo is now only shown at the first page of the report. This will allow the report to show more data.\n\nTesthint(s):\n1. Verify that the reports still show data.","","OSDCOMMAIN-12273","10572669"]
[null,null,1183857,null,null,"","Bug","None","Reporting","Updated look and feel for several reports","Updated the look and feel of the following reports:\n- Employee schedule planner\n- Employee schedule ESS\n- Overview shifts\n- Overview account entries\n- Account for employee ESS\n- Year Roster\n\nFor all these reports we changed the layout to be consistent with the new ORTEC style.The logo is now only shown at the first page of the report. This will allow the report to show more data.\n\nTesthint(s):\n1. Verify that the reports still show data.","","OSDCOMMAIN-11865"]
[null,null,1183857,null,null,"","Bug","Security","Win32 Userinterface","It was possible for a user to drag an understaffed workstation to an employee in OWS Win32 Client without permission to realise a shift","A user without the permission to create a shift realisation could drag an understaffed workstation in the workstation planning to an employee which creates a shift realisation.\nThis has been fixed.\nWhen a user does not have the permission to create a shift realisation, he cannot drag an understaffed workstation to an employee.\n\nTest hints:\n1. Verify that it is possible to drag an understaffed workstation to an employee with SHIFT_REALISATION_PUBLISHED_WRITE granted\n2. Verify that it is NOT possible to drag an understaffed workstation to an employee with SHIFT_REALISATION_PUBLISHED_WRITE revoked","Updating the win-32 client is required for this change to become available. ","OSDCOMMAIN-12292"]
[null,null,1183857,null,null,"","Bug","Reliability","Client","Several translations added for German and French","Several translations have been added for French and German for recent functional changes.\n\nTest hint(s):\n1. None. ","","OSDOWSD-1842"]
[null,null,1186171,null,null,null,null,"Reliability","Client","Integrate German Translations OWS and deliver new files for remaining #changed tokens","Several translations have been added for German. \n\nTest hint(s): \n1. None.","","OSDCOMMAIN-12242","10531086"]
[null,null,1186171,null,null,null,null,"Reliability","Interfaces","Exports used date parameters formatted using regional settings","Exports used date parameters formatted using regional settings.\nThis could cause issues when client/server did not use the same regional settings.\nThis has been fixed by formatting the dates as YYYYDDMMThhmmss.\n\nTest hint(s)\n1. verify exports succeed.","For this solution it is required to install the new OWS Win32 client. ","OSDCOMMAIN-12257","10520489"]
[null,null,1186171,null,null,null,null,"Reliability","Reporting","Report Master Schedule showed incorrect employee groupings when having column size Medium or Wide","In the report 'Master Schedule' in the OWS Client the grouping of employees was correct when having the column size on 'small'. When changing the column size to 'medium' or 'wide' extra incorrect employee groups were shown. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that grouping of employees is correct in the report 'Master Schedule' in the OWS Client","","OSDCOMMAIN-12295","10592529"]
[null,null,1186171,null,null,null,null,"Stability","Database","Running the report 'overview account entries' could give 'String or binary data would be truncated' error","Running a report 'overview account entries' could give 'String or binary data would be truncated' error.\nThe cause of the error is the combination of the shift remark and duty description that could become too large when combined.\nThis has been fixed.\nThe description fields have been enlarged to allow 400 characters in the table functions involved.\n\nTest hint(s):\n1. Verify that the 'overview account entries' returns data.",null,"OSDCOMMAIN-12300","10604417"]
[null,null,1186171,null,null,null,null,"Reliability","Interfaces","Importing user property values using non-ID fields failed","Recently a fix was done for the import of user properties (OSDCOMMAIN-12143). Unfortunately this fix caused a problem in the import of user property values when the user property was not referenced by UPY_ID, but for example by UPY_NAME. This has been fixed.\n\nTest hint(s):\n1. Verify a user property value with a reference to the user property in field UPY_ID can be imported.\n2. Verify a user property value with a reference to the user property in field UPY_NAME is can be imported.","","OSDCOMMAIN-12305","10606432"]
[null,null,1186171,null,null,null,null,"Performance","Self Rostering","Improved performance of the command handler CGetDutiesWhenUnplanShift","The performance of calculating the alternative shifts in round 2 of self scheduling has been improved.\n\nTest hint(s):\n1. Open Employee Self Service or OWS for Employees for a round 2 self scheduling period. Verify that it is possible to request alternatives for a planned shift.","","OSDCOMMAIN-12307",""]
[null,null,1186171,null,null,null,null,"Reliability","Service","The unassign shift option from the 'Search Concept planned shifts' window was not visible anymore","In the Search concept planned shifts, it was not possible anymore to unassign shifts.\nThis has been fixed.\n\nTesthint(s):\n1. Verify that it is possible to unassign a shift from the Search concept planned shifts window.","","OSDCOMMAIN-12316","10627476"]
[null,null,1187623,null,null,null,null,null,"Reliability","Service","Added retry mechanism for HTTP call used by reports and BI","HTTPServer calls from BI or reports can sometimes fail i.e. due to network issues. This causes the BI export to fail and reports to not show any information. \nThis has been improved. \nA retry mechanism to HTTPServer calls is added to make this more robust. The HTTP call will try three times, with three second delay.\n\nTest hint(s): \n1. Verify a report with running account information displays information.\n2. Verify a BI run can be executed.","OSDCOMMAIN-12237","10521020"]
[null,null,1187623,null,null,null,null,null,"Reliability","Data Entry","Changing the availibilty of an employee for a department failed due to subcontracts on another contract","Changing the availibilty of an employee for a department failed due to shifts from another department that are subcontracted to this department on another contract of the same employee. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that the availibility of an employee for a department can be changed when an employee still has subcontracted shifts to the department of the original availibility on another contract.","OSDCOMMAIN-12259","10536796"]
[null,null,1187623,null,null,null,null,null,"","","Flexpool employees were not visible in the Teamrooster schedule in ORTEC WS for Emloyees","In ORTEC WS for Employees the flexpool employees and other lent employees from another department were not visible in the \"Teamroster\" schedule. This has been improved. \n\nTest hint(s): \n1. Verify that lent employees are visible in the \"Teamroster\" schedule in ORTEC WS for Emloyees.","OSDCOMMAIN-12265",""]
[null,null,1187623,null,null,null,null,null,"Reliability","Service","ORTEC WS for Employees did not check \"customerCode\" parameter of the license correctly","ORTEC WS for Employees did not check customerCode parameter of the license correctly in case a non-default customerCode is used. This is important if multiple customers are run on the same server (e.g. for managed services) \nThis has been fixed.\nWhen using a non-default customerCode, add server setting 'CustomerCode' in OWS Settings Manager and enter a valid customer code. \nBy default this setting does not exist and is thus empty and the license will be checked with the default customerCode. \n\nTest hint(s):\n1. Verify that you can start ORTEC WS for Employees if CustomerCode is valid or empty. ","OSDCOMMAIN-12283","10586105"]
[null,null,1187623,null,null,null,null,null,"Reliability","Import / Export","Shifts that are subcontracted and final from a second contract are not considered when contract period changes are imported. ","Final subcontracted shifts from a second contract were not considered when contract period changes were imported. \nThe contract period change could cause the shift to be invisible in the schedule where the shift was contracted to. This could happen when the contract where the shift originated from was deleted by the import.\nThis has been fixed. \nNow the final subcontracted shifts from a second contract are also taken into account when contract period changes are imported.\n\nTest hint(s):\n1. Verify imports using ExtraXMLCreator TEmployeeImportDepartmentUpdate succeed. ","OSDCOMMAIN-12289",""]
[null,null,1187623,null,null,null,null,null,"Reliability","Service","In rare cases, double bookings could appear in BI","In the update of February 7 2019, an issue was introduced that could cause double account entries in BI for night shifts overlapping with the end the department assignment. \nThis has been fixed.\n\nTest hint(s)\n1. Do a BI run, verify no double account entries appear.","OSDCOMMAIN-12327","10654235"]
[null,null,1187623,null,null,null,null,null,"Configuration","Mobile application","Removed definitions for mobile app notifications that used the deprecated Google Cloud Messaging","The Google Cloud Messaging platform is offline. It has been replaced by the Firebase Cloud Messaging. Therefor the definitions to send notifications via Google Cloud Messaging have been removed from the XML definition file.\n\nTest hint(s):\n1. None","OSDOWSD-1905",""]
[null,null,1192426,null,null,"","Bug","","","In ESS Mobile App, SQL timeout error was caused by shifts for picking and requests calls ","In ESS Mobile App, SQL timeout error was caused by shifts for picking and requests calls\nThis has been fixed.\n\nTest hint(s):\n1. Verify that Schedule, Shift picking and Requests windows are opened without any error","","OSDCOMMAIN-11808","10027446"]
[null,null,1192426,null,null,"","New Feature","Reliability","Interfaces","ComtecConfig commandline tool also imported from default path when a path was specified","When adding the /path parameter to an import with the ComtecConfig commandline tool, also files from the default path were used.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that when using a /path parameter, only that path is used for import.","","OSDCOMMAIN-12248",""]
[null,null,1192426,null,null,"","New Feature","Reliability","Interfaces","CJSS Editor of CSCS did not always show the imported jobschedulerconfiguration directly after the import ","When importing the configuration of CJSS, the new configuration was not immeadiately visible. This has been fixed.\n\nTesthint(s):\n1. Import an CJSS configuration, and check that the new configuration is visible after downloading that configuration","","OSDCOMMAIN-12250",""]
[null,null,1192426,null,null,"","New Feature","Configuration","Service","CPMS variables can now be imported","When importing the process configuration using ComtecConfig, the variables were not imported. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that variables are imported correctly. Run 'ComtecConfig /e=EnvironmentName /v /import /path=\"D:\\Temp\\import\\\" /pc'.","","OSDCOMMAIN-12251",""]
[null,null,1192426,null,null,"","New Feature","Stability","Interfaces","When exporting the job scheduler configuration, the information was exported twice","When exporting the job scheduler configuration using ComtecConfig commandline tool, all information about groups, variables and tasks of a job scheduler configuration occured twice in the export file. \nThis has been fixed. \nNow the information is only exported once in the export file. \n\nTest hint(s):\n1. Verify that 'comtecconfig /e=<environmentname> /export /jsc' exports the job scheduler configuration once in the export file.","","OSDCOMMAIN-12252",""]
[null,null,1192426,null,null,"","New Feature","Reliability","Interfaces","While importing new and updating multiple .mhn files specific files can now be specified","It was not possible to specify which network of CMHS to be updated. Now it is possible to update the existing configuration with specific .mhn file(s) using '/include'. Existing network(s) with the same name(s) will be replaced. \n\nTest hint(s):\n1. Verify only the mentioned .mhn files can be imported. Run 'ComtecConfig /e=default /verbose /import /mh /include=importnetwork.mhn' \n2. Verify that files with wrong extensions (e.g. .mhx) raise a warning and are not imported. Run 'ComtecConfig /e=default /verbose /import /mh /include'.","","OSDCOMMAIN-12254",""]
[null,null,1192426,null,null,null,"New Feature","","","Shift Remark and Duty Description parameters were added to BackendAPI model of ShiftPickingOption","Preparational changes have been implemented in BackendAPI needed for showing information about shift remark and description of the duty in shift picking functionality of ORTEC WS for Employees. \n\nTest hint(s): \n1. None.","","OSDCOMMAIN-12344","10680439"]
[null,null,1192426,null,null,null,"New Feature","","","OriginalDepartmentId parameter was added to BackendAPI model of ShiftPickingOption","Preparational changes have been implemented in BackendAPI needed for showing information about original department of the shift in shift picking functionality of ORTEC WS for Employees. \n\nTest hint(s): \n1. None.","","OSDCOMMAIN-12345","10681984"]
[null,null,1198852,null,null,null,"New Feature","Reliability","Planboard","Opening a cyclical schedule gave 'Invalid class typecast' in rare cases","Clockings were loaded when opening a cyclical schedule. This is unnecessary and in rare cases could lead to an error: 'invalid class typecast'.\nThis has been fixed.\n\nTesthint(s):\n1. Verifiy that a cyclical schedule can be opened.","","OSDCOMMAIN-12276",""]
[null,null,1198852,null,null,null,"New Feature","Performance","Employee self-service","Mechanism to request language-id from request to BackendAPI has been improved ","Mechanism to request language-id from request to BackendAPI has been improved.\nFor requests that have the same language as we have in the database, only the request to the database is done once after that it is cached in memory. This improves the performance of backend api.\n\nTest hint(s):\n1. Verify in OWS for Employees works by opening a schedule, verify if selected language is reflected in schedule.\n2. Verify in OWS for Employees that workspaces show lables reflected by the selected language\n3. Verify in OWS for Employees that in Insights when opening an available report is shown in the language as reflected by the selected language.","","OSDCOMMAIN-12279",""]
[null,null,1198852,null,null,"","New Feature","Reliability","Planboard","In Workstation planning the lines in the different grids could be misaligned","In Workstation planning there could be a mismatch between the lines in the different grids, when a horizontal scrollbar was showing in the main grid. \nThis has been fixed.\nNow the side grids and main grid stay aligned even when there is a scrollbar in one of them.\n\nTest hint(s):\n1. Verify in workstation planning the last line of the main grid and the side grid are aligned. ","For this solution to become available it is required to install the new OWS win32 client.","OSDCOMMAIN-12340","10632666"]
[null,null,1198852,null,null,"","New Feature","Technical","Logging","Added additional information on line that is logged when export gives 'EXCEPTION Interface did not succeed' ","Added additional information to be able to collect and investigate errors during (queue) exports and imports\n\nTest hint(s):\n1. None ","","OSDCOMMAIN-12374","10720524"]
[null,null,1202322,"2019-06-06",null,null,"New Feature","Reliability","DataWarehouse","BI: Cost center code always empty in HDM and HDM_STAGE","The cost center CODE field in the HDM and HDM_STAGE tables was always empty.\nThis has been improved.\nThe cost center CODE HDM and HDM_STAGE will be populated with the value from the OWS tables.\nNote: Same as in the OWS database, the value for CODE can also be NULL or empty string.\n\nTest hint(s):\n1. Verify that after running an incremental load the BI database contains the same data in the costcenter CODE HDM and HDM_STAGE as in OWS. ","","OSDCOMMAIN-12260","10538120"]
[null,null,1202322,"2019-06-06",null,null,"New Feature","","","Accounts permissions to view Microsoft reports are now also availible in the access control folder 'Microsoft(Reports)'","Accounts permissions to view Microsoft reports were only available in the access control folder \"Ortec WS for Windows/Accounts\". \nThis has been improved.\nNow these permissions are also added to the folder 'Microsoft(Reports)/Accounts'. \n\nTest hint(s):\n1. Verify report permission of an account can be found in the new category 'Microsoft(Reports)/Accounts' and can be granted.","","OSDCOMMAIN-12262","10544837"]
[null,null,1202322,"2019-06-06",null,null,"Bug","","","A shift note was displayed in the ESS Mobile App for a planned shift with a remark that was not changed","The shift note appended to the shift name was always shown in the app when the shift had a description.\nThis has been fixed.\n \nTest hint(s):\n1. Verify that a shift note is shown after changing the remark of a planned shift.\n2. Verify that a shift note is not shown for a planned shift with a remark that was not changed after planning the shift.","","OSDCOMMAIN-12264","10566680"]
[null,null,1202322,"2019-06-06",null,null,"New Feature","Performance","Employee self-service","Mechanism to request language-id from request to BackendAPI has been improved ","Mechanism to request language-id from request to BackendAPI has been improved.\nFor requests that have the same language as we have in the database, only the request to the database is done once after that it is cached in memory. This improves the performance of backend api.\n\nTest hint(s):\n1. Verify in OWS for Employees works by opening a schedule, verify if selected language is reflected in schedule.\n2. Verify in OWS for Employees that workspaces show lables reflected by the selected language\n3. Verify in OWS for Employees that in Insights when opening an available report is shown in the language as reflected by the selected language.","","OSDCOMMAIN-12279",""]
[null,null,1202322,"2019-06-06",null,null,"New Feature","","","Optimizer to fill wish-requests now also considers part-time contracts","The functionality 'Fill with leave request' of the Automatic Planner in OWS Win-32 client did not take into account part-time contracts.\nThis has been improved. \nNow shifts created by this functionality of the Automatic Planner will have duration proportional to the employee contract. For this the checkbox 'plan contract hours' of the special duty used to create these shifts should be checked.\n\nTest hint(s):\n1. Verify that it is possible to fill leave request by using 'Fill with leave request' for different contract hours.","","OSDCOMMAIN-12302",""]
[null,null,1202322,"2019-06-06",null,null,"New Feature","","","Dependencies on CRBS process in OWS 7 have been removed","The deprecated CRBS Server (process) is not used by ORTEC-WS version 7. Meanwhile, because of obsolete dependencies some processes were not able to start/work without CRBS. This means that if some problem occured with CRBS Server it was required to restart all processes. \nThis has been improved. \nNow the dependencies on CRBS process are removed from the configuration files and therefore this process can be disabled. \n\nTest hint(s): \n1. Verify that CWSS Server starts with/without CRBS Server. ","","OSDCOMMAIN-12336",""]
[null,null,1202322,"2019-06-06",null,null,"New Feature","Functionality","Interfaces","Prepared employee backend route for instructor shift visibility in ORTEC WS For Employees","Technical changes are done in employee routes in the backend (api) to make it possible to show a shift is a student(-) or an instructor (+) shift in ORTEC WS For Employees in the future.\n\nTest hint(s):\nNone","","OSDCOMMAIN-12362",""]
[null,null,1202322,"2019-06-06",null,null,"New Feature","","","Prepared shift backend route for instructor shift visibility in ORTEC WS For Employees","Technical changes are done in shift routes in the backend (api) to make it possible to show a shift is a student(-) or an instructor (+) shift in Ortec WS For Employees in the future.\n\nTest hint(s):\nNone","","OSDCOMMAIN-12364",""]
[null,null,1202322,"2019-06-06",null,null,"New Feature","","","Added extra logging needed for OSDCOMMAIN-12351","Additional logging were added when 'shift is not in a container' consistency check is violated.\n\nTest hint(s):\n1. None.","","OSDCOMMAIN-12372",""]
[null,null,1202322,"2019-06-06",null,null,"Bug","","","Shifts from proposal departments were not available in the schedule to be picked","Shifts from proposal departments were not available in the schedule to be picked. Permission proposalDepartments was not taken into account.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that if the permission proposalDepartments is granted, the user will be able to pick shift notifications from his department and from the departments in the proposal department list of his department. \n2. Verify that if the permission proposalDepartments is revoked, the user will be able to pick shift notifications only from his department.","","OSDGMSSRV-1385",""]
[null,null,1202322,"2019-06-06",null,null,"Bug","","","The wildcard counter was not showing the correct value","The wildcard counter was not showing the correct value. When a wildcard was selected for a day or a shift for \"A department\", the wildcard counter was decreasing on all departments.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that the counter is decreasing/increasing only for the corresponding department when selecting/deselecting a wildcard for a day or a shift.","","OSDGMSSRV-1538",""]
[null,null,1202322,"2019-06-06",null,null,"New Feature","","","Several scheduling criteria now also calculate the correct penalty for two rare cases","Several scheduling criteria were not calculated correctly when a shift started exactly when the previous shift ended. Also in some other cases the calculation was incorrect when a shift started at midnight on the first day of the schedule.\nThis has been fixed.\nThe following criteria have been adjusted: \"Combinations of consecutive shifts\", \"Limit time between shifts\", \"Number of days rest after a shift\", \"Number of days rest before a shift\", \"Preferred workstations and locations\", \"Shift series length\" and \"Unwanted shifts\".\n\nTest hint(s):\n1. Verify the score for the used scheduling criteria in a plan board using the employee calculation 'Planning penalty for employee'.","","OSDOWSD-1736",""]
[null,null,1206084,"2019-06-13",null,null,"","New Feature","Reliability","DataWarehouse","Equal account entries were filtered for BI","When loading 'equal' account entries in BI (i.e. account lines with all fields the same: equal date, employee, account category, shift etc.), only one of the account lines was loaded to BI. This has been introduced in update versions 8.4.0(2019-01-17)_Build1155085 and 8.5.0(2019-01-17)_Build1155260.\nThis has been fixed. \nNow all account entries are loaded in BI.\n\nTest hint(s):\n1. Verify the BI loads run.","","Sodexo"]
[null,null,1206084,"2019-06-13",null,null,"New Feature",null,"","","Added a command handler to run the external planner","A new command handler is available to start the external planner. This can be used to schedule the external planner. The handler will only start the external planner, there is no feedback when the planner is done.\n\nExample of the handler with parameters:\n/hmy/server1/CRunExternalPlanner\n<CRunExternalPlanner>\n  <parameters>\n    <department id=\"1\" />\n    <beginDate value=\"2019-05-01\" />\n    <endDate value=\"2019-06-01\" />\n    <maxRunTimeInMinutes value=\"1\" />\n    <numberOfParallelSchedules value=\"5\" />\n  </parameters>\n</CRunExternalPlanner>\n\nTest hint(s): \n1. Use the CommandSender in CSCS to start the external planner for an scheduling period where the shifts are not assigned. After the calculation time, verify in the OWS client that the shifts have been planned.\nNote: see the manual on how to configure the external planner.","",""]
[null,null,1209462,"2019-06-20",null,null,null,"Functionality","Database","SQL Server 2017 is now supported for OWS7","We now fully support SQL Server 2017 for ORTEC Workforce Scheduling (OWS) 7. ","","OSDOWSD-2161",""]
[null,null,1213255,"2019-06-27",null,null,null,"Reliability","Planboard","Shift Counter (based on duty type) does not sort alphabetically","Shift Counter (based on duty type) did not sort alphabetically\nThis has been fixed.\nWhen 'Faction' Duty type is selected in plan board settings for the Shift Counter, the rows in the Shift Counter grid are initially ordered alphabetically.\n\nTest hint(s):\n1. Verify Shift counter grid orders the rows on duty type when configured as 'faction' in shift counter plan board settings\n2. Verify that the rows in the shift counter grid can still manually be ordered. \n3. Press F5 after verifying 2. and see the order is the same as in 1 then re-verify 1. \n4. Other factions should still have the same order as before. ","","OSDCOMMAIN-12390","10730342"]
[null,null,1213255,"2019-06-27",null,null,null,"Reliability","Reporting","Master schedule ESS: shift text was not readable when there was not enough contrast between font color and background color ","For the reports below, the shift text was not readable when there was not enough contrast between font color and background color.\nThis has been improved.\nThe calculation to get a good contrast by selecting the font color based on the configured background color for a shift has been improved.\n\nThe reports that have changed:\n- Overview shifts\n- Master schedule\n- Master schedule ESS\n\nTest hint(s):\n1. Verify shift names can be read against the background color in the above reports.\n2. For outsourced shifts in the Master schedule reports: Verify the name of the shift is italic.","","OSDCOMMAIN-12391","10743299"]
[null,null,1217275,"2019-07-04",null,null,null,"","","CUASFW\\WindowsAuthentication\\Configuration is not exported when exporting configuration","It was not possible to export CUASFW/WindowsAuthentication settings in ORTEC System Configuration (CSCS), Settings Manager. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that you can export the CUASFW/WindowsAuthentication settings.","","OSDCOMMAIN-12381","10726195"]
[null,null,1217275,"2019-07-04",null,null,null,"Reliability","Planboard","Dynamic filters in Unplanned Shift grid did not handle 'None' properly in some cases","Dynamic filters in the 'vacant shift'-grid in the planboard did not work properly in two cases.\n- When using 'None' for all filters, the grid did not refresh. This has been fixed.\n- When using the 'Shift function'-filter, 'None' showed all shifts. This has been fixed. Now the filter shows only the shifts where either the shift, or one of its activities contains the function. If 'None' is selected, only shifts are shown which do not have a function on the shift and all its activities.\n\nTest hint(s):\n1. Verify that the grid refreshes after selecting 'None' in a filter.\n2. Verify that the right shifts are shown when a filter is selected on the 'vacant shift'-grid.","Updating the win-32 client is required for this change to become available.","OSDCOMMAIN-12384",""]
[null,null,1217275,"2019-07-04",null,null,null,"Functionality","Planboard","Creating new shift in Planboard using the \"New Duty, copy of\"  did not copy costcenter of the duty","When creating a new shift in the planboard (CTRL-N) and using 'Copy of' or 'Based on' the costcenter was not taken into account.\nThis has been fixed.\nWhen creating in a new duty using 'Copy of' or 'Based on' (a duty in a duty set) the new duty will have the costcenter of the duty it was copied from.\nFor new duties that are not 'copied' or 'based up' a duty set duty, the duty will have the costcenter of the department it was created in (This has not changed)\n\nTest hint(s): \n1. Verify creating a new duty as a copy of an existing duty also copies the cost center of that duty. \n2. Verify creating a new duty not as a copy of an existing duty copies the cost center of the department if available.","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12393","10746044"]
[null,null,1217275,"2019-07-04",null,null,null,"","","'Non-social hours allowances in a period before or after a public holiday' remuneration did not release all allocated memory","'Non-social hours allowances in a period before or after a public holiday' remuneration does not release all allocated memory.\nWhen the remuneration was configured to exclude certain weekdays before or after a public holiday, calculations using the remuneration would cause the memory usage to go up unexpectedly ('memory leak').\nThis has been fixed.\n\nTest hint(s)\n1. Verify calculations when 'Non-social hours allowances in a period before or after a public holiday' remuneration is used.","","OSDCOMMAIN-12437",""]
[null,null,1217275,"2019-07-04",null,null,null,"Technical","Planboard","When Multi Language is used not all memory allocated during certain actions was correctly deallocated","When Multi Language Module is activated not all memory allocated during e.g. a plan board refresh and needed calculations was correctly deallocated. \nThis has been fixed. \n\nTest hint(s): \n1. Verify a schedule in the Win32 client can be opened. \n2. For customers with Multi Language Module enabled: Verify that a translation for e.g shift name can be edited.","","OSDCOMMAIN-12439",""]
[null,null,1221631,"2019-07-11",null,null,null,"Reliability","Planboard","Department filter was not available when basic module setting UseCentralDepartments is enabled","The department filter for shifts in the plan board was only available when the FlexPool module setting UseFlexPool was enabled.\nThis has been improved.\nThe department filter for shifts is now made available when the basic module setting UseCentralDepartments is enabled.\n\nTest hint(s):\n1. Verify that departments filter can be selected when UseCentralDepartments  is enabled.","","OSDCOMMAIN-12301","10604450"]
[null,null,1221631,"2019-07-11",null,null,null,"Performance","Planboard","Performance of loading shifts for customers using global setting UseAlwaysSaveOriginalShiftWhenApplyingLeave has been improved","For customers using global setting UseAlwaysSaveOriginalShiftWhenApplyingLeave the \"shift loading mechanism\" had been improved. \nNow there is a better performance while starting OWS-server, opening plan board and performing other standard actions. \n\nTest hint(s): \n1. Verify a plan board can be opened.","","OSDCOMMAIN-12331",""]
[null,null,1221631,"2019-07-11",null,null,null,"Reliability","Calculation","Contract change in an approved schedule could lead to incorrect calculations","In case of a contract change in an approved schedule a recalculation can triggered.\nIn certain cases this could have led to incorrect calculations.\nThis has been fixed.\n\nTest hint(s): \n1. Verify the stored account entries are available after changing contract hours in the past","","OSDCOMMAIN-12406",""]
[null,null,1221631,"2019-07-11",null,null,null,"Reliability","Self Rostering","Self scheduling periods were not visible in ORTEC WS for Employees when employee is borrowed by another department","In ORTEC WS for Employees self-scheduling periods of departments where employee is lent to were not visible. This has been improved.\n\nTest hint(s):\n1. Verify that employee can see self-scheduling periods.","","OSDOWSD-2114",""]
[null,null,1224638,"2019-07-18",null,"","Bug","","","Notifications were not working after site restart","Notifications were not working after site restart.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that after ESS Firebase API site restarts in IIS, the notifications are sent to mobile devices.","","OSDCOMMAIN-12354","10696510"]
[null,null,1224638,"2019-07-18",null,"","New Feature","Reliability","Client","Labor rule 'Weekly rest', did not handle the exception of the rule correctly","The labor rule 'Weekly rest' did not determine correctly whether a rest period could be used as exception for the rule.\nThis has been fixed.\n\nTesthint(s):\n1. Verify that the rule 'Weekly rest' gives violations when the exception was already used.","","OSDCOMMAIN-12371",""]
[null,null,1224638,"2019-07-18",null,"","Bug","Reliability","Employee self-service","Employee Self Service: activity property required a value when default value is empty","An activity property required a value when default value is empty\nThis was introduced in OSDCOMMAIN-12188.\nThis has been fixed by reverting this functionality for the Employee Self Service part back to before the OSDCOMMAIN-12188 changes.\n \nTest hint(s):\n1. Verify adding a remark to a shift succeeds in Employee Self Service when an activity property exists with an empty string as default.","","OSDCOMMAIN-12470","10896653"]
[null,null,1224638,"2019-07-18",null,"","New Feature","Stability","Logging","Added log line could clog up Windows Application event log when Multi Language is used","Added log line could clog up Windows Application event log when Multi Language is used\nThis has been fixed.\nThe log line is no longer added.\n\nTest hint(s):\n1. Verify opening a planboard with horizontal calculations succeeds when using Multi Language","","OSDCOMMAIN-12477",""]
[null,null,1227892,"2019-07-25",null,"","New Feature","Performance","Planboard","When Multi Language is used not all memory allocated during certain actions was correctly deallocated - Part 2","When Multi Language Module is enabled, not all memory allocated during certain actions (e.g. a plan board refresh and needed calculations) was correctly deallocated.\nIn part 1 of this issue (OSDCOMMAIN-12467) this was only partly resolved.\nThe previous solution has been further improved.\n\nTest hint(s):\n1. Verify a schedule in the Win32 client can be opened.\n2. For customers with Multi Language Module enabled: Verify that a translation for e.g shift name can be edited. ","","OSDCOMMAIN-12476","10905358"]
[null,null,1227892,"2019-07-25",null,"","New Feature","","","Created DayOffShiftWasCreated field for reverting employee realisation","Technical change for future improvement for removing shifts that were added in OWS for Employees.\n\nTest hint(s):\n1. Verify that a realisation can be created in a schedule with status higher  than published.","","OSDOWSD-2196",""]
[null,null,1227892,"2019-07-25",null,null,"Bug","","","A description column has been added to account entries in BI","It is possible to export the description of account entries to BI.\n\nNote that besides an update of BI this change also requires: \n- An update of functions in the OWS database \n- An update of the General_BI_XMLDefinitions.xml interface definition\n\nTest hint(s):\n1. Verify that descriptions for account entries on the running account are exported to BI for the configured accounts. ","- The updated General_BI_XMLDefinitions.xml needs to be put in the correct folder containing the used XML definitions.\n- The updated BI packages needs to be put into the correct folder manually.","OSDOWSD-2311",""]
[null,null,1230783,"2019-08-01",null,"","Epic","Functionality","Reporting","Added employee and department properties to BI loads","It is now possible to load employee and department properties and values in the BI database.\nAdded System Configuration setting: Configuration - Settings Manager - CBIS - Dataloads - PROPERTIES in which the OWS database ID of the properties can be entered that need to be loaded in BI (multiple ID's are separated by a comma).\nNOTE: only employee and department properties will be processed during the BI load.\n\nTest hint(s):\n1. Verify that the BI load runs correctly\n2. Verify that property data is loaded for the configured ID's","","OSDOWSD-2105",""]
[null,null,1230783,"2019-08-01",null,"Backend Domains API","New Feature","","","In Ad Hoc Planning the performance of the proposal has been improved","Opening the proposal page in Ad Hoc Planning could result in a timeout in case of a large number of proposed employees. \nThis has been improved. \nThe performance of opening the proposal page has been improved, so the timeout is less likely to occur. \n\nTest hint(s): \n1. Verify that the proposal page displays proposed employees.","","OSDOWSD-2331",""]
[null,null,1236367,"2019-08-15",null,null,"Bug","Reliability","Mobile application","In Self Scheduling module, only ten schedules have been shown","In Self Scheduling module, only ten schedules have been shown.\nThis has been improved.\nNow, all future schedules are shown, and ten newest schedules from the past. \n\nNOTE: For this solution to become available, mobile server update is required.\n\nTest hint(s):\n1. Verify that  all future schedules are shown, and ten newest schedules from the past.","","OSDCOMMAIN-12385"]
[null,null,1236367,"2019-08-15",null,null,"Bug","Reliability","Mobile application","In Self Scheduling module, some shifts on the days outside the selected period were not shown","In Self Scheduling module, some shifts on the days outside the selected period were not shown.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that all the shifts on the days outside the selected period are visible and they have blue color.","","OSDCOMMAIN-12422"]
[null,null,1236367,"2019-08-15",null,null,"New Feature","Reliability","Self scheduling","A command handler was created to revert employee realisation","Technical change for future improvement for removing shifts that were added in ORTEC WS for Employees. \n\nTest hint(s):\n-","","OSDOWSD-2195"]
[null,null,1238234,"2109-08-22",null,null,"New Feature","Reliability","Calculation","Clocking was not adjusted when a duty was copied/cut and pasted with UseProcessClockingWhenPlanningShift","When a shift was copied/cut and then pasted in plan board in Win32 client, the clocking calculations for new shift sometimes were not recalculated, provided the global setting UseProcessClockingWhenPlanningShift set to true. This has been improved.\n\nTest hint(s):\n1. Verify that shift realization is adjusted accordingly when copy a shift in a plan board on a day which has clocking rules configured.","For this solution to become available it is required to install the new OWS win32 client.","OSDCOMMAIN-12401"]
[null,null,1238234,"2019-08-22",null,null,"New Feature","Reliability","Calculation","Approved account entries were not automatically recalculated after adjusting or removing a correction","When adding a new correction on an account entry in an approved scheduling period, calculations that use this account entry were automatically recalculated. \nHowever, deleting or adjusting the same correction did not lead to an automatic recalculation (only after manual recalculation, the change was taken into account).  \nThis has been fixed.\n\nTest hint(s):\n1. Add a new correction on an account entry in an approved scheduling period. Adjust the new correction. Verify that your change was taken into account and led to an automatic recalculation of depending account entries\n2. Add a new correction on an account entry in an approved scheduling period. Delete the new correction. Verify that your change was taken into account and led to an automatic recalculation of depending account entries","For this solution to become available it is required to install the new OWS win32 client.","OSDCOMMAIN-12409"]
[null,null,1240382,"2019-08-29",null,null,"New Feature","Reliability","Planboard","Pasting shifts did unplan shifts of another department","When an employee was lent to a department, copy-pasting shifts in the plan board of Win32-client of this department could lead to unplanning shifts of the employee in another department.\n\nThis has been fixed.\n\nTest hint(s):\n1. Verify when copy/pasting in plan board, no shifts of other departments are unplanned ","","OSDCOMMAIN-12338",""]
[null,null,1240382,"2019-08-29",null,null,"Epic","","","Keep realization history when UseDutyExchanges is True and status published or higher","Realisation history is now stored when UseDutyExchanges is true and the schedule status is published.\n\nTest hint(s):\nCreate multiple realisations on the same shift when UseDutyExchanges is true and the schedule status is published, and verify in Overview Shift Reassignments that all the realisations made, still exist. ","","OSDCOMMAIN-12432",""]
[null,null,1240382,"2019-08-29",null,null,"New Feature","Reliability","Calculation","Labor rule 'Labor time per day for specific kind' considered labor time outside continous period","Labor rule 'Labor time per day for specific kind' provided excess violations in case of too long labour periods. \nThis has been improved.\n\nTest hint(s):\n1. Verify that the labour rule, 'Labor time per day for specific kind' works.","","OSDCOMMAIN-12448",""]
[null,null,1240382,"2019-08-29",null,null,"New Feature","Reliability","Self scheduling","OWS for Employees: Opening the details of a shift showed 'Something went wrong' because of NULL values in the database","OWS for Employees: \"Data is Null\" exception could be thrown when opening shift.\nThis has been improved.\nFor columns (e.g. name, description) in several tables (not all) that are empty (null) in the database the backend api will return the empty string \"\" \n\nTest hint(s):\n1. In OWS for Employees open the employee schedule and verify","","OSDCOMMAIN-12453","10879000"]
[null,null,1240382,"2019-08-29",null,null,"New Feature","","","Performance of the command handler CCleanUpRemovedShifts has been improved","Performance of the command handler CCleanUpRemovedShifts has been improved. This improvement resolves time-out problem of the cleaning task which could occur for some customers. \n\nTest hint(s): \n1. Verify that the command handler CCleanUpRemovedShifts cleans up removed shifts.","","OSDCOMMAIN-12461","10631141"]
[null,null,1242708,"2019-09-05",null,null,"Bug","Functionality","Mobile application","Shifts were set to status closed after realisation in the application","Shifts were set to status closed after realisation in the application. This occurred for a schedule with status Published when setting UseApproveRealisation was disabled, the permission ess.realizeshift.submit was not granted and the permission ess.realizeshift.saveDraft was granted.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that when:\nthe settings UseApproveRealisation is disabled\nthe permission ess.realizeshift.submit is not granted\nthe permission ess.realizeshift.saveDraft is granted\nthe user can enter hours and the shift remains with status Published.\n2. Verify that when:\nthe settings UseApproveRealisation is disabled\nthe permission ess.realizeshift.submit is granted\nthe user can enter hours and the shift will get status Closed.","","OSDCOMMAIN-11843","10052172"]
[null,null,1242708,"2019-09-05",null,null,"New Feature","Reliability","Miscellaneous","An error could occur on the first startup of CWSS Server (process) 1 when upgrading from the previous version","When the conversion took longer than 2 minutes and timed out, the following error could occur:\n\"Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction\"\n\nThis has been improved for the following conversions: \n- TFromAccountUsingExpressionRemConversion \n- TRunningAccountBufferedHistoryConversion \n- TRunningAccountAccessControlPermission_Conversion \nThe default timeout of 2 minutes has been increased to 4 minutes. \n\nTest hint(s):\n1. Verify that after upgrading the application from the previous version, no errors occur on the first startup of CWSS Server (process) 1 ","If the increase of the timeout to 4 minutes is not enough for a certain customer: \nThe default can be changed by adding ConversionDTCTimeOutInSeconds sever setting in OWS Settings Manager.","OSDCOMMAIN-12539","11017316"]
[null,null,1242708,"2019-09-05",null,null,"New Feature","Reliability","Self scheduling","OWS for Employees: The account details showed a wrong translation of the German word 'rounded'","The account details showed a wrong translation of the German word 'rounded'.\nThe used word 'Abgerunded' was incorrect as it implicitly means rounded down. This has been improved by changing it to 'gerunded'\n\nTest hint(s):\n1. Verify running account details are displayed correctly (in German)","","OSDOWSESS-1278",""]
[null,null,1245424,"2019-09-12",null,"","New Feature","Reliability","Planner server","Starting an automatic planner was not possible because some automatic planner(s) still seemed to be running","The administration of the number of automatic planners running can become corrupt when a client is killed after the planner is finished, but before the planner progress window is closed. This may result in new automatic planners not being able to be started anymore. This has been improved.\n\nTest hint(s):\n1. Verify that automatic planner can be started.","","OSDCOMMAIN-12332",""]
[null,null,1245424,"2019-09-12",null,"","New Feature","Functionality","BackendDomainsAPI","Default webpage has been added to the Backend API","Default webpage has been added to easily check the availability of the Backend (API).\n\nTest hint(s):\n1. None","","OSDCOMMAIN-12454","10879330"]
[null,null,1245424,"2019-09-12",null,"",null,"Stability","Security","Usage of special characters in a username caused CWSS Server processes to halt","When the username contained special characters from a character set other than Latin1, the CWSS Server processes were stopped\nThis has been resolved.  \n\nPlease note that a script will be run during the database update that could give the following warning:\n'The table [users] contains records where the userName contains non-latin1 characters.'\nFor the users involved the username in the userName column should be verified and possibly changed via a database script.\n\nTest hint(s):\n1. Verify new users can be created in access control\n2. Verify that you get a warning message when you try to save an ESS user with a username that has special characters from a character set other than Latin1 \n","","OSDCOMMAIN-12535","11014399"]
[null,null,1245424,"2019-09-12",null,"","New Feature","Functionality","BackendDomainsAPI","Configuration tool for BackendDomainApisWebSite does not upload CQMS queries","The \"post install\" step in the BackendDomainsAPI configuration tool could not upload CQMS queries. This has been fixed.\n\nTest hint(s):\n1. None","","OSDOWSD-2809",""]
[null,null,1250852,"2019-09-26",null,"","New Feature","Reliability","Employee self-service","It was not possible to create leave request in ORTEC WS for Employees and ORTEC WS for Managers in Finnish language","It was not possible to create leave request in ORTEC WS for Employees and ORTEC WS for Managers in Finnish language. This has been fixed.\nTest hint(s):\n1. Verify that a leave request can be created in ORTEC WS for Employees without any errors (in all supported languages).\n1. Verify that a leave request can be created in ORTEC WS for Managers without any errors (in all supported languages).","","OSDCOMMAIN-12576","11078977"]
[null,null,1250852,"2019-09-26",null,"","New Feature","None","Planner server","Automatic planner renamed to Optimizer","The old name 'automatic planner' suggests that it delivers the same schedule as the user can create manually, but with less user actions. However, we aim to deliver better schedules so 'Optimizer' fits better.\nEverywhere in the application texts like 'automatic planner' have been replaced by 'optimizer'.\n\nTest hint(s):\n1. Test that the optimizer can be started","","OSDOWSD-2205",""]
[null,null,1250852,"2019-09-26",null,"","New Feature","Security","BackendDomainsAPI","BackenDomainsAPI installer installed unneeded files","The installer for the BackendDomainsAPI installed pdb files. These files are only used for development, are not needed on a production environment.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that after installation no new pdb files are installed","The installer does not remove the pdb files when upgrading. In order to make sure the files are removed from the system, please delete them manually or perform an uninstall first.","OSDOWSD-2922",""]
[null,null,1250852,"2019-09-26",null,"","New Feature","Functionality","Customer - Spec","A new functionality for showing physical location properties and their values has been added in OWS Win-32 Client.","The physical location property values are now displayed\n       - in the shift hint (in the master schedule);\n       - in the activities tab of duty window (duty set, one-time shift, template, when hovered over the workstation of an activity);\n       - in the newly created window 'Location Properties'.\nThe new window 'Location Properties' displays information of the shift including the location property values. This window can be added in the planboard menu.\n\nA new global setting 'UsePhysicalLocationPropertyValueHint' has been added.\nIn order to use this functionality the existing global settings UseWorkstationInHinttextShift' and 'UsePhysicalLocationProperties' should also be enabled.\nTwo new server settings 'AllowedPhysicalLocationPropertyNames' and 'MaxNOfShiftInLocationPropertiesWindow' have been added to the Options/Planboard\nThe physical location property value is displayed only when the property names (separated by a semi-colon ';') is configured in the server setting 'AllowedPhysicalLocationPropertyNames'.\nThe number of shifts to be displayed in the new window 'Location Properties' can be configured in the setting 'MaxNOfShiftInLocationPropertiesWindow' and its default value is '5'\nNote that this functionality only checks USERPROP_XXXX permissions of physical location properties to be displayed.\n\nThis functionality is not available for shifts in the cyclical schedule.\n\nTest Hint(s):\n\nVerify that the physical location properties and its values are visible in:\n1. The shift hint in the planboard.\n2. The workstation hint in the activities tab of duty windows\n3. The new window 'Location Properties' for the selected shifts in the master schedule plan board. ","Ortec WS Client needs to be re-installed for this functionality. ","OSDOWSD-2779",""]
[null,null,1252756,"2019-10-03",null,null,"New Feature","Reliability","Calculation","The maximum length of a 'day' Period type has been increased from 366 to 371","The maximum length of a ''day' Period type has been changed to 371 to allow a specific configuration for calculations\n\nTest hint(s):\n1. Verify that the length of a Period type can be changed\n2. Verify a new department period can be added using a period type of 371 days","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12537","11014505"]
[null,null,1252756,"2019-10-03",null,null,"New Feature","Reliability","Logging","BackendAPI build-number and build-date have been added to the BackendAPI log files.","Build number and build date have been added to the backend(API) log files when starting the backend(API). \nTest Hint(s):\n-","","OSDCOMMAIN-12550","11051158"]
[null,null,1252756,"2019-10-03",null,null,"New Feature","Reliability","BackendDomainsAPI","BackendDomainsAPI build-number and build-date have been added to the BackendDomainsAPI log files.","Build number and build date have been added to the BackendDomainsAPI log files when starting the website. \n\nTest Hint(s):\n-","","OSDOWSD-2771",""]
[null,null,1255129,"2019-10-10",null,null,"New Feature","Stability","Interfaces","Fixed the export queue's 'final_until' date to the begin date of the first available schedule","Fixed out of memory issue triggered by automatic export.\nTest hint(s):\n1. Verify that a salary export can be conducted.","","OSDCOMMAIN-12471","10882591"]
[null,null,1255129,"2019-10-10",null,null,"New Feature","Reliability","Planning","Additional warning has been added when deleting lending rotations lines in win32 client","In Win32 client, a planner of a department could lend an employee to another department and then revoke him. The global setting, \"UseUnassignedShiftWhenResourceNotInDepartment\" was set to true. When the planner was deleting \"borrowing/lending rotations lines\", he was not notified that shifts in the department where an employee was lent to, would be unassigned.\nThis has been improved.\n\n\nAn additional warning was added to inform planners that the \"borrowing/lending rotation line\" contains shifts that would be unassigned after the lending rotation period is deleted. \n\nTest hint(s):\n 1. Verify that it is possible to adjust the \"borrowing/lending rotation line\" when the borrowed employee has assigned shifts.","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12551","11051169"]
[null,null,1255129,"2019-10-10",null,null,"New Feature","Reliability","Planning","A subcontracted shift outside the schedule period could lead to an error during startup","When adjusting the begin and end time of a schedule, normal shifts which are outside the schedule will be removed. Subcontracted shifts cannot be removed, which leads to a startup error. This has been fixed in two ways.\n \n- When a shift outside the schedule has an active subcontract, an error message is shown when adjusting the begin and end time of the schedule.\n- When a shift outside the schedule has a non-active subcontract, the subcontract and shift are removed.\n\nTest hint(s):\n1. Verify that all normal shifts are removed from the schedule when switching begin and end date of a schedule\n2. Verify that shifts with active subcontracts (subcontracted to and from the department) are not removed: when changing dates, an error message should be shown \n3. Verify that shifts with non-active subcontracts (subcontracted from the department) are removed when switching begin and end date of a schedule","","OSDCOMMAIN-12559","11062837"]
[null,null,1255129,"2019-10-10",null,null,"New Feature","Functionality","Client","Department drop down in the Overview sick leave form has been made writable","The department drop down in Overview sick leave form of OWS Win32 client has been made writable.\n\nTest hint(s):\n1. Verify that, user can type in the department drop down and first department in the alphabetical order is selected automatically.","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12560","11062853"]
[null,null,1255129,"2019-10-10",null,null,"New Feature","Functionality","Optimization","Workstation optimizer now takes negative workstation demands into account","The workstation optimizer did not consider workstation demands with a negative amount. Negative amounts are for instance created by lowering an existing demand in the workstation plan board (via the right mouse menu). In previous versions the workstation optimizer didn’t take these negative amounts into account.\nThis has been improved.\nThe optimizer now subtracts negative workstation demands from positive workstation demands with the same workstation, timeslot and activity type.\n\nTest hint(s):\n1. Lower the demand for a workstation from the workstation plan board and run the optimizer. \n2. Verify that the optimizer assigns the correct number of shifts.","","OSDOWSD-2328",""]
[null,null,1255129,"2019-10-10",null,null,"New Feature","Reliability","Client","Danish, Finnish, French and German translations for physical location properties added","Several translations have been added for Danish, Finnish, French and German for recent functional changes. \n\nTest hint(s): \n1. None ","","OSDOWSD-2984",""]
[null,null,1257792,"2019-10-18",null,null,"New Feature","Stability","Calculation","Access Violation occured when using reporting compensation rule, \"Carry over per cost center\" for employees whose employee term group expired","Access violation occured when using reporting compensation rule, 'Carry over per cost center' for employees whose employment condition expired. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that the compensation value is 0 for employee whose employment condition expired for reporting compensation rule, 'carry over per cost center'.","","OSDCOMMAIN-12465","10891880"]
[null,null,1257792,"2019-10-18",null,null,"New Feature","Reliability","Client","Scrollbar for illness availabilities was not working when update permission Illness_ForDepartment is revoked","Scrollbar for illness availabilities was not working when update permission Illness_ForDepartment is revoked.\nThis has been fixed.\n\nTest hint(s):\n1. Verify illness availabilities can be entered when for the user the update permission Illness_ForDepartment is granted\n2. Verify illness availabilities can be viewed when for the user the update permission Illness_ForDepartment is revoked","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12503","10974556"]
[null,null,1257792,"2019-10-18",null,null,"New Feature","Reliability","Interfaces","Fact_Employee_illness in BI displayed multiple records of illness of an employee per day","Fact_Employee_Illness in BI displayed multiple records of illness of an employee per day in case availability percentages were used. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that employee illness is displayed only once per employee per day.","","OSDCOMMAIN-12506","10976222"]
[null,null,1257792,"2019-10-18",null,null,"New Feature","Reliability","Calculation","Copying a compensation rules set did not copy all values set for the rule 'Overtime:Fixed hours and difference cyclical schedule with realised schedule'","Copying a compensation rules set did not copy all values set for the rule 'Overtime:Fixed hours and difference cyclical schedule with realised schedule'\nThis has been fixed.\n\nTest hint(s):\n1. Verify that copying a compensation rules set also copies all values set for a configured 'Overtime:Fixed hours and difference cyclical schedule with realised schedule' rule.","","OSDCOMMAIN-12510","10982990"]
[null,null,1257792,"2019-10-18",null,null,"New Feature","Reliability","Calculation","Exchanges were not always correctly loaded when calculating account entries and using overtime definition \"Overtime: Fixed hours and difference cyclical schedule with realised schedule\"","Exchanges were not correctly loaded when calculating account entries and using overtime definition \"Overtime: Fixed hours and difference cyclical schedule with realised schedule\". This happened when account entries were calculated before opening the planboard of the department for the period of the account entries. When planboard of the department for the period of the account entries is opened, exchanges are loaded again and account entries are shown correct when refreshing.\nThis has been fixed.\n\nTest hint(s):\n1. Verify the correct account entries are shown correctly using overtime definition \"Overtime: Fixed hours and difference cyclical schedule with realised schedule\"  ","","OSDCOMMAIN-12511","10968187"]
[null,null,1257792,"2019-10-18",null,null,"New Feature","Reliability","Planboard","Setting \"ShowClosePlanboardWhenInactiveNotification\" has been added to show notification about inactive planboard going to be closed.","When planboards are closed because they are inactive for a certain number of minutes a message is being shown to the user that a planboard\nwas closed with that reason.\n\nA setting \"ShowClosePlanboardWhenInactiveNotification\" is added to the path\"DEFAULT_USR\\Options\\Planboard\" to suppress that message, so it can be enabled/disabled. \nBy default the setting is enabled to be compatible with current functionality.\n\nTest hint(s):\n1. Verify that if setting is not there or set to 'Y' then the notification is shown\n2. Verify that if setting is set to 'N' then notification is not shown.\n","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12536","11014448"]
[null,null,1257792,"2019-10-18",null,null,"New Feature","Security","Security","Error messages from CSetEmployeeMaxApprovedUntil command handler in Windows Eventlog showed privacy sensitive information about employees","Error messages from CSetEmployeeMaxApprovedUntil command handler in Windows Eventlog showed privacy sensitive information about employees.\nThis has been improved.\nOnly a notification of that an error occurred is logged in the Windows Eventlog. The details will be in the server log.\n\nTest hint(s):\n1. Verify the CSetEmployeeMaxApprovedUntil runs succesfully when running CJSS job 'Set employee max approved until' ","","OSDCOMMAIN-12541","11018952"]
[null,null,1257792,"2019-10-18",null,null,"New Feature","Performance","Database","AccessControl queries on table acCurrentPolicy were sometimes slow","AccessControl queries on table acCurrentPolicy were sometimes slow.\nThis has been improved.\nUPDATE STATISTICS acCurrentPolicy is called after changing the current policy. This ensures up to date statistics will be used in querying the acCurrentPolicy data.\n\nTest hint(s):\n1. Verify permissions can be changed in access control","","OSDCOMMAIN-12549","11051154"]
[null,null,1257792,"2019-10-18",null,null,"New Feature","Security","Security","Some back-end(API) exceptions were stored in the EventLog of back-end(API)","ORTEC WS for Employees and ORTEC WS for Managers displayed exceptions which sometimes contained personal information such as employee names and were stored in the eventlog of the back-end(API). \nThis has been improved.\n\nAfter this change these exceptions will be stored only in the log files of the back-end(API) and will not be displayed in eventlog.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-12561",""]
[null,null,1260261,"2019-10-24",null,"","Bug","","","MS Report: Master Schedule parameter value cleared out when department is changed in SQL Server 2017","MS Report: Master Schedule parameter value cleared out when department is changed in SQL Server 2017. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that when department is changed in master schedule report, other parameters do not change. ","","OSDCOMMAIN-12480","10916393"]
[null,null,1260261,"2019-10-24",null,"","Bug","Reliability","Planning","When realising a duty with on-call activities for the weekend, an ambiguous error was shown in some cases","When realising a duty with an activity for 24 hours, an ambiguous error was shown when option \"automatically move times of activities\" was unchecked. This has been improved.\n\nThe error message has been improved by mentioning that duties with a duration more than 24 hours are not supported. Next to that, in the duty window in the win32 client, an additional label has been added to emphasize whether the duration of a duty is more than 24 hours.\n\nTest hint(s):\n1. Verify that when the duration of a duty is more than 24 hours, an extra red label is visible in the duty window\n2. Verify that when realising a duty with an activity with a duration of 24 hours, and option \"automatically move times of activities\" is unchecked, an understandable error message is shown     ","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12481","10916409"]
[null,null,1260261,"2019-10-24",null,"","Bug","Reliability","Reporting","Report 'Flexpool statistics' did not show the correct shifts in a flexpool department when a subcontract of a shift was rejected","Report 'Flexpool statistics' did not show the correct shifts in a flexpool department when a subcontract of a shift was rejected.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that a shift for which a subcontract is rejected, is shown in the correct department in the report 'Flexpool statistics'","","OSDCOMMAIN-12543","10990332"]
[null,null,1260261,"2019-10-24",null,"","Bug","","","Filtering on employees and then changing date caused missing entries for accounts ","Applying the employee filter before changing the date caused missing entries for accounts.\nThis has been fixed.\nTest hint(s):\n1. Verify that changing the date in any account before and after filtering on employees provides the same account entries.","For this solution to become available it is required to install the new OWS win32 client.","OSDCOMMAIN-12581","11083242"]
[null,null,1263094,"2019-10-31",null,null,"Bug","Employee self-service app","Reliability","ESS Mobile App Bidding notifications depended on permission swap request","ESS Mobile App Bidding notifications depended on permission swap request.\nThis has been fixed.\n\nTest hint(s):\nNotifications should be received now independently from swap request permission. Please note that in order to receive notifications, users in question need to re-authenticate in the app.","","OSDCOMMAIN-12458","10882626"]
[null,null,1263094,"2019-10-31",null,null,"New Feature","Gui","Configuraton","Added several translations for the languages: German","Added several translations for the languages: German\n\nTest hint(s):\n1. Verify that it is possible to upload new translations.","","OSDCOMMAIN-12478","10909828"]
[null,null,1263094,"2019-10-31",null,null,"Bug","Employee self-service app","Reliability","The full name of the user was not displayed correctly according to the highest/newest contract","The full name of the user was not displayed correctly according to the highest/newest contract.\nThis has been fixed. \n\nTest hint(s):\n1. Verify that the full name of the user with the highest/newest contract number is displayed by default.","","OSDCOMMAIN-12494","10960612"]
[null,null,1263094,"2019-10-31",null,null,"New Feature","Planning","Stability","Panic after copying a rotation with 'double' rotationline","Rotation lines with the same rotation unit and same sequence number could appear in the memory of CWSS Server. This could lead to panic exceptions, for instance, when copying the schedule that contains these double rotation lines. The mechanism which associates a sequence number to rotation lines has been improved to prevent this from happening. A query has been added to the  'detect corrupt data' dbupdate script to detect such rotation lines.\n\nTest hint(s):\n1. None \n\n\n\n","","OSDCOMMAIN-12583","11083318"]
[null,null,1263094,"2019-10-31",null,null,"New Feature","Gui","Configuraton","Added several translations for the languages: Danish","Added several translations for the languages: Danish\n\nTest hint(s):\n1. Verify that it is possible to upload translations for Danish language. ","","OSDCOMMAIN-12594","11102126"]
[null,null,1263094,"2019-10-31",null,null,"New Feature","Functionality","Optimization","An option is added to always respect wishes not to work in the schedule optimizer","An option 'respects all wishes not to work' is added to the optimizer 'Optimize schedule'. This option enforces that wishes not to work are never violated, even if that means that shifts remain vacant.\n\nTest hint(s):\n1: Verify that the optimizer does not plan in a shift when an employee has a wish not to work.","For this issue to become available, the win32 client must be installed","OSDOWSD-2327",""]
[null,null,1265712,"2019-11-07",null,"","New Feature","Reliability","Interfaces","Student shifts could not be realised via the import interface","Student shifts could not be realised via the import interface. The ExtraXMLCreator TFillFieldsOfCOMTECShift did not handle student shifts correctly.  This has been fixed.\n\nTest hint(s):\n1. Verify student shifts can be realised via the import interface when using the ExtraXMLCreator TFillFieldsOfCOMTECShift.","","OSDCOMMAIN-12630","11185862"]
[null,null,1265712,"2019-11-07",null,"","New Feature","","","Several translations added for Danish, Finnish and French","Several translations have been added for Danish, Finnish and French for recent functional changes. \n\nTest hint(s): \n1. None","","OSDCOMMAIN-12637",""]
[null,null,1265712,"2019-11-07",null,"","New Feature","Stability","Calculation","Labor rule 'Labor time per day for specified kind' gave an access violation","Labor rule 'Labor time per day for specified kind' gave an access violation when only part of a shift should be taken into account when calculating the labor in a certain period.\nThis has been fixed. \n\nTest hint(s):\n1. Verify that the labor rule 'Labor time per day for specified kind' shows correct violations.","","OSDCOMMAIN-12647","11241537"]
[null,null,1265712,"2019-11-07",null,null,"New Feature","","","It is now possible to filter on multiple duty types in vertical norm \"Number of skills present\"","In the vertical norm 'Number of skills present' it was possible to count only shifts with a specific duty type.\nThis has been improved.\nIt is now possible to specify multiple duty types.",null,"OSDOWSD-3065",11150941]
[null,null,1265712,"2019-11-07",null,"","New Feature","","","Shift and schedule status now can be changed to 'Approved' with pending/concept realisation ","Statuses of schedules and shifts with pending realisations can be updated to status, 'Approved', based on the new permission, 'ALLOWED_TO_CHANGE_SHIFT_STATUS_WITH_EMPLOYEE_REALISATION' in the Access Control.\n\nTest hint(s):\n1. Verify that after enabling the permission, 'ALLOWED_TO_CHANGE_SHIFT_STATUS_WITH_EMPLOYEE_REALISATION', it is possible to change schedule and shift status to approved when they have pending realisations. ","","OSDOWSD-3156",""]
[null,null,1268050,"2019-11-15",null,"","New Feature","","","French translation for tlauth_allowed_to_change_shift_status_with_employee_realisation has been adjusted","Translation for the token tlauth_allowed_to_change_shift_status_with_employee_realisation\nhas been adjusted for French language. \n\nTest hint(s): \n1. None","","OSDCOMMAIN-12660"]
[null,null,1268050,"2019-11-15",null,"","New Feature","","","Added new remuneration rule 'Fixed entry for leave request per calendar day'","A new remuneration rule 'Fixed entry for leave request per calendar day' has been added. This rule will create an entry with the amount of 1 for each day of a leave request that has begintime and endtime of 00:00 hours.\n\nAdded global setting FixedEntryLeaveWishRem which is turned off by default. \n\nTest hint(s):\nPrecondition: the global setting is turned on. \n1. Verify that the rule 'Fixed entry for leave request per calendar day' can be added to a remuneration set.\n2. Verify that the rule 'Fixed entry for leave request per calendar day' books a value of 1 for each day of a leave request that has a begintime and endtime at 00:00 hours. ","","OSDOWSD-3218"]
[null,null,1268050,"2019-11-15",null,"","New Feature","","","Added new renumeration rule 'Variable entry for leave request'","A new remuneration rule 'Variable entry for leave request per calendar day' has been added. This rule will create an entry with the amount of hours for each day of a leave request that has begintime or endtime different from 00:00 hours.\n\nAdded global setting VariableEntryLeaveWishRem which is turned off by default. \n\nTest hint(s):\nPrecondition: the global setting is turned on. \n1. Verify that the rule 'Variable entry for leave request per calendar day' can be added to a remuneration set.\n2. Verify that the rule 'Variable entry for leave request per calendar day' books a value of hours for leave requests that has a begintime or endtime different than 00:00 hours. ","","OSDOWSD-3222"]
[null,null,1268050,"2019-11-15",null,"Shift offering","New Feature","Functionality","BackendDomainsAPI","[Bug] Offer absent shift with begin time > original end time gives 400 Bad Request","When offer an absent shift with not allowed changed begin - end time, a wrong error was given. \nThis has been improved. Now, the error indicates that there is a conflict in the offered shift.\n\nTesthint:\nReport an absence for an employee that has shifts on multiple days. Verify that his shift on the first day can be changed and offered. ","","OSDOWSD-3241"]
[null,null,1273652,"2019-11-29",null,"","Bug","Technical","Tools","Logging for analysis for memory allocations during calculations has been added","When calculating, an internal structure is created for each employee. For analysis purposes we want to know how many times this is being done.\nThis information is now logged in the CWSS Server process log files.\n\nTest hint(s):\n1. Verify a planboard can be opened in the win32 client","","OSDCOMMAIN-12643",""]
[null,null,1273652,"2019-11-29",null,"","Bug","","","Error in ESSApp 1.3.119 when creating new dutyWish when older AppServiceHandler is used","Duty wish could not be created when using latest app connected to an older version of server. Fixed this backwards compatibility issue. \n\nTest hints:\n1. Download latest client version for both iOS and Android. \n1. You need two environments: one that has latest changes/patch applied, and one that doesn't.\n2. For both environments schema validation setting from CSCS should be enabled.\n3. Test if duty requests can be successfully created from both platforms. ","","OSDCOMMAIN-12651","11243428"]
[null,null,1273652,"2019-11-29",null,"","New Feature","Functionality","Client","Several translations added for German Language","Several translations have been added for German for recent functional changes.\n\nTest hint(s):\n1. None ","","OSDCOMMAIN-12673",""]
[null,null,1273652,"2019-11-29",null,"","New Feature","Reliability","Miscellaneous","Central department shifts were not visible in ORTEC WS for Employees","Central department shifts were not visible in ORTEC WS for Employees. \nThis has been fixed.\n\nTest hint(s):\n1. Assign a shift to an employee through central department and verify that the shift is visible in ORTEC WS for Employees.","","OSDCOMMAIN-12674","11263230"]
[null,null,1273652,"2019-11-29",null,"","New Feature","Functionality","Client","Several translations added for Danish, Finnish and French Language","Several translations have been added for Danish and Finnish language for recent functional changes.\n\nTest hint(s):\n1. None ","","OSDCOMMAIN-12696",""]
[null,null,1273652,"2019-11-29",null,"","Bug","","","Several translations added for French, Danish, German and Finnish","Several translations have been added for French, Danish, German and Finnish for recent functional changes.\n\nTest hint(s):\n1. None","","OSDOWSD-3233",""]
[null,null,1273652,"2019-11-29",null,"","New Feature","Reliability","Optimization","The shift sequence planner does not start a sequence for an employee if it cannot be finished in the next scheduling period due to already planned shifts","The shift sequence planner did not take vacations into account that were already planned in the next scheduling period.\nThis has been fixed. Now, the shift sequence planner does not start a shift sequence for an employee, if that sequence has to be continued in the next scheduling period and the employee has already some other shifts on those days.\n\nTest hints:\n1. Run the shift sequence planner and verify that shifts are assigned to employees.","","OSDOWSD-3249",""]
[null,null,1273652,"2019-11-29",null,"","New Feature","","","Included employee names of personal rotation units in the hint text of shift counters and vertical calculations in the cyclical schedule","The name of the employee has been added to the hint text of vertical calculations and shift counters in the cyclical schedule when a relevant shift is assigned to a personal rotation unit. \n\nTest hint(s):\n1: Check the hint text of vertical calculations in the cyclical schedule","","OSDOWSD-3262",""]
[null,null,1275484,"2019-12-05",null,"","New Feature","Functionality","Client","Several translations added for French Language","Several translations have been added for French language for recent functional changes.\n\nTest hint(s):\nNone","","OSDCOMMAIN-12699",""]
[null,null,1275484,"2019-12-05",null,"Ad Hoc Planning","New Feature","Functionality","BackendDomainsAPI","[Translations] Update Finnish translations","Some texts in Ad Hoc Planning were shown in English.\nThis has been fixed. Now, Finnish texts are also available.","The BackendDomainsApi needs to be updated in order to use the new Finnish translations.","OSDOWSD-3432",""]
[null,null,1278387,"2019-12-12",null,"","Bug","","","App self scheduling displayed an error when employee was borrowed","When opening self scheduling, the app was displaying an error if the employee was borrowed.\nThis has been fixed.\n\nTest hint(s):\n1. Check that when opening self scheduling the schedule is loaded correctly if the employee is borrowed.","","OSDCOMMAIN-12552","11051249"]
[null,null,1278387,"2019-12-12",null,"","New Feature","Technical","Logging","Show correct memory usage for 'HarmonyPMHost' lines logged by OWS Server processes","When the OWS server processes logged memory usage as 'HarmonyPMHost' in the logfile, the memory usage value could be negative when more than 2Gb was used.\nThis has been fixed.\nWhen the OWS server processes logs memory usage as 'HarmonyPMHost' higher than 2Gb this is logged correctly as a positive number\n\nTest hint(s):\n1. verify OWS server processes start and shutdown correctly.","","OSDCOMMAIN-12646","11238882"]
[null,null,1278387,"2019-12-12",null,"","Bug","","","Push notifications arrive without sound on iOS devices","Push notifications arrive without sound on iOS devices.\nThis has been fixed.\n\nTest hint(s):\n1. Check that when a notification is received a sound alert is triggered.","","OSDCOMMAIN-12717","11336072"]
[null,null,1278387,"2019-12-12",null,"","New Feature","","","Employees with ending contracts were not always visible in the employee picker in the account window for valid dates","Employees with ending contracts were not always visible in the employee picker in the account window for valid dates.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that an employee, whose contract has ended, is visible in the employee picker in account window when from/to date is changed to a date when the employee's contract was valid. ","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12730","11345582"]
[null,null,1278387,"2019-12-12",null,"","New Feature","Functionality","Client","Several translations added for German Language","Several translations have been added for German for recent functional changes.\n\nTest hint(s):\n1. None ","","OSDCOMMAIN-12736",""]
[null,null,1278387,"2019-12-12",null,null,"New Feature","","","Technical changes for future improvement to make it possible to automatically check the leave balance of an employee when entering or adjusting a leave request in ORTEC WS for Employees.","Technical changes for future improvement to make it possible to automatically check the leave balance of an employee when entering or adjusting a leave request in ORTEC WS for Employees.\n\n1. Added new back-end route checkLeaveRequestBalance\nThe back-end route checkLeaveRequestBalance calls the command handler CCheckLeaveBalance with the given leave request as input. The response of the command handler is the response of the back-end route.\n\n2. Added new command handler CCheckLeaveBalance\nThe command handler CCheckLeaveBalance calculates the balance of an account including the imported or updated leave request. If the balance is larger or equal to zero, the command handler returns 'OK'. Otherwise the command handler returns 'Failed', including an information message. \nThe account to calculate the balance of, and the period to calculate can be configured:\n  * The account can be linked to an activity type for which 'Relevant for leave' is true. This account can be set in the 'Activity type'-tab in the Organization window. The account which is linked to the activity type of the leave request is used for calculation of the balance.\n  * The period to calculate the balance of, is derived from the department periods defined on the root department\n      - A new setting should be added 'WISH/LEAVEWISH/PERIODTYPEIDFORCHECKINGLEAVEBALANCE' in which the id of the period type to check can be set\n      - All department periods of the given type which overlap with the leave request are used for calculation of the balance\n\nNote 1: If the leave request does (partly) not overlap with a department period, the balance can not be calculated and an error is returned.\nNote 2: If the activity type of a leave request is not linked to any account, the command handler will return 'OK'.\nNote 3: If the period type id is not set correct (empty, incorrect id), the balance can not be calculated and an error is returned.\nNote 4: The imported leave request is not actually created or updated, this information is only used to calculate the new leave balance on the account and to verify whether it is possible to add this leave request based upon the new balance.\n\n3. Added server setting UseCheckLeaveBalance\nIf UseCheckLeaveBalance is true, the command handler CCheckLeaveBalance calculates the balance of an account for one or more department periods. Otherwise, the command handler will not calculate anything and return 'OK'.\n\nTest hint(s):\nNone","","OSDOWSD-3342",""]
[null,null,1281023,"12-19-2019",null,null,"Bug","","","Firebase notifications error/crash","If an error occurred when a notification file was processed, the notification would not be deleted from the folder, triggering a loop.\nThis was fixed. \n\nTest hint(s):\n1. Make sure that when a notification file is generated in designated folder for FirebaseMobileApi it is processed successfully. \n2. A notifications should be received on the device if the user is logged in with appropriate credentials.  ","","OSDCOMMAIN-12671","11261244"]
[null,null,1281023,"12-19-2019",null,"","",null,null,"Initials of sick employees were not displayed in MSS.","Sickness window In ORTEC WS for Managers did not show full names of sick employees. This has been improved. \n\nTest hint(s):\n1. Verify that names of sick employees are shown with initials and prefixes included. ","","OOBA-401","11069745"]
[null,null,1284554,"2020-01-09",null,"","",null,null,"Changed information of several settings for ORTEC WS for Managers in CSCS","Changed description of several settings for ORTEC WS for Managers in CSCS.\nTest hint(s):\n1. None","","OOBA-402",""]
[null,null,1284554,"2020-01-09",null,"","",null,null,"\"Overview of Leave Requests\" showed leave requests of wrong departments ","When a user opened \"Overview of Leave Requests\" of a department \"DepX\" in Win32 client, he received all leave requests from all the departments that contained \"DepX\" in their names. \nThis has been improved.\n\nTest hint(s):\n1. Verify that \"Overview of Leave Requests\" form displays leave requests of employees of the selected department. ","","OSDCOMMAIN-12575","11078490"]
[null,null,1284554,"2020-01-09",null,"Reliability","Optimization",null,null,"When external optimizer loaded wishes it did not initialize those loaded wishes correctly","When external optimizer loaded wishes it did not initialize those loaded wishes correctly.\nWhen the wishes were loaded all the properties that could be set by a planner were initialized only to the default values.\nAny saved changes on these properties for wishes the planner adjusted (or user via self scheduling) for specific employees were not taken into account.\nResulting in not correctly optimized schedules.\nThis has been fixed.\nThe wish properties are loaded and initialized correctly when starting an external optimizer.\n\nNOTE: When using the internal optimizer all wishes were loaded correctly on server startup.\n\nTest hint(s):\n1. Verify the schedule optimizer can be started externally and optimizes the schedule.\n","","OSDCOMMAIN-12764","11372948"]
[null,null,1284554,"2020-01-09",null,"","",null,null,"Shifts open for bidding during the night could not be picked in ORTEC WS for Employees","Shifts open for bidding during the night could not be picked in ORTEC WS for Employees. Timezones were not taken into account correctly. This has been fixed.\n\nTest hint(s):\n1. Verify an employee can pick shifts open for bidding in ORTEC WS for Employees.","","OSDOWSD-3019",""]
[null,null,1284554,"2020-01-09",null,"Reliability","Self scheduling",null,null,"A preference for a shift \"open for bidding\" during the night was created on the wrong date in ORTEC WS for Employees","A preference for a shift \"open for bidding\" during the night was created on the wrong date in ORTEC WS for Employees. Timezones were not taken into account correctly. This has been fixed.\n\nTest hint(s):\n1. Verify an employee can enter shift preference in ORTEC WS for Employees.","","OSDOWSD-3020",""]
[null,null,1284554,"2020-01-09",null,"","",null,null,"Non-standard time separators were not supported","In case a customer used a non-standard time separator, the integration of shifts to Shift Offering could not be done. \nThis has been fixed.\nNow, also non-standard separators like . can be used.\n\nTest hint(s):\n1. Plan a shift in the win32 client and offer it using the Ad Hoc planning UI.\n","","OSDOWSRES-14",""]
[null,null,1284554,"2020-01-09",null,"Configuration","Utilities",null,null,"Starting to use shift offering required a restart of all CWSS servers","It was not possible to start using Shift Offering without restarting the CWSS servers.\nThis has been improved.\nAfter installing this CWSS server update, synchronization can be started by sending the request <start /> to the command handler /hmy/server/integration/CStartIntegrationServerUpdateForAllServers from CSCS . \n\nTest hint(s):\n1. None","","OSDOWSRES-15",""]
[null,null,1284554,"2020-01-09",null,"Performance","Service",null,null,"[CWSS] Cannot stop server while handling integration server updates","In case of a large backlog in the syncing process, we could no longer stop the servers normally. This has been fixed.\n\nTest hint(s): \n1. Create a shift in the win32 client and verify it can be offered from the Ad Hoc Planning.","","OSDOWSRES-7",""]
[null,null,1284554,"2020-01-09",null,"Reliability","Service",null,null,"Refreshing IDP metadata often caused other calls to wait","Refreshing IDP metadata often caused other calls to wait. This has been improved. Now the refresh of the IDP metadata does not cause other calls to wait. \n\nTest hint(s): \nNone",null,"OSDOWSRES-18"]
[null,null,1287099,"2020-01-16",null,null,"Bug","Technical","Database","When stored procedure sp_WaitForDtcCommit timed out, the message shown to the user could show information of another customer","When stored procedure sp_WaitForDtcCommit timed out, the message shown to the user could contain information of another customer.\nThis has been improved.\nInstead of the database name (that could contain the or parts of a customer name) the database id is shown in the message when such a time out occurs.\n\nTest hint(s):\n1. Verify changing status of a plan board succeeds works.","","OSDCOMMAIN-12544",""]
[null,null,1287099,"2020-01-16",null,null,"Bug","Stability","Client","Your Login session is no longer valid, the application will be terminated was shown when manual export/import took too long","When exporting and importing from OWS client takes longer than 30 minutes, a message has been added to let the user know that the login session is no longer valid. This message appears after the export or import is completed.\n\nTest hint(s):\n1. In the event that an export or import takes longer than 30 minutes, verify that a message appears after the export or import is completed. After that the user needs close the application and re-login.","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12564","11051511"]
[null,null,1287099,"2020-01-16",null,null,"Bug","Reliability","Calculation","Labor rule \"Number of on call shifts\" did not check status of the schedule when adding a violation","The Labor Rule \"Number of on call shifts\" did not check status of the schedule when adding a violation. This could lead to the situation when violation occurs in the schedule with status which is not allowed by the configuration of the rule. This has been fixed.\n\nTest hint(s):\n1. Check that the labor rule \"Number of on call shifts\" shows expected violations in proper schedule statuses.","","OSDCOMMAIN-12569","11068797"]
[null,null,1287099,"2020-01-16",null,null,"Bug","Reliability","Interfaces","Error logging in HTTPGET_OLE/CLR function does not work","Error logging in HTTPGET_OLE function did not work.\nThis has been improved.\n\nTest hint(s):\n1. None ","","OSDCOMMAIN-12570","11069725"]
[null,null,1287099,"2020-01-16",null,null,"Bug","Reliability","Client","Saving a settings in two or more Win32 clients simultaneously could cause access violations","Saving a settings in two or more Win32 clients simultaneously could cause access violations.\nThis has been improved.\nWhen saving a settings simultaneously the internal structure that holds the settings is better protected, this will cause the settings to be saved sequentially.\n\nTest hint:\n1. start multiple Win32 clients\n  a. save planboard settings with multiple clients for different users and verify the settings are save correctly (using OWS settings manager)\n\n","","OSDCOMMAIN-12582","11083253"]
[null,null,1287099,"2020-01-16",null,null,"Bug","Performance","DataWarehouse","Added indexes on FACT_PROPERTY_VALUE table in BI HDM database","Querying data from FACT_PROPERTY_VALUE in the BI HDM database was found slow.\nThis has been improved.\nBy adding Indexes on FACT_PROPERTY_VALUE table in BI HDM database.\n\nTest hints:\n1. Verify historical load and incremental load for BI succeed","","OSDCOMMAIN-12597","11110296"]
[null,null,1287099,"2020-01-16",null,null,"Bug","Performance","Calculation","The 'Number of violations' criterium created calculation statistics for all future scheduling periods and resources, even when a scheduling period is not relevant for the resource given future violation settings","The 'Number of violations' criterium created calculation statistics for all future scheduling periods and resources, even when a scheduling period is not relevant for the resource given future violation settings. This has been improved. Only scheduling periods which are relevant for the resource, given future violation settings are checked.\n\nTest hint(s):\n1. Verify the 'candidates for shift' for a shift can be requested in a schedule.","","OSDCOMMAIN-12636",""]
[null,null,1287099,"2020-01-16",null,null,"Bug","Performance","Calculation","When using 'Number of violations' or 'Balance of account category' criterium a lot of memory was used during calculations","When using 'Number of violations' or 'Balance of account category' criterium a lot of memory was used during calculations.\nDuring analysis of OSDCOMMAIN-11742 it was found that when calculating the same employee over different schedules the same account category structure is used.\nThis has been improved.\nWhere we can during calculations for the same employee and multiple schedules we share a resource that is in memory. This reduces the memory pressure during above mentioned calculations.\n\nTest hint(s):\n1. Verify in win32 client that 'candidates for shift' works.\n2. Verify in win32 client that planboard with calculations based on account categories can be opened correctly.","","OSDCOMMAIN-12645",""]
[null,null,1287099,"2020-01-16",null,null,"Bug","","","Some relevant shifts were not loaded in the memory of export server when doing exporting of running accounts values.","Not all relevant shifts were loaded in the memory of export server when doing exporting of running accounts values for the period outside of the buffered history. This could lead to incorrect values in exported running accounts. This has been improved.\n\nTest hint(s):\n1. None.","","OSDCOMMAIN-12697",""]
[null,null,1287099,"2020-01-16",null,null,"Bug","Configuration","Manager self-service","Updated default values for NoWorkTreatment setting for ORTEC WS for Managers","Updated default values for NoWorkTreatment setting for ORTEC WS for Managers.\nThe treatment VACATION has been added has default.\n\nNOTE: For existing customers that had the default configured this will mean that VACATION will also be added to the current configured setting.\n\nTest hint(s):\nNone.","","OSDOMSSWEB-489",""]
[null,null,1287099,"2020-01-16",null,null,"Bug","","","A realisation was not correctly saved while the summer hour was active","A realisation was not correctly saved while the summer hour was active.\nThis has been fixed.\n\nTest hints(s):\n1. Check that if setting UseServerDateTimeOffset is on, the shift realisation is correctly saved if the summertime hour is active.\n2. Check that if setting UseServerDateTimeOffset is on, the shift realisation is correctly saved if the wintertime hour is active.","","OSDOWSESS-1686",""]
[null,null,1287099,"2020-01-16",null,null,"Bug","","","Refreshing IDP metadata often caused other calls to wait","Refreshing IDP metadata often caused other calls to wait.\nThis has been improved.\nNow the refresh of the IDP metadata does not cause other calls to wait.\n\nTest hint(s):\n1. None","","OSDOWSRES-18",""]
[null,null,1289443,"2020-01-23",null,null,null,"Security","Security","Users could not be authenticated because ORTEC Identity Gateway did not support the new SameSite=None secure cookie settings.","Users could not be authenticated because ORTEC Identity Gateway did not support the new SameSite=None secure cookie settings required for upcoming Chrome 80 release\nChrome 80, planned to be released in February 2020, will treat cookies that have no declared SameSite value as SameSite=Lax cookies. Only cookies with the SameSite=None; Secure setting will be available for external access, provided they are being accessed from secure connections. \nFor more information see:\nhttps://blog.chromium.org/2019/10/developers-get-ready-for-new.html\nFor customers using ORTEC Identity Gateway in combination with SAML this could lead to users not being authenticated.\nThis has been resolved.\n\nTest hint(s):\n1. verify that users can login into ORTEC Workforce for employees using supported browsers.","","OSDCOMMAIN-12796","11438849"]
[null,null,1289443,"2020-01-23",null,null,null,"Reliability","Calculation","Leave request compensation rules did not take the global setting 'UseApprovalForWish' into account","The Leave request compensation rules \nThe leave request compensation rules 'Variable entry for leave request ' and 'Fixed entry for leave request per calendar day' (introduced in OSDOWSD-3222 and OSDOWSD-3218) did not take into account UseApprovalForWish globalsetting.\nThis has been fixed.\nThe leave request compensation rules do take into account the UseApprovalForWish globalsetting\n\nTest hint(s):\n1. Verify bookings for 'Fixed entry for leave request per calendar day' and 'Variable entry for leave request'  given the UseApprovalForWish global setting configuration for the cases below:\n  - a leave request with status 'open' is booked when UseApprovalForWish=False\n  - a leave request with status 'concept approved' is not booked when \nUseApprovalForWish=True and rule is configured to book only when status is 'approved'.\n\n\n","","OSDCOMMAIN-12809",""]
[null,null,1289443,"2020-01-23",null,null,null,"Functionality","Client","Several translations added for Danish, German, Finish and French Languages","Several translations have been added for Danish and Finnish language for recent functional changes.\n\nTest hint(s):\n1. None ","","OSDCOMMAIN-12829",""]
[null,null,1289443,"2020-01-23",null,null,null,"Reliability","Manager self-service","Employee was counted more than once in Insights in ORTEC WS for Managers","Employee was counted more than once in Insights in ORTEC WS for Managers when it was borrowed mulitple times in a period. This has been fixed.\n\nTest hint(s):\n1. Verify in Insights in ORTEC WS for Managers","","OSDOMSSWEB-969","10968214"]
[null,null,1289443,"2020-01-23",null,null,null,"","","Change information message of checkleavebalance","The message that appears when a user requests more leave than available has been improved.\nTest hint(s):\n1. None","","OSDOWSD-3509",""]
[null,null,1289443,"2020-01-23",null,null,null,"Functionality","Import / Export","Added new queue export filter 'ShiftSubcontractedQueueFilter'","A new filter ShiftSubcontractedQueueFilter has been added for queue export that is able to filter shift records, so that only subcontracted shifts with an ‘active’ subcontract will be exported. \nAn ‘active’ subcontract means that the shift is subcontracted to another department and the subcontract status is neither declined nor cancelled.\n\nAn optional parameter, 'receivingdepartmentcodes' can be added to define one or multiple department codes which can be used in the filter. If a shift has an active subcontract to one of these departments, it is included in the queue export. Otherwise it is filtered out. Note that multiple department codes should be separated by a semi-colon (;).\n\nExamples:\n1. <ShiftSubcontractedQueueFilter/>\n2 <ShiftSubcontractedQueueFilter receivingdepartmentcodes=\"\"/>\n3. <ShiftSubcontractedQueueFilter receivingdepartmentcodes=\"depcode1\"/>\n4. <ShiftSubcontractedQueueFilter receivingdepartmentcodes=\"depcode1;depcode2\"/>\n\nTest hint(s):\n1. Verify the new filter can be used in the configuration of export queues.\n","","OSDOWSD-3522",""]
[null,null,1291461,"2020-01-30",null,null,"New Feature","","","Maximum labor-time based on account balance rule caused violations when the optimizer in OWS client is used.","In employee condition, the rule 'maximum labor-time based on account balance' caused unexpected violations when the optimizer in OWS client is used. This has been fixed. \n\nIn order to get optimized schedules with the least number of violations, \nin employment conditions 'Labor time on shifts' based on rule type 'maximum labor-time based on account balance' \nthe checkbox 'This balance depends on the shifts in the period .... ' \nmust be checked.\n\nTest hint(s):\n1. Check the box; Un-assign all shifts and plan vacant shifts in the optimizer. \n2. Verify that there are less violations\n","","OSDCOMMAIN-12798","11442333"]
[null,null,1291461,"2020-01-30",null,null,"New Feature","Reliability","Import / Export","Separator for multiple department codes in the subcontracted shift export queue filter changed from semi-colon to comma","Separator for multiple department codes in the subcontracted shift export queue filter changed from semi-colon to comma. This has been changed to handle department codes containing a semi-colon correctly.\n\nThe export queue filter for multiple departments should be called as \n<ShiftSubcontractedQueueFilter receivingdepartmentcodes=\"depcode1,depcode2\"/>\n\nTest hint(s):\n1. Verify the new filter can be used in the configuration of export queues.","","OSDOWSD-3572",""]
[null,null,1293744,"2020-02-06",null,null,"Bug",null,null,"The Firebase API dashboard value of \"Is Google Firebase api accessible?\" was false","The Firebase API dashboard value of \"Is Google Firebase api accessible?\" was false. However, notifications were send correctly.\nThis has been fixed.\n\nTest hint(s):\n1. Check that when browsing the FirebaseApi site the \"Is Google Firebase api accessible?\" value is true.","","OSDCOMMAIN-12769","11392825"]
[null,null,1293744,"2020-02-06",null,null,"Epic",null,null,"Added new functionality for automatically creating a leave shift after approval of a leave request","A new functionality of creating a leave shift after the approval of a leave request has been implemented. This functionality is configurable for the whole organization in OWS Settings Manager.\nNew settings have been implemented in WISH\\LEAVEWISH path of OWS Settings Manager.\n\nIn order to enable this functionality, WISH\\LEAVEWISH\\USEPROCESSLEAVEALGORITHM should be set to Y.\n\nThe leave shifts are created based on one of the four following configurations. These configurations represent which pattern should be followed when leave shifts are created. Configurations:\n1. ContractHours\n2. WorkPattern\n3. CyclicalSchedule\n4. ReplaceExistingShifts\n\nThe configurations above can be set up for each of the two following settings:\n1. WISH\\LEAVEWISH\\LEAVEPROCESSTYPEPLANNING (For schedules with status: Plan, Default configuration: ContractHours)\n2. WISH\\LEAVEWISH\\LEAVEPROCESSTYPEPUBLISHED (For schedules with status: Published or higher, Default configuration: ReplaceExistingShifts)\n\nNote 1: When setting, WISH\\LEAVEWISH\\APPLYLEAVEFORPARTIALSHIFT is set to Y and leave requests are made with 'Take leave for part of shift' checkbox checked, only ReplaceExistingShifts configuration will be applied, irrespective of configurations in settings: LEAVEPROCESSTYPEPLANNING and LEAVEPROCESSTYPEPUBLISHED. \nNote 2: When 'Take leave for part of shift' checkbox is checked and a leave request longer than 24 hours has been made, no leave shifts will be created.\n\nTest hint(s):\n1. Turn the relevant settings on and configure them as mentioned above.\n2. Create leave requests (and approve in case UseApprovalForWish is turned on)\n3. Verify that leave shifts corresponding to the configurations above have been created.","","OSDOWSD-3458",""]
[null,null,1296263,"2020-02-13",null,null,"New Feature","Technical","Import/Export","Calculating the number of days in February for leap years was not done correctly by the date:difference stylesheet function.","Calculating the number of days in February was not done correctly for leap years.\nWhen the date:difference function was used in a xsl-stylesheet transformation for the number of days did not take into account leap years correctly for the number of days in February.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that date:difference library function in xsl-stylesheet transformation works and gives the expected results.","","OSDCOMMAIN-12831","11454103"]
[null,null,1296263,"2020-02-13",null,null,"New Feature","Reliability","Self scheduling","When entering actuals with multiple new activities and different activity properties in OWS for Employees wrong values were applied.","When entering actuals with multiple new activities and different activity properties in OWS for Employees wrong values were applied.\nThis has been fixed.\n\nTest hint(s):\n1. Verify OWS for Employees that actuals can be entered.","","OSDCOMMAIN-12857","11484620"]
[null,null,1296263,"2020-02-13",null,null,"Bug","","","ESS Mobile App: receiving notifications with unexpected datetime format could crash the app","Receiving notifications with unexpected datetime format could crash the app.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that notifications are received correctly","","OSDCOMMAIN-12873",""]
[null,null,1296263,"2020-02-13",null,null,"New Feature","Reliability","User Interface","Translations added for German and French","Several translations have been added for French and German language for recent functional changes.\n\nTest hint(s):\n1. None ","","OSDOWSD-3591",""]
[null,null,1299185,"2020-02-21",null,"","New Feature","Functionality","Tools","Added the possibility to add or update global variables for existing message hub configuration using the ComtecConfig commandline tool","It was not possible to update or add global variables for existing message hub configuration in the ComtecConfig commandline import.\nThis has been improved.\nNow it is possible to add a parameter '/include=*.gcp' to the commandline import, so that the current configuration is updated with the new global variables. Existing global variables are updated and new global variables are added. This also holds for environment-specific variables.\n\nNote: it is only possible to import one .gcp-file in the configuration file at the time to avoid multiple overrides of the same global variable.\n\nTest hint(s):\n1. Run 'comtecconfig /e=default /verbose /import /mh /include=*.gcp' and check in ORTEC System Configuration that the current message hub configuration is updated correctly.","","OSDCOMMAIN-12686",""]
[null,null,1299185,"2020-02-21",null,"","New Feature","Stability","Calculation","An error was shown when shifts overlapped between scenario and schedule","In Win-32 client an error was shown when opening a scenario which has shifts overlapping with night shifts of previous schedule. This happened only when some labor rules used \"Labor Period Definition\". This has been fixed. \n\nTest hint(s):\n1. Verify that no errors are shown when opening a scenario with shifts overlapping with night shifts of previous schedule.","","OSDCOMMAIN-12687",""]
[null,null,1299185,"2020-02-21",null,"","New Feature","","","Activities of shifts in MSS were not always sorted according to the begin time","In ORTEC WS for Managers activity details of shifts and employee realizations were not always sorted according to the begin time. This has been improved.\n\nTest hint(s):\n1. None. ","","OSDCOMMAIN-12731","11345934"]
[null,null,1299185,"2020-02-21",null,"","New Feature","","","The clocking rounder rules did not consider the value for the selected employee property","The clocking rounder rules did not consider the value for the selected employee property. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that rounding is done only when the employee property value of an employee matches with the selected employee property value in the clocking rounder rule.","","OSDCOMMAIN-12742","11357493"]
[null,null,1299185,"2020-02-21",null,"","New Feature","","","Performance of loading shifts for customers using global setting UseAlwaysSaveOriginalShiftWhenApplyingLeave has been improved","For customers using global setting UseAlwaysSaveOriginalShiftWhenApplyingLeave the \"shift loading mechanism\" had been improved.\n\nTest hint(s):\n1. Verify a plan board can be opened with a begin date e.g week before the configured BUFFEREDHISTORY so data is loaded when planboard is opened\n2. Verify an external optimizer can be run","","OSDCOMMAIN-12892","11566844"]
[null,null,1300287,"2020-02-25",null,"","New Feature","","","Labor rule \"Maximum number of working days in department period\" did not check status of the schedule when calculating violations","The Labor Rule \"Maximum number of working days in department period\" did not check status of the schedule when calculating violations. This could lead to the situation when violation occurs in the schedule with status which is not in scope by the configuration of the rule. This has been fixed.\n\nTest hint(s):\n1. Check that the labor rule \"Maximum number of working days in department period\" shows expected violations in proper schedule statuses.","","OSDCOMMAIN-12610","11146195"]
[null,null,1300287,"2020-02-25",null,"","New Feature","Reliability","Planboard","Personal plan board did not show shifts when employee has multiple contracts","When employee has multiple contracts and the contract with the latest end date has no shifts, then personal plan board did not show shifts. \nThis has been fixed.\n\nTest hint(s):\n1. Verify when an employee has multiple contracts  and the contract with the latest end date does not have any shifts, then all the shifts of the employee are visible in the personal planboard.","","OSDCOMMAIN-12689","11283634"]
[null,null,1300287,"2020-02-25",null,"","New Feature","Reliability","Calculation","Labor rule \"Shift series\" did not check consecutive shifts correctly when calculating violations","Labor rule \"Shift series\" did not check consecutive shifts correctly when calculating violations. This has been fixed. Shift are now only considered as consecutive when there is a rest of less than 32 hours between them.\n\nTest hint(s):\n1. Check that the labor rule \"Shift series\" shows expected violation.","","OSDCOMMAIN-12741","11357338"]
[null,null,1300287,"2020-02-25",null,"","New Feature","Functionality","Tools","Added the possibility to only upload system reports in PostInstall","It was not possible to upload only system reports via PostInstall or CSCS. This has been improved.\nA checkbox 'Overwrite only system reports' (default checked) has been added to the part of 'Upload reports' in the PostInstall. \n\nTest hint(s):\n1. Verify reports can be uploaded adjusted in both CSCS and PostInstall.","","OSDCOMMAIN-12746",""]
[null,null,1300287,"2020-02-25",null,"","New Feature","Reliability","Reporting","Overview 'Shift reassignment' did not show correct name of shift","Overview 'Shift reassignment' did not show correct name of shift. When updating the name of a shift in a published scheduling period, only the new name was visible in the overview when UseDutyExchanges is switched on. This has been fixed.\n\nTest hint(s):\n1. Verify the overview 'Shift reassignment' shows the correct shift names ","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12748","11360307"]
[null,null,1300287,"2020-02-25",null,"","New Feature","Stability","Calculation","When refreshing the clockings in the Clock Times window an Access Violation could occur","When refreshing the Clock Times window an Access Violation could occur.\nThe change in OSDCOMMAIN-12742 could cause this Access Violation when a clocking did not have a shift.\nThis has been fixed.\nThe Clock Times window can be refreshed properly\n\nTest hint(s):\n1. Verify the Clock Times window can be refreshed properly when interval used contains clockings with and without association to a shift.","","OSDCOMMAIN-12900","11582813"]
[null,null,1300287,"2020-02-25",null,"","New Feature","","","Command Handler to start External Planner did not support the option to 'Always respect wishes'","The command handler CRunExternalPlanner (that can be used to start external planner server) did not take resource wishes into account. This has been improved. Now it also supports the option to always respect all wishes not to work. Add the tag <wishesAreRequired> with value \"true\" to use this.\n(Note: See earlier release notes for issues OSDOWSD-2005 and OSDOWSD-2327)\n\nTest hint(s): \n  1) Use the handler to start the external planner server with the new tag set to true and verify that all wishes not to work are satisfied.","","OSDOWSD-3491",""]
[null,null,1300287,"2020-02-25",null,"","Bug","Reliability","Client","Add German translations for optimizer","Added several German translations for the optimizer\n\nTest hint(s):\nNone",null,"OSDOWSD-3605",""]
[null,null,1303281,"2020-03-05",null,"","New Feature","","","Master schedule ESS report showed schedules in status planning","Master schedule ESS report showed schedules in status planning in Employee Self Service. It has been fixed.\nTest hint(s):\n1. Assign a shift to an employee in a schedule with status plan and verify in Employee Self Service that the shift and the schedule with status plan are not shown in Master schedule ESS report.","","OSDCOMMAIN-12620","11171002"]
[null,null,1303281,"2020-03-05",null,"","New Feature","Reliability","Logging","Error message from OIDC tokenvalidation in logging was not very informative","Error message from OIDC tokenvalidation in logging was not very clear. This has been approved. When the audience(s) in the token does not correspond to the required audience, quotes are added to the audiences.\n\nTesthint(s):\n1. Verify that a user can login into OWS for Employees","","OSDCOMMAIN-12692","11295659"]
[null,null,1303281,"2020-03-05",null,"EP4","New Feature","","","An error occurred during saving a compensation rule if there was a nested expression that contained period types in 'CONTRACTDAYSININTERVAL' identifier.","An error occurred during saving a compensation rule if there was a nested expression that contained period types in 'CONTRACTDAYSININTERVAL' identifier.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that it's possible to save a compensation rule with a nested expression that contained period types in 'CONTRACTDAYSININTERVAL' identifier. Make sure that the account, that is linked to your compensation rule, shows correct bookings.","","OSDCOMMAIN-12732","11345936"]
[null,null,1303281,"2020-03-05",null,"","New Feature","","","A setting has been added in violation checks to ignore activities with the same class as the one in the leave wish","In OWS Employee leave wishes can be configured to have associated activity. \nIf the leave wish was approved and an employee had a shift in the period of the leave wish, a violation was shown in two cases:\n1. The activity types of the shift are not equal to the activity type of the wish \n2. The activities do not have the same class of the activity of the leave wish (for instance leave, work etc). This should not also be the case. \nThis has been improved.\n \nA new setting \"wish\\leaveWish\\ConsiderOriginalActivityTypeForLeaveWish\" in OWS Settings Manager has been introduced to be able to differentiate between the two cases. If this setting is set to 'Y', only in case 1 a violation will be raised. If the setting is set to 'N', in both case 1 and 2 a violation will be raised. The default value is 'N' to make the change backwards compatible.\n\n\nTest hint(s):\n 1. Verify that a violation is shown or not based on the value of the setting.","","OSDCOMMAIN-12743",""]
[null,null,1303281,"2020-03-05",null,"","New Feature","Reliability","Installer","Back-end API queries were not all available in updates since first delivery of OWS 7","Back-end API queries were not all available in updates since the first delivery of OWS 7. This has been fixed.\nThe configuration of creating updates was extended with back-end API queries.\nThis means that when changes are done in one of those queries the update zip for back-end API queries will contain the latest version for each query.\n\n \tExternal Release Notes:\nBack-end API queries were not all available in updates since the first delivery of OWS 7. This has been fixed.\nThe configuration of creating updates was extended with back-end API queries.\nThis means that when changes are done in one of those queries the update zip for BackendAPIQueries will contain the latest version for each query.\n\nTest hints:\n1. Verify the delivered back-end API queries update zip can be used to update the delivered queries using the Patch Util","","OSDCOMMAIN-12768","11384718"]
[null,null,1303281,"2020-03-05",null,"","New Feature","Reliability","Win32 Userinterface","The reference field in the 'Carry over between accounts' window was not correctly translated.","The reference field in the 'Carry over between accounts' window was not correctly translated.\nThis has been fixed\n\n1. Verify that the ''Reference' field in the 'Carry over between accounts'  windows in the Win32 clients shows the correctly translated value.","For this solution to become available, the win32 client must be installed","OSDCOMMAIN-12888","11554065"]
[null,null,1303281,"2020-03-05",null,"","New Feature","Technical","GUI","Added build dates of the CWSS Server and the win32 client in 'about'-screen in the win32 client","Added build dates of the ORTEC WS Client and Server in 'Help About' - screen in the win32 client.\n\nTest hint(s): \nNone ","For this solution to become available, the win32 client must be installed.","OSDOWSD-3083",""]
[null,null,1306171,"2020-03-12",null,null,"Bug","","","The FirebaseAPI did not start when Identity Gateway was configured ","The FirebaseAPI did not start when ORTEC Identity Gateway was configured as Identity Provider for the ESSMobileApp.\nThis has been fixed.\n\nTest hint(s):\n1.Verify that the FirebaseApi dashboard is displayed correctly if ORTEC Identity Gateway is configured as Identity Provider.","","OSDCOMMAIN-12879","11544970"]
[null,null,1306171,"2020-03-12",null,null,"New Feature","","","Fixed workstation optimizer when demand was lowered in workstation plan board","Since October, the workstation optimizer plans the adjusted demand instead of the original demand in the demand is lowered from the plan board. However, this did not always work correctly due to rounding errors.\nThis has been fixed.\n\nTest hint(s):\n1. Lower the demand from the workstation plan board, run the workstation optimizer and verify that no overstaffing is created.","","OSDCOMMAIN-12898","11573351"]
[null,null,1306171,"2020-03-12",null,null,"New Feature","","","The version number of the Master Schedule ESS report file is updated","Master schedule ESS report had the wrong version number. This has been fixed.\nTest hint(s):\nNone","","OSDCOMMAIN-12928",""]
[null,null,1306171,"2020-03-12",null,null,"New Feature","Functionality","Planning","Leave shifts were not unassigned when unapproved for some leave request settings","Leave shifts were not unassigned when unapproved for some leave wish specific settings. This has been fixed.\n\nTest hint(s):\n1. Verify that a leave shift when unapproved is unassigned when any of the following settings in WISH\\LEAVEWISH path is set to Y.\ni. CreateNewLeaveShiftIfNoShiftExists\nii. CreateNewLeaveShiftBasedOnCyclicalSchedule\niii. UseProcessLeaveAlgorithm","","OSDOWSD-3634",""]
[null,null,1306171,"2020-03-12",null,null,"New Feature","Functionality","Optimization","Workstation Optimizer: Shuffle workstations and shifts based on date","In the workstation optimizer, we frequently search the best employee to occupy a workstation. When more than one employee was considered as the best option, it was highly likely that the same employee was selected every time.\nThis was not seen as a fair strategy and has been solved. \nIn case of a tie, now a random employee is selected. This randomness depends on the begin time of the period that is being scheduled, so that the result of the workstation optimizer is still reproducible, but also gives different results for different periods. \n\nTest hint(s): \n1. Run the workstation optimizer twice, for different days but with the same shifts and workstation demands and verify that the result is different.","","OSDOWSD-3641",""]
[null,null,1306171,"2020-03-12",null,null,"Epic","Functionality","Service","Added support for non-domain users when using Auth0","OWS is in the progress to use Auth0 as the identity provider of choice. \nAs a next step, a new cloud service has been launched that can synchronize the non-domain users from OWS into an Auth0 user database.\nThe users in this Auth0 user database can then login to our cloud applications without the need for Comtec Authentication.\n\nIn order for this synchronization to work, changes have been made to several parts of OWS server.\n1. CUAS/AccessControl:\n  It is now possible to specify the authentication provider 'Auth0 user database' for a user. Every user with this authentication provider enabled will be synchronized to Auth0 if the synchronization is enabled. Note that if this provider is selected, the username must be an email address.\n\n2. CWSS:\n  The user import has been updated, so it is possible to specify an authentication provider per user.\n\n3. BackendEventPublisher:\n  This CPMS process has been updated, to enable sending user changes to the cloud service. \n\n4. BackendDomainsAPI\n  The API has been extended to supply the user info that is needed to add or update users in Auth0.\n\nThe following configuration needs to be done by an Ortec consultant:\n- An Auth0 environment needs to be requested if that was not already done. \n- A tenant registration needs to be requested to connect the Auth0 environment with one or more OWS environments\n- The CSMS setting 'BackendEventPublisher\\URLs\\UserSynchronizationServiceURL' needs to be filled with the url of the syncrhonization service. \n\nTest hint(s):\n1. Verify users an authentication provider can be imported into CWSS and are visible in the Access Control website.\n2. Verify that in Access Control website, the authentication provider of a user can be changed.\n3. Verify that in Access Control website, the user name can be updated.","","OSDOWSRES-248",""]
[null,null,1310707,"2020-03-26",null,null,"New Feature","Functionality","Employee self-service","Multi-language module has been made available for ORTEC WS for Employees","Multi-language module has been made available for ORTEC WS for Employees. \n\nSeveral queries have been adjusted so the correct translations are retrieved. A list of the changed queries: (They can be found in CSCS under Query Manager):\n- Comtec.Workforce.BackendAPI/Portal/v2/ActivityDetailOfActiveDutiesByShiftIds\n- Comtec.Workforce.BackendAPI/Portal/v2/ActivityDetailOfPendingDuties\n- Comtec.Workforce.BackendAPI/Portal/v2/ActivityTypes\n- Comtec.Workforce.BackendAPI/Portal/v2/AllShifts\n- Comtec.Workforce.BackendAPI/Portal/v2/ApprovedOrHigherOrWithUnapprovedShifts\n- Comtec.Workforce.BackendAPI/Portal/v2/Departments\n- Comtec.Workforce.BackendAPI/Portal/v2/DepartmentsOfResource\n- Comtec.Workforce.BackendAPI/Portal/v2/DistinctDutyNames\n- Comtec.Workforce.BackendAPI/Portal/v2/DutyWishesByEmployee\n- Comtec.Workforce.BackendAPI/Portal/v2/GetRequirementList\n- Comtec.Workforce.BackendAPI/Portal/v2/GetScheduleParams\n- Comtec.Workforce.BackendAPI/Portal/v2/List/workstation\n- Comtec.Workforce.BackendAPI/Portal/v2/NextSchedule \n- Comtec.Workforce.BackendAPI/Portal/v2/OpenDutiesDemandsInInterval\n- Comtec.Workforce.BackendAPI/Portal/v2/PendingDutyToApprove\n- Comtec.Workforce.BackendAPI/Portal/v2/PreviousSchedule\n- Comtec.Workforce.BackendAPI/Portal/v2/RequestsByEmployee\n- Comtec.Workforce.BackendAPI/Portal/v2/ScheduleDataByDepartmentIds\n- Comtec.Workforce.BackendAPI/Portal/v2/ScheduleDataByResourceIds\n- Comtec.Workforce.BackendAPI/Portal/v2/ScheduleDataByScheduleId\n- Comtec.Workforce.BackendAPI/Portal/v2/ShiftsForDepartmentsInInterval\n- Comtec.Workforce.BackendAPI/Portal/v2/SpecialDuties\n- Comtec.Workforce.BackendAPI/Portal/v2/TemplateSpecialDuties\n- Comtec.Workforce.BackendAPI/Portal/v2/workstation\n\nNote: The translations can only be entered in the win32 client when the Multi-language module has been enabled.\n\nTest hint(s):\n1. Verify ORTEC WS for Employees can be logged into and language can be switched.\n2. Verify ORTEC WS for Managers can be logged into and language can be switched.","","OSDOWSD-3637",""]
[null,null,1310707,"2020-03-26",null,null,"New Feature","","","Removed feature toggle UseDetailsPlanningCostForm","The server setting: 'FeatureToggle\\UseDetailsPlanningCostForm' has been removed. This setting was introduced early 2019 to prevent that a client update was mandatory when the server was updated. \nSince this is more than a year ago, this is no longer needed and the setting could be safely removed. This functionality is now always enabled.\n\nTest hint(s):\n1. Verify that the window 'Details of planning costs' can be opened in case a calculation of the type 'Planning penalty for employee' is available in the Employee calculations grid.","","OSDOWSD-3648",""]
[null,null,1312966,"2020-04-02",null,"","New Feature","Security","Tools","DBAnonymize did not remove all privacy sensitive information from CPMS process configuration","DBAnonymize did not remove all privacy sensitive information from CPMS process configuration. This has been fixed.\n\nTest hint(s):\n1. Verify passwords and usernames are emptied in the parameter xml of processes after running DBAnonymize","","OSDCOMMAIN-12950",""]
[null,null,1312966,"2020-04-02",null,"Shift Offering","New Feature","Reliability","BackendDomainsAPI","Adhoc Violations do not show in Finnish language","In Ad Hoc Planning, the details of an employee who requested an offered shift and had a violation for working too many hours on a day, would show that there are no violations because there is no Finnish translation for this particular violation. This happened only in Finnish.\nThis has been fixed. Now, the default English violation text will be shown in case the Finnish translation is not available.\n\nNote that in the near future, when the missing Finnish translation is available, the violation will be shown in Finnish.\n\nTest hint(s):\n1. In Ad Hoc Planning, open the details of an employee that requested an offered shift and works too many hours on a day. Verify that the violation is shown.","","OSDOWSRES-233","11554797"]
[null,null,1312966,"2020-04-02",null,"Shift Offering","New Feature","Configuration","BackendDomainsAPI","[Backend]Create route to get shiftofferingintegrationsettings","Added functionality to use Comtec System Configuration to change the value of Integration service settings. From now on, the following settings are available in the Settings Manager and will be synchronized with the Integration service:\n\nShiftOffering\\Employees\\ZeroHourContractsCountAsOwnDepartment\nShiftOffering\\Employees\\AccountName_ForBalance\nShiftOffering\\Employees\\AccountCategoryName_ForBalance\nShiftOffering\\Employees\\UserPropertyName_ForEmployee_CanBeOfferedShift\n\nTesthint(s)\n1. Verify that the correct balance is shown for an employee that requested an offered shift.\n2. Verify that a shift is sent to the correct employees when offering it.","After installing this version, but before starting the BackendDomainsApi, the values of the following CSCS settings MUST be set:\n\nShiftOffering\\Employees\\AccountName_ForBalance\nShiftOffering\\Employees\\AccountCategoryName_ForBalance\nShiftOffering\\Employees\\UserPropertyName_ForEmployee_CanBeOfferedShift\n\nThese values will be used to determine the values of the current Integration service settings:\naccountCategoryId_ForAccountCategoryLines\nuserPropertyId_ForEmployee_CanBeOfferedShift\nThese settings in the Integration service will not be filled in manually anymore. The values will be retrieved from the values in CSCS. This also means that if the settings in CSCS do not have a value, or have a wrong value, that the balance for an employee in shift offering will not be shown correctly, and that the wrong/no/all employees might get a notification when a shift is offered.\n\n--\n  \nIn the near future, the default behavior of zero hour contracts will change. Previously, zero hour contracts were not counted as own department contracts. This will change to counting zero hour contracts for a department as own department contracts. To keep the previous behavior, it is important to set the following setting to 'False' already:\n\nShiftOffering\\Employees\\ZeroHourContractsCountAsOwnDepartment\n\n-- \n\nPlease be reminded that after changing a setting the Backend API will need to be restarted for the new settings values to take effect.","OSDOWSRES-49",""]
[null,null,1312966,"2020-04-02",null,null,"New Feature","Technical","BackendDomainsAPI","Logfile message of the Backend Domains Api was not indicating the employee id which had no rule set code","The message in the logfile of the Backend Domains Api was not indicating the employee id which had no rule set code.\nThis has been fixed.\nNow, if there is an employee without rule set code that has a response to an offered shift, this line will be shown in the logfile:\nEmployee with id: 1234 does not have a rule set code\n\nTest hint(s):\n1. In Ad Hoc Planning, open the details of an offered shift that has a response from an employee without rule set code. Verify that the logline is shown in the logfile of the Backend Domains Api.","For this functionality, it is needed to update the Backend Domains Api.","OSDOWSRES-171",11528004]
[null,null,1314295,"2020-04-09",null,null,"New Feature","Functionality","Miscellaneous","Windows 2019 is supported","Deploying OWS 7 on Windows 2019 is supported.","","OSDOWSD-3609",""]
[null,null,1314295,"2020-04-09",null,null,"New Feature","Reliability","Optimization","Workstation plan board raised an error when changing the workstation of subcontracted shifts","In workstation plan board an error was displayed when the property of a  fixed shift was adjusted.\nThis has been improved.\nNow the error is shown only in the case when shift is blocked. It is only possible to block a shift if the global setting 'UseBlockedShift' is set to true and permissions with 'SHIFT_TOGGLE_BLOCKED' enabled.\nNote that subcontracted shifts in the status 'final planning' are also fixed shifts.\n\nTest hint(s):\n  1. Verify that it is possible to adjust non-blocked shifts in the workstation plan board.\n  2. Verify that it is possible to adjust also a subcontracted shifts.","To be able to set the property 'blocked' of a shift, the global setting 'UseBlockedShift' and permissions with 'SHIFT_TOGGLE_BLOCKED' need to be enabled.","OSDOWSD-3666",""]
[null,null,1314295,"2020-04-09",null,null,"New Feature","Reliability","Optimization","Workstation optimizer did not plan any workstations on subcontracted shifts with status 'final planning'","Workstation optimizer did not consider the blocked shifts for planning and the subcontracted shifts with status 'final planning' were considered to be fixed. This lead to the problem of subcontracted shifts with status 'final planning' being ignored by the optimizer. This has been improved.\nThe workstation optimizer now takes into account all the non blocked shifts, instead of fixed shifts.\nIt is only possible to block a shift if the global setting 'UseBlockedShift' is set to true and and permissions with 'SHIFT_TOGGLE_BLOCKED' enabled.\n\nTest hint(s):\n1. Verify the workstation optimizer can assign a workstation to a regular non-blocked shift. \n2. Verify the workstation optimizer can assign a workstation to a subcontracted shift with status 'final planning'.  ","To be able to set the property 'blocked' of a shift, the global setting 'UseBlockedShift' and permissions with 'SHIFT_TOGGLE_BLOCKED' need to be enabled.","OSDOWSD-3667",""]
[null,null,1317128,"2020-04-16",null,"","New Feature","Performance","Database","Reading setting EMPLOYEEHISTORY for a department context on a permission could cause concurrency problems\n","Reading setting EMPLOYEEHISTORY for a department context on a permission could cause concurrency problems\n\nThe setting EMPLOYEEHISTORY is used to consider employees to be valid for certain permissions when using the\n IsInDepartment, IsLentToOrInDepartment and IsInAnyDepartment context specifiers.\nWhen this value is read for a large number of concurrent users at the same time, this could cause concurrency problems (e.g. deadlocks on the database).\nThis has been improved.\nThe EMPLOYEEHISTORY is read once and is cached for 2 hours per process.\nTest hint(s):\n1. Verify a non administrative user can login to either ORTEC WS for Employees, ORTEC WS for Managers or the win32 client.","","OSDCOMMAIN-12842","11467383"]
[null,null,1317128,"2020-04-16",null,"","New Feature","Reliability","Self scheduling","Employees could see entries in status planning Ortec WS For Employees irrespective of permissions","Employees could see entries in status planning Ortec WS For Employees irrespective of permissions. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that employee can only see entries if they have '/CWGS/OWS/ESS/runaccounts_plan' permission granted in Access Control and for that running account, 'Show entries in status planning to employee' in the options tab of the account in OWS Win32 client is checked.","","OSDCOMMAIN-12875",""]
[null,null,1317128,"2020-04-16",null,"","New Feature","Reliability","Win32 User Interface","An error occurred when creating a new clocking in the win32 client when the CWSS Server and the win32 client had different date and time format","When creating a new clocking in the win32 client, sometimes the following error was shown: 'Could not convert variant of type (UnicodeString) into type (Date)'. It only happened when the CWSS Server and the win32 client were installed on machines with a different date and time format.\nThis has been fixed.\n\nTest hint(s): \n1. Verify a new clocking can be created in the win32 client","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12882","11550140"]
[null,null,1317128,"2020-04-16",null,"","New Feature","Performance","Client","Time lag occurred when typing employee numbers in the search box of the employee management window","Time lag occurred when typing employee numbers in the search box of the employee management window. It has been improved.\nTest hint(s):\n1. Open the search box of the employee management window in the OWS WIn32 client and verify that typing employee numbers does not cause any lag.","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12944","11657015"]
[null,null,1317128,"2020-04-16",null,"","New Feature","Reliability","Optimization","Several translations added for German, Finnish, Danish and French","Several translations have been added for German, Finnish, Danish and French for recent functional changes. \n\nTest hint(s): \nNone","","OSDCOMMAIN-12978",""]
[null,null,1317128,"2020-04-16",null,"Integration service / Rescheduler","New Feature","Performance","Service"," Salary export with retroactive corrections blocks integration server updates","When using Ad Hoc Planning with Shift Offering, changes on OWS Server are communicated to the Integration Service for showing them in Adhoc Planning UI. \n\nActions that lead to many small changes on OWS, like a salary export with retroactive corrections, cause a lot of changes to be sent to the integration server. This leads to high network traffic which is not desired. This has been improved.\nChanges that are never relevant for Shift Offering are filtered out before they are sent to the Integration Service\n\nTest hint(s):\n1. Verify that setting a shift open for bidding in OWS client is shown as an offered shift in Ad Hoc Planning.","","OSDOWSRES-386","11550218"]
[null,null,1318933,"2020-04-23",null,"","New Feature","Reliability","Reporting","Added French translations for reports","French translations have been added for report parameters used in the OWS standard reports.\n\nTest hint(s):\n1. Verify the reports work from OWS for Employees and/or OWS win32 client\n","We have seen that just uploading and overwriting existing reports does not update report parameters. \nTo assure the report parameters are translated using these new translations it can be that the reports should first be deleted from the report server and then uploaded again using CSCS.\n","OSDCOMMAIN-12773","11396805"]
[null,null,1318933,"2020-04-23",null,"","New Feature","Reliability","Planboard","A borrowed employee was not shown in a schedule if he had a shift in the preview period only and was no longer valid in the actual scheduling period","A borrowed employee was not shown in a schedule if he had a shift in the preview period only and was no longer valid in the actual scheduling period. This has been fixed.\n\nFeature toggle INCLUDEDAYSOFHISTORYFORRELEVANTRESOURCES has been introduced and is by default TRUE \n \nTest hint(s):\n1. Verify that a borrowed employee who is valid in the preview period of a schedule but not valid during the scheduling period is shown in a schedule when the preview period for a schedule is enabled.\n\n","For this solution to become available the OWS win32 client must be installed.","OSDCOMMAIN-12864","11490427"]
[null,null,1318933,"2020-04-23",null,"","New Feature","Reliability","Interfaces","Import to lending plus normal group was not possible","Import to lending plus normal group was not possible. This has been fixed.\nTest hint(s):\n1. Verify that employee importing works.","","OSDCOMMAIN-12918","11593494"]
[null,null,1318933,"2020-04-23",null,"","New Feature","Security","Configuration","A permission, 'CREATE_OR_UPDATE_ALTERNATING_SHIFT' added for creating and updating alternating shifts","A permission, 'CREATE_OR_UPDATE_ALTERNATING_SHIFT' added for creating and updating alternating shifts.\nTest hint(s):\n1. Enable the permission, 'CREATE_OR_UPDATE_ALTERNATING_SHIFT', and the setting, 'UseAlternatingShift' verify that an alternating shift can be created or updated in a cyclical schedule.","","OSDCOMMAIN-12947","11669541"]
[null,null,1318933,"2020-04-23",null,"","New Feature","Reliability","Calculation","Reporting rule \"Carry over per cost center\" returned error when resource is switching a contract","Reporting rule \"Carry over per cost center\" returned error when resource is switching a contract. This has been fixed.\n\nTest hint(s):\n1. Verify two bookings are created by the reporting rule \"Carry over per cost center\" when there is a contract switch in the requested period","","OSDOWSD-3659",""]
[null,null,1320865,"2020-04-30",null,"","New Feature","Reliability","Calculation","Using remarks with special characters in clockings could cause \"JSON string is not proper JSON\" error","Using remarks with special characters in clockings could cause \"JSON string is not proper JSON\" error.\nThose special characters include (but are not limited to) \", [ , }\nThis has been fixed.\n\nTest hint(s):\n1. Verify that clockings can be add/updated/removed","For this solution to become available, the win32 client must be installed.","OSDCOMMAIN-12933","11641936"]
[null,null,1320865,"2020-04-30",null,"","New Feature","Stability","Calculation","Server error when calculating deeply nested reporting compensation rules","When reporting compensation rules needed to look back through too many nested calculations and the \"Entries for approved schedules known until\" date of the employee had a date far in the past, an error could occur that would halt the CWSS process.\nThis has been improved. \nA mechanism has been added for reporting compensation rules that will abort the calculation if too many levels of nested calculations are detected and an error is shown to the user. This mechanism is similar to the one used for normal compensation rules. \n\nTest hint(s):\n1. Verify the account entries on a reporting account.","","OSDCOMMAIN-12946",""]
[null,null,1320865,"2020-04-30",null,"","New Feature","Functionality","Client","Several translations added for German and French Language","Several translations have been added for French and German language for recent functional changes.\n\nTest hint(s):\n1. None ","","OSDCOMMAIN-12992",""]
[null,null,1320865,"2020-04-30",null,"","New Feature","","","New privacy mode for Master schedule ESS and Master Schedule Planner reports has been created","New privacy mode for Master schedule ESS and Master Schedule Planner reports has been created. \nThe following settings need to be created in the OWS Win32 client > Maintenance > Organization > Select Department > Department Properties to avail this privacy mode:\n'MasterScheduleESSprivacy' (Y/N input)\n'MasterScheduleprivacy' (Y/N input)\n'MasterScheduleabsencecode' (Text input)\n\nThis privacy mode will replace shifts with the activity treatments: 'COMPLEAVE','DAYOFF','ILLNESS','ILLNESSNL','ILLNESSNW','LEAVE','VACATION','VACATIONNL','VACATIONNW' with 'MasterScheduleabsencecode' (Default: 'A') in Master Schedule ESS and Master Schedule Planner reports.\n\nThis privacy mode is turned on by default for Master Schedule ESS and turned off for Master Schedule Planner.\n\nTest hint(s):\n1. Verify that a shift with any of the above mentioned activity treatment is replaced by 'MasterScheduleabsencecode' in the Master Schedule ESS and Master Schedule Planner reports when 'MasterScheduleESSprivacy' and 'MasterScheduleprivacy' are set to 'Y'.","In order to avail this functionality, Master Schedule ESS.rdl and Master Schedule Planner.rdl must be uploaded to CSCS or Report Server.","OSDOWSD-3604",""]
[null,null,1320865,"2020-04-30",null,"","New Feature","","","Unused PasswordEncryption in DBAnonymize has been removed","Unused PasswordEncryption in DBAnonymize has been removed.\nTest hint(s):\n1. Verify that DBAnonymize.exe works.","","OSDOWSD-3688",""]
[null,null,1322423,"2020-05-07",null,"","New Feature","Functionality","Calculation","Added a minimum (MIN) operator for 'Calculation based on other calculations' ","Added a minimum (MIN) operator for 'Calculation based on other calculations' which calculates the minimum of two calculations.\n\nTest hint(s):\n1. Verify that in 'Calculations based on other calculations' in Daily Calculations, Employee Calculations, and KPI Calculations, a minimum operator is visible and can be applied. ","","OSDOWSD-3693",""]
[null,null,1322423,"2020-05-07",null,"","New Feature","Functionality","Calculation","Added a maximum (MAX) operator for 'Calculation based on other calculations'","Added a maximum (MAX) operator for 'Calculation based on other calculations' which calculates the maximum of two calculations.\n\nTest hint(s):\n1. Verify that in 'Calculations based on other calculations' in Daily Calculations, Employee Calculations, and KPI Calculations, a maximum operator is visible and can be applied. ","","OSDOWSD-3694",""]
[null,null,1322423,"2020-05-07",null,"","New Feature","Functionality","Manager self-service","Added addressId to model of activity in back-end API","Changes were made in the back-end API, to make future changes in ORTEC WS for Managers possible. These changes will be related to the pending duty functionality.\n\nTest hint(s):\nnone","","OSDOWSD-3695",""]
[null,null,1322423,"2020-05-07",null,"","New Feature","","","A command handler has been created to set AuthorisationNeeded field of a given employee property","A command handler, SetAuthorisationNeededForUserProperty, has been created to set AuthorisationNeeded field of a given user property (like an employee property)\n\nTest hint(s):\n1. Use the command handler with a user property id and authorisationNeeded value=\"True\", and verify that read and update permissions corresponding to the user property have been created in Access Control.\n\nCommand handler input example:\n\n<CSetAuthorisationNeededForUserProperty>\n  <parameters>\n    <authorisationNeeded value=\"True\" />\n    <userProperty id=\"2582055\" />\n  </parameters>\n</CSetAuthorisationNeededForUserProperty> ","","OSDOWSD-3696",""]
[null,null,1322423,"2020-05-07",null,"","New Feature","Stability","Service","AdhocPlanning, show employee proposal fails on certain shifts","There was a problem handling employee activity history when the given employee had had an activity with a duration of maximum 1 hour ending during the skipped hour between 2am and 3am at the DST change in the spring. Due to the one hour skip these activities had a negative duration, resulting in a server error response.\n\nThis has been resolved. Activities with a duration equal or smaller to zero are removed and the surrounding activities are adjusted to ensure continuity when applicable.","","OSDOWSRES-507","11733677"]
[null,null,1322423,"2020-05-07",null,"","New Feature","Performance","Service","After changing the status of a scheduling period in OWS, the status update of every single shift was communicated to the Integration Service","After changing the status of a scheduling period in OWS, the status update of every single shift was communicated to the Integration Service for Ad Hoc Planning to keep the systems up to date. These shift updates were superfluous since an update for the department status change was send as well.\nThis has been improved. \nTo reduce network traffic, OWS will now only send the department status update to the Integration Service.\n\nTest hint(s): \n1. Publish a scheduling period in OWS and verify that Ad Hoc Planning is updated.","","OSDOWSRES-554",""]
[null,null,1324474,"2020-05-14",null,"","New Feature","Reliability","Manager self-service","Prepared 'shifts/all', back-end route for instructor shift visibility in ORTEC WS For Managers","External Release Notes:\nTechnical changes are done in a shift route in the back-end (API) to make it possible to show a shift is a student(-) or an instructor (+) shift in ORTEC WS For Managers.\n\nTest hint(s):\nNone","","OSDCOMMAIN-12964",""]
[null,null,1324474,"2020-05-14",null,"","New Feature","","","Four German translations added for MS Report","Four German translations added for MS Report.\n\nTest hint(s):\nNone","In order to use the translations, the translation file must be uploaded in CSCS.","OSDCOMMAIN-13000","11800080"]
[null,null,1328444,"2020-05-28",null,null,"New Feature","Functionality","Win32 Userinterface","Mailing a CSV export of account information from the Win32 client was not possible","Mailing a CSV export of account information from the Win32 client was not possible.\nThis has been improved.\nMailing a CSV export of account information from the Win32 client is now possible by configuring:\n- \\Options\\RunningAccounts\\ExportToExcel=N (existing server setting in OWS Settings Manager)\n- \\Options\\RunningAccounts\\MailExportToExcel=Y (new server setting in OWS Settings Manager)\n- Configure the general email settings in the Win32 client (under General | Options | Email)\nWhen configured and exporting account information the user is show a send mail dialog where he/she directly can send the exported information as an attachment.\n\nTest hint(s):\n1. Verify that mailing a CSV export of account information when using the above mentioned settings succeeds. \n \n","For this solution to become available the Win32 Client has be installed.\n\nFor security reasons, as sending this account information can contain privacy sensitive information, it is advised to ask written permission by customer and their Security Officer to configure the settings as described in the release notes. ","OSDOWSD-3705",""]
[null,null,1328444,"2020-05-28",null,null,"New Feature","Functionality","BackendDomainsAPI","An error occurred when assigning an employee to a shift if a planner didn't have permissions to an employee department ","A mismatch between permissions on employees in Shift Offering and permissions on employees in Ad Hoc Planning caused an error when assigning an employee to a shift using Shift Offering. The employee was assigned to shift from a proposal department, but the planner did not have permissions on that proposal department. \n\nThis has been fixed by changing the permission logic used in Ad Hoc Planning. It is now allowed to assign employees from proposal departments to a shift if the planner has permissions to the department of the shift.\n\nRemoved permission \"domain.AdhocPlanner.Employees\". All permissions are now checked using the department's permission.\n\nTest hint(s)\n1. Verify that employee names are still shown on a shift in Ad Hoc Planning\n2. Verify that an employee that responded to an offer for a shift can be assigned to that shift","","OSDOWSRES-512","11738071"]
[null,null,1328444,"2020-05-28",null,null,"New Feature","Functionality","Service","Sending changes to cloud services lead to problems with duplicate CSCS environment names","The BackendEventPublisher that is used to send changes in CWSS to the registered cloud services sends only the CSCS environment name, which is not guaranteed to be unique among customers. This could give problems when multiple customers with the same CSCS environment will use the same cloud service.\nThis has been improved. \nTwo settings have been added to specify the name of the cloud tenant where the changes has to be send to.\n\nAdded CSMS settings:\n- BackendEventPublisher\\CloudTenantNames\\ReschedulingIntegrationServiceCloudTenantName\n- BackendEventPublisher\\CloudTenantNames\\UserSynchronizationServiceCloudTenantName\n\nTest hint(s):\n1. Verify that changes done in CWSS are send to the cloud service\n  a. Open a shift for bidding should be offered in Ad Hoc Planning if Shift Offering is used\n  b. A new user in Access Control should be added to Auth0 if the Auth0 user integration service is used",null,"OSDOWSRES-585",""]
[null,"Y",1332104,"2020-06-11",null,"","New Feature","Technical","Installer","Added new binaries which create new dependencies for OWS 7","OWS 7 binaries are build using the following tools: \n- InstallShield 2018\n- Microsoft Visual Studio 2019\n- Microsoft Report Viewer 2015\n\nThese tools add dependencies on new binaries and these need to be deployed next to the OWS 7 executables and all installers have been updated.\n\nFor more details see upgrade notes. ","This update of OWS 7 introduces some new libraries it depends on that adds some additional steps to roll out this update:\n\n1. Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019\n  \n   The libraries can be installed using the VC_redist.x86.exe/VC_redist.x64.exe delivered as a manual update:\n   Manual_Update_1332104_RedistributablesVS2015-2019.zip\n   \n   When these libraries are NOT installed, starting any OWS 7 specific executable will\n   show an error message stating the 'msvcr140.dll' is missing.\n   \n2. Microsoft Report Viewer 2015 (12.0)\n\n  It has a dependency on Microsoft System CLR Types for SQL Server 2014.\n   \n   These libraries can be installed using the SQLSysClrTypes.msi and ReportViewer.msi delivered as a manual update:\n   Manual_Update_1332104_ReportViewer2015.zip\n   \nFor all (main and secondary) servers where the updates are rolled out to, the following needs to be installed FIRST:\n\n  1. Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019\n\nFor all client machines where client updates are rolled out to, the following needs to be installed FIRST:\n\n  1. Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019\n  2. Microsoft Report Viewer 2015 (12.0)\n\n  When the OWS 7 win32 client is installed on shared desktop environments like Citrix/Terminal server:\n  Additional packaging or install requirements of these libraries might be necessary.\n  Please inform and consult the system administrator of the customer to assist in installing these libraries on such environments\n  NOTE: The delivered ORTEC Workforce Scheduling Client installer also includes the Microsoft Report Viewer 2015 dependency","OSDOWSD-3654",""]
[null,"Y",1332104,"2020-06-11",null,"","New Feature","Calculation","Functionality","Added new labor rule 'Rest day after labor on Sunday or public holiday'","A new labor rule 'Rest day after labor on Sunday or public holiday' has been added. This labor rule checks that if there is work on a Sunday or Public holiday, there is a compensation free day within 2 weeks (Sunday) or 8 weeks (Public holiday) following the worked day. With a checkbox, it can be arranged that Sundays/holidays and compensation days must have either 11 hours of rest before or after the day.\n\n\nAdded global setting RestDayAfterSundayOrHolidayLaborReq, which is turned off by default.\n\nTest hint(s):\n1. Verify the new rule can be added to a labor rules set after it has been enabled.","For this functionality to become available, the OWS Win32 client must be installed.","OSDOWSD-3717",""]
[null,"Y",1332104,"2020-06-11",null,"","New Feature","Performance","BackendDomainsAPI","Performance improvement for opening the Ad Hoc Planning Schedule View","Performance of opening the schedule view could become slow when many employees are assigned to the shifts that are shown in the schedule.\nThis has been improved.\n\nTest hint(s):\n1. Verify that opening the schedule view still shows the correct shift and employee information.","","OSDOWSRES-615",""]
[null,null,1334166,"2020-06-18",null,"","New Feature","Reliability","Calculation","BI displayed double bookings for cost centers","BI displayed double bookings for cost centers. This has been fixed.\n\nTest hint(s):\nNone","","OSDCOMMAIN-12963","11716182"]
[null,null,1334166,"2020-06-18",null,"","New Feature","Reliability","Calculation","In rare cases, shift counter on duty type did not count consistent when dutysets from old dutyset periods are used","In rare cases, the shift counter on duty type did not count consistent when dutysets from old dutyset periods are used. \nThis has been fixed by adding a new server setting OPTIONS/PLANBOARD/NUMBEROFDAYSINTHEPASTTOCHECKFORDUTYSETINREGULARSCHEDULE with default value 0. When a value > 0 is set, this number of days is used to look back for duties dutysets from old dutyset periods.    \n\nTesthint(s):\nNone","","OSDCOMMAIN-12973","11684095"]
[null,null,1334166,"2020-06-18",null,"","New Feature","Reliability","Calculation","BI: Several 'Activity Types' were not taken into account populating activity data ","BI: Several 'Activity Types' were not taken into account populating activity data\nThis has been fixed.\nThe following 'Activity Types' are now also considered when populatig activity data:\n  'WorkStandBy', 'IllnessNoRest', 'IllnessNoLabourNoRest', 'IllnessNoWorkNoRest' and 'BreakOnCall'.\n\nNote: there is no repair script to fill the hour types of activities and shifts for the period before the IL period.\n\nTest hint(s):\n1. Verify that the incremantal load for BI succeeds \n  \n","","OSDCOMMAIN-12994","11787715"]
[null,null,1334166,"2020-06-18",null,"","New Feature","Security","Employee self-service","Update of a leave request is rejected if the request has already been approved","Update of a leave request is rejected if the request has already been approved.\n\nTest hint(s):\n1. Verify that when a leave request has been approved, it cannot be updated from ORTEC WS for Employees ","","OSDCOMMAIN-13040",""]
[null,null,1334166,"2020-06-18",null,"","New Feature","Reliability","Calculation","Clocking violation rules did not work correct when resource switches contracts","Clocking violation rules did not work correct when resource switches contracts. This has been fixed. When a resource switches contracts, the clocking violation rules of the correct employment conditions are taken into account.\n\nTest hint(s):\n1. Verify that the correct clocking violations are shown in the planboard and clocking overview ","","OSDCOMMAIN-13043","11933891"]
[null,null,1334166,"2020-06-18",null,"","New Feature","Reliability","Client","Several translations added for French and German","Several translations have been added for German, French for recent functional changes.\n\nTest hint(s):\nNone",null,"OSDOWSD-3762",""]
[null,null,1336349,"2020-06-25",null,"","New Feature","Reliability","Reporting","Report 'Flexpool statistics' did not show the correct shifts in a flexpool department when a subcontract of a shift was declined or cancelled","Report 'Flexpool statistics' did not show the correct shifts in a flexpool department when a subcontract of a shift was declined or cancelled.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that a shift for which a subcontract is rejected, is shown in the correct department in the report 'Flexpool statistics'","","OSDCOMMAIN-12953","11679407"]
[null,null,1336349,"2020-06-25",null,"","New Feature","Security","Security","Cloud key for shift generation plugin was saved unencrypted","Cloud key for shift generation plugin was saved unencrypted. This has been improved. When using an old process configuration for the shift generation plugin with an unencrypted cloud key, this is still possible, but a warning will be logged.\n\nTest hint(s):\n1. Verify the shift generation plugin works","","OSDCOMMAIN-12957",""]
[null,null,1336349,"2020-06-25",null,"","New Feature","","","Approving or declining realization for shifts subcontracted to flexpool is now possible for MSS users who have at least permission for the original department","Approving or declining realization for shifts subcontracted to flexpool is now possible for MSS users who have at least permission for the original department.\nTest hint(s):\n1. Verify that for an MSS user who does not permission for flexpool can approve/decline a pending update of shift, subcontracted from the user's department to flexpool.","","OSDCOMMAIN-12965",""]
[null,null,1336349,"2020-06-25",null,"","New Feature","Reliability","Calculation","Concurrency problems could occur when approved until date for a department was set back, and forward again","Concurrency problems could occur when approved until date for a department was set back, and forward again.\nThis happened because recalculations were handled instantly instead of being handeled by the job 'SetEmployeeMaxApprovedUntil'\nThis has been improved.\nThese recalculations will be handled by job 'SetEmployeeMaxApprovedUntil' when a schedule is unapproved and when the approved until date is in the past.\n\nThis functionality is implemented behind a feature toggle 'RECALCULATEONLYIFDATEEARLIERTHANAPPROVEDUNTILDATE' \nThis feature toggle is enabled by default after dbupdate has been executed.\n\nTest hint(s):\n1. Verify changing the approved until date of a schedule succeeds.","","OSDCOMMAIN-12976",""]
[null,null,1336349,"2020-06-25",null,"","New Feature","","","Monitoring queries added a number of days instead of weeks ","Monitoring queries added a number of days instead of weeks. It has been fixed.\n\nTest hint(s):\nNone","","OSDCOMMAIN-12991","11780537"]
[null,null,1336349,"2020-06-25",null,"","Bug","","","FirebaseNotificationApi did not always pick up the last added file in the folder","FirebaseNotificationApi did not always pick up the last added file in the folder.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that when adding a notification file in the monitored folder, it is picked up by the Api and processed.","","OSDCOMMAIN-13023","11880606"]
[null,null,1336349,"2020-06-25",null,"","New Feature","Technical","Import / Export","Calculating the number of days in February was not done correctly for leap years in stylesheets","Calculating the number of days in February was not done correctly for leap years in stylesheets.\nWhen the date:difference function was used in a xsl-stylesheet transformation for the number of days did not take into account leap years correctly for the number of days in February.\nThis fix was not included in the previous updates.\n\nTest hint(s):\n1. Verify that date:difference library function in xsl-stylesheet transformation works and return the correct days for February in a leap year.","","OSDCOMMAIN-13051","11952679"]
[null,null,1336349,"2020-06-25",null,"Backend Event Publisher","New Feature","Technical","Service","[BE EventPublisher] Add logging to CreateShiftOfferingResponseHandler","It happened that an ESS user responded to a request to work a certain shift, and that the response was not present in Shift Offering. We could not find any details about an error in any logs. We concluded that the logging of the Backend Event Publisher could be improved.\nThis has been done. Now, if the Backend Event Publisher fails to process a request, information about the error and the request is logged to the event viewer.\n\nTest hint(s):\n1. Create a response in ESS to an offered shift. Verify that it is visible in the offered shift details in Ad Hoc Planning.","","OSDOWSRES-660",""]
[null,null,1338034,"2020-07-02",null,"","New Feature","Configuration","Interfaces","Default server number for backend API communication is set to 50","The default value of the interface server used for backend api updates was 1. We do not want these updates on server 1, due to performance reasons. The default server number is changed to 50. When the current server number differs from 1, the current value of the server number will not change.\n\nTest hint(s):\n1. Check that ESS still works","When the current server number for backend API updates is set to 1, this will change to 50. Please check if there is an interface server with this value available. If not, change the value of the setting to the correct interface server number. If server number 50 is a busy worker, please consider changing the setting to another interface server.","OSDCOMMAIN-13048","11948914"]
[null,null,1338034,"2020-07-02",null,"","New Feature","Reliability","Client","Several translations added for German and Finnish Language ","Several translations have been added for German and Finnish.\n\nTest hint(s):\nNone","","OSDCOMMAIN-13057","11961236"]
[null,null,1338034,"2020-07-02",null,"","New Feature","Functionality","Calculation","New command handler CRecalculateShiftDuration has been created to update the duration of a shift according to working pattern or contract hours","New command handler CRecalculateShiftDuration has been created to update the duration of a shift according to working pattern or contract hours.\nThis command handler has 3 input parameters available:\n1. Shift id to adjust.\n2. ShouldUseWorkPattern: when 'True', the workpattern of the assigned employee is used to adjust the shift. When 'False' or not configured, the contract of the assigned employee is used to adjust the shift.\n3. NofWorkDaysPerWeek: when the contract of the assigned employee is used, the number of workdays per week is used to calculate the daily working time. When not configured, the server setting NOFWORKDAYSPERWEEK is used. \n\nAn example message which can be send to the command handler CRecalculateShiftDuration is:\n<?xml version=\"1.0\"?>\n<CRecalculateShiftDuration>\n  <parameters>\n    <shift id=\"646308\"/>\n    <ShouldUseWorkPattern value=\"False\"> <!-- optional -->\n    <NofWorkDaysPerWeek value=\"4\"/> <!-- optional -->\n </parameters>\n</CRecalculateShiftDuration>\n\nTesthint(s):\n1. Verify you can adjust a shift according to workpattern with command handler CRecalculateShiftDuration\n2. Verify you can adjust a shift according to contract hours with command handler CRecalculateShiftDuration","","OSDOWSD-3765",""]
[null,null,1338034,"2020-07-02",null,"","New Feature","Functionality","Interfaces","New transaction setting IsRelevantForQueues has been added for update-handlers","A new transaction setting IsRelevantForQueues has been added for update handlers.\nWhen this setting is set to N, the update will be ignored by the queues (if any configured).\nWhen the setting is not configured, the default value is Y.\n\nTo use the new setting, it can be added to a command as follows:\n<TransactionSettings IsRelevantForQueues='N'/>\nThis should be set as a child-node of the command handler name (same level as 'parameters'-tag).\n\nTesthint(s):\nNone","","OSDOWSD-3774",""]
[null,null,1338034,"2020-07-02",null,"","New Feature","","","Improve installation of FirebaseAPI - Enter input params in a single file","Installing the FirebaseAPI required to fill in variables in two separate files.\nThis has been changed. All necessary variables can be entered in the InstallFirebaseAPI.xml","","OSDOWSD-3781",""]
[null,null,1339922,"2020-07-09",null,"","New Feature","","","When illness replace type is planned shifts and multilang module is used, translations of shift name were not correct","When illness replace type is planned shifts and multilang module is used, translations of shift name were not correct. This has been fixed.\n\nTest hint(s):\n1. When using multilang module, verify you can replace shifts with illness shifts and translated shift name is shown","","OSDCOMMAIN-13018","11826457"]
[null,null,1339922,"2020-07-09",null,"","New Feature","Performance","Win32 User Interface","OWS win32 client: Message form could be slow when handling a lot of messages","The Message form in the OWS win32 could be slow when handling a lot of messages.\nThis particularly happened when scrolling through the messages or using the arrow keys.\nThis has been improved.\n\nWhen a refresh of all messages is done in the Message form an additional log line has been added for analysis purposes. \n\nTest hint(s):\n1. Verify the messages can be processed in the OWS Win32 client message form.","For this change to become available, the OWS Win32 client needs to be updated.","OSDCOMMAIN-13047","11948683"]
[null,null,1339922,"2020-07-09",null,"Ad Hoc Planning, Shift Offering","New Feature","Functionality","BackendDomainsAPI","Skills originating from parent departments are not shown in Ad Hoc Planning","Required shift skills that originate from a parent department of the shift were not shown in the shift in Ad Hoc Planning. This could also lead to errors when editing the skills from a shift before offering the shift.\nThis has been fixed. Now, also the skills that originate from parent departments of a shift are shown in the shift details in Ad Hoc Planning.\n\nTest hint(s):\n1. Verify that the skills of a shift are shown in the schedule in Ad Hoc Planning","For this fix to be available, install the new version of the Backend Domains Api.","OSDOWSRES-688",""]
[null," ",1341658,"2020-07-16",null,"","New Feature","Stability","Import / Export","The calculation period was too large with automatic export of account entries of new department","The calculation period was too large (started at 01-01-1900) with automatic export of account entries of new department. This has been fixed.\n\nTest hint(s):\n1. Verify the export for existing roster group works still fine.\n2. Verify the export for new department after approval of schedule works fine with right improved dates.","","OSDCOMMAIN-13008"]
[null,null,1341658,"2020-07-16",null,"","New Feature","Reliability","Calculation","Horizontal calculation for reports only returned calculations of a single department irrespective of the department chosen","Horizontal calculation for reports only returned calculations of a single department irrespective of the department chosen.\n\nThis has been fixed.\n\nTest hint(s):\n1. Verify that the horizontal calculations are the same in the planboard of OWS Win32 client and reports.","","OSDCOMMAIN-13011"]
[null,null,1341658,"2020-07-16",null,"","New Feature","Stability","Client","It was not possible to enter date specific duty demands with a value higher than 100","It was not possible to enter date specific duty demands with a value higher than 100.\nManually entering a value > 100 for a date specific duty demand gave an error while using the spin edit buttons allow a value where 0 <= x <= 999.\nThis has been aligned.\nManually entering a value <= 999 is now allowed.\n\nTest hint(s):\n1. Verify date specific duty demands can be entered","For this change to become available the Win32 client has to be installed.","OSDCOMMAIN-13061"]
[null,null,1341658,"2020-07-16",null,"","New Feature","","","Users' Own calculations could not be chosen in the OWS Win32 client if the user name contains '@'","Users' Own calculations could not be chosen in the OWS Win32 client if the user name contains '@'.\n\nThis has been fixed.\n\nThis functionality is implemented behind a feature toggle 'DONOTREMOVEPARTOFUSERNAMEINCOMCLIENTINFORMATION' \nThis feature toggle is enabled by default after dbupdate has been executed.\n\nTest hint(s):\n1. Verify that a user can view his/her own calculations in the OWS Win32 client.\n","","OSDCOMMAIN-13075"]
[null,null,1344319,"2020-07-23",null,"","New Feature","Reliability","Tools","Added new monitoring query to retrieve the number of planned contracts per month","A new monitoring query to retrieve the number of planned contracts per month was added:\nSystemMonitoring/CMHS/Weekly/DataAmounts/NumberOfPlannedContractsPerMonth\n\nTest hint(s):\n1. Verify that monitoring data collected includes the newly queried data","","OSDCOMMAIN-13005","11780537"]
[null,null,1344319,"2020-07-23",null,"","New Feature","Functionality","Import / Export","Export/import CQMS queries changed query kind from system to user","Export/import CQMS queries changed query kind from system to user. It has been fixed.\n\nTest hint(s):\n1. Verify in the query manager that when a query with 'system' kind is imported, it does not change into 'user' kind.","","OSDCOMMAIN-13017","11845270"]
[null,null,1344319,"2020-07-23",null,"","New Feature","Reliability","Calculation","It was not possible to configure the workstation optimizer profile rule 'Preferred workstations and locations of 0 percent' as a requirement","It was not possible to configure the workstation optimizer profile rule 'Preferred workstations and locations of 0 percent' as a requirement. This has been fixed.\n\nTest hint(s):\n1. Verify when running the workstation optimizer with the rule 'Preferred workstations and locations of 0 percent', employees with a preference of 0% for a workstation, will not be assigned to that workstation","","OSDCOMMAIN-13020","11865268"]
[null,null,1344319,"2020-07-23",null,"","New Feature","Reliability","Reporting","Report Flexpool Statistics did not show all statuses in summary","Report Flexpool Statistics did not show all statuses in summary.\nThis has been fixed.\nWhen a status is selected in the 'status' filter the corresponding column in the summary will be shown, even when no data (shift with that subcontract status is available)\n\n1. Verify Flexpool statistics show the expected values in summary and details","","OSDCOMMAIN-13035","11919555"]
[null,null,1344319,"2020-07-23",null,"","New Feature","Functionality","Database","BI - New cost center added in IL was created with wrong effective_from_date","During an incremental load new cost centers were inserted in DIM_COST_CENTER with an effective_from_date set to the date of the BI run. This prevented certain links to cost centers being set.\nNow new cost centers will have an effective_from_date of 2001-01-01.\nFor existing cost centers, the effective_from_date of the first record is updated by DBUpdate.\n\nTest hint(s):\n1. Verify that when a new cost center is created, the cost center has the effective_from_date of 2001-01-01 in DIM_COST_CENTER.","","OSDCOMMAIN-13050","11951257"]
[null,null,1344319,"2020-07-23",null,"","New Feature","Reliability","Client","Cost center with a valid from date could not be chosen for an activity in a shift realization in a cyclical schedule","Cost center with a valid from date could not be chosen for an activity in a shift realization in a cyclical schedule.\nThis has been improved.\n\n1. Verify a cost center with a valid from date can be selected when applying a shift realization in cyclical schedule","For this solution to come available the OWS Win32 has to be updated.","OSDCOMMAIN-13090","12025865"]
[null,null,1344319,"2020-07-23",null,"","New Feature","Reliability","Planboard","'Own employees' filter in planboard did not show employee who switches contract and is also borrowed","'Own employees' filter in planboard did not show employee who switches contract and is also borrowed. This has been fixed.\n\nTest hint(s):\n1. Verify correct employees are shown in planboard when filter 'Own employees' is configured ","","OSDCOMMAIN-13096","12029214"]
[null,null,1344319,"2020-07-23",null,"","New Feature","Reliability","Planning","It was possible to set a department as its own proposal department","It was possible to set a department as its own proposal department. This could occur when a sub department was selected as proposal department for a root department. This has been fixed. \n\nTest hint(s):\n1. Verify when selecting proposal departments for a root department, a sub department is not selected as its own proposal department","","OSDCOMMAIN-13106","12043394"]
[null,null,1344319,"2020-07-23",null,"","New Feature","Functionality","Calculation","Imported accounting line was not processed correctly in memory of interface worker","Imported accounting line was not processed correctly in memory of interface worker. \nThis has been fixed. \nIt is possible to import an accounting line either via a shift realisation with accounting line or via a separate accounting line.\nFor importing a shift realisation with accounting lines the TFillFieldsOfCOMTECShift extra xml creator should be used.\n\nNote: importing an accounting line with a duration is not supported\n\nTest hint(s):\n1. Verify you can import an accounting line\n2. Verify you can import a shift realisation including an accounting line","","OSDOWSD-3818",""]
[null,null,1344319,"2020-07-23",null,"","New Feature","Reliability","Service","Backend Event Publisher writes an error to the event log","The Backend Event Publisher process could write event log errors when employee calculation \"Employee rotation unit according to cyclical schedule\" was changed in OWS win 32 client. This was caused by a column in the database that was too small for the name of this calculation.\n\nThis has been fixed.\n\nTest hint(s):\n1. Verify that the Backend Event Publisher is not writing this error after changing the employee calculation \"Employee rotation unit according to cyclical schedule\"","","OSDOWSRES-696","12030713"]
[null,null,1345618,"2020-07-30",null,"","New Feature","Reliability","Self scheduling","ORTEC WS for Employees: Retrieving all allowed cost centers could fail when more than 2100 cost centers exist for a single department","Retrieving all allowed cost centers could fail when more than 2100 cost centers exist for a single department.\nThis has been fixed.\n\nTest hint(s):\n1. Verify actual details can be shown (when a large number of allowed cost centers exist for the department the actual is in)","","OSDCOMMAIN-13121","12064874"]
[null,null,1345618,"2020-07-30",null,"","New Feature","Functionality","Optimization","The commandhandler 'RunExternalPlanner' has been adjusted to enable optimizing partly published schedules","The commandhandler 'RunExternalPlanner' has been adjusted such that the planning part of a partly published schedule can be optimized.\n\nTest hint(s):\n1. Create a partly published schedule and verify that it can be optimized with the command handler 'RunExternalPlanner'","","OSDOWSD-3835",""]
[null,null,1345618,"2020-07-30",null,"","New Feature","Functionality","Optimization","Optimizer is now enabled to run in a partly published schedule\n","It is now possible to run the optimizer on the planning part of a schedule that is partly in status published.\n\nTest hint(s):\n1. Create a schedule that is partly published and verify that an optimizer can be run in that schedule.","For this functionality to become available, the OWS Win32 client must be installed.","OSDOWSD-3836",""]
[null,null,1345618,"2020-07-30",null,"","New Feature","Stability","Service","Shift offer requests were not synchronized","The backend event publisher could return an error when the user created a shift offering response: \"String or binary data would be truncated\". This would happen in case some internal ids had a long length.\nThis has been fixed. \n\nTest hint(s):\n1. Create a request to work an offered shift, and verify that it is shown in Ad Hoc Planning.",null,"OSDOWSRES-724","12082503"]
[null,null,1347482,"2020-08-06",null,"","New Feature","Reliability","Optimization","Workstation optimizer did split workstation demands on boundaries of optimization interval when it was not allowed","Workstation optimizer did split workstation demands on boundaries of optimization interval when it was not allowed. \nThis has been fixed. \nWhen a workstation demand which cannot be split (with \"The demanded activity can be broken down by the optimizer into xx:xx hours\" unchecked) starts within and ends outside the optimization interval, it is only assigned as a whole if possible.\n\nTest hint(s):\n1. Verify the workstation optimizer does not split workstation demands on the boundary of the optimization interval if it is not allowed. ","","OSDCOMMAIN-13134","12085699"]
[null,null,1347482,"2020-08-06",null,"","New Feature","Reliability","Optimization","Workstation optimizer tried to add a break within activity longer than the activity itself\n\n","When UseBreakWithinActivities=True, the workstation optimizer could give an error that the break within the activity was longer than the activity itself. This has been fixed.\n\nTesthint(s)\n1. Verify that the workstation optimizer still works","","OSDCOMMAIN-13135","12085735"]
[null,null,1348896,"2020-08-13",null,"","Bug","","","The team members' sick leave was displayed with a green bar in their schedule","The team members' sick leave was displayed with a green bar in their schedule.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that the sick leave of a colleague is no longer displayed.\n2. Verify that the sick leave in Schedule is still displayed with a green bar.","","OSDCOMMAIN-13019",""]
[null,null,1348896,"2020-08-13",null,"","New Feature","Reliability","Planning","Some back-end routes did not return correct values of shifts when there was an open realisation","Some back-end routes did not return correct values of shifts when there was an open realisation. This has been fixed.\n\nTest hint(s):\n1. Verify for shifts with an open pending update, the correct values are visible in ORTEC WS for Employees","","OSDCOMMAIN-13125",""]
[null,null,1348896,"2020-08-13",null,"","New Feature","Reliability","Calculation","Importing multiple horizontal calculations in a calculation set was not possible","Importing multiple horizontal calculations in a calculation set was not possible.\nThis has been fixed.\nTest hint(s):\n1. Verify that there is no error when importing multiple calculations to an existing horizontal calculation set.","","OSDCOMMAIN-13137",""]
[null,null,1348896,"2020-08-13",null,"","New Feature","","","It was not possible to run the workstation optimizer for one day","It was not possible to start the workstation optimizer  or plan weekend shifts for only one day.\nThis has been fixed.\n\nTest hint(s):\n1. Start an optimizer for one day","For this update to become available, the win32 client must be installed","OSDCOMMAIN-13147",""]
[null,null,1348896,"2020-08-13",null,"","New Feature","","","Calendar month added as an option for \"Number of free days on a weekday\" labor rule","In the labor rule, Number of free days on a weekday, calendar month has been added as an option for period.\n\nTest hint(s):\n1. Create a labor rule, Number of free days on a weekday with calendar month as period kind and open a schedule.","","OSDOWSD-3855",""]
[null,null,1350227,"2020-08-20",null,"","New Feature","Functionality","Client","Several translations added for French and German language","Several translations added for French and German language for recent functional changes.\n\nTest hint(s):\n1. None ","","OSDCOMMAIN-13143"]
[null,null,1350227,"2020-08-20",null,"","New Feature","Reliability","Calculation","Ordering calculations in a calculations set was no longer possible in OWS Win32 client","Ordering calculations in a calculations set was no longer possible in OWS Win32 client\nThis was introduced in OSDCOMMAIN-13137.\nThis has been resolved \n\nTest hints:\n- verify that ordering of horziontal calculations can be changed when changing calculation sequence number\n","","OSDCOMMAIN-13162"]
[null,null,1354223,"2020-09-03",null,"","New Feature","Stability","Import / Export","Importing a decentral department link with decentral department that has employees assigned is no longer possible","Importing a decentral department link with decentral department that has employees assigned is no longer possible. Before, it was possible to import such a decentral department link, but this resulted in a corrupt database. This has been fixed.\n\nTest hint(s):\n1. Verify a decentral department link can be imported when no resource is assigned to the decentral department\n2. Verify a decentral department link cannot be imported when at least one resource is assigned to the decentral department","","OSDCOMMAIN-13109","12016967"]
[null,null,1354223,"2020-09-03",null,"","New Feature","Reliability","Planning","Validity period of existing template wishes was not initialised correctly when applying DBUpdate","Validity period of existing template wishes was not initialised correctly when applying DBUpdate. This has been fixed.\n\nTest hint(s):\nnone","","OSDCOMMAIN-13174",""]
[null,null,1354223,"2020-09-03",null,"","New Feature","Functionality","Calculation","A new rule has been added: Maximum number of special periods per month","A new rule has been added: Maximum number of special periods per month. \nEnable the rule with setting MaxNofSpecialPeriodsPerMonthReq in OWS Settings Manager.\n\nTest hint(s):\n1. Verify that after enabling the rule it can be used in a employment conditions.","","OSDOWSD-3857",""]
[null,null,1354223,"2020-09-03",null,"","New Feature","Functionality","Planboard","A consistency check was added for new rule 'Maximum number of special periods per calendar month'","A consistency check was added for new rule 'Maximum number of special periods per calendar month'\n\nTest hint(s):\n1. Verify server can be (re)started when the rule has been added in the rules configuration","","OSDOWSD-3859",""]
[null,null,1354223,"2020-09-03",null,"","New Feature","Functionality","Calculation","A new rule has been added: Maximum number of on call periods per month","A new rule has been added: Maximum number of on call periods per month. \nEnable the rule with setting MaxNofOnCallPeriodsPerMonthReq in OWS Settings Manager.\n\nTest hint(s):\n1. Verify that after enabling the rule it can be used in a employment conditions.","","OSDOWSD-3860",""]
[null,null,1354223,"2020-09-03",null,"","New Feature","Functionality","Calculation","A new rule has been added: Daily rest after a shift (labor period)","A new rule has been added: Daily rest after a shift (labor period). \nEnable the rule with setting DailyRestAfterLaborPeriodReq in OWS Settings Manager.\n\nTest hint(s):\n1. Verify that after enabling the rule it can be used in employment conditions.","","OSDOWSD-3864",""]
[null,null,1354223,"2020-09-03",null,"","New Feature","Reliability","Client","Several translations added for Dutch, French and German","Several translations have been added for Dutch, German and French for recent functional changes.\n\nTest hint(s):\nNone","","OSDOWSD-3876",""]
[null,null,1354223,"2020-09-03",null,"","New Feature","Functionality","Security","Added outbound proxy configuration possibility for BackendEventPublisher","When ORTEC WS uses the Backend Event Publisher to send updates to the OWS cloud services, it is not possible to use an outgoing proxy server to reach the URL of the cloud service.\nThis has been improved.\nThe setting from ORTEC System Configuration - Settings Management - CUASFW\\OIDC has been moved to the general SharedCFW\\Network\\OutboundProxyConfiguration. A shared proxy server settings page is available to configure and enable/disable a proxy server.\nIf enabled the configured outgoing proxy server is used to connect to the OIDC provider and the OWS cloud services.\n\nIf changes are applied to this proxy server configuration, processes that rely on the OIDC provider for token validation as well as the Backend Event Publisher should be restarted.\n\nTest hint(s):\n1. Verify ORTEC System Configuration can be started and the proxy configuration can be edited.\n2. Verify user can logon to ORTEC Workforce Scheduling for Employees when ORTEC WS has been configured as Resource Server for OIDC.\n3. Create a response in ESS to an offered shift. Verify that it is visible in the offered shift details in Ad Hoc Planning.","","OSDOWSRES-485",""]
[null,null,1354223,"2020-09-03",null,"Shift Offering","New Feature","Functionality","BackendDomainsAPI","Offering a shift including adjusting its properties caused change in original shift","When the time/skill properties of a shift were changed during offering, the original employee would get the shift with the changed properties, and the offered shift would still have the old properties.\nThis has been fixed. Now, the offered shift that is assigned to an employee, will have the changed properties. The employee that was assigned the original shift, will still have the shift with the original properties.\n\nTesthint(s):\n1. Offer and change a shift. Assign it to an employee. Verify that the original and the new employee have shifts with the correct properties.","","OSDOWSRES-764",""]
[null,null,1355970,"2020-09-10",null,"","New Feature","","","User property value was not taken into account for the rule 'Maximum labor-time of shifts' when shifts for shift picking are returned to ORTEC WS for Employees","User property value was not taken into account for the rule 'Maximum labor-time of shifts' when shifts for shift picking are returned to ORTEC WS for Employees. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that shifts are visible for bidding in ORTEC WS for Employees.","","OSDCOMMAIN-13118","12028033"]
[null,null,1355970,"2020-09-10",null,"","New Feature","Reliability","Client","'Search Employee'-functionality in OWS Win32-Client became case sensitive","'Search Employee'-functionality in OWS Win32-Client had become case sensitive. This has been fixed.\n\nIt has been introduced in OSDCOMMAIN-12944 in update 8.5.0(2020-04-16)_Build1317128 \n\nTest hint(s):\n1. Verify employees can be searched in win32 client"," For this functionality to become available, the OWS Win32 client must be installed.","OSDCOMMAIN-13181","12196328"]
[null,null,1355970,"2020-09-10",null,"","New Feature","Reliability","Reporting","Master Schedule Planner and Master Schedule ESS reports displayed instructor shift name twice","Master Schedule Planner and Master Schedule ESS reports displayed instructor shift name twice. This has been fixed.\n\nTest hint(s):\n1. Verify that the instructor shift name is shown correctly in Master Schedule Planner and Master Schedule ESS reports","","OSDCOMMAIN-13183","12196343"]
[null,null,1355970,"2020-09-10",null,"","New Feature","Reliability","User Interface","Several translations added for French and German language","Several translations added for French and German language.\nThe German translations have been added for the ESS Mobile App.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13190","12207727"]
[null,null,1355970,"2020-09-10",null,"","New Feature","Stability","Calculation","When optimizing workstations, not all memory allocated during certain actions was correctly deallocated ","When optimizing workstations, not all memory allocated during certain actions was correctly deallocated. \nThis has been fixed.\n\nNOTE: This issue was introduced in issue:\nOSDCOMMAIN-13134 Workstation optimizer did split workstation demands on boundaries of optimization interval when it was not allowed\n\nTest hint(s):\n1. Verify the workstation optimizer works","","OSDOWSD-3886",""]
[null,null,1355970,"2020-09-10",null,"Ad Hoc Planning","New Feature","Stability","BackendDomainsAPI","BackendDomainsAPI could not recover from an sql connection issue","Sometimes, SQL connection issues happened when calling the integration api.  The Backend Domains Api could not recover from that.\nThis has been fixed. Now, in case of an SQL connection issue, the Backend Domains Api can recover from that when SQL is available again.\n\nTest hint(s):\n1. Verify that the home page of Ad Hoc Planning can be opened (this will need a SQL connection).","","OSDOWSRES-772",""]
[null,null,1357935,"2020-09-17",null,"","New Feature","Security","Employee self-service","ORTEC WS for Employees: It was possible to change a preference after approval","It was possible to change a preference after approval. This has been fixed.\n\nTest hint(s):\n1. Verify that when a preference has been approved, it cannot be updated from ORTEC WS for Employees","","OSDCOMMAIN-13107","11913744"]
[null,null,1357935,"2020-09-17",null,"","New Feature","Security","Employee self-service","ORTEC WS for Employees: It was possible to delete an approved exchange request","It was possible to delete an approved exchange request. It has been fixed.\n\nTest hint(s):\n1. Verify that when an exchange request has been approved, it cannot be deleted from ORTEC WS for Employees","","OSDCOMMAIN-13108","11913744"]
[null,null,1357935,"2020-09-17",null,"","New Feature","","","Exception of “Duration of a night shift (labor period)” took long dayshifts into account","Some day shifts were taken into account when using the exception of the rule \"Duration of night shift (labor period)\", leading to incorrect violations.\nThis has been fixed.\n\nTest hint(s):\n1. Create some long day shifts of more than 10 hours and some night shifts. Verify that for the rule \"Duration of night shift (labor period)\" the day shifts are not counted for the exceptions.","","OSDCOMMAIN-13115","12051235"]
[null,null,1357935,"2020-09-17",null,"","New Feature","","","Performance degradation could occur due to concurrency in settings table on the server","Performance degradation could occur due to concurrency problems in settings table on the server.\nThis has been fixed.\n\nAdded Feature Toggle:\nFEATURETOGGLES\\LOCKSETTINGSTABLEWHENWRITINGCHANGE, possible values 'Y', 'N', 'True', 'False'. Default value set to Y.\n\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\nNone","","OSDCOMMAIN-13117",""]
[null,null,1357935,"2020-09-17",null,"","New Feature","Stability","Reporting","Opening the Master Schedule report at the end of the year 2021 could give an error","Opening the Master Schedule report at the end of the year 2021 could give the error \"The conversion of a varchar data type to a datetime data type resulted in an out-of-range value\".\nThis has been fixed.\nThe dbo.GETISOWEEK and dbo.GETISOYEAR database functions have been updated in this fix.\n\nTest hint(s):\n1. Verify that the reports in OWS Win32 client function correctly","","OSDCOMMAIN-13170","12165084"]
[null,null,1357935,"2020-09-17",null,"","New Feature","Reliability","Reporting","Stylesheet used for showing horizontal calculations in Master Schedule report was not delivered correctly in weekly update","Stylesheet used for showing horizontal calculations in Master Schedule report was not delivered correctly in weekly update 8.5.0(2020-07-16)_Build1341658 for issue OSDCOMMAIN-13011. This has been fixed.\n\nThe stylesheet HorizontalCalculationsFromResources.xsl was previously not delivered and is now added to the interfaces-update. The default location to rollout this stylesheet to is \\Interfaces\\Stylesheets\\Libraries.\n\nTest hint(s):\n1. Verify that the horizontal calculations are the same in the planboard of OWS Win32 client and in the reports. ","A stylesheet is replaced in the default location <installpath>\\Interfaces\\Stylesheets\\Libraries.\nPlease make sure this stylesheet is also replaced on the  customers stylesheet locations/machines.","OSDCOMMAIN-13195","12211742"]
[null,null,1357935,"2020-09-17",null,"","New Feature","Functionality","Client","Several translations added German and French language","Several translations added for German and French language for recent functional changes.\n\nTest hint(s):\n1. None ","","OSDCOMMAIN-13198",""]
[null,null,1357935,"2020-09-17",null,"Integration service","New Feature","Reliability","Service","Adhoc Planner copied newly created and assigned shifts to the vacant shifts","When a shift was created for an employee in OWS Client, it was copied to the vacant shifts and got a remark that it was moved and thus not visible in Ad Hoc Planning. This happened because the Integration Service updated the shift in a wrong way.\nThis has been fixed. Now, the shift is not changed by the Integration Service after creating it.\n\nTest hint(s):\n1. Create a shift for an employee in OWS Client. Verify that after some minutes, it is still assigned to that employee, and has the same properties.","","OSDOWSRES-799","12221846"]
[null,null,1359659,"2020-09-24",null,"","New Feature","Stability","Calculation","When calculating violations in the planboard for labor rules concerning night shifts, an error \"ADateTime too high\" could occur","When calculating violations in the planboard for a labor rule concerning night shifts, an error \"ADateTime too high\" could occur. This has been fixed.\n\nTest hint(s):\n1. Verify violations can be calculated in the planboard for labor rules concerning night shifts ","","OSDCOMMAIN-13141","12114847"]
[null,null,1359659,"2020-09-24",null,"","New Feature","","","Error message while opening cards in ORTEC WS for Employees was unclear on non-published schedules","Error message while opening cards in ORTEC WS for Employees was unclear on non-published schedules.\nIt has been fixed.\nTest hint(s):\n1. Verify that when an employee does not have a schedule published tries to open a card, an error message is shown","","OSDCOMMAIN-13169","12160451"]
[null,null,1359659,"2020-09-24",null,"","New Feature","Reliability","Import / Export","An error occured when importing recurring wish with duration other than 8 hours","An error occured when importing recurring wish with duration other than 8 hours. This has been fixed. \nWhen importing recurring wish, it is not possible any more to pass the field WISHEND. The end of the wish is deducted from the duration and wish start.\n\nTest hint(s):\n1. Verify recurring wishes can be imported\n2. Verify recurring wishes can be created and adjusted in the Win32 client","","OSDCOMMAIN-13189","12135424"]
[null,null,1359659,"2020-09-24",null,"","New Feature","Stability","Employee self-service","ORTEC WS For Employees: A reverted shift added by an employee could halt an interface worker when changing the schedule status","ORTEC WS For Employees: A reverted shift added by an employee could halt an interface worker when changing the schedule status\n\nTest hint(s):\n1. In ORTEC WS For Employees add a new shift (UseApproveRealisation=Y) and revert/cancel it. Change status of the schedule in the ORTEC WS Win32 Client where shift was added","","OSDCOMMAIN-13206","12213283"]
[null,null,1359659,"2020-09-24",null,"Integration service","New Feature","Reliability","Service","Adhoc Planner copied newly created and assigned shifts to the vacant shifts","When a shift was created for an employee in OWS Client, it was copied to the vacant shifts and got a remark that it was moved and thus not visible in Ad Hoc Planning. This happened because the Integration Service updated the shift in a wrong way.\nThis has been fixed. Now, the shift is not changed by the Integration Service after creating it.\n\nTest hint(s):\n1. Create a shift for an employee in OWS Client. Verify that after some minutes, it is still assigned to that employee, and has the same properties","","OSDOWSRES-799","12221846"]
[null,null,1361657,"2020-10-01",null,"","New Feature","Functionality","Planboard","Declined subcontracted shifts prevented the deletion of the original schedule the shift belonged to","Declined subcontracted shifts prevented the deletion of the original schedule the shift belonged to.\nThis has been fixed.\n\nAdded Feature Toggle: FEATURETOGGLES\\IMPROVEHANDLINGSUBCONTRACTEDSHIFTSWHENDELETINGSCHEDULE and is by default enabled.\n\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\n1. Verify that if a department subcontracts a shift and the subcontract is declined then the schedule of the originating department can be deleted.","","OSDCOMMAIN-13127",""]
[null,null,1361657,"2020-10-01",null,"","New Feature","","","Schedule could not be deleted when there existed exchange requests","Schedule could not be deleted when there existed exchange requests. This has been fixed.\n\nNote for customers already facing the issue: Please change the schedule status to 'Published', then to 'Plan' and finally delete it.\n\nTest hint(s):\n1. Verify that a schedule status can be set to 'Plan' and deleted if there are exchange requests. ","","OSDCOMMAIN-13163","12077077"]
[null,null,1361657,"2020-10-01",null,"","New Feature","Stability","Employee self-service","Swap requests in ORTEC WS for Employees showed error when an employee initial, prefix or first name was empty","Swap requests in ORTEC WS for Employees showed error when an employee initial, prefix or first name was empty. It has been fixed.\n\nTest hint(s):\n1. Verify that swap requests in Ortec WS for Employees does not show any error when any of the following is empty: employee initial, prefix or first name.\n","","OSDCOMMAIN-13182","12196335"]
[null,null,1361657,"2020-10-01",null,"","New Feature","Reliability","Calculation","Error occured when retrieving account entries in ORTEC WS for Employees due to old central department","Error occurred when retrieving account entries in ORTEC WS for Employees due to old central department. This happened when employee is not allowed to see accounts in status 'Plan'. This has been fixed.\n\nTest hint(s):\n1. Verify account entries can be retrieved in ORTEC WS for Employees for an employee who is linked to an old central department","","OSDCOMMAIN-13192","12207788"]
[null,null,1363724,"2020-10-08",null,"","New Feature","Reliability","Calculation","Night shifts on boundary of published period did not give the correct account entries for compensation rule 'Allowances per salary code for activity classes' ","When using the compensation rule 'Allowances per salary code for activity classes' on a night shift that started in a published schedule and ended in a non-published schedule, the result was unexpected. The rule did consider the first of the shift as published and the second part of the shift as planned.\nThis has been fixed.\nThe whole shift is now considered as published.\n\nTest hint(s):\n1. Create a compensation rule \"Allowances per salary code for activity classes\" and attach it to a user.\n2. In the menu, under \"Accounts\", create an account that uses this rule.\n3. Create a roster that is published until day 10, the remainder should have status \"Plan\".\n4. Create a shift that starts on day 9 22:00 untill day 10 05:00.\n5. Check the account created in 2., it should not have any hours of this shift booked.","","OSDCOMMAIN-13191","12207790"]
[null,null,1363724,"2020-10-08",null,"","New Feature","Functionality","Planning","When an employee works for multiple departments and leave shifts were automatically created based on cyclical schedules, leave shifts were only created for the cyclical shifts of the main department","When an employee works for multiple departments and leave shifts were automatically created based on cyclical schedules, leave shifts were only created for the cyclical shifts of the main department. This has been fixed by adding a new leave processor which creates leave shifts based on cyclical shifts of all departments of the employee.\n\nTo enable this new leave processor, in OWS Settings manager the setting WISH/LEAVEWISH/USEPROCESSLEAVEALGORITHM must be enabled and the setting WISH/LEAVEWISH/LEAVEPROCESSTYPEPLANNING (and/or PUBLISHED) must be set to CyclicalScheduleAllDepartments\n\nNote: it can be that the pre-existing functionality is desired. For this case, no adjustments are done to the pre-existing functionality.\n\nTest hint(s):\n1. Verify that for an employee with two cyclical schedules in different departments, for both departments leave shifts are created when setting above is set to CyclicalScheduleAllDepartments","","OSDCOMMAIN-13223",""]
[null,null,1363724,"2020-10-08",null,"","New Feature","Performance","Reporting","The Master schedule reports could stall when using grouplabels as sort group","The Master schedule reports could stall when using grouplabels as sort group. This has been fixed.\n\nTest hint(s):\n1. Verify master schedule reports can be opened","","OSDCOMMAIN-13230","12263772"]
[null,null,1363724,"2020-10-08",null,"","New Feature","Reliability","Client","Several translations added for French and German","Several translations have been added for French and German for recent functional changes.\n\nTest hint(s):\nNone","","OSDOWSD-3933/ OSDCOMMAIN-13235","12271977"]
[null,null,1365532,"2020-10-15",null,"","New Feature","Functionality","Optimization","An out of memory could occur when using an optimizer in a cyclical schedule in combination with the Shift series length criterion","An out of memory could occur when using an optimizer in a cyclical schedule in combination with the Shift series length criterion.\nThis has been fixed.\n\nTest hint(s): \n1. Run the optimizer in a cyclical schedule.","","OSDOWSD-3936",""]
[null,null,1365532,"2020-10-15",null,"","New Feature","Functionality","Optimization","It was no longer possible to start an optimizer in a cyclical schedule","It was no longer possible to start an optimizer in a cyclical schedule. This has been fixed.\n\nTest hint(s): \n1. Open a cyclical schedule and start the optimizer.","","OSDOWSD-3940",""]
[null,null,1365532,"2020-10-15",null,"Ad Hoc Planning, Integration Service","New Feature","Stability","BackendDomainsAPI","Ad Hoc Planning could not open a proposal with shifts of over 24 hours present","Ad Hoc Planning could not open a proposal for a vacant shift if one of the proposed employees had a shift of more than 24 hours during the past year.\nThis has been fixed. Now, Ad Hoc Planning and Integration Service will not give errors when there is a shift of more than 24 hours present.\n\nTest hint(s):\n1. Have an employee with a shift of more than 24 hours in the past. Open the employee proposal window for a shift, that fits the employee. Verify that the employee is shown in the proposal window.\n2. Have a shift of more than 24 hours. Verify that it is synchronized to the Shift Offering database.","","OSDOWSRES-824","12297258"]
[null,null,1366154,"2020-10-16",null,"","New Feature","","","Settings were no longer saved","When changing settings they were not saved to the database to make them persistent between sessions.\nThis has been fixed.\n\nNOTE: This issue was introduced in 8.5.0(2020-09-24)_Build1359659 ","","OSDCOMMAIN-13269"]
[null,null,1369237,"2020-10-29",null,null,"New Feature","","","Current schedule was not shown in ORTEC WS for Employees when the schedule is published or higher","Current schedule was not shown in ORTEC WS for Employees when the schedule is published or higher. \nIt has been fixed.\n\nTest hint(s):\n1. Verify that when a current schedule is partly published or higher, it is shown in ORTEC WS for Employees.\n2. Verify that when a current schedule is partly planned and partly published, it is not shown in ORTEC WS for Employees.","","OSDCOMMAIN-13236","12273977"]
[null,null,1369237,"2020-10-29",null,null,"New Feature","Reliability","Planboard","It was not possible to remove or unassign shift of borrowed employee when on same day a shift in main department with status Final was planned","It was not possible to remove or unassign shift of borrowed employee when on same day a shift in main department with status Final was planned. \nThis has been fixed.\n\nTest hint(s):\n1. Verify shifts can be unassigned and removed from borrowed employees","","OSDCOMMAIN-13249",""]
[null,null,1369237,"2020-10-29",null,null,"New Feature","","","ORTEC WS for Employees: Shift-picking a Flexpool shift did not have subcontract status Final despite enabled setting 'AUTOMATICFINALPLANNING'","Flexpool shfits picked via Ortec for Employees Shift-picking did not have subcontract status 'Final planning' despite setting 'AUTOMATICFINALPLANNING' being True.\nIt has been fixed.\n\nTest hint(s):\n1. Verify that when AUTOMATICFINALPLANNING is set to true and an employee from other department than Flexpool picks a shift subcontracted to Flexpool, the shift has the subcontract status, 'Final planning'.","","OSDCOMMAIN-13272","12300471"]
[null,null,1369237,"2020-10-29",null,null,"New Feature","Reliability","Planning","Leave processor CyclicalScheduleAllDepartments did not take into account 0 hour department assignments","Leave processor CyclicalScheduleAllDepartments did not take into account 0 hour department assignments. \nThis has been fixed.\n\nTest hint(s):\n1. When using leave processor CyclicalScheduleAllDepartments, verify cyclical shifts are rolled out for departments for which an employee has a contract with 0 hours.","","OSDCOMMAIN-13284","12352107"]
[null,null,1369237,"2020-10-29",null,null,"New Feature","Functionality","Mobile application","New functionality has been added for sending notifications to Ortec Relevance App","New functionality has been added for sending notifications to Ortec Relevance App.\nTo enable this new functionality, the settings in the folder OrtecRelevancePushNotificationSender in CSCS should be set as follows:\n- Connection/'Use relevance' checkbox must be checked (default unchecked)\n- Connection/'Magazine' must be filled in with the correct number. This must be supplied by the development team of the Ortec Relevance app (default empty)\n- Connection/'Notifications url' must be filled in with the correct url. This must be supplied by the development team of the Ortec Relevance app (default empty)\n- Connection/'Notifications url key' must be filled in with the correct key. This must be supplied by the development team of the Ortec Relevance app (default empty)\n\nAfter correctly filling in the settings, the new process OrtecRelevancePushNotificationSender must be enabled in Process Configuration.\n\nThere are 2 types of notifications supported:\n1. ShiftOfferNotification - when shift is open for bidding in Ortec WS Client or AdHoc Planner\n2. GotShiftNotification - when shift is assigned in AdHoc Planner to an employee that responded to the offer\n\nThe status of the connection with the Ortec Relevance API can be checked by calling the command handler /ortecRelevancePushNotificationSender/CCheckStatusRelevanceAPI with an empty command\n\nRelevance Push Notification logging is done in ROS_NOTIFICATION_SENDER_LOGGING. ROS_NOTIFICATION_SERVER_UPDATES and ROS_NOTIFICATION_SENDER_UPDATES are used for temporarily storing the notifications before being processed.\n\nIf both Firebase API and Relevance Push Notification Connection are enabled, then Relevance Push Notification Connection takes precedence\nTo use Firebase API for notifications, it is necessary to:\n- disable the Relevance Push Notification Connection in CSCS Settings Manager\n- fill out the base URL of Firebase API in CSCS Settings Manager > Notifications > InternalNotificationsAPIUrl\n","For this solution to become available, the new version of the Backend Domains Api must be installed, and settings from release notes must be configured correctly.\n","OSDOWSD-3915",""]
[null,null,1371008,"2020-11-05",null,null,"New Feature","","","Export configuration was not compatible with MS reporting for multiple environments","Export configuration was not compatible with MS reporting for multiple environments. This has been fixed.\n\nTest hint(s):\n1. Verify only reports for the current environment are exported when multiple environments are there","","OSDCOMMAIN-13204","12241342"]
[null,null,1371008,"2020-11-05",null,null,"New Feature","Stability","Mobile application","FirebaseMobileApi: Task Scheduler task to keep site alive did not work correctly","FirebaseMobileApi: Task Scheduler task to keep site alive did not work correctly. This task has been removed from the installer script. In the install script it has been added to periodically recycle Application pool to keep the FirebaseMobileApi working correctly.\n\nTest hint(s):\nNone","For this solution to become available, the FirebaseMobileApi must be installed.","OSDCOMMAIN-13238","12274152"]
[null,null,1371008,"2020-11-05",null,null,"New Feature","Reliability","DataWarehouse","BI - Support View FACT_NL_Ingeplande_Dienst had wrong translation for a shift status","BI - Support View FACT_NL_Ingeplande_Dienst had wrong translation for a shift status.\nThis has been fixed.\n\nTest hint(s):\n1. Verify the BI support view FACT_NL_Ingeplande_Dienst gives expected results","","OSDCOMMAIN-13240","12274511"]
[null,null,1371008,"2020-11-05",null,null,"New Feature","Functionality","Planboard","Create a new duty based on template duty with no cost center now assigns cost center of the department","When creating a new duty using 'based upon' a template duty with no cost center, the new duty had no cost center. This holds for both creating a new duty from the maintenance / duty set form as from the plan board using 'New duty'.\nThis has been improved.\nThis scenario will now assign the cost center of the department to this duty. In case the 'based upon' template duty has a cost center, the new duty will still have that cost center.\n\nTest hint(s):\n1. Create a template duty A with no cost center.\n2. Create a new duty B for department X, based on the template duty A.\n3. Verify that duty B has as cost center the cost center of department X.","For this functionality to become available, the OWS Win32 client must be installed.","OSDCOMMAIN-13241","12287464"]
[null,null,1371008,"2020-11-05",null,null,"New Feature","Functionality","Planboard","Personal planboard showed scenario shifts","The personal planboard showed scenario shifts and regular scheduled shifts.\nThis has been fixed, the scenario shifts are no longer shown.\n\nTest hints:\n1. Create a scenario\n2. Create some shifts in the scenario and in the schedule\n3. Open the personal planboard, it should only show the regular scheduled shifts.","","OSDCOMMAIN-13278","12335855"]
[null,null,1371008,"2020-11-05",null,null,"New Feature","","","Fixed error when unfinalizing a subcontracted shift while a scenario exists with this shift ","When trying to unfinalize a subcontracted shift, while a scenario exists with this shift, an error would occur if the global setting UseUnassignedShiftWhenResourceNotInDepartment was set to False.\nThis has been fixed.\n\nThis fix is optional based on feature toggle: FeatureToggles\\EnableDeleteTransferForUnfinalization. The fix is by default enabled.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\n1. Create a subcontracted shift and set its status to final\n2. Create a scenario for the original department containing this shift\n3. Change the status of the subcontracted shift to concept, no error should occur","","OSDCOMMAIN-13280","12312655"]
[null,null,1371008,"2020-11-05",null,null,"New Feature","","","Several translations added for German language","Several German translations added.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13290","12362330"]
[null,null,1373136,"2020-11-12",null,"","New Feature","Reliability","Planning","An error could occur when switching status of schedule which contained declined/deleted subcontracts","An error could occur when switching status of schedule which contained declined/deleted subcontracts. This error occurred with the following settings configured:\n\n1. FEATURETOGGLES\\IMPROVEHANDLINGSUBCONTRACTEDSHIFTSWHENDELETINGSCHEDULE = Y\n2. OPTIONS\\ROSTERPERIOD\\DELETEUNASSIGNEDSHIFTSINSTATUS\\PUBLISHED = Y\n\nThis has been fixed. \nNOTE: This issue was introduced in 8.5.0(2020-10-01)_Build1361657\n\nTest hint(s):\n1. Verify switching status of schedule goes okay when mentioned settings are configured ","","OSDCOMMAIN-13298","12392660"]
[null,null,1373136,"2020-11-12",null,"","New Feature","Reliability","Client","Several translations added for French and German language","Several translations have been added for French and German for recent functional changes.\n\nTest hint(s):\nNone","","OSDOWSD-3988",""]
[null,null,1373136,"2020-11-12",null,"Backend Domains API","New Feature","Functionality","BackendDomainsAPI","An empty rulesetcode would lead to an Oops page when opening a proposal for a shift","Calculating the violations for a proposal in Ad Hoc Planning required a ruleset to be assigned to an employee. When there was none assigned, an error was returned that led to an Oops page in the UI.\nThis has been changed. \nNow, having no ruleset for an employee is a valid situation. The UI will show that there are no violations instead of an Oops page.\n\nTest hint(s):\n1. The proposal screen in Ad Hoc Planning can be shown correctly","","OSDOWSRES-685",""]
[null,null,1375551,"2020-11-19",null,"","New Feature","Security","Database","DBAnonymize did not remove data related to notification push sender functionality","DBAnonymize did not remove data related to notification push sender functionality.\nWhen the functionality is enabled that was introduced in \"OSDOWSD-3915 New functionality has been added for sending notifications to Ortec Relevance App\" data written to tables ROS_NOTIFICATION_SEVER_UPDATES, ROS_NOTIFICATION_SENDER_LOGGING, ROS_NOTIFICATION_SENDER_UPDATE was not properly anonymized with DBAnonymize.\nThis has been fixed.\n\nTest hints:\n1. Verify that when anonymizing a database with DBAnonymize data in ROS_NOTIFICATION_SEVER_UPDATES is truncated.\n2. Verify that when anonymizing a database with DBAnonymize data in NOTIFICATION_SEVER_UPDATES is truncated.\n3. Verify that when anonymizing a database with DBAnonymize data in ROS_NOTIFICATION_SENDER_LOGGING is truncated.","","OSDCOMMAIN-13304",""]
[null,null,1375551,"2020-11-19",null,"","New Feature","Security","Security","DBAnonymize did not anonymize csms settings","DBAnonymize did not anonymize csms settings. This has been improved.\n\nTesthint(s):\n1. Verify database can be anonymized via tool DBAnonymize","","OSDCOMMAIN-13305",""]
[null,null,1375551,"2020-11-19",null,"","New Feature","Stability","Planboard","Changing employees in workstation planboard worked inconsistently","In the workstation planboard, when trying to change an employee by clicking on the right mouse button, the pop-up window sometimes did not show the employee.\nThis has now been fixed. \n\nTest hint(s):\n1. Verify when changing an employee in the workstation planboard by clicking on the right mouse button the correct employee is shown in the pop-up window","","OSDCOMMAIN-13308","12408625"]
[null,null,1375551,"2020-11-19",null,"","New Feature","Functionality","Calculation","New labor rule \"Minimum time between attendance shift and long shift\" has been added","A new rule \"Minimum time between attendance shift and long shift\" has been added. This rule is needed for German heathcare customers.\nAdded global setting TimeBetweenAttendanceAndLongLaborPeriodReq which is turned off by default.\n\nTest hints:\n1. Activate the new rule and see if it creates the correct violations if a schedule does not meet this rule.","","OSDOWSD-3994",""]
[null,null,1375551,"2020-11-19",null,"","New Feature","Functionality","Calculation","New labor rule \"Minimal rest after work stand by (labor period)\" has been added","A new rule \"Minimal rest after work stand by (labor period)\" has been added. This rule is needed for German health care customers.\nAdded global setting MinRestAfterWorkStandByLaborPeriodReq which is turned off by default.\n\nTest hint(s):\n1. Activate the new rule and see if it creates the correct violations if a schedule does not meet this rule.","","OSDOWSD-3996",""]
[null,null,1375551,"2020-11-19",null,"","New Feature","Reliability","Client","Several translations added for German and French","Several translations have been added for German, French for recent functional changes.\n\nTest hint(s):\nNone","","OSDOWSD-4002",""]
[null,null,1377499,"2020-11-26",null,"","New Feature","Technical","Mobile Communication","OrtecRelevancePushNotificationSender: notifications sent by cpms process could not be processed","OrtecRelevancePushNotificationSender: notifications sent by cpms process could not be processed. Reason for this was that the arguments of the message sent was in the wrong order.\nThis has been fixed.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13332",""]
[null,null,1377499,"2020-11-26",null,"Ad Hoc Planning","New Feature","Performance","BackendDomainsAPI","Improved performance of proposal window by changing violations calculation\n","The performance of opening the proposal window in Ad Hoc Planning is slow, partly because violations need to be calculated. \nThis has been improved. Now, the performance of the part where violations are calculated is improved.\n\nNote that this is one of two issues where we will improve the performance of the proposal window.\n\nTest hint(s):\n1. Open an employee proposal for a shift in Ad Hoc Planning. Verify that violations are shown if applicable.","","OSDOWSRES-504",""]
[null,null,1379158,"2020-12-02",null,"","New Feature","","","Approving realizations in Ortec WS for Managers could give an error if there were no shifts left to approve","Approving realizations in Ortec WS for Managers could give an error if there were no shifts left to approve.\nIt has been fixed.\n\nPlease note that, this problem was introduced in 8.5.0(2020-09-17)_Build1357935.\n\nTest hint(s):\n1. Verify that shifts can be approved in Ortec WS for Managers.\n","","OSDCOMMAIN-13340","12452088"]
[null,null,1379158,"2020-12-02",null,"","New Feature","Functionality","Calculation","New labor rule \"Maximum labor time of shifts (labor period)\" has been added ","A new rule \"Maximum labor time of shifts (labor period)\" has been added. This rule is needed for German health care customers.\nAdded global setting MaxLaborTimeOfLaborPeriodsReq which is turned off by default.\n\nTest hint(s):\n1. Activate the new rule and see if it creates the correct violations if a schedule does not meet this rule. ","","OSDOWSD-3991",""]
[null,null,1379158,"2020-12-02",null,"","New Feature","Functionality","Calculation","Labor rule \"Daily rest after a shift (labor period)\" extended with option for on call","The labor rule \"Daily rest after a shift (labor period)\" has been extended. It now contains an option to handle rests with on call differently, as required by some German labor laws.\n\nTest hint(s):\n1. When already using this rule, verify that the same violations occur as before\n2. To test the change: activate the new option of the rule and verify that the violations are as expected.","","OSDOWSD-3998",""]
[null,null,1379158,"2020-12-02",null,"","New Feature","Reliability","Client","Several translations added for German, French, Danish and Finnish","Several translations have been added for German, French, Danish and Finnish for recent functional changes.\n\nTest hint(s):\nNone","","OSDOWSD-4009/OSDOWSD-4016",""]
[null,null,1379158,"2020-12-02",null,"Ad Hoc Planning","New Feature","Performance","BackendDomainsAPI","Improved performance of retrieving a proposal by getting the data differently","The performance of opening the proposal window in Ad Hoc Planning is slow, partly because of the way data is retrieved from the OWS database.\nThis has been improved. Now, the performance of getting the data from the OWS database is improved.\n\nNote that this is one of two issues where we will improve the performance of the proposal window.\n\nTest hint(s):\n1. Open an employee proposal for a shift in Ad Hoc Planning. Verify that it shows the correct employees.","","OSDOWSRES-505",""]
[null,null,1381385,"2020-12-10",null,"","New Feature","Planboard","Functionality","In some cases the visualization of overnight workstation demands was wrong","When the FeatureToggleDoNotSplitOvernightWorkstationDemand was turned on, the visualization of overnight workstation demands was wrong. It would only show the demand on the first day, and not on the second day.\nThis has been fixed.\n\nTest hint(s):\n1. Open a workstation demand (Planning > Schedule management > Workstation demand)\n2. Open the workstation demand on Monday and create a demand from 22:00 to 02:00\n3. Open the workstation demand on Tuesday\n4. Verify the demand is now correctly shown","","OSDOWSD-4025",12431109]
[null,null,1383027,"2020-12-17",null,null,"New Feature","Technical","","Removed feature toggle LockSettingsTableWhenWritingChange","The server setting FeatureToggle\\LockSettingsTableWhenWritingChange has been removed. This setting was introduced in September 2020 in the issue OSDCOMMAIN-13117.\n\nSince this is more than three months ago and has been used extensively, this is no longer needed and the setting could be safely removed. This functionality is now always enabled.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13201",""]
[null,null,1383027,"2020-12-17",null,null,"New Feature","Reliability","Calculation","In some cases, it was not possible to selfroster available duties in a duty group in Ortec WS for Employees","In some cases, it was not possible to selfroster available duties in a duty group in Ortec WS for Employees. This has been fixed.\n\nTest hint(s):\n1. Verify the duties in duty groups can be selfrostered ","","OSDCOMMAIN-13294","12335904"]
[null,null,1384430,"2020-12-23",null,null,"New Feature","Functionality","Client","Cost Center with validity period resulted in an error message when assigned to a department with validity period","An error message could be shown when selecting another department in the organisation window. This could happen when a cost center with a validity period was assigned to a department with validity period. This has been fixed. \n\nTest hint(s):\n1. Verify that a cost center with validity period can be assigned to a department valid within that period.","Updating the win-32 client is required for this change to become available.","OSDCOMMAIN-13296","12387797"]
[null,null,1384430,"2020-12-23",null,null,"New Feature","Reliability","Database","DBUpdate failed over LAST_UPDATED_AT","Running the database update script for \"Add LAST_UPDATED_AT column to all entity tables\" (buildnr 1241050) would fail if some tables already had the column LAST_UPDATED_AT. \nThis has been fixed.\n\nTest hint(s):\n1. DBUpdate running updates still works","","OSDCOMMAIN-13303","12396260"]
[null,null,1384430,"2020-12-23",null,null,"New Feature","","","Getting the default period of an account in ORTEC WS for Employees resulted in an error message when the schedule(s) of the employee is in status 'Plan'","Getting the default period of an account in ORTEC WS for Employees resulted in an error message when the schedule(s) of the employee is in status 'Plan'. This has been fixed.\n\nTest hint(s):\n\n1. Verify that it is possible to retrieve the default period of an account without error when the schedule(s) of the employee is in status 'plan'.","","OSDCOMMAIN-13347","12434453"]
[null,null,1384430,"2020-12-23",null,null,"New Feature","Reliability","Planboard","Access violation occured when shortening a schedule period with subcontracted shifts","An access violation occured when shortening a schedule period with subcontracted shifts, which also contained other non-subcontracted shifts.\nThis has been fixed\n\nTest hint(s):\n1. Add a new scheduling period\n2. Add at least 2 shifts\n3. Subcontract 1 shift to another department\n4. Change the to date of the scheduling period to a date earlier than the date of the subcontracted shift\n5. You should now receive 2 messages:\n5. a. This action might lead to a loss of shifts\n5. b. This action cannot be performed since subcontracted shifts cannot be deleted","","OSDCOMMAIN-13358","12501950"]
[null,null,1384430,"2020-12-23",null,null,"New Feature","Functionality","Calculation","Added an option 'Assign workstations to fixed shifts' in the workstation optimizer","Added an option 'Assign workstations to fixed shifts' in the workstation optimizer. \nWhen disabled, fixed shifts will not be used by the optimizer. \nWhen enabled, fixed shifts will be used by the optimizer. \nBlocked shifts can never be used by the optimizer (no change here).\n\nTest hint(s):\n1. Open a workstation planboard\n2. Under 'Optimizers', open the 'Workstation optimizer' and expand the 'Details <<' \n3. At the bottom, the checkbox 'Assign workstations to fixed shifts' is added","For this change to become available, the win32 client must be updated","OSDCOMMAIN-13362",""]
[null,null,1384430,"2020-12-23",null,null,"New Feature","","","Interface worker caused an access violation and later halted when a realization is reverted and a new realization is created on the same day","Interface worker caused an access violation and later halted when a realization is reverted and a new realization is created on the same day. This has been fixed.\n\nTest hint(s):\n1. Verify that reverting an employee realization and creating another realization on the same day does not result in interface worker halting.","","OSDCOMMAIN-13378","12525985"]
[null,null,1386678,"2021-01-07",null,"CDBA","Bug","Performance","Security","Anonymizer issue - growing SQL log file","The DBAnonymizer tool could give an error for databases with a large number of UDF records, this was caused by a transaction log that grew very big. \n\nThis is prevented now, by not executing individual anonymization scripts within one transaction by default.\nTest hint(s):\n1. None","","OSDCOMMAIN-11575","9814804"]
[null,null,1386678,"2021-01-07",null,"","New Feature","","","Calculation list in master schedule planner report showed the same calculation multiple times when there exists calculation of type 'Calculation based on other calculations'","Calculation list in master schedule planner report showed the same calculation multiple times when there exists calculation of type 'Calculation based on other calculations'. It has been fixed.\n\nTest hint(s):\n1. Verify that when calculation of type 'Calculation based on other calculations' is used, the calculation is shown only once in the master planner report calculation list.","","OSDCOMMAIN-13311","12411336"]
[null,null,1386678,"2021-01-07",null,"","New Feature","Stability","Import / Export","Interfaceworker halted when changing an imported field that contained a certain unicode character ","Interfaceworker halted when changing an imported field that contained a certain unicode character. This has been improved. Unknown characters are converted to '?' in database and in memory of interfaceworker.\n\nTest hint(s):\n1. Verify fields containing unicode characters can be imported\n2. Verify after restarting interfaceworker the imported field can be adjusted  ","","OSDCOMMAIN-13323","12431061"]
[null,null,1386678,"2021-01-07",null,"","New Feature","Functionality","Calculation","Duties with workstation were not booked properly in transfer and carry over rules in maintenance reporting remuneration","Duties with workstation were not booked properly in transfer and carry over rules in maintenance reporting remuneration. This has been fixed.\n\nTest hint(s):\n1. Verify that when a duty has assigned workstation, that duty is correctly booked on transfer and carry over rules in maintenance reporting remuneration.","","OSDCOMMAIN-13348","12447236"]
[null,null,1386678,"2021-01-07",null,"","New Feature","","","Several translations updated and added for Danish and French","Several translations updated and added for Danish and French.\n\nTest hint(s):\n1. None","For the correct translation of the 'Content' group box in the Messages window in OWS Win32 client, the new client needs to be installed.","OSDCOMMAIN-13387","12556910"]
[null,null,1386678,"2021-01-07",null,"","New Feature","Reliability","Optimization","Workstation optimizer did not copy properties of original activities (e.g. costcenter) when assigning workstations ","Workstation optimizer did not copy properties of original activities (e.g. costcenter) when assigning workstations. This has been fixed.\nNote: when using option 'merge activities with same workstation', it is allowed to merge activities with different properties.\n\nThis fix is optional based on feature toggle: FeatureToggles\\CopyActivityPropertiesInWorkstationOptimizer. The fix is by default enabled.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s): \n1. Verify when running workstation optimizer, original activity properties are kept when assigning workstations.","","OSDOWSD-4059",""]
[null,"Y",1388837,"2021-01-14",null,"","New Feature","Reliability","Tools","SQL Server version support has changed","SQL Server version support has changed\n\nSQL Server 2019 is now supported.\n\nSQL Server 2014 is no longer supported.\n","","OSDCOMMAIN-13406"]
[null,"Y",1388837,"2021-01-14",null,"","New Feature","Technical","Database","BI packages have been merged","BI packages have been merged.\nBI packages for SQL Server 2016 and SQL Server 2017 have been moved to a single folder, 'BI Packages' which supports Server 2016, SQL Server 2017 and SQL Server 2019.\n\nTest hint(s): \n1. Verify BI still works as expecedt by executing an incremental load","","OSDOWSD-3971"]
[null,"Y",1388837,"2021-01-14",null,"","New Feature","","","Updated OWS 7 binaries","OWS 7 binaries are built using Delphi 10.4.\n\nTest hints:\n1. Verify CMHS Networks function as expected (if applicable)\n2. Verify configured reports can be opened in OWS win32 client (if applicable)\n","For this update to become available, it is mandatory to install the OWS Win32 client. \n\nDue to the Delphi upgrade all binary files have been updated. \n\nIt is highly recommended to use the OWS Client installer to:\n\n- Update the Client distribution packages (e.g. for Citrix)\n- Update the Client on a Terminal Server\n- Update the Client on FAT Clients\n\nIt is recommended to use the separate PatchConfiguraton application instead of the full CSCS","OSDOWSD-3986"]
[null,null,1390394,"2021-01-21",null,"","New Feature","Reliability","Win32 Userinterface","Typing a time after adding an activity in a duty set could lead to unexpected time values","Typing a time after adding an activity in a duty set could lead to unexpected time values\nWhen typing values in a time edit (hh:mm) in a dutyset after the actions Add activity, Split activity or Delete activity the behaviour of the time edit could cause the resulting value to differ from the value actually entered.\nE.g. '12:34' could becomes ' 2:34'. These would have to be corrected manually.\nThis has been fixed.\n\nTest hints:\n1. Verify that changing Begin or End time after adding an activity to a duty in a dutyset","For this functionality to become available, the OWS Win32 client must be installed.","OSDCOMMAIN-13415","12590701"]
[null,null,1390394,"2021-01-21",null,"","New Feature","Functionality","Optimization","Workstation optimizer: added options to determine how workstation demand should be planned","Workstation optimizer: added options to determine how workstation demand should be planned.\nThere are 2 options to choose from in the details of the workstation optimizer:\n1. \"Partly (overlapping with optimization period)\". This option is selected by default. It means that workstation demands and shift activities are planned for their part within the optimization period. Nothing will be changed outside the optimization period.\n2. \"Completely (starting in optimization period)\". Behind this option new functionality is implemented. It means that only the workstation demands and shift activities that start in the optimization period are planned. Also, the shift activities can be planned for their part outside the optimization period.  \n\nNote 1: In case demands can be broken down by the optimizer the individual parts are considered as separate demands.\nNote 2: The functionality changed for OSDCOMMAIN-13134 is now behind the new option\nNote 3: OSDCOMMAIN-13344 is fixed with the new option\n\nTest hint(s):\nNone","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4069",""]
[null,null,1390394,"2021-01-21",null,"","New Feature","Reliability","Client","Several translations added for German and French","Several translations have been added for German and French for recent functional changes.\n\nTest hint(s):\nNone","","OSDOWSD-4085",""]
[null,null,1390394,"2021-01-21",null,null,"New Feature","Security","Miscellaneous","Added support for CPMS plugin Comtec.Workbench.Project.Common.Email to send mail using TLS ","Added support for CPMS plugin Comtec.Workbench.Project.Common.Email to send Client mails using TLS.\nIn the OWS Win32 Client it was not possible to directly send mails via an SMTP server with (only) TLS support. Now this is made possible by using an external plugin.\n\nA recent version of the CPMS plugin Comtec.Workbench.Project.Common.Email is to be installed and configured. Please note that this is an external plugin that can be used as-is.\n\nIn order to use this functionality, the following needs to be configured:\n\n1. Settings in OWS Settings manager:\n  - OPTIONS\\MAIL\\SENDMAILCOMMANDHANDLERNAME = /comtec.workbench.project/common/email/CSendEmail\n  - OPTIONS\\MAIL\\SENDMAILVIACOMMANDHANDLER = Y\n\n2. The Comtec.Workbench.Project.Common.Email CPMS plugin will send the email from the server it is running on.\n  This server needs to be allowed to connect to the SMTP server configured in the plugin process settings.\n\nTest hints:\n1. When OPTIONS\\MAIL\\SENDMAILVIACOMMANDHANDLER = Y is already configured with another command handler verify mailing from OWS Win32 Client works as expected\n2. When OPTIONS\\MAIL\\SENDMAILVIACOMMANDHANDLER = N verify mailing from OWS Win32 Client works as expected","For this functionality to become available, the OWS Win32 client must be installed.\n\nThe required plugin has been made available in the following location:\n\\\\ortec.intranet\\logis\\Products\\OWS\\7\\Projects\\ORTEC-Plugins","OSDOWSD-4066"]
[null,null,1392461,"2021-01-28",null,null,"New Feature","Performance","Manager self-service","OWS for Employees/Managers: Retrieving permissions could be slow for some routes","Retrieving permissions for some routes could be slow.\nThis has been improved.\nThe impact of the improvement can be significant when Access Control has a complex role structure.\nFor OWS for Managers the impact is more noticeable than for OWS for Employees\n\nTest hints:\n1. OWS for Employees\n  a. verify user can logon\n  b. verify reports can be configured and viewed\n2. OWS for Managers: \n  a. verify manager can logon\n  b. verify reports can be configured and viewed",null,"OSDCOMMAIN-13414",12590668]
[null,null,1392461,"2021-01-28",null,null,"New Feature","Reliability","GUI","In the OWS Win32 Client some windows were unexpectedly incomplete in size, so action buttons were (partially) not shown","In the OWS Win32 Client some windows were unexpectedly incomplete in size, so action buttons were (partially) not shown.\nThis has been fixed.\n\nTest hints:\n1. Verify a salary group can be added\n2. Verify a property can be added to an employee","For this functionality to become available, the OWS Win32 client must be installed.","OSDOWSD-4091"]
[null,null,1392461,"2021-01-28",null,"Ad Hoc Planning","New Feature","Functionality","BackendDomainsAPI","It was not possible to assign a shift that starts or ends with a Pause activity in adhocplanning","It was not possible to assign a shift in Ad Hoc Planning when the shift started or ended with an activity that is not work related (e.g a break).\n\nThis has been fixed.\nIt is now possible to assign any vacant shift to an employee using the proposal in Ad Hoc Planning.\n\nTest hints:\n1) Use a proposal to assign a vacant shift to an employee  ",null,"OSDOWSRES-268"]
[null,null,1393892,"2021-02-04",null,"","New Feature","","","Several translations updated for German","Several translations updated for German.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13433","12632438"]
[null,null,1393892,"2021-02-04",null,"Ad Hoc Planning","New Feature","Functionality","Service","Added support to call an employee to shift proposal","Added functionality to see the phone number(s) of an employee in the shift proposal. A phone button was added to the proposed employee line, which when clicked, will open a detail window showing the phone number(s) of the employee. If the device is configured to make phone calls, the employee will be called when the phone number is clicked.\nFor this functionality to be available to the user, a new permission in AccessControl must be granted: ORTEC WS Ad Hoc Planning/Phone Numbers in Adhoc Planner. By default, this permission is revoked.\n\nTest hint(s):\n1. Open a shift proposal. Verify that the phone icon is shown only in case the user has permission in AccessControl to see the phone numbers\n2. Open a shift proposal. Verify that the phone icon is shown only in case the employee has at least one phone number\n3. Open a shift proposal with an employee with phone numbers. Click the phone button. Verify that the phone numbers of the proposed employee are shown","For this functionality to become available, CWSS Server and Backend Domains API must be updated to build 1393892 or higher.","OSDOWSRES-884",""]
[null,null,1395368,"2021-02-11",null,"","New Feature","Functionality","Planboard","Opening old schedules in OWS Win32 client has been made dependent on an Access Control permission and a server setting ","Opening old schedules in OWS Win32 client has been made dependent on an Access Control permission and a server setting for performance improvement.\n\nWith this change, users with the newly created Access Control permission, OPEN_OLD_ROSTERS granted are allowed to open any schedule of the department the permission is given to irrespective of how old the schedule is.\n\nWhen the permission OPEN_OLD_ROSTERS is not granted, the user is only allowed to open a schedule based on a newly created server setting, MaxNofDaysInPastToOpenRosters. The user is then not allowed to open any schedule, whose begin date is older than MaxNofDaysInPastToOpenRosters days from the current date. \n\nThe default value of MaxNofDaysInPastToOpenRosters is set to 365. This setting has been created in OWSSettingsManager/Users = Server/Options/Planboard.\n\nTest hint(s):\n1. Verify that there exists a permission, OPEN_OLD_ROSTERS in Access Control and a server setting MaxNofDaysInPastToOpenRosters in OWSSettingsManager/Users = Server/Options/Planboard.\n\n2. Verify that when the permission OPEN_OLD_ROSTERS is granted, the user is allowed to open any schedule for the department the permission is granted for.\n\n3. Verify that when the permission OPEN_OLD_ROSTERS is not granted, the user is only allowed to open schedules not older than MaxNofDaysInPastToOpenRosters.","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4111",""]
[null,null,1397158,"2021-02-18",null,"","New Feature","Reliability","Logging","When a manual clock-in is done in ORTEC WS Win32 client, server log was incorrect","When a manual clock-in is done in ORTEC WS Win32 client, server log wrongly showed that all resources were refreshed in the Clocking Form. It is been fixed.\n\nTest hint(s):\n1. Verify that clocking can be done in ORTEC WS Win32 client.","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDCOMMAIN-13382","12541023"]
[null,null,1397158,"2021-02-18",null,"","New Feature","Functionality","Manager self-service","ORTEC WS for Managers: Query to retrieve ShiftsToApprove failed when there are more than 4500 shifts","ORTEC WS for Managers: Query to retrieve ShiftsToApprove failed when there are more than 4500 shifts.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that shifts with pending realizations can be retrieved in ORTEC WS for Managers.","","OSDCOMMAIN-13396","12579290"]
[null,null,1397158,"2021-02-18",null,"","New Feature","","","Several translations added for French and German language","Several translations added for French and German language.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13457","12362330"]
[null,null,1397158,"2021-02-18",null,"","New Feature","Reliability","Win32 Userinterface","ORTEC WS win32 client: Creating/Changing/Removing clockings in Clockings Times could cause access violations","ORTEC WS win32 client: Creating/Changing/Removing clockings in Clockings Times could cause access violations\nThis has been improved.\n\nTest hint(s):\n1. Verify Creating/Changing/Removing clockings in Clock Times","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDCOMMAIN-13466","12717192"]
[null,null,1397158,"2021-02-18",null,"","New Feature","Functionality","Data entry","A new configurable consistency check, ROTATIONUNITLINESINGLEDEPARTMENTCHECK has been added to avoid assigning employees to multiple departments","A new configurable consistency check, ROTATIONUNITLINESINGLEDEPARTMENTCHECK has been added that can be used to avoid assigning employees to multiple departments at the same time. This consistency check is located in OWSSettingsManager/User=Server/ConsistencyChecks. This consistency check has been disabled by default. When it is disabled, OWS functionalities remain as before (i.e. employees can be assigned to multiple departments). When enabled, this consistency check will prevent employees being assigned to multiple departments at the same time. However, an employee can still be assigned to a central department or lent out to another department (it only affects the direct department assignments). This consistency check, when enabled, will also affect imports.\n\nThe consistency check, ROTATIONUNITLINESINGLEDEPARTMENTCHECK will not be performed at startup, and therefore will have no impact on any employee with multiple assignments before the check has been enabled.\n\nTest hint(s):\n\n1. Verify that consistency check, ROTATIONUNITLINESINGLEDEPARTMENTCHECK exists in OWSSettingsManager/User=Server/ConsistencyChecks, it is disabled by default and can be enabled.\n\n2. Verify that when the check is disabled, employees are allowed to be assigned to multiple departments including during import.\n\n3. Verify that when the check is enabled, employees are not allowed to be assigned to multiple departments in the Client as well as during an import.","","OSDOWSD-4107",11883361]
[null,null,1398831,"2021-02-25",null,"","New Feature","Reliability","Reporting","Report Master Schedule did not always show general absence in privacy mode","Report Master Schedule did not always show general absence in privacy mode. This was the case for the report in the ORTEC WS Win32 client and ORTEC WS for Employees. This has been fixed.\n\nThe issue occurred when a leave or illness shift was realised with a work activity.\n\nTest hint(s):\n1. Verify correct shift names are shown in report","","OSDCOMMAIN-13355","12500791"]
[null,null,1398831,"2021-02-25",null,"","New Feature","Configuration","Documentation","Firebase documentation update of readme.txt","Readme.txt has been updated for Firebase Mobile Api.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13373","12522227"]
[null,null,1398831,"2021-02-25",null,"","New Feature","Reliability","Datawarehouse","BI: COST_CENTER_KEY in DIM_Departments was not updated when a new DIM_COST_CENTER entry was created","BI: COST_CENTER_KEY in DIM_Departments was not updated when a new DIM_COST_CENTER entry was created.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that BI Table, DIM_Departments is correctly updated with COST_CENTER_KEY  when a new DIM_COST_CENTER entry was created.","","OSDCOMMAIN-13374","12524499"]
[null,null,1398831,"2021-02-25",null,"","New Feature","Stability","Planboard","Processing all sick-leaves as reported could halt a worker due to a concurrency issue","Processing all sick-leaves as reported could halt a worker due to a concurrency issue\nWhen using 'All new or altered sick-leave (x) have been reported' in the sick-leave window, the sick-leaves were processed without protection against concurrent actions i.e. removal/change of a sick-leave. This could corrupt memory while all sick-leaves were processed. A worker could halt when handling an update with the corrupted data.\nThis has been improved.\nWhile all sick-leaves are processed they are protected against concurrent actions.    \n\nTest hint(s):\n1. Verify that sick-leaves can be processed.","","OSDCOMMAIN-13376","12524604"]
[null,null,1398831,"2021-02-25",null,"","New Feature","Configuration","Interfaces","The Logfiles.xsl has been added to the update","The Logfiles.xsl has been added to the update.\nAn english version and german version have been added.\n\nThe files can used in OWS SettingsManager setting SERVER\\INTERFACES\\LOGFILESTYLESHEET.\nThis is used as stylesheet to format the import/export messages that are retrieved in the message box.\n\nTest hint(s)\n1. Verify that import/export messages are formatted correctly in the message box","","OSDCOMMAIN-13388","12556910"]
[null,null,1398831,"2021-02-25",null,"","New Feature","Reliability","Win32 Userinterface","When opening from ORTEC WS Win32 Client, Dual client windows sometimes opened minimized","When opening from ORTEC WS Win32 Client, Dual client windows sometimes opened minimized.\nIt has been fixed by introducing a new server setting, CWGS_SAVE_MINMAXSTATE, in OWS Settings Manager\\Users=Server. The default value of the setting is set to 'Y'.\n\nTest hint(s):\n1. Verify that dual client windows (e.g. Date management view, Leave requests) open normally when server setting, CWGS_SAVE_MINMAXSTATE is set to 'Y' or 'N'.","For this solution to become available, ORTEC WS WIn32 client must be installed.","OSDCOMMAIN-13393","12572131"]
[null,null,1398831,"2021-02-25",null,"","New Feature","Stability","Miscellaneous","Interface worker could halt after trying to unplan a shift a 2nd time in ORTEC WS for Employees","Interface worker could halt after trying to unplan a shift a 2nd time in ORTEC WS for Employees\nWhen a transaction that deleted the shift is not yet finished: the shift is removed from memory but not yet from the database. This could cause reloading the data of that same shift when a 2nd transaction tried to delete the shift again at the same time.\nThis could causing memory inconsistency.\nThis could cause the worker to halt. \nThis has improved.\nWhen such a 2nd deletion takes place the transaction is aborted with an error message.\n\nTest hints:\n1. Verify planning/unplanning shifts in OWS for Employees\n","","OSDCOMMAIN-13398",""]
[null,null,1398831,"2021-02-25",null,"","New Feature","Stability","Data Entry","Employee name and number were not always shown in interface message","When an employee with a shift with option 'Plan contract hours' was imported, and the availabiltiy of the employee was changed to 0 hours, the interface message did not contain the name and number of the employee. This information has been added. \nThe employee name and number are now shown in the interface message, but not in the logfile and in the manual interface window.\n\nTest hint(s):\n1. Verify that importing an employee works.","","OSDCOMMAIN-13401","12581629"]
[null,null,1398831,"2021-02-25",null,"","New Feature","Reliability","BackendDomainsAPI","Improved error handling in notifications API","Errors that occur when sending notifications for shift offering will be retried after a short while. In some cases, this will lead to attempts to resend a message while it is already known that this will not succeed. This happens when an employee can work a shift, but this employee does not have a phone running the mobile app. \nThis has been improved. \nThe BackendDomainsApi will now return a more fine grained response when an error occurs, so no retries will be done when an employee does not have the mobile app.\n\nTest hints:\n1) Offer a shift in Ad Hoc Planning","","OSDOWSRES-684",""]
[null,null,1400514,"2021-03-05",null,null,"New Feature","Functionality","Import / Export","Added import of Holiday property values","Added import of Holiday property values.\nIt is now possible to add property values during import of a public holiday. This can be done by adding the next lines: \n<THoliday>\n..\n  <TUserPropertyValuess>\n    <TUserPropertyValues>\n      <UPY_NAME>Test</UPY_NAME>\n      <VALUE>bla</VALUE>\n    </TUserPropertyValues>\n  </TUserPropertyValuess>\n</THoliday>\n\nTest hint(s):\n1. Verify new holidays can be imported with and without properties\n2. Verify existing holidays can be imported with and without properties","","OSDOWSD-4155",""]
[null,null,1403267,"2021-03-12",null,"","New Feature","Functionality","Planboard","'Replace by activity type' and 'Change shift remark' functionalities are now available for shifts in the planboard of a central department for both: shifts sent to the central department and shifts in the decentral departments","'Replace by activity type' and 'Change shift remark' functionalities are now available for shifts in the planboard of a central department for both: shifts sent to the central department and shifts in the decentral departments.\n\nThese functionalities are only available to the users who have ows.hmy.ROSTER_PLAN_WRITE/ows.hmy.ROSTER_PUB_WRITE_ForDepartment (Depending on the status of the shift) permission granted for the current department of the shift.\n\nPlease note that, the functionalities are not available when more than one shift is selected at the same time.\n\nTest hint(s):\n1. Verify that it is possible to change a shift in the central department by right clicking the shift and selecting 'Replace by activity type'. \n2. Verify that it is possible to change a remark of a shift in the central department.","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4161",""]
[null,null,1405047,"2021-03-19",null,"","New Feature","Technical","Planning","Added permissions for deleting availability in ORTEC WS for Employees","Added permissions for deleting availability in ORTEC WS for Employees.\nTwo new permissions are made available for deleting availabilities and unavailabilities: /CWGS/OWS/ESS/DeleteAvailabilityAction and /CWGS/OWS/ESS/DeleteUnavailabilityAction. These will be used in ORTEC WS for Employees. This logic is not yet available but will be implemented in OSDOWSESS-2236\n\nTest hint(s):\n1. Verify new permissions are available in Access control","","OSDCOMMAIN-13472",""]
[null,null,1405047,"2021-03-19",null,"","New Feature","Reliability","Security","Improved multi-level domain support for locating User Principal Names ","Improved multi-level domain support for locating User Principal Names.\nWhen users that should be allowed access to the system could exist in different domains, their User Principle names could not be located using the Directory Services.\nThis has been improved.\nIn the Windows Authentication configuration it is now possible to add a semi-colon separated list of domains that should be used to locate the User Principal information.\n\nTest hint(s)\n1. Verify users can login and use the client applications\n2. Verify users can login ORTEC System Configuration\n","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4169",""]
[null,null,1405047,"2021-03-19",null,"Ad Hoc Planning, Shift Offering","New Feature","Functionality","BackendDomainsAPI","[BDA]Added setting 'UseShiftProposal'","Added CSMS setting: AdhocPlanning\\ShiftProposals\\UseShiftProposal, with default value false. If the value is set to true, or if the Ad Hoc Planning tenant does not have Shift Offering configured, then the Ad Hoc Planning user can open the shift proposal for vacant shifts.\n\nTest hint(s):\n1. Set the value of the new setting to: true. Open an employee proposal for a shift in Ad Hoc Planning.","For this functionality to become available, issue OSDOWSRES-1038 for the Ad Hoc Planning frontend must also be released.","OSDOWSRES-909",""]
[null,null,1407033,"2021-03-26",null,"","New Feature","","","Several translations updated for French and German","Several translations added for French and German.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13490",""]
[null,null,1407033,"2021-03-26",null,"","New Feature","Stability","Core Framework","Queueing of processing command handler calls in worker could cause Access Violation in CCDS.cem","Queueing of processing commandhandler calls in worker could cause Access Violation in CCDS.cem\nThis has been improved.\nWhen handling commands received in the worker a local copy (a part) of the command document is used to parse the command. This prevents the Access Violation from happening\n\nTest hints:\n1. verify shortage and surplus information can be retrieved in ORTEC WS for Managers\n","","OSDCOMMAIN-13501","12811662"]
[null,null,1407033,"2021-03-26",null,"","New Feature","Functionality","Planboard","It is now possible to add shifts to a planboard based on a permission, when department has the status Closed or higher","When the newly created permission, ADD_SHIFT_IN_ROSTER_CLOSED_OR_HIGHER in Access Control/Ortec WS for Windows/Planboard is granted to a user, the user is now allowed to add shift to a planboard when department status is Closed or higher for the department the permission is granted for.\n\nWhen the department status is Closed, the created shift will have a realization of the duty chosen for the shift.\n\nWhen the department status is higher than Closed,  the created shift will have a pending update of the duty chosen for the shift.\n\nTest hint(s):\n1. Verify that when permission ADD_SHIFT_IN_ROSTER_CLOSED_OR_HIGHER  is granted, it is possible to add a shift to a planboard of a department which has status Closed or higher.","","OSDOWSD-4182",""]
[null,null,1409925,"2021-04-09",null,"","New Feature","","","Creating a new salary period was not be possible when the salary period is more than a year apart and requirement 'Number of free weekends' is used","Creating a new salary period was not be possible when the salary period is more than a year apart and requirement 'Number of free weekends' is used.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that salary periods can are created when the requirement Number of free weekends is used.","","OSDCOMMAIN-13504","12840405"]
[null,null,1409925,"2021-04-09",null,"","New Feature","Performance","Calculation","Adding or deleting manual clocking updated all employees in Clock Times Overview","Adding or deleting manual clockings updated all employees in Clock Times Overview.\nBased on goal mentioned in analysis ticket OSDCOMMAIN-13491 a part of the refreshing the grid has been improved.\nWhen a manual clocking that can be associated to a shift is added or deleted only the changed lines of the grid are updated\nWhen a manual clocking that cannot be associated to a shift is added or deleted the full update of the grid is still done.\n\nTest hint(s):\n1. Verify that manual clock in and clock out can be done in Clock times\n2. Verify that clockings can be deleted in Clock times","For this solution to become available, ORTEC WS Win32 client needs to be installed.","OSDCOMMAIN-13518",""]
[null,null,1411742,"2021-04-15",null,"","New Feature","Reliability","Employee self-service","An error occured in Self-Scheduling in ORTEC WS for Employees if a shift ends at 0200 on the day daylight saving starts","An error occured in Self-Scheduling in ORTEC WS for Employees if a shift ends at 0200 on the day daylight saving starts. This has been fixed.\n\nTest hint(s):\n1. Verify that Self-Scheduling in ORTEC WS for Employees does not cause an error on the day daylight saving starts.","","OSDCOMMAIN-13404","12588773"]
[null,null,1411742,"2021-04-15",null,"","New Feature","Reliability","Reporting","OWS for Employees: Overview shift reassignments did not show the correct title in different languages","OWS for Employees: Overview shift reassignments did not show the correct title in different languages.\nThis has been fixed.\n\nTest hint(s):\n1. Verify the Overview shift reassignments report works as expected in OWS for Employees","","OSDCOMMAIN-13431","12628892"]
[null,null,1411742,"2021-04-15",null,"","New Feature","Functionality","Manager self-service","Open realizations were not visible in ORTEC WS for Managers when the schedule is partly approved","Open realizations were not visible in ORTEC WS for Managers when the schedule is partly approved. This has been fixed.\n\nTest hint(s):\n1. Verify that when there is an open realization in the closed/published/plan part of a partly approved schedule, it is visible in ORTEC WS for Managers.","","OSDCOMMAIN-13435","12597516"]
[null,null,1411742,"2021-04-15",null,"","New Feature","","","Shift counters of one-time shifts not sorted alphabetically ","Shift counter of one-time shifts based on duty name or duty property factions were not sorted alphabetically.\nThis has been fixed.\nThe factions are sorted alphabetically after a refresh of the planboard\n\nTest hint(s):\n1. Verify that shift counter grid has alphabetically sorted rows when configured for one-time shifts based on duty name or duty property factions in shift counter plan board settings.\n2. Verify that the rows of the shift counter grid can still be manually re-arranged.\n3. Refreshing the plan board by pressing F5 should show the alphabetic ordering of the rows of the shift counter grid.","","OSDCOMMAIN-13443","12682142"]
[null,null,1411742,"2021-04-15",null,"","New Feature","","","Recurring requests did not allow to create new recurring request within repetition period","Recurring requests did not allow to create new recurring request within repetition period. It has been fixed.\n\nTest hint(s):\n1. Verify that recurring requests can be created within the repetition period of existing recurring requests in Shifts/Request View of Planboard in ORTEC WS Win32 Client.","","OSDCOMMAIN-13444","12684672"]
[null,null,1411742,"2021-04-15",null,"","New Feature","Stability","Calculation","A memory peak could occur in compensation rule 'Transferbooking based on expression'","A memory peak could occur in compensation rule 'Transferbooking based on expression'. \n\nThis has been improved when bookings are grouped per shift, per equal properties or per entry day.\n\nTest hint(s): \n1. Verify bookings for the compensation rule 'Transferbooking based on expression' are correct","","OSDCOMMAIN-13470",""]
[null,null,1411742,"2021-04-15",null,"","New Feature","","","Several translations updated for German language","Several translations have been added for German for recent functional changes.\n\nTest hint(s):\nNone","","OSDCOMMAIN-13517","12886526"]
[null,null,1411742,"2021-04-15",null,"","New Feature","","","Removed feature toggle UseAsynchronousEventSending and asynchronous event sending is now always enabled","Removed feature toggle UseAsynchronousEventSending and asynchronous event sending is now always enabled.\n\nTest hint(s):\n1. None","","OSDOWSRES-703",""]
[null,null,1413028,"2021-04-22",null,"Backend Domains Api","New Feature","Performance","BackendDomainsAPI","Improved performance of proposal window by changing getting data for violations calculation","The performance of opening the proposal window in Ad Hoc Planning is slow, partly because the query to retrieve activities for the violation calculation takes too much time.\nThis has been improved. Now, the performance of the part where violations are calculated is improved.\n\nNote that this is one of multiple issues where we will improve the performance of the proposal window.\n\nThis issue also fixes the error when a shift or an activity is present, which is completely during the time that is skipped during the DST change in spring.\n\nTest hint(s):\n1. Open a schedule in Ad Hoc Planning.\n2. Open an employee proposal for a shift in Ad Hoc Planning. Verify that violations are shown if applicable.","","OSDOWSRES-985",""]
[null,null,1414212,"2021-04-29",null,"","New Feature","Functionality","Import/Export","When using TFillFieldsOfCOMTECShift in an import definition the shift NAME was not updated when adding a realisation on an existing shift","When using TFillFieldsOfCOMTECShift in an import definition the shift NAME was not updated when adding a realisation on an existing shift.\nThis has been improved.\nWhen the NAME of a shift is available in the import xml of the shift that is to be realised.the NAME is used in the realisation.\n\nNOTES:\n1. When using TIdentifyCOMTECShift extra xml creator set the parameter CheckShiftStatus=False to allow a NAME change\n2. The HighestAllowedDepartmentStatus parameter could prohibit a NAME change on an imported shift.\n\nTest hints:\n1. verify shift imports, using the TFillFieldsOfCOMTECShift extra xml creator in the import definition, work as expected.","","OSDOWSD-4232",""]
[null,null,1414212,"2021-04-29",null,"","New Feature","Functionality","Import/Export","When using TFillFieldsOfCOMTECShift in an import definition the shift STATUS of a shift could not be updated ","When using TFillFieldsOfCOMTECShift in an import definition the shift STATUS of a shift could not be updated (without using TChangeShiftStatusXMLCreator)\nThis has been improved.\n\nThe TFillFieldsOfCOMTECShift extra xml creator has a new parameter ShouldTakeShiftStatusIntoAccount, Default False.\nWhen ShouldTakeShiftStatusIntoAccount=True in the import definition the STATUS field (per shift) in the xml data imported will be used as shift status when data has been imported in the system.\n\nNOTES:\n1. When using TIdentifyCOMTECShift extra xml creator set the parameter CheckShiftStatus=False to allow a STATUS change\n2. The HighestAllowedDepartmentStatus parameter could prohibit a STATUS change on an imported shift.\n\nTest hints:\n1. Verify shift (realisation) imports, using the TFillFieldsOfCOMTECShift extra xml creator in the import definition, work as expected.   ","","OSDOWSD-4233",""]
[null,null,1414212,"2021-04-29",null,"Backend Domains Api","New Feature","Functionality","Service","Added Labor Rule Validation translations for Swedish and Danish","Added Swedish to the translations of the violation texts for the labor rule validation used by Ad Hoc Planning. Also added and changed some Danish violation text translations.\nThis functionality will be available for the users when Swedish and Danish are made available in the Ad Hoc Planning frontend.\n\nTest hint(s):\n1. Open a proposal in Ad Hoc Planning, or a request of an employee for an offered shift in Shift Offering. Verify that the violations are shown when the Swedish or Danish language is selected.\n","","OSDOWSRES-1089",""]
[null,null,1415216,"2021-05-06",null,"","New Feature","Reliability","Import/Export","Importing new duty with TFillFieldsOfCOMTECShift does not create an exchange","Importing shifts did not create any exchanges.\nThis has been fixed.\nTwo additional exchanges are created when importing new shifts.\n\nAdded Feature Toggle: FEATURETOGGLES\\CREATEEXCHANGESWHENIMPORTINGSHIFTS and is by default enabled.\n\nTest hint(s):\n1. Import a shift on a published planboard. Overview shift reassignments will show the new shift as expected.","","OSDOWSD-4142",12674516]
[null,null,1416276,"2021-05-12",null,"","New Feature","Functionality","","Borrowed employees in decentral department are now visible in the central department planboard based on a newly introduced checkbox, 'Show borrowed employees' ","It is now possible to see employees lent to decentral departments in the central department planboard. This can be done by checking the checkbox, 'Show borrowed employees'\nin the Decentral Departments tab in the Organization Window in the ORTEC WS Win32 client. \n\nThis checkbox is by default unchecked to conform to the existing functionality of not showing borrowed employees in the central departments.\n\nThis change will only be applied to borrowing periods that are valid in or after the month this update is applied to ORTEC WS. Historic borrowing periods are not considered. Older planboards will therefore not show borrowed employees, regardless of the new checkbox.\n\nPlease note that, an external planner started using the command handler will not take the checkbox into account. Therefore, it will use the borrowed employees in optimizing central department planboard.\n\nTest hint(s):\n\n1. Verify that no borrowed employee is shown by default in the central department planboard.\n2. Verify that after checking the checkbox, 'Show borrowed employees', borrowed employees with borrowing period valid on the current month and future are shown in the central department planboard.\n","For this solution to become available, the client must be installed.","OSDOWSD-4200",""]
[null,null,1416276,"2021-05-12",null,"","New Feature","Functionality","Calculation","Added functionality in Ad hoc planning to retrieve violations from CWSS Server","Added functionality in Ad Hoc Planning to retrieve violations from CWSS Server. These violations are retrieved when requesting a proposal for a shift. \n\nThis functionality will be available if the setting 'LaborRulesValidation/Calculation/UseCWSSForViolations' in CSCS is switched on.\n\nTest hint(s):\n1. Verify proposals can be retrieved in Ad Hoc Planning and violations are shown correctly","","OSDOWSRES-1016",""]
[null,null,1417164,"2021-05-20",null,"Backend Domains Api","New Feature","Stability","BackendDomainsAPI","The violation calculation could fail in the proposal for employees with multiple contracts","The violation calculation could fail in the proposal for employees with multiple contracts. This happened only when violations were calculated using CWSS, only for the contracts that were not created first, and only if the contract was in another department than the first created contract or the first contract was finished.\nThis has been fixed. Now, violations for the proposal can be calculated using CWSS for every contract.\n\nTest hint(s):\n1. Have an employee with multiple contracts available to work a shift. Open a proposal for that shift in Ad Hoc Planning. Verify that violations are calculated.","","OSDOWSRES-1114",""]
[null,null,1418324,"2021-05-27",null,"","New Feature","","","Several translations updated for French","Several translations updated for French\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13546","12962636"]
[null,null,1418324,"2021-05-27",null,"","New Feature","Reliability","Reporting","ORTEC WS for Employees: account report was calculating with incorrect published until date","ORTEC WS for Employees: account report was calculating with incorrect published until date.\n\nThis has been fixed. Now the published until date for an employee is taken as minimum published until date of all departments, the employee is assigned to during the period.\n\nTest hint(s):\n1. Verify account report can be opened in ORTEC WS For Employees","","OSDOWSESS-2353","12391626"]
[null,null,1418324,"2021-05-27",null,"Backend event publisher","New Feature","Security","Service","Improve security on events sent from BackendEventPublisher","Events sent to the integration services are signed using cryptographic keys. To improve security, the length of the keys has been increased from 1024 to 2048 bits.\n\nTest hints:\n1) Create or change a shift and offer it using Ad Hoc Planning","","OSDOWSRES-822",""]
[null,null,1419748,"2021-06-03",null,"","New Feature","Reliability","Calculation","Compensation rule 'Overtime: fixed in regard to publication' did not consider realised shift in status planning","Compensation rule 'Overtime: fixed in regard to publication' did not consider realised shift in status planning\nWhen comparing published shifts against the planned shifts (at the moment of publication) to calculate overtime\nshift realisation for planned shifts were not taken into account correctly.\nThis has been improved.\n\nTest hints\n1. When using Compensation rule 'Overtime: fixed in regard to publication' is used verify overtime compensation is calculated correctly.","","OSDCOMMAIN-13538",""]
[null,null,1421005,"2021-06-10",null,"","New Feature","Reliability","Planboard","Day with 3 shifts (1 shift from other department) were automatically planned out when 4th shift was planned in ","Day with 3 shifts (1 shift from other department) were automatically planned out when 4th shift was planned in. This has been fixed.\n\nOnly shifts of the department of the planboard will be changed.\n\nTest hint(s):\n1. Verify shifts can be planned on borrowed employees in the planboard","","OSDCOMMAIN-13516","12821077"]
[null,null,1421005,"2021-06-10",null,"","New Feature","Reliability","Import/Export","Importing existing duty with TFillFieldsOfCOMTECShift did not create an exchange","Importing existing duty with TFillFieldsOfCOMTECShift did not create an exchange. This has been fixed.\nIn 2 cases an exchange is created now:\n1. When importing a shift that reassigns it to another employee.\n2. When importing a shift that realizes it (if setting UseDutyExchanges = true). \n\nNote: In OSDOWSD-4142, release 8.5.0-1415216, this was fixed for new duties. By disabling the feature toggle setting FeatureToggleCreateExchangesWhenImportingShifts introduced in OSDOWSD-4142 no exchanges are created\n\nTest hint(s):\n1. Verify exchanges are created when importing existing shifts ","","OSDCOMMAIN-13568","13025883"]
[null,null,1422678,"2021-06-17",null,"","New Feature","Reliability","Win32 Userinterface","ORTEC WS Win32 Client: When errors occurred retrieving the messages for a user, it was not directly clear which message was involved","ORTEC WS Win32 Client: When errors occurred retrieving the messages for a user, it was not directly clear which message was involved.\nThis has been improved.\nA log line is written to identify the message involved when errors occur while retrieving the messages for a user.\n\nTesthint(s):\n1. Open the ORTEC WS Win32 Client and inspect the messages the user has received.","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDCOMMAIN-13477","12716824"]
[null,null,1422678,"2021-06-17",null,"","New Feature","Reliability","Planboard","In some cases the visualization of overnight workstation demands was wrong in the workstation planboard","In some cases the visualization of overnight workstation demands was wrong in the workstation planboard. This occured when the FeatureToggleDoNotSplitOvernightWorkstationDemand was turned on.\n\nThis has been fixed. \n\nTest hint(s):\n1. Verify all workstation demand is visible in the workstation planboard ","","OSDOWSD-4034",""]
[null,null,1422678,"2021-06-17",null,"","New Feature","Technical","Planboard","Introduced setting SplitOvernightWorkstationDemand to be able to remove FeatureToggleDoNotSplitOvernightWorkstationDemand in the future","Introduced setting Options/WorkstationPlanboard/SplitOvernightWorkstationDemand to be able to remove FeatureToggleDoNotSplitOvernightWorkstationDemand in the future. The default value of the setting is Y.\n\nNote: For existing customers, the current value of the feature toggle will be taken into account and functionality won't change.\n\nTest hint(s):\nNone",null,"OSDOWSD-4035",""]
[null,null,1422678,"2021-06-17",null,"","New Feature","Reliability","Database","Rolling out a cyclical schedule could give the error \"name too long, maximum length is 30\"","Rolling out a cyclical schedule could give the error \"name too long, maximum length is 30\"\nThis was because a consistency check did not correctly consider shifts with a name of 30 characters and a remark.\nThis has been fixed.\n\nTest hint(s):\n1. Create a cyclical schedule with 1 shift in it with a name of 30 characters. Add a remark to the shift or mark it as an instructor shift and rollout the cyclical schedule. There should not be a consistency check for the shift name failing.","","OSDOWSD-4202",""]
[null,null,1422678,"2021-06-17",null,"","New Feature","","","Improved changing skill levels before offering a shift. The change to the level is now directly shown in Ortec WS Win32 client","Improved changing skill levels before offering a shift. The change to the level is now directly shown in Ortec WS Win32 client.\nTest hint(s):\n\n1. None","","OSDOWSRES-1071",""]
[null,null,1422678,"2021-06-17",null,"","New Feature","","","Planning horizon of Ad Hoc Planning has now been configured to be set by a new CSCS setting, PlanningHorizonDays instead of current 8 days","Planning horizon of Ad Hoc Planning has now been configured to be set by a new CSCS setting, PlanningHorizonDays instead of current 8 days.\nThe default value of the setting, PlanningHorizonDays is set to 8. This setting can be configured to have any value between 8 and 15. If PlanningHorizonDays is configured \nwith a value lower than 8 or higher than 15, it will then take the minimum value (8) or the maximum value (15).\n\nThe setting, PlanningHorizonDays can be found in CSCS/Configuration/Settings Manager/AdhocPlanning/General.\n\nTest hint(s):\n\n1. Verify that the setting PlanningHorizonDays exists with a default value of 8.\n\n2. Verify that the number of days shown in the schedule view in Ad Hoc Planning is the same number of days as the value of PlanningHorizonDays. ","","OSDOWSRES-1144",""]
[null,null,1423771,"2021-06-24",null,"","New Feature","","","A shift from another department was planned out when planning an activity type overlapping that shift","A shift from another department was planned out when planning an activity type overlapping that shift.\nThis has been fixed.\nAdded feature toggle setting: FeatureToggles\\PlanActivityDoesNotUnplanOverlappingShiftsFromOtherDepartment and is by default enabled.\n\nTest hint(s):\n1. Plan in an activity or disturbance type over a shift from a lending department. This should show an informative error and do not perform any planning or remove any shifts.","","OSDCOMMAIN-13482","12744361"]
[null,null,1423771,"2021-06-24",null,"","New Feature","Reliability","Reporting","Report Flexpool Statistics did not show amounts correctly in summary","Report Flexpool Statistics did not show amounts correctly in summary.\nThis has been fixed.\n\nTest hint(s):\n1. Verify the summary of the report is correct ","","OSDCOMMAIN-13497","12814982"]
[null,null,1423771,"2021-06-24",null,"","New Feature","Reliability","Self Rostering","ORTEC WS for Employees - First day of schedule was considered same schedule status as previous schedule period","ORTEC WS for Employees - First day of schedule was considered same schedule status as previous schedule period\nThis has been fixed.\n\nTest hint(s):\n1. Verify in ORTEC WS for Employees the correct options can be selected when adding a shift on the first day of the month","","OSDCOMMAIN-13526","12896034"]
[null,null,1423771,"2021-06-24",null,"","New Feature","Stability","Self scheduling","ORTEC WS for Employees: Opening a schedule for an employee could cause a timeout when retrieving the shifts using query Comtec.Workforce.BackendAPI/Portal/v2/AllShifts","ORTEC WS for Employees: Opening a schedule for an employee could cause a timeout when retrieving the shifts (using query Comtec.Workforce.BackendAPI/Portal/v2/AllShifts)\nThis has been improved.\nThe Comtec.Workforce.BackendAPI/Portal/v2/AllShifts query has been improved.\n\nTest hint(s)\n1. Open a schedule in ORTEC WS for Employees for an employee ","","OSDCOMMAIN-13531","12913123"]
[null,null,1423771,"2021-06-24",null,"","New Feature","Stability","Cleaning","When cleaning up shifts using CCleanUpRemovedShifts the estimated transactionTimeout could be exceeded causing the clean up to fail","When cleaning up shifts using CCleanUpRemovedShifts the estimated transactionTimeout could be exceeded causing the clean up to fail.\nAn optional setting for the command handler has been added that can override the default timeout of 120 seconds.\nExample:\n<TransactionSettings DtcTimeOut=\"240\"/>\nThis will make transaction timeout 240 seconds, if the estimate  calculated in command handler based on the shifts exceeds this value, this setting needs to be set to the estimated value.\n\nTest hint(s):\n1. Execute CCleanUpRemovedShifts manually or via a job","","OSDCOMMAIN-13571","13043729"]
[null,null,1423771,"2021-06-24",null,"","New Feature","Reliability","Planboard","ORTEC WS Win32 Client: \"Division by zero\" error occurred when hovering over shift","ORTEC WS Win32 Client: \"Division by zero\" error occurred when hovering over shift. This could occur when a lot of shifts were planned on the same day (both in the cyclical and master schedule). This has been fixed.\n\nTest hint(s):\n1. Verify multiple shifts can be planned via drag-and-drop in the planboard","For this functionality to become available, ORTEC WS Win32 client must be installed.","OSDCOMMAIN-13580","13049994"]
[null,null,1423771,"2021-06-24",null,"","New Feature","Reliability","Client","Several translations added for French","Several translations have been added for French for recent functional changes.\n\nTest hint(s):\nNone","","OSDOWSD-4319",""]
[null,null,1423771,"2021-06-24",null,"Backend Domains Api","New Feature","Configuration","BackendDomainsAPI","BackendDomains API database migration has been moved to DBUpdate","Using the database migration from the configuration tool of the BackendDomainsAPI could cause problems if the connection string was created for an incorrect user. \nThis has been improved.\nThe decision has been made to remove the migration and move the database management for Ad Hoc Planning to DBUpdate.\nIn this process, the tables have also been renamed to clarify they are used for Ad Hoc Planning.\n\nTest hints:\n1) Verify that after installation of the BackendDomainsAPi the migration cannot be used anymore\n2) Verify that an absence can still be created in Ad Hoc Planning ","","OSDOWSRES-1109","12984406"]
[null,null,1425164,"2021-07-01",null,"","New Feature","","","Self scheduling ESS report summed up duty demands when multiple dutyset periods are active in self scheduling period","Self scheduling ESS report summed up duty demands when multiple dutyset periods are active in self scheduling period.\nThis has been fixed.\n\nTest hint(s)\n1. Verify the duty demands shown in the \"Self Scheduling ESS\" report .","","OSDCOMMAIN-13409","12589609"]
[null,null,1425164,"2021-07-01",null,"","New Feature","Performance","Optimization","Schedule optimizer: Some requirements where checked multiple times per employee and shift combination","Schedule optimizer: Some requirements where checked multiple times per employee and shift combination.\nThis has been improved.\nThe requirements that are being preprocessed are of the following form: employee E may not do shift S on day D. In CWSS Server, there are 30 constraints that are of this form. These requirements are now only be checked once at the beginning of the optimizer run for each combination of employee and shift.\n\nTest hint(s):\n1. Verify when running schedule optimizer in the planboard that no requirements are violated  ","","OSDOWSD-4251",""]
[null,null,1425164,"2021-07-01",null,"","New Feature","Security","Optimization","ShiftGeneration plugin did not support TLS 1.2","ShiftGeneration plugin did not support TLS 1.2\nThis has been improved.\n\nTest hint(s)\n1. Verify that calling the shift generation plugin is succesful","","OSDOWSD-4280",""]
[null,null,1425164,"2021-07-01",null,"","New Feature","","","Improved changing skill levels before offering a shift. The change to the level is now directly shown in Ortec WS Win32 client","Improved changing skill levels before offering a shift. The change to the level is now directly shown in Ortec WS Win32 client.\nTest hint(s):\n\n1. None","","OSDOWSRES-1071",""]
[null,null,1425164,"2021-07-01",null,"Shift Offering","Bug","Stability","BackendDomainsAPI","Shift with higher than skill level 1 had an automatic realization with skill level 1","When creating a shift with required skills with levels higher than the minimum in the ORTEC WS Win32 Client, it could happen that the skill levels were automatically set tot the minimum. This was caused by the synchronization process for Shift Offering. This has been fixed.\nNow, the skill levels are not automatically changed anymore.\n\nTest hint(s):\n1. Create a shift in the ORTEC WS Win32 Client. Verify that it does not get a realization automatically (this may take a minute). ","","OSDOWSRES-1178",""]
[null,null,1426692,"2021-07-08",null,"","Question","Reliability","Interfaces","When importing using TFillFieldsOfCOMTECShift a shift status was not taken into account when the import of a record was retried","When importing using TFillFieldsOfCOMTECShift a shift status was not taken into account when the import of a record was retried.\nThis has been fixed.\n\nTest hint(s):\n1. Import (realisations) of shifts using TFillFieldsOfCOMTECShift and include the STATUS field (requires ShouldTakeShiftStatusIntoAccount extra xml creator parameter enabled, introduced in OSDOWSD-4233) ","","OSDCOMMAIN-13604","13133740"]
[null,null,1426692,"2021-07-08",null,"","Bug","Stability","Win32 User Interface","OWS Win32 Client: In a planboard a 'List index out of bounds' error could appear suddenly on mouse movement and/or applying actions","OWS Win32 Client: In a planboard a 'List index out of bounds' error could appear suddenly on mouse movement and/or applying actions\nThis has been fixed.\n\n1. Test hints use a planboard to manipulate shifts and shift data.\n","For this functionality to become available, ORTEC WS Win32 client must be installed.","OSDCOMMAIN-13615","13190028"]
[null,null,1427986,"2021-07-15",null,"","Bug","Stability","Interfaces","Approve a realization of added shift in approved schedule did not work on interface server ","Approving a realization of added shift in an approved schedule did not always work on interface server.\nSometimes data was not loaded in memory.\nThis has been improved.\n\nTest hint(s):\n1. Verify that approving a realization of a shift in an approved schedule succeeds as expected.","","OSDCOMMAIN-13609",""]
[null,null,1427986,"2021-07-15",null,"","New Feature","","","Applied French translations on ESS web and mobile app","Applied French translations on ESS web and mobile app.\nThis has been finished.\n\nTest hint(s):\n1. Verify that updated translations appear in the mobile app and in the ESS portal.","","OSDOWSESS-2426","12886583"]
[null,null,1429559,"2021-07-22",null,"","New Feature","Stability","Core Framework","Parsing the command in command handlers could cause an access violation in ccds.cem","Parsing the command in command handlers could cause an access violation in ccds.cem\nWhen multiple commands where handled and parsed simultaneously a concurrency issue could cause an access violation, causing main server and workers to stop handling some or all commands. \nThis has been improved.\n\nTest hint(s)\n1. None.","","OSDCOMMAIN-13622","13209570"]
[null,null,1429559,"2021-07-22",null,"","New Feature","Functionality","Self scheduling","ORTEC WS For Employees: new back-end (API) routes were added for future functionality","ORTEC WS For Employees: new back-end (API) routes were added for future functionality\n\nRemark: For this new functionality the 'Standard request' will be enabled when the following modules are enabled:\n- Employee Self Service module (modESS)\n- Self rostering module (modSelfrostering)\n\nTest hint(s)\n1. Verify wildcards can be placed on a day or on a shift in ORTEC WS for Employees","","OSDOWSD-4307",""]
[null,null,1429559,"2021-07-22",null,"","New Feature","Reliability","Optimization","Optimizer scheduled inconsistently on recurring duty wishes","Optimizer scheduled overnight shifts inconsistently on the day before recurring shift requests.\nThis has been fixed.\n\nTest hint(s):\n1. Create a vacant overnight shift on a day before a recurring shift request not to work on that shift. Run the optimizer for the shift day and expect it to be assigned to that employee with no violations.","","OSDOWSD-4331",""]
[null,null,1430436,"2021-07-29",null,"","New Feature","Reliability","DataWarehouse","Dates of changed records in DIM_COST_CENTER overlapped, causing double entries in Fact tables","Dates of changed records in DIM_COST_CENTER overlapped, causing double entries in Fact tables. It has been fixed.\n\nTest hint(s):\n1. Verify that after a cost center is changed, entries for that cost center in DIM_COST_CENTER do not have the same Effective_From_Date and Effective_Until_Date. \n2. Verify that there are no double entries in the fact tables.","","OSDCOMMAIN-13579"]
[null,null,1430436,"2021-07-29",null,"","New Feature","Reliability","DataWarehouse","BI - Deleted assigned shifts directly after publication were not taken into account in the Fact_Published_Shift table. ","Deleted assigned shifts directly after publication were not taken into account in the Fact_Published_Shift table.\nThis has been improved.\nSuch deleted assigned shifts are added to the  Fact_Published_Shift table\n\nTest hint(1):\n- verify that an incremental load shows the expected published shifts (shifts on publication) in the Fact_Published_Shift table\n","","OSDCOMMAIN-13587"]
[null,null,1430436,"2021-07-29",null,"","New Feature","Reliability","Calculation","The text of the Workstation optimizer rule 'Workstation other than in the past' was not clear","The text of the workstation optimizer rule 'Workstation other than in the past' was not clear.\nThe rule text did not give a good indication that the period mentioned in the rule text is the period before the optimization period.\nThis has been improved.\nThe rule does not plan the selected workstation in the optimazation period when that workstation was planned the number of days before the optimization period.\n\nNOTES\n1. The text of the workstation optimizer rule 'The same workstation as in the past' was changed in a similar way\n2. For a new customer a new rule was estimated to look both before and in the optimization period. \nPlease contact PO and mention issue OSDCOMMAIN-13638 if additional information on that estimated rule is required.\n\nTest hint(s):\n- verify that properties of the named workstation rules can be adjusted ","","OSDCOMMAIN-13638"]
[null,null,1430436,"2021-07-29",null,"","New Feature","Functionality","Optimization","[OPT] Schedule optimizer improvement: Log number of violated requirements","Schedule optimizer improvement: Log number of violated requirements.\nBy adding the logging it can be found which requirements are never violated during running the schedule optimizers. These requirements can be candidates to be turned off to improve performance of the schedule optimizer. This should be discussed with the OR-specialist.\n\nThe new functionality is behind server setting 'GENETIC ALGORITHM / LOGVIOLATEDREQUIREMENTS' which is default false. Only enable this setting when analyzing cases for the optimizer. \n\nTest hint(s):\n1. Verify extra loglines are added in the server log when running the schedule optimizer and setting LOGVIOLATEDREQUIREMENTS = Y","","OSDOWSD-4304"]
[null,null,1431897,"2021-08-06",null,"","New Feature","Reliability","DataWarehouse","BI - Effective_From_Date in Dim_Cost_Center and Dim_Location were incorrect for the first entries of cost centers and locations","BI - Effective_From_Date in Dim_Cost_Center and Dim_Location were incorrect for the first entries of cost centers and locations. It has been fixed,\n\nTest hint(s):\n1. Verify that the Effective_from_date for the first entries of cost centers and locations in Dim_cost_center and Dim_Location is 2001-01-01 after a DBUpdate and Incremental Load run.","","OSDCOMMAIN-13429","12600003"]
[null,null,1431897,"2021-08-06",null,"","New Feature","Reliability","Import / Export","Employee name and number were sometimes shown in interface error log for  incorrect dates for a skill in an employee import","Employee name and number were sometimes shown in interface error log for incorrect dates for a skill in an employee importThis has been fixed.\nChecks should now always show an error with the employee number when the end date for a skill is invalid. \nThe employee name should not be shown anymore in the interface logs.\n\nTest hint(s):\n1. Add a skill with an end date later than 2447-07-30T00:00:00 in an employee import. Check in the interface log there is an error message about the invalid date, that also shows the employee number.","","OSDCOMMAIN-13533","12895236"]
[null,null,1431897,"2021-08-06",null,"","New Feature","Reliability","Planboard","An error about a cancelled distributed transaction could occur when creating a scenario from a scheduling period with a large number of shifts","An error about a cancelled distributed transaction could occur when creating a scenario from a scheduling period with a large number of shifts.\nIn case of a large number of shifts i.e. 2000 or higher the following error could occur:\nThe Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction\nThe transaction timed out after 120 seconds.\nThis has been improved.\nAn estimation is done on the possible time needed for the transaction given the number of shifts, and that time is used a transaction timeout\n\nTest hint(s):\n1. Verify a scenario can be created from a scheduling period","","OSDCOMMAIN-13541","12938080"]
[null,null,1431897,"2021-08-06",null,"","New Feature","Stability","DataWarehouse","BI: Increased performance of FACT_PROPERTY_VALUE","BI: Increased performance of FACT_PROPERTY_VALUE.\nThis was done to prevent timeouts during the BI run.\n\nTest hint(s):\nnone","","OSDCOMMAIN-13573","13047979"]
[null,null,1431897,"2021-08-06",null,"","New Feature","Reliability","Calculation","Incorrect Ad Hoc Planning account balance was shown when account booking percentage was not 100% for a compensation rule","Incorrect Ad Hoc Planner account balance was shown when account booking percentage was not 100% for a compensation rule. This has been fixed.\n\nTest hint(s):\n1. Verify that correct account balance is shown in Ad Hoc Planner.","","OSDCOMMAIN-13586","13073172"]
[null,null,1431897,"2021-08-06",null,"","New Feature","Functionality","Calculation","Several translations updated for German and French","Several translations updated for German and French.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13640",""]
[null,null,1431897,"2021-08-06",null,"","New Feature","Reliability","Optimization","Schedule optimizer considered requirements that were not valid for the schedule status","Schedule optimizer considered requirements that were not valid for the schedule status. This has been fixed.\n\nNote: this has been introduced in OSDOWSD-4251, 8.5.0(2021-07-01)_Build1425164\n\nTest hint(s):\n1. Verify schedule optimizer can be run","","OSDCOMMAIN-13647","13270973"]
[null,null,1431897,"2021-08-06",null,"","New Feature","Functionality","Core Framework","CommandHandlers did not show a description or a command example in CSCS Command Sender","CommandHandlers did not show a description or a command example in CSCS Command Sender.\nThis has been improved.\nWhen available a description is shown and a command example can be requested if available after selecting a command handler in CSCS Command Sender.\n\nTest hint(s)\n1. Verify CSCS Command Sender can be used.","","OSDOWSD-4340",""]
[null,null,1434718,"2021-08-26",null,"","New Feature","Reliability","Manager self-service","ORTEC WS for Managers showed wrong information for copied duty realizations","MSS showed wrong information for copied duty realizations.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that shift information  in MSS is correct for copied shifts with multiple realisations.","","OSDCOMMAIN-13450","12697731"]
[null,null,1434718,"2021-08-26",null,null,"New Feature","Stability","Self scheduling","ORTEC WS for Managers: Retrieving the demand of planned shifts on a date could cause a deadlock and cause EObjectIsBusy errors","ORTEC WS for Managers: Retrieving demands for shifts on a date could cause a deadlock and cause EObjectIsBusy errors\nThis has been improved.\nFor the command handler CGetDutyDemand the way locks are set has been changed.\n\n1. In ORTEC WS for Managers: verify opening a scheduling period for self scheduling","","OSDCOMMAIN-13563","13009340"]
[null,null,1434718,"2021-08-26",null,"","New Feature","Reliability","Interfaces","Improved error message when importing incorrect out-clocking using employee number","Improved error message when importing incorrect out-clocking using employee number.\nWhen importing incorrect out-clocking using employee number, the employee information was not shown. This has been fixed.\n\nTest hint(s):\n1. Verify out-clockings can be imported","","OSDCOMMAIN-13576","13048604"]
[null,null,1434718,"2021-08-26",null,"","New Feature","Reliability","Interfaces","Importing clockings twice did not show employee information to identify the erronous record","Improved error message when importing incorrect out-clocking using employee number.\nThe error message has been made more informative by adding information about the employee linked to the clocking, when using ExtraXMLCreator TIdentifyClockingByBadgeAndTime or TIdentifyClockingByEmployeeNumberAndDateTime \n\nTest hint(s):\n1. Verify when importing a double clocking, an informative error message is shown","","OSDCOMMAIN-13577","13048699"]
[null,null,1434718,"2021-08-26",null,"","New Feature","Reliability","Employee self-service","Shifts with duties that are not valid were displayed in the dropdown in Ortec WS for Employees","Shifts with duties that are not valid were displayed in the dropdown in Ortec WS for Employees. It has been fixed.\n\nTest hint(s):\n1. Verify that only shifts with valid duties are displayed in  Ortec WS for Employees.","","OSDCOMMAIN-13606","13050276"]
[null,null,1434718,"2021-08-26",null,"","New Feature","Reliability","Planboard","Replace feature toggle IncludeDaysOfHistoryForRelevantResources with a setting","Feature toggle IncludeDaysOfHistoryForRelevantResources added in OSDCOMMAIN-12864 has been replaced with a new setting.\nAdded setting: Options\\Planboard\\IncludeDaysOfHistoryForRelevantResources with default value 'Y'. \nThe new setting keeps the same value of the removed feature toggle.\n \nTest hint(s):\n1. Verify that a borrowed employee who is valid in the preview period of a schedule but not valid during the scheduling period is shown in a schedule when the preview period for a schedule is enabled.\n\n","For this solution to become available the OWS win32 client must be installed.\n","OSDCOMMAIN-13611",""]
[null,null,1434718,"2021-08-26",null,"","New Feature","Reliability","Planboard","Skill violations were inconsistent between the master schedule and workstation planning","Skill violations were inconsistent between the master schedule and workstation planning.\nThis has been improved.\nViolations should now be shown when performing certain actions in workstation planboard.\n\nTest hint(s):\n1. 1. Check that the following actions in the workstation planning now give a violation:\n  - drag and drop an unassigned demand to an employee who does not have the required skill(s).\n  - drag and drop an assigned workstation to another employee who does not have the required skill(s). \n  - add a realisation to an assigned duty by changing to a workstation that does not match with the employee's skills.\n  - right-click on a workstation and change to an employee who does not have the required skill(s).\n  - right-click on a workstation and select to replace workstation in a period. Select a workstation that conflicts with the skills of an employee.","","OSDOWSD-4246",""]
[null,null,1434718,"2021-08-26",null,"","New Feature","","","Day-off definition requirement read more historical data than needed","Day-off definition requirement read more historical data than needed. It has been fixed.\n\nTest hint(s):\n1. Verify that violations are correctly created for Day-off definition requirement.","","OSDOWSD-4337",""]
[null,null,1434718,"2021-08-26",null,"","New Feature","","","Schedule optimizer removed day off shifts not belonging to schedule","Schedule optimizer removed day off shifts not belonging to a schedule.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that schedule optimizer does not remove day-off shifts not belonging to the schedule.","","OSDOWSD-4338",""]
[null,null,1436019,"2021-09-02",null,"","New Feature","Reliability","Planboard","Evaluated and removed feature toggle : EnableDeleteTransferForUnfinalization","Removed feature toggle EnableDeleteTransferForUnfinalization. The functionality remains as if the feature toggle was enabled.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13297",""]
[null,null,1436019,"2021-09-02",null,"","New Feature","","","Error occured when clicking 'Candidates for shift' on an assigned shift if 'Use proposal departments' is checked in ORTEC WS Win32 Client","Error occured when clicking 'Candidates for shift' on an assigned shift if 'Use proposal departments' is checked in ORTEC WS Win32 Client. It has been fixed.\n\nTest hint(s):\n1. Verify that when 'Use proposal departments' is checked, no errors occur when clicking on Candidates for shift on an assigned shift.","","OSDCOMMAIN-13641","13246898"]
[null,null,1436019,"2021-09-02",null,"","New Feature","","","Translated error message was wrong when changing the start time of a duty set duty to a period of a closed or higher schedule","Translated error message was wrong when changing the start time of a duty set duty to a period of a closed or higher schedule. \nThis has been fixed.\n\nTest hint(s):\n1. Verify error message text when setting the Valid From date of a duty set duty to a date within a period of a schedule with status closed or higher and with a demanded duty set for that date.","","OSDCOMMAIN-13658","13313362"]
[null,null,1436019,"2021-09-02",null,"Backend Domains Api","New Feature","Reliability","BackendDomainsAPI","AHP - Shift offers are not sent to employees from proposal departments","Shift offers were not sent to employees in proposal departments. This has been fixed.\nNow, shift offers are also sent to employees that are not in the same department as the shift, but only in a proposal department of the shift.\n\nTest hint(s):\n1. Offer a shift. Verify that it is offered to employees in the department of the shift, and also to employees in the proposal departments of the shift.","","OSDOWSRES-1270","13326152"]
[null,null,1437331,"2021-09-09",null,"","New Feature","Reliability","Employee self-service","ORTEC WS for employees shift details had incorrect activity time on daylight saving transition","ORTEC WS for employees shift details had incorrect activity time on daylight saving transition.\n\nThis has been fixed. When retrieving the activity times the timezone is corrected if the shift overlaps with the daylight saving transition.\n\nTest hint(s):\n1. Verify that activities of shifts that overlap with the daylight saving transition are shown correct in the shift details\n2. Verify realisations on these shifts are correct","","OSDCOMMAIN-13595","13115080"]
[null,null,1437331,"2021-09-09",null,"","New Feature","Reliability","Gui","Several translations added for German","Several translations have been added for German for recent functional changes. \n\nTest hints: None","","OSDCOMMAIN-13667","13344704"]
[null,null,1437331,"2021-09-09",null,"","New Feature","Functionality","DataWarehouse","BI: Duty description has been added to activity tables and views","BI: Duty description has been added to activity tables and views.\n\nTest hint(s):\n1. Verify that a new column, Description is added to Fact_Assigned_Activity, FACT_Published_Activity, FACT_Vacant_Activity, FACT_CYCLIC_ACTIVITY, FACT_ACTIVITY_DEMAND, FACT_US_Assigned_Activity, FACT_US_Published_Activity, FACT_US_Vacant_Activity, FACT_US_CYCLICAL_ACTIVITY and FACT_US_DEMAND_ACTIVITY.\n2.  Verify that a new column, Omschrijving is added to FACT_NL_Ingeplande_Activiteit, FACT_NL_Gepubliceerde_Activiteit,  FACT_NL_CYCLISCHE_ACTIVITEIT and  FACT_NL_BEZETTINGSEIS_ACTIVITEIT.\n3. Verify that in the above mentioned tables and views, duty description is filled in the Description/Omschrijving column.  \n","","OSDOWSD-4347",12741084]
[null,null,1439135,"2021-09-16",null,"","New Feature","Stability","Win32 User Interface","Two internal settings for clocking functionality have been removed","Two internal settings for clocking functionality have been removed. These were introduced in OSDCOMMAIN-12933 and OSDCOMMAIN-12882 respectively in order to be backwards compatible for new server and old client. Since more than a year has passed after introduction of the functionalities, backwards compatibility is no longer needed.\n\nTest hint(s):\nNone","","OSDCOMMAIN-13370",""]
[null,null,1439135,"2021-09-16",null,"","New Feature","Functionality","","Monitoring query CQMS CountDepartmentsNotApprovedRecently was incorrect","Monitoring query CQMS CountDepartmentsNotApprovedRecently was incorrect. The query was not returning the correct number of the most recently approved departments.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that the correct number of recently approved departments is returned.","","OSDCOMMAIN-13672","13372825"]
[null,null,1439135,"2021-09-16",null,"","New Feature","Reliability","Reporting","MS Reporting: Some dates were not correctly formatted for several reports","MS Reporting: Some dates were not correctly formatted for several reports. This has been fixed for the following reports:\n- Accounts (ORTEC WS for Employees)\n- Employee schedule (ORTEC WS for Employees)\n- Master schedule (both ORTEC WS for Employees and Win32 client)\n- Overview shifts (Win32 client)\n- Self scheduling (ORTEC WS for Employees)\n- Violations (Win32 client)\n\nTest hint(s): \n1. Verify all dates are correctly formatted when retrieving data for the mentioned reports\n","","OSDCOMMAIN-13673","13372844"]
[null,null,1439135,"2021-09-16",null,"","New Feature","","","Several translations updated for Danish and Finnish","Several translations updated for Danish and Finnish.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13675",""]
[null,null,1439135,"2021-09-16",null,"","New Feature","Functionality","DataWarehouse","A retry mechanism has been added to DIMENSION_IL, FACTS and STAGING_LOOKUP packages for incremental loads","A retry mechanism has been added to DIMENSIONS_IL, FACTS and STAGING_LOOKUP packages for incremental loads. \nThis mechanism will enter a retry on failure of any of the failing child packages in DIMENSIONS_IL, FACTS and STAGING_LOOKUP.\nA retry attempt will be logged in the HDM_Stage database table: Logging.\n\n The number of retries can be configured in a new setting 'MaximumRetryAttempts' created in ORTEC System Configuration/Configuration/Settings Manager/CBIS/Dataloads with a default value of 2. \n\nA waittime of 10 seconds is added before entering a retry. If necessary, this can be configured in the new query file: 'Wait_For_Delay.sql'.\n\n Note: This mechanism is intended to cope with errors as network hickups or temporary inavailability of SQL Server. But any type of failure will be retried.\n\n Test hint(s):\n1. Verify that incremental load runs correctly.","","OSDOWSD-4385",""]
[null,null,1439135,"2021-09-16",null,"Backend Domains Api","New Feature","Reliability","BackendDomainsAPI","Employees could not be calculated when a huge number of employees is available to work an offered shift","The functionality that calculates employees available to work a shift raised a database error in case there were more than 2100 employees available for the shift. There could be so many employees available because of having a lot of proposal departments for the department of the shift. Due to the error, the details of the shift could not be opened in Ad Hoc Planning anymore.\nThis has been fixed. Now, notifications will be sent even if more than 2100 employees are available for the department of the shift. \nAlso, the functionality that takes into account the absences of employees is active again.\n\nTest hint(s):\n1. Offer a shift. Verify that notifications are sent to the employees.","","OSDOWSRES-1305",""]
[null,null,1440375,"2021-09-23",null,"","New Feature","","","Color of vertical calculation \"Number of skills present\" was incorrect when value was a range","Color of vertical calculation \"Number of skills present\" was incorrect when value was a range.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that vertical calculations based on the \"Number of Skills\"  show the expected set colors for different amounts of available skills .","","OSDCOMMAIN-13652","13274008"]
[null,null,1440375,"2021-09-23",null,"","New Feature","Functionality","Optimization","Added functionality to apply result of Rescheduling proposal","Added functionality to apply result of Rescheduling proposal.\nIn the window of the rescheduling proposal a new 'apply'-button has been added. Groups of shift moves can be selected to be applied. Moreover, phone numbers are added in the hint text of the window.\n\nNote: the rescheduling proposal functionality is behind feature toggle USERESCHEDULINGPLANNER \n\nTest hint(s):\n1. Verify the rescheduling proposal can be applied for one or multiple shifts","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4388",""]
[null,null,1443174,"2021-10-07",null,"","New Feature","","","Error when mailing for multiple departments","When trying to mail a standard report in which multiple departments can be selected (e.g. Attendance list per department) you get the error:\nThere was an error when retrieving the mailing list.\n\nThis has been fixed.\n\nTest hint(s):\n1. Verify that when trying to mail a standard report in which multiple departments can be selected (e.g. Attendance list per department), no errors are returned when selecting a single as well as multiple departments.\n","","OSDCOMMAIN-13607","13138926"]
[null,null,1443174,"2021-10-07",null,"","New Feature","","","Several translations updated for French","For rescheduling proposal, translations are added for French.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13694",""]
[null,null,1443174,"2021-10-07",null,"","New Feature","Configuration","Client","Feature toggle ShowDialogToAddOrRemoveEmployeesForARotation turned on by default","Feature toggle FeatureToggles\\ShowDialogToAddOrRemoveEmployeesForARotation is now set to 'on' by default. \nThis feature toggle was introduced in OSDOWSD-424.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nThere is 1 known issue when this feature toggle is enabled: \nWhen using the window add or remove employees from a cyclical schedule plan board, it could take a long time to remove rows for employees that are no longer part of a department for large departments. Also, an error message could appear for each removed row that the plan board could not be updated. \nThis has been improved in OSDOWSD-454 and can be enabled through the feature toggle \\FeatureToggles\\IgnoreUpdateWhileRefreshEventIsPendingForRotation, which is disabled by default: \n - If updating the plan board takes a long time only 1 message appears stating that the plan board could not be updated in time even if multiple rows are removed. By default the plan board should update properly within 10 seconds (This is configured in OWS Settings manager with setting SERVER\\OPTIONS\\TOTALTIMETOWAITFORALLCLIENTGRIDMANAGERSTOBEUPDATEDINMS)\n\nTest hint(s):\n1. Check if FEATURETOGGLES\\SHOWDIALOGTOADDORREMOVEEMPLOYEESFORAROTATION in ROS_SETTINGS is set to Y after updating the database with all scripts ","","OSDCOMMAIN-13695",""]
[null,null,1443174,"2021-10-07",null,"","New Feature","Configuration","Client","Feature toggle ShowDialogToUpdateAndDeleteShiftsWhenUpdatingRotationDateWhenDefault turned on by default","Feature toggle FeatureToggles\\ShowDialogToUpdateAndDeleteShiftsWhenUpdatingRotationDateWhenDefault is now set to 'on' by default. \nThis feature toggle was introduced in OSDOWSD-423.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\n1. Check if FEATURETOGGLES\\SHOWDIALOGTOUPDATEANDDELETESHIFTSWHENUPDATINGROTATIONDATEWHENDEFAULT in ROS_SETTINGS is set to Y after updating the database with all scripts ","","OSDCOMMAIN-13696",""]
[null,null,1443174,"2021-10-07",null,"","New Feature","Reliability","Client","Updated Finnish translation","For the forbidden combination of shifts criterion specifications text, translation updated for Finnish.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13699","13435502"]
[null,null,1443174,"2021-10-07",null,"","New Feature","Technical","Client","OWS Win32 Client: Application could not be uniquely identified in RDWeb environment on application title","OWS Win32 Client: Application could not be uniquely identified in RDWeb environment on application title.\nThis has been improved.\nThe startup parameter 'ApplicationTitleAddition' has been added so additional information can be shown in the application title.\n\nTest hint(s):\n1. Verify client shows the added information from the command line parameter in application title. ","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4400",""]
[null,null,1445113,"2021-10-14",null,"","New Feature","","","PostInstall only allowed adding language Afrikaans","PostInstall only allowed adding language Afrikaans\nThis has been fix.\nAll available languages are available again.\n\nTest hint:\n1. verify when adding a language using the postinstall utility that all (supported) languages can be added.","","OSDCOMMAIN-13704",""]
[null,null,1445113,"2021-10-14",null,"","New Feature","Stability","Win32 User Interface","Day-off definition requirement could cause access violation preventing opening planboards when there are more than one day off shifts for an employee","Day-off definition requirement could cause access violation preventing opening planboards when there are two or more day off shift (as defined in Day-off definition requirement) for an employee for the first time. This has been fixed.\n\nPlease note that this issue was introduced in OSDOWSD-4337.\n\nTest hint(s):\n1. Verify that planboard can opened without access violation.","","OSDCOMMAIN-13708","13474809"]
[null,null,1445113,"2021-10-14",null,"Backend Domains API","New Feature","Performance","BackendDomainsAPI","Labor rules validation endpoint for shift offering is slow","When calculating the employees that will receive a notification for an offered shift, a check is performed for every employee if assigning the shift will lead to extra violations. One of the database queries used in this check caused performance issues for some customers.  \nThis query has been improved.\n\nTest hints:\n1) Offer a shift in Ad Hoc Planning and verify notifications are send to available employees","","OSDOWSRES-1365",""]
[null,null,1445967,"2021-10-21",null,"","New Feature","Performance","DataWarehouse","Queries on Access control login sessions (acLoginSessionLog) were slow","Queries on Access control login session log (acLoginSessionLog) were slow.\nThis has been improved.\nA non-clustered index has been added to improve query performance when sessionId, user id and eventType are included in the query.\n\n1. Test hint(s)\nNone","","OSDCOMMAIN-13594","13112472"]
[null,null,1445967,"2021-10-21",null,"","New Feature","Reliability","Client","Access violation was shown on hint text of an illness with an unassigned illnesstype","Access violation was shown on hint text of an illness with an unassigned illnesstype\nThis has been improved.\nWhen an illness type is not available '* ERROR *' is shown in the hint text.\nA server log line is added for investigation purposes.\n\nTest hint(s):\n1. Verify if an sick leave can be added or changed.","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDCOMMAIN-13624","13211228"]
[null,null,1445967,"2021-10-21",null,"","New Feature","Reliability","Calculation","Overtime calculation based on publication created incorrect records when planning realizations were used","Overtime calculation based on publication created incorrect records when planning realizations were used.\nThis has been fixed.\n\nTest hint(s):\n1. Verify when only planning realizations are created for shifts, no overtime records are calculated","","OSDCOMMAIN-13637","13229293"]
[null,null,1445967,"2021-10-21",null,"","New Feature","Reliability","GUI","Several translations added for German","Several translations have been added for German for recent functional changes. \n\nTest hints: None","","OSDCOMMAIN-13718","13344704"]
[null,null,1445967,"2021-10-21",null,"","New Feature","Functionality","Optimization"," Added functionality to criterion \"Combinations of consecutive shifts\": the definition of a shift series has been made adjustable","Added functionality to criterion \"Combinations of consecutive shifts\": the definition of a shift series has been made adjustable.\n\nA new checkbox has been added to the text of the criterion which is default false. If this is set to true, the definition of a shift series can be changed by defining the maximum duration between two shifts. \nNote: the end time of the first shift is compared to the begin time of the second shift.\n\nTest hint(s):\n1. Verify in criterion \"Combinations of consecutive shifts\" the default shift series definition can be adjusted\n2. Verify different costs are used in calculation of optimizers when using the non-default definition","","OSDOWSD-4457",""]
[null,null,1445967,"2021-10-21",null,null,"New Feature","Utilities","Reliability","Added 'UnattendedUpdates' scripts for updating an ORTEC WS 7 installation","UnattendedUpdates is a set of PowerShell scripts and tools that can be used as a means to update an existing ORTEC WS 7 installation without human interaction.\nFeatures include:\n- Suitable for single or multi-environment installations\n- Download latest OTEC WS 7 update from ORTEC EFT\n- Process regular and manual update files\n- Update win-32 Client on Terminal Servers\n- Provide feedback on success or exceptions by email\n- UnattendedUpdates will update itself\nThe update process can be scheduled without human interaction or be triggered manually.",null,"OSDOWSD-4014",""]
[null,null,1447808,"2021-10-29",null,"","New Feature","Reliability","Employee self-service","ESS - Leave request on last contract day unsuccessful","Leave requests created in ORTEC WS for Employees on the last day of the employee's contract would not be processed.\nThis has been fixed.\n\nTest hint(s):\n1. In ORTEC WS for Employees, verify that leave requests with any duration can be created on the last contract day up until midnight. ","","OSDCOMMAIN-13527","12896064"]
[null,null,1447808,"2021-10-29",null,"","New Feature","Reliability","Client","In the planboard of ORTEC WS Win32 client, Duty Palet and Location Properties did not show due to location stored on bigger monitor","In the planboard of ORTEC WS Win32 client, Duty Palet and Location Properties did not show due to location stored on bigger monitor.\nThis has been fixed.\n\nTest hint(s):\n1. Verify the duty palet and location properties can be opened in the planboard in the ORTEC WS Win32 client","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDCOMMAIN-13614","13188048"]
[null,null,1447808,"2021-10-29",null,"","New Feature","Reliability","Reporting","Report Master schedule planner couldn't be requested for more than 100 days","Report Master schedule planner couldn't be requested for more than 100 days.\nThis has been fixed. \n\nTest hint(s):\n1. Verify that the report Master schedule planner can be requested for more than 100 days.","","OSDCOMMAIN-13623","13211205"]
[null,null,1447808,"2021-10-29",null,"","New Feature","Reliability","Import / Export","Not all changes for a pending update were applied on all workers","Not all changes for a pending update were applied on all workers. \nBefore, missing changes could lead to halted workers. \nThis has been fixed.\n\nTest hint(s):\n1. Verify pending updates can be created from ORTEC WS For Employees","","OSDCOMMAIN-13649","13247573"]
[null,null,1447808,"2021-10-29",null,"","New Feature","Technical","Import / Export","Improvement on ignoring importing shift pending update","When importing a shift pending update, the DAY_OFF_SHIFT_WAS_CREATED field was ignored when present. \nThis has been improved.\nNow, the field is deleted and logging is added.\n\nTest hint(s):\n1. Verify that when importing a shift pending update, the DAY_OFF_SHIFT_WAS_CREATED field is not updated regardless of its value in the input. If it is in the input, a line is also added to the logging.","","OSDCOMMAIN-13650","13247573"]
[null,null,1447808,"2021-10-29",null,"","New Feature","Reliability","GUI","Several translations added for German and French","Several translations have been added for German and French for recent functional changes. \n\nTest hint(s): \nNone","","OSDCOMMAIN-13722",""]
[null,null,1447808,"2021-10-29",null,"Backend Domains Api","New Feature","Performance","BackendDomainsAPI","Improved Backend Domain Apis queries to reduce CPU usage ","Technical changes made in Backend Domain Apis to improve query performance such that CPU usage on the database is reduced.\n\nTest hint(s):\n1. Register an absence","","OSDOWSRES-1386",""]
[null,null,1448735,"2021-11-04",null,"","New Feature","Performance","Self scheduling","ORTEC WS for Employees: Retrieving illness information for an employee using route api/v2/employees/sicknesses was slow","ORTEC WS for Employees: Retrieving illness information for an employee using route api/v2/employees/sicknesses was slow\nThis has been improved.\n\nTest hint(s):\n1. Verify retrieving illness data in OWS for Employees succeeds","","OSDCOMMAIN-13537","12932962"]
[null,null,1448735,"2021-11-04",null,"","New Feature","Reliability","Reporting","ORTEC WS for Managers: reports opened with wrong date format for default values of From and To date parameters","ORTEC WS for Managers: reports opened with wrong date format for default values of From and To date parameters in different languages.\nThis has been fixed. \n\nTest hint(s):\n1. Verify default date parameters for reports are correct in MSS & ESS for multiple languages","","OSDCOMMAIN-13620","12929349"]
[null,null,1448735,"2021-11-04",null,null,"New Feature","Functionality","Calculation","Adjusted bounds of compensation rule 'Time between shifts'","Adjusted bounds of compensation rule 'Time between shifts'. \nPreviously the bounds were defined as \n\"If the time between a shift and the [previous] shift is greater than [00:00] and less than [00:00], a fixed amount of [0] will be entered.\" \n\nThis has been changed to \"greater than or equal to\" and \"less than or equal to\", to facilitate the case where an account entry is needed when two shifts are directly consecutive.\n\nNote: for existing versions of this compensation rule, nothing is changed functionally. The minimum time is increased by one minute, and the maximum time is decreased by one minute for these versions.\n\nTest hint(s):\n1. Verify correct account entries are created by the compensation rule 'Time between shifts' ","","OSDOWSD-4429",""]
[null,null,1450050,"2021-11-11",null,"","New Feature","Stability","Data Entry","Adding a derived cost center to cost center in use could cause a CWSS Server (process) not to start","Adding a cost center to leaf cost center could cause a CWSS Server (process) not to start\nThis has been improved.\nDetection scripts have been added in dbupdate. \nImporting changes that would cause the issue by changing leaf cost centers to become a parent are prevented.\n\nTherefor a check has been added that validates a cost center cannot be added as leaf to an already in use (leaf) cost center.\nIn case this check fails for a valid reason we did not anticipate, a bug report should be submitted. The check can be disabled in the mean time by setting CONSISTENCYCHECKS\\COSTCENTERCANBEPARENTCHECK\\ENABLED to N\n\nTest hint(s):\nNone","","OSDCOMMAIN-13553","12914308"]
[null,null,1450050,"2021-11-11",null,"","New Feature","Reliability","GUI","Several translations added for German","Several translations have been added for German \n\nTest hint(s): \nNone","","OSDCOMMAIN-13730",""]
[null,null,1450050,"2021-11-11",null,"","New Feature","Technical","Installer","Technical change: ORTEC WS binaries are build with VS 2019 U9 in stead of VS 2019 U4","Technical change: ORTEC WS binaries are build with VS 2019 U9 in stead of VS 2019 U4\n\nThis adds dependencies on new binaries and these need to be deployed next to the OWS 7 executables and all installers have been updated. \n\nFor more details see upgrade notes.","NOTE: this is only when installing on a new environment!\n\nThis update of OWS 7 introduces a new library it depends on. This causes some additional steps to roll out this update.\nThe new library to add is Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019:\n  \n   The library can be installed using the VC_redist.x86.exe/VC_redist.x64.exe delivered as a manual update:\n   Manual_Update_1332104_RedistributablesVS2015-2019.zip \n   \n   When this library are NOT installed, starting any OWS 7 specific executable will\n   show an error message stating the 'msvcr140.dll' is missing.","OSDOWSD-4397",""]
[null,null,1451903,"2021-11-18",null,"","New Feature","Reliability","GUI","Several translations added for German","Several translations have been added for German for recent functional changes. \n\nTest hint(s): \n1. None","","OSDCOMMAIN-13725",""]
[null,null,1451903,"2021-11-18",null,"","New Feature","Reliability","Optimization","Rescheduling proposal: shift name was not translated when UseMultiLang","Rescheduling proposal: shift names were not translated in the result when UseMultiLang.\nThis has been fixed.\n\nTest hint(s):\n1. Verify a rescheduling proposal can be requested in the planboard of the Win32-client","For this change to become available, the Win32-client must be installed","OSDOWSD-4435",""]
[null,null,1451903,"2021-11-18",null,"","New Feature","Functionality","Optimization","Rescheduling proposal: It was possible to select a large number of shifts","Rescheduling proposal: It was possible to select a large number of shifts.\nThis has been improved. Selecting a large number of shifts for the rescheduling proposal could lock the ORTEC WS win32 client. \n\nA new server setting has been introduced to bound this number of shifts:  \\Planner\\ReschedulingProposal\\MaxNofShiftsSelected with default value 25. \n\nNote: only change this setting when discussed with a member from AKT!\n\nTest hint(s): \n1. Verify the rescheduling proposal can be requested for 25 or less shifts\n2. Verify when requesting a rescheduling proposal for more than 25 shifts an error message is shown","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4436",""]
[null,null,1451903,"2021-11-18",null,"","New Feature","Stability","Utilities","UnattendedUpdates - Stopping Client, CSCS and Settings Manager waited for user confirmation","In some cases the command for stopping CSCS, OWS Settings manager and the OWS Client needed confirmation, causing the UnattendedUpdate process to stall. This has been fixed\n\nTest hint(s):\nNone","","OSDOWSD-4473",""]
[null,null,1453407,"2021-11-25",null,"","New Feature","Reliability","Optimization","Applying rescheduling proposal with extra moves raised error","Applying rescheduling proposal with extra moves raised an error.\nThis occurred when use DoNotDeleteUnnecessaryShift was disabled and the duty to be reassigned was overstaffed. This has been fixed.\n\nTest hint(s):\n1. Verify the rescheduling proposal can be applied with use DoNotDeleteUnnecessaryShift disabled  ","","OSDCOMMAIN-13737","13579686"]
[null,null,1453407,"2021-11-25",null,"","New Feature","Reliability","GUI","Several translations added for French","Several translations have been added for French for recent functional changes. \n\nTest hint(s): \n1. None","","OSDCOMMAIN-13755","13344704"]
[null,null,1454712,"2021-12-02",null,"","New Feature","Technical","Client","OWS Win32 Client: When closing a planboard fails an invalid pointer operation could be shown","OWS Win32 Client: When closing a planboard fails an invalid pointer operation could be shown.\nThis has been improved.\nWhen gracefully closing a planboard is not feasible, a less gracefull close is done. This is logged.\n \nTest hint(s):\n1. Open and close planboard in OWS Win32-client","For this change to become available, the Win32-client must be installed","OSDCOMMAIN-13751",""]
[null,null,1454712,"2021-12-02",null,"Backend event publisher","New Feature","","","Preparations for Shift Offering improvements","As preparation for some improvements that will be done to Shift Offering, the backend event publisher has been changed. The changes are twofold:\n- Less events are sent to the integration service\n- Preparations are done to send events directly to Shift Offering. Note that this will not be used yet\n\nTest hint(s):\n1) Verify responses for offered shifts created in Employee Self Service are correctly send to Shift Offering","","OSDOWSRES-1447",""]
[null,null,1454712,"2021-12-02",null,"Backend Domains API","New Feature","","","Preparations for new cloud application","The Backend Domains API has been extended with functionality to support the new cloud application ORTEC WS for Team Schedulers. This application recently went into pilot phase.\n\nTest hint(s):\n1. Verify login to Ad Hoc Planning still works","","OSDOWSRES-1494",""]
[null,null,1456277,"2021-12-09",null,"","New Feature","Technical","Tools","Log4net library used by CAIS is updated to version 2.0.13","Log4net library used by CAIS is updated to version 2.0.13\n\nTest hint(s):\n- Verify CAIS starts and processing of calls using CAIS succeed","","OSDCOMMAIN-13742",""]
[null,null,1456277,"2021-12-09",null,"","New Feature","Performance","Database","Altered indexes for ROS_SHIFTS to better support SQL 2019 performance improvements","Altered indexes for ROS_SHIFTS to better support SQL 2019 performance improvements.\nSome indexes on the ROS_SHIFTS table have been altered in such a way that the query optimizer for SQL 2019 (but also for previous versions) can make better optimized query plans.\nThe  plans created with these changes have shown improvements on performance of queries where the ROS_SHIFTS table was involved.\n\nTest hint(s):\nNone.","","OSDCOMMAIN-13747","13599069"]
[null,null,1456277,"2021-12-09",null,null,"New Feature","Reliability","Client","Dayparts were not shown in vacant shift filtering option","Dayparts were not shown in vacant shift filtering option.\nThis has been fixed.\nWhen ShiftInDayParts is configured it is fully visible again in the vacant shift filtering options.\n\nTest hint(s):\nNone","For this change to become available, the Win32-client must be installed","OSDCOMMAIN-13767","13651828"]
[null,null,1456277,"2021-12-09",null,"","New Feature","Reliability","GUI","Several translations added for Finnish, Danish, English and German","Several translations have been added for Finnish, Danish, English and German\n\nTest hints: \nNone","","OSDCOMMAIN-13771","13344704"]
[null,null,1456277,"2021-12-09",null," ","New Feature","Reliability","Database","Added checks in DBupdate on SQL Server Compatibility Level and Legacy Cardinality Estimation SQL Server database properties","Added checks in DBupdate on SQL Server Compatibility Level and Legacy Cardinality Estimation SQL Server database properties.\nThese checks were added to show and advise that Compatibility Level should be the highest possible given the SQL Server version and that the Legacy Cardinality Estimation should be OFF.  \nA warning is shown if this is not the case when performing a DBUpdate.\nWhen these settings are configured differently performance of queries might not be optimal.\n\nTest hint(s):\nNone.","","OSDCOMMAIN-13774","13599069"]
[null,null,1457935,"2021-12-16",null,"","New Feature","Reliability","Planboard","Categories were omitted from shift counters in case of other category with same name, using different capitalization","In the shift counters on the planboard, categories that only differed in capitalization (e.g. 'Test' and 'test') were not properly displayed in different categories. One category was displayed, others were omitted.\nThis has been fixed.\nWhen categories have the same name but with different capitalization, these categories will be displayed separately. In such a case, categories in upper case will be sorted before those in lower case.\n\nTest hint(s):\n1. Verify shift counters on the planboard are displayed correctly, meaning that every duty is represented within a category and that the categories are sorted alphabetically.","","OSDCOMMAIN-13773","13679321"]
[null,null,1457935,"2021-12-16",null,"","New Feature","Reliability","GUI","Several translations added for German and French","Several translations have been added for German and French.\n\nTest hint(s): \n1. None","","OSDCOMMAIN-13779",""]
[null,null,1457935,"2021-12-16",null,"","New Feature","Functionality","Client","Added functionality to duty demand windows to include demanded skills","This change includes the first part of the project to add skill requirements. \nAdded global setting UseDemandedDutySkills which is turned off by default.\nWhen turned on, it becomes possible in the client to add demand for specific skills to a selected duty demand, for weekly recurring as well as date-specific duty demands. \nIn the next steps of the project, functionality will be added so that these demanded duty skills can be used.\n\nTest hint(s):\n1. Verify that when UseDemandedDutySkills is on, a 'Demanded duty skills' grid is available within the regular duty demand window as well as the date-specific one. In this grid, it should be possible to add demanded duty skills to the selected duty demand.","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4471",""]
[null,null,1459598,"2021-12-23",null,"","New Feature","Functionality","Client","OWS Win32 Client: Access Control can be opened as dual client window","OWS Win32 Client: Access Control can be openend as dual client window\n\nThe Access Control application can be openend as dual client window after applying some configuration settings.\nBy default this functionality is disabled.\n\nThis is functionality is in a pilot phase. This functionality may only be enabled after approval of the ORTEC Workforce Scheduling PO. \nUPDATE: As of September 2022 this functionality is no longer in pilot phase and can be used at any customer. \n\nTo use this functionality enable the featuretoggle 'FEATURETOGGLES\\ENABLEACCESSCONTROLINDUALCLIENT' and add the general setting CWGSACCESSCONTROLBASEURL to OWS Settings Manager. This can also be done by script:\ndeclare @ACURL varchar(500)\nset @ACURL = 'https://accesscontrolURL.domain'\nexecute ChangeSetting 'CWGSACCESSCONTROLBASEURL', @ACURL\nexecute ChangeSetting 'FEATURETOGGLES\\ENABLEACCESSCONTROLINDUALCLIENT', 'Y';\n\nAfter adding the above settings the menu item 'Access Control' needs to be added to the OWS Client by customizing the menu.\n\nTest hint(s):\n- None","For this change to become available, the Win32-client must be installed","OSDOWSD-4464",""]
[null,null,1459598,"2021-12-23",null,"","New Feature","Reliability","Optimization","Criterion \"Combinations of consecutive shifts\" was not working correctly when selecting one day for optimization when non-default shift series is used","Criterion \"Combinations of consecutive shifts\" was not working correctly when selecting one day for optimization when non-default shift series is used.\nThis has been fixed\n\nTest hint(s):\n1. Verify Schedule optimizer can be run with criterion \"Combinations of consecutive shifts\"","","OSDOWSD-4486",""]
[null,null,1459598,"2021-12-23",null,"","New Feature","Security","Self Rostering","Personal addresses of employees were shown when entering a realization in ORTEC WS for Employees","Personal addresses of employees were shown when entering a realization in ORTEC WS for Employees.\nThis has been fixed. \nAdded BackendAPI setting UseNonEmployeeAddresses which is turned on by default. Turning this off will disclose employee addresses which is a GDPR violation. This should only be done under direct guidance and responsibility of the customer.\nWhen this setting is active, addresses that are linked to an employee will no longer be displayed when selecting an address for a realization. \nNote that this means that addresses that are linked to both an employee and a physical location/activity/department will also not be displayed. If this is the case, this will be detected during DBUpdate.\n\nTest hint(s):\n1. Verify that when UseNonEmployeeAddresses is on, no addresses of employees are shown among the selectable addresses when entering a realization in ORTEC WS for Employees.","","OSDOWSD-4493",""]
[null,null,1462155,"2022-01-06",null,"","New Feature","Reliability","Optimization","Minimum rest time requirement was not checked correctly during optimization","Minimum rest time requirement was not checked correctly during optimization, causing combinations of shifts that result of a violation. \nThis has been fixed. \nThe constraint was marked as a constraint that could be preprocessed when the maximum time between consecutive shifts equaled the MinHoursBetweenShifts server setting. \nFurthermore, an incorrect setting-path was used for this setting. This is corrected in a DBUpdate script\n\nTest hint(s):\n1. Verify that after running DBUpdate, the setting 'ALGORITHMREGISTRYPATH\\MINHOURSBETWEENSHIFTS' no longer exist. If this was set to another value than the default value 8, this value can now be found in GENETIC ALGORITHM\\MINHOURSBETWEENSHIFTS\n2. Verify that when using the Minimum Rest Time requirement, no combinations of shifts that result in a violation are created by the optimizer.","","OSDCOMMAIN-13780",""]
[null,null,1462155,"2022-01-06",null,"","New Feature","Reliability","Planboard","Add shift did not work for cyclical schedules if first schedule in department had status 'Closed' or higher","Add shift functionality did not work for cyclical schedules if the first scheduling period in the department has a status of 'Closed' or higher. \nThis has been fixed. \nChecks that are applied when adding a shift to a schedule that has been closed have been removed for cyclical schedules. \n\nTest hint(s):\n1. Verify that 'Add shift' planboard functionality works correctly for cyclical schedules","","OSDCOMMAIN-13792","13732349"]
[null,null,1462155,"2022-01-06",null,null,"New Feature","Reliability","Self Rostering","ORTEC WS for Employees: Activity property values were not correctly shown when entering a realization","ORTEC WS for Employees: Activity property values were not correctly shown when entering a realization. \nIn case of multiple activities and properties, the property values of another activity were sometimes shown for the activity selected. \nThis has been fixed. \n\nTest hint(s);\n1. Verify that when a shift has multiple activities, and activities have multiple properties, the correct property values are shown for every activity when creating a realization. ","","OSDOWSD-4498","13.476.395"]
[null,null,1463312,"2022-01-13",null,"","New Feature","Reliability","Calculation","Shifts involved in labor period violations could not be found when they take place after a trial scenario/self scheduling period and start with a work-free period","Shifts involved in labor period violations could not be found when they take place after a trial scenario/self scheduling period and start with a work-free period. This could lead to unexpected exceptions.\nThis has been fixed. \n\nTest hint(s):\n1. Verify that no exceptions are thrown when working with labor period violations (e.g. Rest per number of hours (labor period)) in either a trial scenario or during self scheduling.","","OSDCOMMAIN-13758","13586240"]
[null,null,1463312,"2022-01-13",null,null,"New Feature",null,"","BI Incremental load sometimes failed for cost center effective from dates","BI Incremental load sometimes failed for cost center effective from dates.\nIt has been fixed.\nTest hint(s):\n1. Verify that BI Incremental load runs.","","OSDCOMMAIN-13790","13719854"]
[null,null,1463312,"2022-01-13",null,"","New Feature","Reliability","Client","New duty based on template duty did not get costcenter of department","New duty based on template duty did not get costcenter of department. \nIf the template duty validity period did not match the validity period of the department's costcenter, the new duty would be added any way but without a cost center. There would be an error in the logging, but not in the client.\nThis has been fixed.\nNow an error is thrown in the client instead, and no new duty is added.\n\nTest hint(s):\n1. Verify that an error is shown in the client if you try to add a new duty, based on a template duty, and the validity periods of the template duty and the department's costcenter do not match.\n","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4412",""]
[null,null,1464524,"2022-01-20",null,"","New Feature","Reliability","Planboard","Thread that handled planboard updates remained in a corrupt state causing other planboard updates not to be propagated","Thread that handled planboard updates remained in a corrupt state causing other planboard updates not to be propagated.\nThis has been fixed behind feature toggle RESPAWNJOBTHREADAFTERTERMINATEDONSYSTEMERROR which is enabled by default.\n\nTest hint(s):\n1. Verify using the same planboard in multiple clients goes okay\n","","OSDCOMMAIN-13684","13373871"]
[null,null,1464524,"2022-01-20",null,"","New Feature","Reliability","Client","Subcontract functionality did not work when employee also has a shift on a central department","Subcontract functionality did not work when employee also has a shift on a central department on the same day. \nThis has been fixed. \nIt is now possible to use the subcontract actions when there are shifts in the same planboard cell that have been sent to a central department, as well as subcontracted shifts.\n\nTest hint(s):\n1. Verify that subcontract actions are available when the planboard cell contains shifts that have been sent to a central department as well as subcontracted shifts.","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDCOMMAIN-13698","13435349"]
[null,null,1464524,"2022-01-20",null,"","New Feature","Reliability","Logging","Added additional logging when errors occur on handling queue updates","Added additional logging when errors occur on handling queue updates. \nIf feature toggle AlwaysQueryTransactionDataObject is disabled and errors occur, a suggestion will also be logged to enable the feature toggle.\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13811",""]
[null,null,1464524,"2022-01-20",null,"Backend Domains Api","New Feature","Reliability","BackendDomainsAPI","Wrong shift for absence in Adhoc planning","The wrong shift could be shown as 'Absent'. This could happen in case there was a shift starting late in the evening on the day before the absence. \nThis has been fixed. Now, only the shift that starts at the day of the absence, is shown as 'Absent'.\n\nTest hint(s):\n1. Report an employee absent in Ad Hoc Planning. Verify that only shifts starting during the absence are shown as 'Absent'. ","","OSDOWSRES-1561","13736052"]
[null,null,1467292,"2022-02-03",null,"","New Feature","Functionality","Import / Export","Importing rotation unit lines did not consider gap between assignment in same department","Importing rotation unit lines did not consider gap between assignment in same department when using the ExtraXMLCreator TEmployeeImportDepartmentUpdate.\nThis has been fixed. \nAn XML import setting FillGapBetweenAssignmentsWhenOverriding was added. By default it has value False. If this value is set to True, it will fill these gaps. If set to False, if there are any gaps in the existing rotation unit lines, these will remain after the import finished. \n\nTest hint(s):\n1. Verify that when importing rotation unit lines using the ExtraXMLCreator TEmployeeDepartmentUpdate, gaps between assignments are filled when FillGapBetweenAssignmentsWhenOverriding is set to True and behavior did not change when setting it to False or omitting it.","","OSDCOMMAIN-13633","13195618"]
[null,null,1467292,"2022-02-03",null,"","New Feature","Reliability","GUI","Several translations added for German and French","Several translations have been added for German and French.\n\nTest hint(s): \nNone","","OSDCOMMAIN-13801","13774739"]
[null,null,1467292,"2022-02-03",null,"","New Feature","Reliability","GUI","Several translations added for German","Several translations have been added for German \n\nTest hint(s): \nNone","","OSDCOMMAIN-13821",""]
[null,null,1467292,"2022-02-03",null,"","New Feature","Functionality","Optimization","Schedule optimizer created violations in the future for labor rule 'Rest after shift'","Schedule optimizer created violations in the future for labor rule 'Rest after shift'.\nThis has been fixed for the labor rule.\n\nTest hint(s):\n1. Verify no violations in the future for labor rule 'Rest after shift' will be created when running the schedule optimizer.\n\nNote: The schedule optimizer assumes in general that the planning is made chronologically, starting from an empty planning. Given this, unexpected behavior can happen when there are already shifts planned in the future. It does not look at violations in the future.","","OSDOWSD-4534",""]
[null,null,1467292,"2022-02-03",null,"","New Feature","Functionality","Optimization","Schedule optimizer created violations in the future for labor rule 'Rest per number of hours'","Schedule optimizer created violations in the future for labor rule 'Rest per number of hours'.\nThis has been improved for the labor rule.\n\nTest hint(s):\n1. Verify no violations in the future for labor rule 'Rest per number of hours' will be created when running the schedule optimizer.\n\nNote: The schedule optimizer assumes in general that the planning is made chronologically, starting from an empty planning. Given this, unexpected behavior can happen when there are already shifts planned in the future. It does not look at violations in the future.\n\nNote 2: An individual shift planned by the optimizer will no longer create a violation because of shifts outside of the optimized period.\nHowever, a violation might still occur due to a combination of shifts planned by the optimizer in the defined rest period (such as multiple shifts on 1 day). Combinations of optimized shifts can not be checked in the pre-processing step as implemented in this fix.","","OSDOWSD-4535",""]
[null,null,1470284,"2022-02-17",null,"","New Feature","","","Several translations updated for German","Several translations updated for German\n\nTest hint(s):\n1. None","","OSDCOMMAIN-13831","13845854"]
[null,null,1470284,"2022-02-17",null,"","New Feature","Reliability","Self scheduling","OWS for Employees: Instead of an access violation show a more meaningful message when retrieving alternatives on a just deleted shift","OWS for Employees: Instead of an access violation show a more meaningful message when retrieving alternatives on a just deleted shift\nWhen retrieving alternatives for a shift that was just deleted, an access violation could be shown.\nThis has been improved\nBefore we retrieve the alternatives we (re)verify if the shift is still available, if it is not a message it shown that the data was changed by a different user.\n\n\nTest hint(s)\n1. request alternatives in OWS for Employees","","OSDCOMMAIN-13843","13915460"]
[null,null,1470284,"2022-02-17",null,"","Bug","","","Commandhandlers should use the causing user","When updating or assigning shifts in ad hoc planner or shift offering, the user who is performing the action is sent to the OWS server.  This user will appear in the shift reassignment overview instead of the default interface user.\n\nTest hints:\n1. Test that updating and reassigning still works in ad hoc planner and shift offering","","OSDOWSTS-205",""]
[null,null,1472746,"2022-03-03",null,null,"New Feature","Configuration","Optimization","Rescheduling optimizer (introduced in OSDOWSD-1505) available behind general setting UseReschedulingPlanner","Feature toggle USERESCHEDULINGPLANNER has been moved to become a Use within general settings.\nThis makes the Rescheduling optimizer (introduced in OSDOWSD-1505) available behind this general setting.\nLike other planners, UseReschedulingPlanner is only visible when UseAdvancedPlanning is on. It can be found under General -> Automatic planning and is part of the module modGenerator.\nA DBUpdate script has been included to automatically activate this Use for customers that currently have this feature toggle turned on, as well as remove this feature toggle from the database.\n\nTest hint(s):\n1. Verify that the new UseReschedulingPlanner general setting is visible when UseAdvancedPlanning is on.\n2. Verify that when UseReschedulingPlanner is off, rescheduling proposals cannot be created for vacant shifts and vice versa.","","OSDOWSD-1548"]
[null,null,1474171,"2022-03-10",null,"","New Feature","Security","Security","UseNonEmployeeAddresses did not consider the alternative travel addresses","In OSDOWSD-4493, personal addresses of employees were filtered out when entering a realization in ORTEC WS for Employees in case BackendAPI setting UseNonEmployeeAddresses was turned on.\nIn that change employees travel addresses were not filtered out while these are personal addresses.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that when UseNonEmployeeAddresses is on, no travel addresses of employees are shown among the selectable addresses when entering a realization in ORTEC WS for Employees.","","OSDCOMMAIN-13857","13969387"]
[null,null,1474171,"2022-03-10",null," ","New Feature","Functionality","Calculation","Technical change: added functionality for buffering and calculation of upcoming demanded duty skills functionality","Technical change: added functionality for buffering and calculation of upcoming demanded duty skills functionality.\n\nWhen configuring the new worker that does the calculations for the skill demand optimization be sure to have a worker for handling OWS for Employee calls (ESS) and skill demand optimizations:\n1. Configure a worker server number for the skill demand optimization and add a OWS Settings manager using Options\\SkillMatching\\DedicatedServerNumber with the worker number\n2. Configure a worker for handling OWS for Employees (ESS) to be a different worker and configure this number in CSCS Settings Manager: Comtec.Workforce.BackendAPI\\Portals\\InterfaceServerNumber\n\nTest hint(s):\n1. None","","OSDOWSD-4524",""]
[null,null,1474171,"2022-03-10",null,"","New Feature","","","Technical changes made to Back-end API for Front-end changes needed for upcoming demanded duty skills functionality","Technical changes made to Back-end API for Front-end changes needed for upcoming demanded duty skills functionality.\n\nTest hint(s):\n1. None","","OSDOWSD-4547",""]
[null,null,1474171,"2022-03-10",null,"Shift Offering","Bug","Stability","Mobile application","Resend notifications when users don't have a registered device","Firebase returned a 'BadRequest' in case no employees were linked to a user or had a device registered. This is not something that the calling app is responsible for, but it may retry to send notifications. This has been fixed.\nNow, Firebase will return 'Ok' in case no employees are linked to a user or have a device registered.\n\nTest hint(s):\n1. Offer a shift in Ad Hoc Planning, and verify that the expected employees receive a notification.","","OSDOWSRES-1611","13845770"]
[null,null,1477295,"2022-03-25",null,"","New Feature","Stability","Planboard","Changing the status of a scheduling period could cause an integer overflow error","Changing the status of a scheduling period could cause an integer overflow error\nWhen changing a status of a scheduling period an estimation is done on how long such a transaction should take.\nDuring a performance test it was observed that changing a status of a scheduling with a lot of shifts this could cause that estimated value to be too large, resulting in a integer overflow exception.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that changing the status of a scheduling period does not cause an integer overflow error.","","OSDCOMMAIN-13860",""]
[null,null,1477295,"2022-03-25",null,"","New Feature","Performance","Optimization","OWS win32 Client: While the demanded duty set form is shown a lot of requests to CWSS Server (process) were done that could cause performance degradation","OWS Win32 Client: While the demanded duty set form is shown a lot of requests to CWSS Server (process) where done that could cause performance degradation \nThis has been improved.\nTo enabled/disable the buttons a request was done to CWS SServer to identify the selected demanded duty several times\nThe number of these requests has been reduced.\n\nNOTE: This was introduced in OSDOWSD-4471 Added functionality to duty demand windows to include demanded skills and only noticeable when UseDemandedDutySkills was enabled.\n\nNext the above mentioned issue an improvement has been done for calculating the under/overstaffing for demanded duty skills.\nThis could show an Invalid type cast error.\n\nTest hint(s):\n1. Verify that the buttons within the demanded duty skills window work correctly","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDCOMMAIN-13863",""]
[null,null,1477295,"2022-03-25",null,"","New Feature","Configuration","Installer","Added functionality to set 'Require Server Name Indication' on the website binding to the back-end API installation script","The BackendAPI installation script had no option to configure 'Require Server Name Indication' in the website binding. \nThis has been improved.\n'Require Server Name Indication' will be enabled by default but can be disabled in the InstallPortal.xml configuration file.\n\nTest hint(s):\n1. Verify whether one can login to WS for Employees, WS for Managers and ESS7 App (backendAPI version) and data is retrieved.\n","To disable 'Require Server Name Indication' in any existing InstallPortal.xml, add the following node:\n\n<!-- Require Server Name Indication in website binding, use True or False -->\n<requireServerNameIndication>False</requireServerNameIndication>\n\nNote: If 'Require Server Name Indication' should be enabled by default the above node does not need to be added to an existing InstallPortal.xml","OSDCOMMAIN-13870","14016585"]
[null,null,1477295,"2022-03-25",null,"","New Feature","Functionality","Client","Technical preparation of upcoming demanded duty skills functionality","Technical preparation of upcoming demanded duty skills functionality.\n\nTest hint(s):\nNone",null,"OSDOWSD-4603",""]
[null,null,1478670,"2022-03-31",null,"","New Feature","","","Opening personal schedule loaded all unassigned and removed shifts of the schedule","Opening personal schedule loaded all unassigned and removed shifts of the schedule. \nThis has been improved.\n\nAdded feature toggle setting: FeatureToggles\\DoNotLoadRemovedAndUnassignedShiftsForPersonalSchedule and is by default enabled. \n\nTest hint(s):\n1. Verify that a personal schedule of an employee can be opened in ORTEC WS Win32 client.","","OSDCOMMAIN-13859","13998147"]
[null,null,1478670,"2022-03-31",null,"","New Feature","Functionality","Self Rostering","Added skill requirement functionality to demanded duty","This update includes the second part of the project that enables skill requirements for demanded duties.\nWhile the first part was about the ability to define skill requirements, this second part focuses on calculating which skills are missing based on the employees assigned to demanded duty shifts. An algorithm optimizes this calculation by matching employee skills to the skill requirements, such that the number of missing skills is the lowest. This is especially relevant when employees have multiple skills.\nAn important assumption of this functionality is that employees can only be matched for one of their available skills.\n\nIn order to enable this functionality:\ni. Global setting UseDemandedDutySkills introduced in (OSDOWSD-4471) must be turned on\nii. Added ORTEC WS Settings Manager setting Server/Options/SkillMatching/DedicatedServerNumber which determines where calculations will be performed. It is strongly advised to use a dedicated interface worker.\n\nThe number of missing skills is visible in a newly introduced shift counter option (Display settings > General > Shift counters):\ni. Added counter: Assigned / Request according to duty demand / Skill requirements\nii. Added compare method for counter: Request according to duty demand / Skill requirements\nThe third number in the counter is the number of missing skills and the hint text shows the details of the skill matching optimization. It shows which skills can be used to reduce the understaffing.\n\nA new hierarchical criteria, \"Skill staffing\" has been created. To turn on this criteria, enable the general setting DemandedDutySkillsHCrit in ORTEC WS Settings Manager. This criteria can be used to impose additional restrictions in self scheduling rounds, based on the skill requirements and the currently assigned employees.\n\nTest hint(s):\n1. Verify that if demand duties have skills requirements, the shift counter will show the number of missing skills.\n2. Verify that the hierarchical criteria \"Skill staffing\" can be configured.\n3. Verify that additional restrictions are applied in a self scheduling round based on hierarchical criteria \"Skill staffing\".","For this solution to become available, the ORTEC WS Win32 client must be installed.","OSDOWSD-4611",""]
[null,null,1478670,"2022-03-31",null,"","New Feature","Stability","Optimization","Schedule optimizer: Several labor rules were checked incorrectly on violations in the future","Schedule optimizer: Several labor rules were checked incorrectly on violations in the future:\n- 'Rest after shift, two exceptions'\n- 'Rest per week for shift with certain activity kind' \n- 'Rest before and after shift with certain activity kind'\n- 'Daily rest time' (note: this rule has been deprecated, please use 'Rest per number of hours' instead)\nThis has been fixed. \nThese labor rules are no longer checked for violations in the future. \nChecking for violations in the future is only done for labor rules 'Rest after shift' and 'Rest per number of hours'. \nNote: this has been introduced in OSDOWSD-4534, 8.5.0(2022-02-03)_Build1467292\n\nTest hint(s):\n1. Verify the optimizer works correctly for the labor rules mentioned above.","","OSDOWSD-4637",""]
[null,null,1479657,"2022-04-07",null,"","New Feature","Functionality","Self Rostering","OWS for managers: When approving a leave request and adding a remark to it, the remark was not shown","When approving a leave request from OWS for managers and adding a remark to it, the remark would not be shown to the employee in OWS for employees. \nThis has been fixed.\nThis has also been fixed for declining a leave request. \n\nTest hint(s):\n1. Approve a leave request from OWS for managers and leave a remark\n2. In OWS for employees it should show the remark","","OSDCOMMAIN-13646","13257439"]
[null,null,1479657,"2022-04-07",null,"","New Feature","Performance","DataWarehouse","Improved performance and accuracy of retrieving cost centers in BI package FACT_Cyclic_Activity","The BI package FACT_Cyclic_Activity matched cost center records row by row. This would cause a lot of queries on the HDM database with a higher chance of network errors between the HDM_Stage and HDM databases.\nThis has been improved.\nThe package will now match cost centers in one go. This is more stable and also increases the package performance.\n\nAlso improved the accuracy of retrieving the cost center of a cyclic activity. Due to a bug in matching the validity period of a (historical) cost center record, an incorrect historical cost center record could be returned or no cost center record could be found.\n\nTest hint(s):\n1. Verify the package runs and retrieves the correct data","","OSDCOMMAIN-13682","13390575"]
[null,null,1479657,"2022-04-07",null,"","New Feature","Reliability","Calculation","Demanded duty skill counter was calculated incorrectly for employees with shifts assigned in trial scenarios","Demanded duty skill counter was calculated incorrectly for employees with shifts assigned in trial scenarios. \nThis has been fixed.\nShifts in trial scenarios are not taken into account anymore.\n\nTest hint(s):\n1. Verify demanded duty skill counter is correctly calculated when trial scenarios are also in use.","","OSDOWSD-4651",""]
[null,null,1482226,"2022-04-21",null,"","New Feature","Functionality","Reporting","Master schedule Report could show unexpected shift name","Master schedule Report could show unexpected shift name. This could happen when setting SAVESHIFTBEFORELEAVEWHENREPLACEACTIVITYTYPEININTERVAL and privacy mode were ON. \nThis has now been fixed.\n\nTest hint(s):\n1. Run the master schedule Report\n2. Verify all shift names are as expected in the Master schedule report","","OSDCOMMAIN-13636","13229077"]
[null,null,1482226,"2022-04-21",null,"","New Feature","Reliability","Planboard","Number of vacant shifts were incorrectly shown in the ORTEC WS Win32 client planboard when an employee has multiple contracts","Number of vacant shifts were incorrectly shown in the ORTEC WS Win32 client planboard when an employee has multiple contracts. \nThis has been improved.\n\nTest hint(s):\n1. Verify that correct number of vacant shifts are shown in ORTEC WS Win32 client planboard when one of the demanded duties are assigned to an employee with multiple contracts.","","OSDCOMMAIN-13703","13467077"]
[null,null,1482226,"2022-04-21",null,"","New Feature","Stability","Import / Export","The planner results import would fail if multiple imports ran simultaneously","The planner results import would fail if multiple imports ran simultaneously.\nThis has been improved.\nIt now retries 300 times with a 1 second interval between each retry.\n\nTest hint(s):\n1. Verify that running planner result imports succeeds","","OSDCOMMAIN-13723","13505042"]
[null,null,1482226,"2022-04-21",null,"","New Feature","Reliability","Utilities","Several command handler examples in Command Sender were incorrect","Several command handler examples in Command Sender were incorrect.\nThis has been improved.\nThe following command handlers have received a new example:\nhmy/server1/CAcceptSubcontractShifts\nhmy/server1/CCancelSubcontractShifts\nhmy/server1/CConceptPlanSubcontractShifts\nhmy/server1/CDeclineSubcontractShifts\nhmy/server1/CDeleteShift\nhmy/server1/CFinalizeSubcontractShifts\nhmy/server1/CReplaceShiftByActivityType\nhmy/server1/CReplaceShiftByIllness\nhmy/server1/CReplaceShiftByLeave\nhmy/server1/selfroster/CUnplanShifts\nhmy/server1/CSendShiftsBackToDecentralDepartment\nhmy/server1/CSendShiftsToCentralDepartment\nhmy/server1/CSubcontractShiftsToDepartment\n\nTest hint(s):\n1. Verify that the new examples are displayed for the command handlers listed above","","OSDCOMMAIN-13748","13599086"]
[null,null,1482226,"2022-04-21",null,"","New Feature","Reliability","Planboard","When history is shown, increase or decrease day specific demanded duty could also be applied to duties of previous duty set","When history is shown, increase or decrease day specific demanded duty action in the shift counters could also be applied to duties of previous duty set. \nSelecting a duty from the previous duty set would then result in an error.\nThis has been fixed.\nOnly duties that are part of the duty set assigned of the current duty set period will now be available when the increase or decrease action is chosen.\n\nTest hint(s):\n1. Verify increase and decrease day specific demanded duty actions in the shift counter work correctly. ","","OSDCOMMAIN-13756","13626379"]
[null,null,1482226,"2022-04-21",null,"","New Feature","Reliability","Optimization","Timestamp in name of logfile ShiftPlannerExport was not distinctive","Timestamp in name of logfile ShiftPlannerExport was not distinctive. \nThis has been improved.\n\nThe name of the logfile now also includes milliseconds and the schedule in the format like ShiftPlannerExport_yyyymmdd_hhmmsszzz_Sched_id.json\n\nNote, this logfile is only created when server setting \\Planner\\ShiftPlannerExport\\WriteShiftPlannerExport is True\n\nTest hint(s):\n1. When running the schedule optimizer, verify logfile for ShiftPlannerExport is created ","","OSDCOMMAIN-13763","13634996"]
[null,null,1482226,"2022-04-21",null,"","New Feature","Reliability","Client","When using the filter 'Shift with activity type' in accounts on departments without a schedule, an assertion failure would be shown","When using the filter 'Shift with activity type' in accounts on departments without a schedule, an assertion failure would be shown.\nThis has been improved. \nNow the client will show the error message 'The filter 'Shift with activity type' is not available when the selected department is all departments, a parent department, or a sub department without a schedule.'\n\nTest hint(s):\n1. Verify that when the filter 'Shift with activity type' in accounts is applied to a all departments, a parent department, or a sub department without a schedule, the new error message is shown.","","OSDCOMMAIN-13794","13732623"]
[null,null,1482226,"2022-04-21",null,"","New Feature","Reliability","Database","Last_Updated_At column of ROS_SHIFTS table in ORTEC WS database did not update when a shift status is changed","Last_Updated_At column of ROS_SHIFTS table in ORTEC WS database did not update when a shift status is changed.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that when a shift status is changed in ORTEC WS Win32 client, the corresponding entry of Last_Updated_At in ROS_Shifts table is updated.","","OSDCOMMAIN-13889","14074917"]
[null,null,1482226,"2022-04-21",null,"","New Feature","Reliability","Self Rostering","Skill staffing shift proposal criterion caused access violation when command handler selfroster/CUnplanShifts was called on one-time duty","Skill staffing shift proposal criterion caused access violation when command handler selfroster/CUnplanShifts was called on one-time duty.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that when the skill staffing shift proposal criterion is active, no access violations occur when unplanning a one-time duty through the selfroster/CUnplanShifts command handler","","OSDCOMMAIN-13894",""]
[null,null,1482226,"2022-04-21",null,"","New Feature","Reliability","Planboard","Plan in activity type would not plan the selected activity when shifts were planned in a trial scenario on the same day, and the other way around","Plan in activity type would not plan the selected activity when shifts were planned in a trial scenario on the same day, and the other way around (using plan in activity type in a trial scenario, while a shift was planned in the regular schedule). \nThis has been fixed.\n\nTest hint(s);\n1. Verify that when using 'Plan in activity type' on a day in the regular schedule on which there is also a shift planned in a trial scenario, the action works correctly.\n2. Verify that when using 'Plan in activity type' on a day in a trial scenario on which there is also a shift planned in the regular schedule, the action works correctly. ","","OSDCOMMAIN-13896","14115317"]
[null,null,1482226,"2022-04-21",null,"","New Feature","Stability","Calculation","Skill staffing shift proposal criterion could throw an access violation when shift and skills are both understaffed","Skill staffing shift proposal criterion could throw an access violation when shift and skills are both understaffed. \nThis has been fixed.\n\nTest hint(s):\n1. Verify the 'Skill staffing' shift proposal criterion works correctly when both the shift and the skills are understaffed","","OSDCOMMAIN-13900",""]
[null,null,1482226,"2022-04-21",null,"","New Feature","Technical","Service","Removed featuretoggle IMPROVEDLOCKINGMECHANISM","Removed featuretoggle IMPROVEDLOCKINGMECHANISM.\nIn OSDCOMMAIN-12019 - 'Erroneous administration of locks can cause 'Cannot dec FCount below 0' error' this feature toggle was added as a safe-guard to safely revert an improvement on the locking mechanism. \nAnalysis of this improvement has shown it works as expected, so by removing the feature toggle the improvement becomes the default.\n\nTest hint(s)\n1.  Verify that multiple users of ORTEC WS Win32 clients can do concurrent actions in planboards  ","","OSDOWSD-1547",""]
[null,null,1482226,"2022-04-21",null,"","New Feature","Stability","Database","The DetectCorruptData script could wrongfully classify some data as corrupt","The DetectCorruptData script could wrongfully classify some data as corrupt.\nThis has been fixed.\n\nTest hint(s):\n1. Run DetectCorruptData through DBUpdate and verify that there are no unexpected errors.","","OSDOWSD-4346",""]
[null,null,1482226,"2022-04-21",null,"","New Feature","Reliability","Tools","UnattendedUpdates - Script stops without error handling when release notes csv file is not present","UnattendedUpdates script could not handle a missing \n Cumulative_ReleaseNotes_OWS7.csv and would stop after a successful update, but before a confirmation email could be sent.\nThe script will now proceed in such a situation and state that the release notes could not be processed in the 'update finished' email.","","OSDOWSD-4424",""]
[null,null,1482226,"2022-04-21",null,"","New Feature","Technical","Employee self-service app","Technical changes made to Back-end API for Front-end changes needed for retrieving ORTEC WS for Employees Departments","Technical changes made to Back-end API for Front-end changes needed for retrieving ORTEC WS for Employees Departments.\n\nTest hint(s):\n1. None ","","OSDOWSD-4574",""]
[null,null,1483503,"2022-04-29",null,null,"New Feature",null,null,"Approving a leave wish also replaced shifts on other contracts of the same employee","Approving a leave wish also replaced shifts on other contracts of the same employee.  \nThis has been fixed.  \n\n\nTest hint(s): \n1. Verify that when approving a leave wish for an employee with more than one contract, only shifts on that contract are replaced by the chosen leave activity. ",null,3135,13469589]
[null,null,1483503,"2022-04-29",null,null,"New Feature",null,null,"Ad Hoc Planning - Show subcontracted shifts in their current department instead of their original department","Subcontracted shifts were shown in their original department. This has been fixed. Now, the subcontracted shifts are shown in their new department. Also, the department name shown in the shift details in Shift Offering is the new department. \r\nNote that it is possible to keep the previous behaviour by setting the value of the new setting AdhocPlanning\\Shifts\\UseCurrentDepartmentOfShift to False. \r\n\r\n\r\nTest hint(s): \r\n1. Create a subcontracted shift in OWS Client. Verify that it is visible in the schedule of the new department in Ad Hoc Planning, and not in the old department. \r\n2. Verify that the department name shown in the shift details when offering a shift is of the new department. ",null,2776]
[null,null,1483503,"2022-04-29",null,null,"New Feature",null,null,"Unattended Updates - added support for multiple BackendDomainsApi websites","In case multiple websites are created on the BackendDomainsAPI installation the Unattended Updates script could not stop all BackendDomainsAPI websites and application pools as only one website and application pool is expected in a regular installation.  \r\nThis has been improved.  \r\nThe script will now stop all websites and application pools linked to the installation directory of the BackendDomainsAPI.  \r\n\r\n\r\nTest hint(s):  \r\n1. Verify that an update for the BackendDomainsAPI succeeds when a single or multiple BackendDomainsAPI websites exist. ",null,3158]
[null,null,1483503,"2022-04-29",null,null,"New Feature",null,null,"Leave process algorithm did not work correctly in central departments","Leave process algorithm did not work correctly in central departments. This occurs for the type ReplaceExistingShifts.\n\nThis has been fixed. \n\n\nTest hint(s): \n1. Verify approving leave wishes for employees with shifts in central department goes correct \nVerify reverting leave wishes for employees with shifts in central department goes correct",null,3141,13800673]
[null,null,1483503,"2022-04-29",null,null,"New Feature",null,null,"OWS for managers: It was not possible to approve multiple realizations if one or more shifts overlap","OWS for managers: It was not possible to approve multiple realizations if one or more shifts overlap.  \r\nThis has been fixed.  \r\nIt will now approve all valid realizations and return an error message if one or more approvals failed.  \r\n\r\n\r\nTest hint(s):  \r\n1. Verify that approving multiple realizations succeeds ",null,3140,13800665]
[null,null,1483503,"2022-04-29",null,null,"New Feature",null,null,"Unattended Updates - Script did not stop when unknown errors occurred in the PatchUtilConsole","The UnattendedUpdates script did not stop when unknown errors occurred in the PatchUtilConsole.  \r\nThis has been fixed.  \r\nExtra error handling has been added and unknown messages will be raise a warning per email.  \r\n\r\n\r\nTest hint(s):  \r\n1. Verify Unattended Updates script still works ",null,3155]
[null,null,1485063,"2022-05-05",null,null,"New feature",null,null,"OWS for Employees: Account for Employee report returned wrong data when rotation unit end date is before the last published until end date","OWS for Employees: Account for Employee report returned wrong data when rotation unit end date is before the last published until end date. \nThis has been fixed. \n\nTest hint(s): \n1. Verify in OWS for Employees that the Account for Employee report returns the correct data when the employee's rotation unit end date is before the last published until end date.",null,3139,13734066]
[null,null,1485063,"2022-05-05",null,null,"Bug",null,null,"OWS for Employees: Account for Employee report returned wrong data when all schedules are published","OWS for Employees: Account for Employee report returned wrong data when all schedules are published. \nThis has been fixed. \n\nTest hint(s): \n1. Set all schedules to published for department A \n2. Verify in OWS for Employees that the Account for Employee report returns the correct data",null,3027,13689714]
[null,null,1485063,"2022-05-05",null,null,"New feature",null,null,"Technical change to command handler CCleanUpRemovedShifts to prevent panic exceptions","Technical change to command handler CCleanUpRemovedShifts to prevent panic exceptions\nDue to a technical issue, using the command handler CCleanUpRemovedShifts could result in a panic exception. \nThis has been improved. \nThis new functionality is added behind a new feature toggle setting: FeatureToggles\\ImproveLockingForCleanUpRemovedShifts and is by default enabled.\n\nTest hint(s): \n1. Verify that calling CCleanUpRemovedShifts does not result in a panic exception",null,3039]
[null,null,1485063,"2022-05-05",null,null,"New feature",null,null,"UnattendedUpdates - Improved file handling during backup of downloaded update files","During the backup of downloaded updates all zip files were removed. This could have an unintended effect in case the BackupLatestUpdateFolder for the test environment is used as the PatchUtilFolder for the production environment.\nAdjusted file filtering will now only remove Manual_Update*.zip, Update*.zip and Cumulative_ReleaseNotes_OWS7.csv, thus leaving any other zip files (like ToDo_(Manual_)Update files) in the BackupLatestUpdateFolder. \nThe Cumulative_ReleaseNotes_OWS7.csv file was not regarded during cleaning the PatchUtil folder before download of updates or backing up the downloaded update. This file will now also be handled.\n\nTest hint(s): \n1. Verify the UnattendedUpdate process returns no errors on download and backup in case the configuration file option <downloadUpdates> is set to Y ",null,3157]
[null,null,1485063,"2022-05-05",null,null,"New feature",null,null,"date:add function in the library stylesheet date.add.template.xsl did not work correctly when using a negative number of minutes","The date:add function in the library stylesheet date.add.template.xsl did not work correctly when using a negative number of minutes.\nThis has been fixed.  \n\nTest hints(s): \n1. Verify the date:add function in the library stylesheet date.add.template.xsl works correctly when using a negative number of minutes. ",null,3137,13706049]
[null,null,1485063,"2022-05-05",null,null,"New feature",null,null,"ORTEC WS for Employees: The query that populates contracts sometimes returned an unexpected contract","In ORTEC WS for Employees the query that populates contracts sometimes returned an unexpected contract. \nThis has been fixed.\nIt now selects the latest contract always.\n\nTest hint(s): \n1. From ORTEC WS for Employees request the contracts of an employee\n2. Verify the latest contract is returned",null,3143,13378028]
[null,null,1486167,"2022-05-12",null,"Technical improvements","New feature",null,null,"Added DBUpdate detect script and monitoring query that detect whether user queries exist that were previously system queries","Added DBUpdate detect script that detects whether active user queries exist that were previously system queries. If this is the case, a warning will be displayed that it is advised to fix these if not intended, as they might have been incorrectly changed through import/exports done before build 1344319.\nA monitoring query SystemMonitoring/CMHS/Weekly/Other/GetNumberOfSystemQueriesChangedToUserQuery was also added to count the affected number of queries. \nIn both cases, CRGS queries as well as BackendDomainsAPI/LaborRuleValidation/RuleSetCodeForEmployee are explicitly excluded from this check.\n\nTest hint(s):\n1. Verify DBUpdate does or does not raise a warning, depending on whether any user queries that were previously system queries exist\n2. Verify SystemMonitoring/CMHS/Weekly/Other/GetNumberOfSystemQueriesChangedToUserQuery query returns the correct number of user queries that were previously system queries","Exported queries via the 'Post install | Export configuration' action which were made before OWS7 update 1344319 contained queries that should not have been exported. These exported files should be cleaned/renewed because uploading them with postinstall (they are selected by default) can lead to system queries with an incorrect revision.\n\nAny detected invalid querykinds can be repaired with a script on the repair script library:\nDocument 00.866.753 - Repair CQMS user queries that should be system queries",3136,13599171]
[null,null,1486167,"2022-05-12",null,"OWS for Employees","New feature",null,null,"ORTEC WS for Managers - Staffing page showed duplicated employee for the described scenario in the task","OWS for Managers - Staffing page showed duplicated employee for the described scenario in the task. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that the staffing employees and demands are displayed correctly",null,3191]
[null,null,1486167,"2022-05-12",null,"OWS for Managers","New feature",null,null,"ORTEC WS for Employees: Team schedule showed shifts in status \"Plan\" when this is not allowed","The team schedule view in ORTEC WS for Employees always showed non-published shifts. \nThis has been improved by respecting the values of the following settings when retrieving shifts:\nCWGSESS\\PersonalRoster\\NumberOfDaysToShowPlannedShifts\nCWGSESS\\PersonalRoster\\ShowConceptPlannedShifts \n\nTest hint(s):\n1. None ",null,3285]
[null,null,1486167,"2022-05-12",null,"Technical improvements","New feature",null,null,"Technical change to logging of authentication level for DCOM ","Technical change to logging of authentication level for DCOM \nMicrosoft is about to make changes concerning the DCOM AuthenticationLevel. \nReference for this change is: https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-feature-bypass-cve-2021-26414-f1400b52-c141-43d2-941e-37ed901c769c\nThis logging was added to more easily see these settings for our applications and warn about misconfigurations\n\nTest hint(s): \n1. None ",null,3171]
[null,null,1486167,"2022-05-12",null,"Technical improvements","New feature",null,null,"DBAnonymize did not anonymize skill matching update tables","DBAnonymize did not remove data related to skill matching optimization functionality. \nThis has been fixed.\n\nTest hint(s):\n1. Verify that when anonymizing a database with DBAnonymize data in ROS_SKILL_MATCHING_UPDATES is truncated.","DBAnonymize has been updated. Requested databases should be anonymized using this new version.",3169]
[null,null,1488042,"2022-05-19",null,"Technical improvements",null,null,null,"Performance improvement made in Back-end API query to retrieve shifts","Performance improvement made in Back-end API query to retrieve shifts.  \n\nTest hint(s): \n1. None",null,3245,14129979]
[null,null,1488042,"2022-05-19",null,"Basic functionalities",null,null,null,"New hierarchical criterion \"Skill understaffing\" has been created","A new hierarchical criterion \"Skill understaffing\" has been created which can be used in the \"Candidates for shift\" functionality. \n\nIt is meant to be used together with the skill requirements functionality added in build 1477295. The criterion will indicate whether the employee has a skill that reduces the skill understaffing for the shift. \nIf this is the case 'Yes' will be displayed, and 'No' otherwise. It is possible to hide the employees that do not have a skill that reduces the skill understaffing.  \n\nIf there is no skill understaffing for the shift, a '-' will be displayed for all employees.  \n\nTo turn on this criterion, enable the general setting UnderstaffedSkillsHCrit in ORTEC WS Settings Manager. \n\nTest hint(s): \n1. Verify that the hierarchical criterion \"Skill understaffing\" can be configured \n2. Verify the results when using the criterion within the 'Candidates for shift' functionality",null,2721]
[null,null,1488042,"2022-05-19",null,"Technical improvements",null,null,null,"Improved query performance for 'Detect corrupt data' in DBUpdate","Improved query performance for 'Detect corrupt data' in DBUpdate. \n\nTest hint(s): \n1. Verify DBUpdate functions correctly.",null,3374,14205313]
[null,null,1488042,"2022-05-19",null,"OWS For Employees",null,null,null,"OWS for Employees: Team Schedule showed shifts in status plan when schedule is partially published","Team schedule overview: When a schedule is partially published all shifts of the schedule were returned.  \nThis is now improved. \nOnly the shifts in the published part are returned taken into account the configured number of days to show planned shifts. \n\nTest hint(s): \n1. Open team schedule and verify there are shifts with status plan when the schedule is partially published. ",null,3400]
[null,null,1488042,"2022-05-19",null,"OWS For Employees",null,null,null,"OWS For Employees: a new permission was added for future changes","OWS For Employees: a new permission was added for future changes\n\nA new AC permission object was added for ESS7 app \nAC object code = guiactions.ows.ess.createMultipleExchangeRequests.\nValue will be included in result of route /api/v2/OrtecApplications/ess/actionPermissions when Comtec.Workforce.Backend.V2.Model at front-end is updated. \n\nTest hint(s):\n1. Verify that users still can log on to OWS for Employees ",null,3311]
[null,null,1488042,"2022-05-19",null,"Technical improvements",null,null,null,"SQL Server Change Tracking could cause DBUpdate to fail","SQL Server Change Tracking could cause DBUpdate to fail.  \nThis has been fixed.  \nWhen the updates are applied, change tracking will now be disabled. After applying the updates, change tracking is re-enabled and the tables for which change tracking was active are logged in the update logging.  \nIn order to support and appropriately warn the user, the following items have also been added:  \nIn DBUpdate.exe a warning will be shown when change tracking is enabled on the selected database, after which the user can choose to continue. \nWhen using DBUpdateConsole a new optional parameter 'ContinueWhenChangeTrackingIsEnabled' is available, with allowed values 'Y' and 'N' (case insensitive). The default value is 'N'. When Change Tracking is enabled, the update will stop unless this parameter has value 'Y'. \nIn the Database Update Wizard an additional screen will be displayed. If Change Tracking is active, the following text will be displayed: \"The system has identified that SQL Server Change Tracking is enabled in the <database name> database. Please make sure you have taken the appropriate actions to synchronize the data before continuing. This is necessary to prevent losing the change tracking history. Abort when you are not sure.\"\nThe user then needs to check the checkbox 'Data has been synchronized successfully' before they can continue.\nIf Change Tracking is not active, the screen will simply say 'No change tracking was found on the chosen database. No further actions are required.' \nThe new DBUpdateConsole parameter ContinueWhenChangeTrackingIsEnabled has also been added to the UnattendedUpdates script with value 'Y'. \n\nTest hint(s): \n1. Verify DBUpdate, DBUpdateWizard, DBUpdateConsole and the UnattendedUpdates script work as expected ","The Database Update Wizard has an additional screen about Change Tracking. If SQL Server Change Tracking is active,  the following text will be displayed: \"The system has identified that SQL Server Change Tracking is enabled in the <database name> database. Please make sure you have taken the appropriate actions to synchronize the data before continuing. This is necessary to prevent losing the change tracking history. Abort when you are not sure.\"\nThe user then needs to check the checkbox 'Data has been synchronized successfully' before they can continue. \nIf Change Tracking is not active, the screen will simply say 'No change tracking was found on the chosen database. No further actions are required.'  \n\nThe UnattendedUpdates script will automatically disable change tracking when applying updates, and re-enable again afterwards. Please be aware that this disabling will result in a loss of the change tracking history, so the data should be synchronized before running the update script. ",3246,14130036]
[null,null,1489738,"2022-05-31",null,"Development\\OWSforAdHocPlanners",null,null,null,"UseCWSSForViolations did not work for Shift Offering when proposal departments are used","The CSCS setting UseCWSSForViolations did not work in Shift Offering in case the shift was offered to an employee that was not yet available to the department of the shift. This can happen if proposal departments are used.\nThis has been fixed. Now, the violations can be calculated by CWSS also when the employee is in a proposal department.  \nNote that in case the employee gets that shift assigned, that employee will be lend in for the duration of the shift (this is existing functionality). \n\nTest hint(s): \n1. Offer a shift and verify that only employees that would not get a violation, are in the sent-to list. Also verify that an employee in a proposal department gets a notification for the shift. ",null,3015]
[null,null,1489738,"2022-05-31",null,"Development\\OWS7\\OWS for Employees",null,null,null,"ORTEC ESS Mobile App: Detailed information on absence was shown ","ORTEC ESS Mobile App: Detailed information of absence was shown\nThis has been improved.\nThe detailed absence information in activity and shift that are replaced by a general absence code default is 'A'.\n\nThe settings involved to determine what is replaced as absence see settings:\nComtec.Workforce.BackendAPI\\Portals\\TreatmentsReplacedByGeneralAbsenceCode\nComtec.Workforce.BackendAPI\\Portals\\GeneralAbsenceName\n\nTest hint(s):\n1. Verify that schedule information is displayed correctly in ORTEC ESS Mobile App ",null,3561]
[null,null,1489738,"2022-05-31",null,"Development\\OWS7\\OWS for Employees",null,null,null,"A duty wish created from typing in the planboards requests view had an incorrect enddate","When creating a dutyWish by typing a duty name in the planboards request view (F12), the endtime of the wish would be set to infinite (2447-07-30). \nThis caused the schedule in WS for Employees to display the dutyWish (indicated by a dot) on the day of the dutyWish and all consecutive days. \nAdding a dutyWish in this manner will now use the same endtime as adding a dutyWish in the employee requests form. \n\nA DBUpdate repair script was also added to correct existing dutyWishes with an incorrect endtime. \n\nTest hint(s): \n1. Verify that new and existing dutyWishes created by typing a duty name in the planboards request view (F12) are only displayed on the day of the wish in the schedule of WS for Employees. ",null,3350,14201017]
[null,null,1489738,"2022-05-31",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Added workstation planner rule: Employee experience on workstation","Added workstation planner rule: Employee experience on workstation. This rule can be enabled by checking WPRuleExperienceHoursInPeriod in ORTEC WS Setting Manager > General Settings. If configured, this rule will take employee's experience in a workstation into account. It will prioritize scheduling employees on workstations on which they, compared to their colleagues, have worked least number of hours in the past X days. \n\n\nThe past X days to consider employee experience is by default set to 30 days. It can be set to any days between 1 and 365. However, if the number of days exceed the buffered history, the buffered history will be used in the calculations instead.\n\nTest hint(s):\n1. None",null,2915]
[null,null,1489738,"2022-05-31",null,"Development\\OWS7\\Basic functionalities",null,null,null,"#CHANGED# was displayed as a prefix for many Finnish translations","#CHANGED# was displayed as a prefix for many Finnish translations.  \nThis has been fixed.  \nPlease be aware that this prefix indicates that functionality has changed. Only the #CHANGED# were removed as requested, so the Finnish translations have not been updated and might be incorrect. \n#CHANGED# will still be present for translations which were newly added. \n\nTest hint(s): \n1. Verify no more '#CHANGED#' prefixes are shown when using the client in the Finnish language  ",null,3423,14043790]
[null,null,1489738,"2022-05-31",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Changed German translation","Translation has been changed for German.  \n\nTest hint(s): \n1. None ",null,3297,14143226]
[null,null,1489738,"2022-05-31",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Added functionality to show the experience hours of an employee on a workstation in a workstation's employee proposal","It is now possible to show the experience hours of an employee on a workstation in a workstation's employee proposal.  \nThe additional column can be enabled in ORTEC WS Settings Manager: OPTIONS\\WORKSTATIONPLANBOARD\\WORKSTATIONRESOURCEPROPOSAL\\SHOWEXPERIENCEHOURS (y/n) \n\nThe experience hours are calculated by summing all planned hours (regardless of the activity treatment) on that workstation in the past X days, not including the current day. \nX is based on a newly introduced setting which can also be set in ORTEC WS Settings Manager: OPTIONS\\WORKSTATIONPLANBOARD\\WORKSTATIONRESOURCEPROPOSAL\\NROFDAYSFOREXPERIENCEHOURS (default value 30) \n\nNotes: \n- To prevent performance problems, X can never be higher than the buffered history. If the setting is higher than the buffered history, X will be replaced in code by the buffered history value \n- The experience hours are only shown for employees that are permitted on the workstation. \n- The experience hours are only shown in the normal employee proposal, not the (extra) one. \n\n\nTest hint(s): \n1. Verify the experience hours are visible in the workstation's employee proposal when the new setting is enabled ","For this solution to become available, the ORTEC WS Win32 client must be installed.",2819]
[null,null,1489738,"2022-05-31",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Several translations changed for German","Several translations have been changed for German \r\n\r\n\r\nTest hint(s): \r\n1. None ",null,3422,14043787]
[null,null,1489738,"2022-05-31",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Several translations added for German","Several translations added for German. \n\nTest hint(s):  \n1. None ",null,3504]
[null,null,"1491589","2022-06-10",null,"Development\\OWS7\\Technical improvements",null,null,null,"Monitoring: Removed unused process counters from system monitoring configuration","Removed process counters handlesCount, privateMemory and workingSet from ORTEC System Monitoring configuration as these were not used in Monitoring reports. \nNote the counters are still available in the repository (monitoringConfigurationSystem_<environment>_repository.xml) but they are no longer sent to email recipients. \n\nTest hint(s): \n1. None",null,3296,14141824]
[null,null,"1491589","2022-06-10",null,"Development\\OWS7\\Schedule optimizer",null,null,null,"Add DayShiftPlanner to Schedule optimizer","Added new functionality to schedule optimizer to solve simple assignment problem to optimality. \nThe shift assignment problem is consider as a simple assignment problem when  \n- There are no vertical or horizontal requirements or criteria \n- An employee can only work one shift per day  \n\nNote: the new functionality is behind feature toggle UseDayShiftPlanner (Default enabled) and it is only used when more than one schedule is used by the schedule optimizer \n\nTest hint(s): \n1. Verify the schedule optimizer still creates feasible solutions ",null,3367]
[null,null,"1491589","2022-06-10",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Several translations changed for German","Several translations changed for German.\n\nTest hint(s):\n1. None ",null,3688,14269030]
[null,null,"1494101","2022-06-23",null,"Development\\OWS7\\Technical improvements",null,null,null,"SkillMatchingAlgorithm triggered on cyclical shift","The worker with role=SkillDemandOptimization could halt in case an overstaffed shift from a cyclical schedule is unplanned and OWS is setup to force delete unplanned overstaffed shifts. \r\nThis has been fixed. \r\n\r\n\r\nTest hint(s): \r\nNone ",null,3828,14312351]
[null,null,"1494101","2022-06-23",null,"Development\\OWS7\\Technical improvements",null,null,null,"A warning was logged on CWSS Server startup when parameter AuthenticationLevel to initialize DCOM security was not passed on command line","A warning was logged on CWSS Server startup when parameter AuthenticationLevel to initialize DCOM security was not passed on command line.\n\nThis has been improved.\n\nThe warning is only shown when the parameter is passed and lower than the advised level 5 (since KB5004442 - Manage changes for Windows DCOM Server Security Feature Bypass (CVE-2021-26414) (microsoft.com) )\n\nTest hint(s): \n1. Verify that on startup of the CWSS Server no message is shown unless a low AuthenticationLevel is configured",null,3685]
[null,null,"1494101","2022-06-23",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Make 'Hide employees without a valid contract' a user setting","In the 'Employee management' form, there is a checkbox to 'Hide employees without a valid contract'. \nThe value of this checkbox is now remembered and stored as a user setting:\nOPTIONS/EMPLOYEE/HIDEEMPLOYEESWITHOUTVALIDCONTRACT with default value N.\n\n\nTest hint(s): \n1. Verify that the value of the checkbox is stored when closing and reopening the form.","For this solution to become available, the ORTEC WS Win32 client must be installed.",3730]
[null,null,"1494101","2022-06-23",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Several translations added for French","Several translations have been added for French for recent functional changes.  \r\n\r\n\r\nTest hint(s):  \r\nNone",null,3817]
[null,null,"1494101","2022-06-23",null,"Development\\OWS7\\Technical improvements",null,null,null,"Added new server role SkillDemandOptimization to force calculations of skill matching algorithm on specific worker","Added new server role SkillDemandOptimization to force calculations of skill matching algorithm on specific worker. \r\nTo enable, use the CPMS commandline parameter: Role=SkillDemandOptimization on the relevant CWSS process. \r\n\r\n\r\nNote: A server with the new role will not be available for imports, exports, or other functionalities (The only command handlers that will be available on this server are for analysis purposes) \r\n\r\n\r\nTest hint(s): \r\nVerify relevant changes trigger skill requirement updates ","To enable the skill matching algorithm, a dedicated server should be assigned a new role in CSCS -> CPMS process configuration -> CWSSServer commandline parameter: Role=SkillDemandOptimization\r\n\r\nWithout a dedicated server with this assigned role, skill requirement calculations will not be performed and the user might look at the wrong counters. In addition, event viewer errors will be generated for every pending calculation.\r\n\r\n\r\n\r\nThis new role replaces the OWS Settings Manager setting '\\options\\SkillMatching\\DedicatedServerNumber'. If it exists, this setting can be removed. ",3750]
[null,null,"1494101","2022-06-23",null,"Development\\OWS7\\Technical improvements",null,null,null,"Added the possibility for BackendAPI installation on other location than Default Web Site","The BackendAPI can now be installed in (or updated to) a different location than the standard Default Web Site. \r\nIn the InstallPortal.xml you can change the value of the tag <websitePath> to a desired location. \r\nE.g. <websitePath>D:\\Program Files(x86)\\ORTEC\\</websitePath> \r\nWhen the tag <websitePath> remains unchanged, the BackendAPI will still be installed under the Default Web Site. \r\n\r\n\r\nNotes:  \r\n- Please do not install in the <installDir>\\ORTEC\\Workforce Scheduling\\ folder!  \r\n  That can obstruct a correct execution of the PatchUtility.\r\n\r\n- Please do not make the <websitePath> longer than 255 characters.\r\n\r\n\r\n\r\nTest hint(s): \r\nNone ","When you move the BackendAPI from c:\\inetpub\\wwwroot to a different location, the previous installation files under c:\\inetpub\\wwwroot\\<websiteName> are not removed. \r\nRemoving these files is considered to be a one-time manual operation. ",3715]
[null,null,"1496687","2022-07-07",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Overview shift reassignments form did not show display characters of shift","A shift's display characters (* for shift remark, + for instructor shift, - for student shift) were no longer displayed in the overview shifts reassignments form.\nThis has been fixed.\nNote this issue was introduced in OWS7 Update 1300287 (2020-02-25) by OSDCOMMAIN-12748\n\nTest hint(s):\n1. Verify that a shifts display characters will be displayed as expected in the Overview shift reassignments form.","For this solution to become available, the ORTEC WS Win32 client must be installed.",3026,13634812]
[null,null,"1496687","2022-07-07",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Translation for Remaining Working Times scheduling criterion did not properly represent functionality","Translation for 'Remaining Working Times' scheduling criterion did not properly represent functionality.\nThe translation stated that it avoids a total working time deviating from the contract hours of an employee, while the criterion actually looks at the number of hours the employee is available for the department.\nThe translation has been fixed accordingly.\n\nTest hint(s):\n1. None","",3031]
[null,null,"1496687","2022-07-07",null,"Development\\OWS7",null,null,null,"Improved performance for self rostering","Some technical changes have been done to improve the performance of self rostering.\nThe changes are behind featuretoggle USEINDIVIDUALROSTERSFORSELFROSTERINGOPTIONS which is enabled by default.\n\nTest hint(s):\n1. Verify same options are retrieved in ORTEC for Employees when using self rostering","",3659]
[null,null,"1496687","2022-07-07",null,"Development\\OWS7\\Technical improvements",null,null,null,"A server halting sometimes did not stop if there were still running transactions or command handlers","A server halting sometimes did not stop if there were still running transactions or command handlers.\nThis has been improved.\nA new server setting GRACEFULSHUTDOWNTIMEOUTINSECONDS has been introduced, with default value 120. When shutting down, if there are still any running transactions or command handlers, the server will wait at most this number of seconds for these operations to finish.\nOnce that time has passed, the server will be stopped and the running operations aborted. Note that this is an ungraceful shutdown and will likely produce errors, but will prevent a possibly infinite loop where we wait for these operations to finish.\n\nTest hint(s):\n1. Confirm halted servers stop properly after GRACEFULSHUTDOWNTIMEOUTINSECONDS number of seconds has passed and do not stay in the halting state indefinitely","",3684,14221670]
[null,null,"1496687","2022-07-07",null,"Development\\OWS7\\Technical improvements",null,null,null,"Added monitoring functionality for skill matching algorithm","Added monitoring functionality for skill matching algorithm.\nThe runs of the skill matching algorithm are saved in a new table ROS_SKILL_DEMAND_OPTIMIZATION_RUNS. Cleaning is also implemented on this table.\nThe entries of the new table are sent to the monitoring database on a daily base.\n\nTest hint(s):\n1. Verify when skill demand functionality is enabled, runs are saved to the table ROS_SKILL_DEMAND_OPTIMIZATION_RUNS","",3736]
[null,null,"1496687","2022-07-07",null,"Development\\OWS7",null,null,null,"Monitoring query CheckServerUpdateBacklogInMinutes gave incorrect results","Monitoring query CheckServerUpdateBacklogInMinutes gave incorrect results. It has been fixed.\n\nTest hint(s):\n1. Verify that the monitoring query CheckServerUpdateBacklogInMinutes now provides the correct time for the entries in ROS_SERVER_UPDATES and ROS_QUEUE_UPDATES tables.","",3791,14304074]
[null,null,"1496687","2022-07-07",null,"Development\\OWS7",null,null,null,"Added stacktrace for exceptions in CWSS Server process logging","Added stacktrace logging for analysis purposes for certain exceptions in CWSS Server process.\nThis logging is behind a server setting LogExceptionStackTraceWhenStarted available in ORTEC WS Settings Manager and default set to true.\n\nIn addition it is possible to override this setting per CWSS Server process.\nThis can be done by adding LogExceptionStackTraceWhenStarted=True/False to the process commandline parameters configuration:\nCSCS > Configuration > Process Configuration > Processes > Select CWSS Server > Commandline parameters\n\nTest hint(s):\n1. None","",3798]
[null,null,"1496687","2022-07-07",null,"Development\\OWS7\\Technical improvements",null,null,null,"Creating a scenario triggered skill demand optimization","Creating a scenario triggered skill demand optimization.\nThis has been fixed.\nCreating a scenario will no longer trigger skill demand optimization. This will only be done in schedules with status plan or published.\n\nTest hint(s):\n1. Verify no skill demand optimization results are created or skill demand optimization runs are done when creating a scenario","",3910]
[null,null,"1498030","2022-07-14",null,"Development\\OWS7",null,null,null,"Processing the result of an external planner stopped on first imported shift that would cause overlap","Processing the result of an external planner stopped on first imported shift that would cause overlap.\r\nThis could occur when schedule data of borrowed employees changed while an external planner was calculating the schedule data.\r\nThis could cause overlap in at least one of the shifts while processing the external planner result. This would lead cancellation of the import of that external planner result.\r\nThis has been improved.\r\nWhen in OWS Settings Manager the new setting PLANNER\\IGNOREOVERLAPONSHIFTIMPORTFROMEXTERNALPLANNER is set to TRUE (default is FALSE)\r\nprocessing the shift data from an external planner will ignore any overlap that would occur on fixed shifts due to changes while the external planner was running.\r\nA shift that would cause overlap with a fixed shift will not be planned at the target employee but will be moved to the vacant shifts\r\nNote that when an imported shift that overlaps with a non-fixed shift, the imported shift will replace the existing non-fixed shift.\r\n\r\nTest hint(s)\r\n1.  verify that running the external planner will show the results in the schedule the planner was run for.","",3033]
[null,null,"1498030","2022-07-14",null,"Development\\OWS7\\OWS for Managers",null,null,null,"WS for Managers did not show partly published/planned schedules on the Approval page","WS for Managers did not show partly published schedules (Published..Plan) on the Approval page.\r\nPending realizations in the published part of such a schedule could therefor not be approved. This has been fixed.\r\n\r\nTest hint(s):\r\n1. Verify that a partly published/plan schedule is now shown on the approval page.\r\n2. Verify that pending realizations in such a schedule can be approved.","",3034]
[null,null,"1498030","2022-07-14",null,"Development\\OWSforTeamSchedulers",null,null,null,"Create new Database table TEAMSCHEDULING_ROLL_OUT_SCHEDULE_PROGRESS","Feature for Team Scheduling: Added database table TEAMSCHEDULING_ROLL_OUT_SCHEDULE_PROGRESS","",3706]
[null,null,"1498030","2022-07-14",null,"Development\\OWS7",null,null,null,"RestPerNumberOfHoursLaborPeriodReq caused incorrect violations","RestPerNumberOfHoursLaborPeriodReq caused incorrect violations. This has been fixed.\nPlease note that, previously, this rule considered the rest time between shifts/activities within a labor period as the rest time for this rule. This is no longer the case. This rule now only considers rest time outside labor periods.\n\nTest hint(s):\nVerify that correct violations are created for this rule for shifts with multiple activities.","",3723]
[null,null,"1498030","2022-07-14",null,"Development\\OWS7",null,null,null,"ORTEC WS Win32 Client could make full use of a CPU after closing when errors occurred","ORTEC WS Win32 Client could still make full use of a CPU core after closing when errors occurred    This has been improved.In some cases where the client is closed after an access violation or invalid pointer error, the application is forcefully terminated\r\n\r\nTest hint(s):\r\n1. Verify after working with ORTEC WS win32 client closing the application can be closed succesfully.","For this solution to become available, the ORTEC WS Win32 client must be installed.",3915,14297833]
[null,null,"1498030","2022-07-14",null,"Development\\OWS7",null,null,null,"Several translations have been added for German","Several translations have been added for German.\r\n\r\nTest hint(s):\r\nNone","",4080,14361878]
[null,null,"1498030","2022-07-14",null,"Development\\OWS7\\OWS for Employees",null,null,null,"Improved WS for Employees query performance for TeamSchedule and Workstation Assignment","Improved the performance of the BackendAPI query that retrieves shifts with a general absencename.\nThis query is used in WS for Employees' Team Schedule and Workstation Assignment forms.\n\nTest hint(s):\nVerify that 'the team schedule' and 'workstation assignment' forms return the expected shifts","",4135,14409198]
[null,null,"1500449","2022-07-29",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Value stored for 'Use proposal departments' could cause an error when no proposal departments existed","Value stored for 'Use proposal departments' could cause an error when no proposal departments existed for that department.\nThis has been fixed.\n\nTest hint(s):\n- Verify the 'use proposal departments' functionality does not raise an error.","",3024,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWS7\\Interfacing",null,null,null,"All employees were locked when exporting data through a Queue Export","All employees were locked when exporting data through a Queue Export\nThis has been improved.\nWhen locks are set for the queue export the data to export is used to determine the employees that need to be locked.\nThis should reduce the number of locks taken for certain Queue exports which should improve concurrency and performance to some extent.\nThis functionality was implemented behind feature toggle UseTransactionDataForEmployeeLocksInQueueExport and turned on by default.\nA setting with the same name (UseTransactionDataForEmployeeLocksInQueueExport ) can be added to a queue export definition such that it can be disabled per queue export if required.\n\nTest hint(s)\n- Verify that queue exports work as expected","",3029,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS Team Schedulers: New GetProgress endpoint","Feature for Team Scheduling: Added new GET route to get the progress of the rollout of a schedule or demands.","",3704,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS Team Schedulers: Apply roll-out request","Feature for Team Scheduling: Added new POST route to apply a request to roll out a schedule or demands.","",3705,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS Team Schedulers:  Command handler: Roll out in new thread.","Feature for Team Scheduling: Added command handler teamscheduling/CRollout to handle rollout requests by Team Scheduling.","",3707,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"No CRunExternalPlanner commandhandler available on interfaceworkers  ","The optimizer did not work in case the CSCS setting Workforce.BackendDomainsApis\\CWSS\\ServerNumber was set to an interfaceworker number.\nThis has been fixed.\n\nTest hint(s):\n- Use an interface worker to process requests from the BackendDomainsApi. Verify that the optimizer runs.","",3784,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWS7\\Technical improvements",null,null,null,"Chromium component has been upgraded","Chromium component has been upgraded. This upgrade is done behind feature toggle, 'UseNewChromiumComponent'. The feature toggle has the default value 'Y' (True).\n\nTest hint(s):\n- None","For this solution to become available, the ORTEC WS Win32 client must be installed.",3897,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS Team Schedulers:  Add remark to roll out schedule progress table","Feature for Team Scheduling: Added column REMARK to database table TEAMSCHEDULING_ROLL_OUT_SCHEDULE_PROGRESS.","",4037,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"Update packages BDA vulnerabilities","There were possible vulnerabilities in the Backend Domains API. These have been solved now.","",4057,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS Team Schedulers:  Support the roll out of multiple cyclical schedules","Feature for Team Scheduling: Added support to roll out multiple cyclical schedules by Team Scheduling.","",4061,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Minimum ATW rest to end shift series has been made configurable for some requirements","For a number of labor rules, it has been made configurable when a shift series ends. Previously it was fixed at 32 hours of rest, which meant that after 32 hours of rest the shift series would end by default.\nWith this change, a new setting has been introduced called 'MinimumATWRestToEndShiftSeriesInHours' which is available in ORTEC WS Settings Manager in the Server/Requirements path.\nThe new setting has a default value of 32 such that no existing functionalities are impacted. It has a minimum value of 1 and maximum value of 168. The labor rules that will use this setting during calculation are:\n Number of night shift series Early shift after night shift  Shift series Night shift series Semi night shift series Rest after night shift series Rest after shift series  Rest day after night shift series  \nPlease note that while the labor rule 'Shift Series' will use this new setting, the labor rule 'Shift Series (Labour Period)' will continue to use a fixed 32 hours. This is because it is using a different method for handling series.\n\nTest hint(s):\n- Verify that the setting, MinimumATWRestToEndShiftSeriesInHours exists in OWS Settings Manager in the Server/Requirements path. Verify the setting has a default value of 32. Verify the configured value of the setting is used in the calculations of the labor rule mentioned above.","",4270,""]
[null,null,"1500449","2022-07-29",null,"Development\\OWS7\\Technical improvements",null,null,null,"By default enabled LogExceptionStackTraceWhenStarted setting could cause instability for CWSS Server processes","By default enabled LogExceptionStackTraceWhenStarted setting could cause instability for CWSS Server processes\nThe LogExceptionStackTraceWhenStarted setting was introduced in OWS7 8.5.0(2022-07-07)_Build1496687 and was enabled by default. \nThis has been changed.\n The LogExceptionStackTraceWhenStarted setting is now by default set to false.\nAn update script was provided that updates existing setting in OWS Settings Manager.\n\nLogExceptionStackTraceWhenStarted can still used be used as a command line parameter to override the setting LogExceptionStackTraceWhenStarted  in OWS Settings Manager.\nIf any issues arise when LogExceptionStackTraceWhenStarted is enabled as setting or command line parameter for a CWSS Server process in the process configuration in CSCS it is advised to \n- disable the setting in OWS Settings manager.\n- disable or remove the setting from the command line for the CWSS Server process(es).\n\nTest hint(s):\n- none.","",4470,"144408611"]
[null,null,"1500449","2022-07-29",null,"Development\\OWS7\\OWS for Employees",null,null,null,"ORTEC ESS Mobile App: Shift picking could give message that something went wrong on server","ORTEC ESS Mobile App: Shift picking could give message that something went wrong on server\nIn the event log the error \"System.IndexOutOfRangeException\" and message \"absence_treatment_count\" were mentioned.Same was found to occur for retrieving information for swapping shifts.\nThis was introduced in issue 3561 \"ORTEC ESS Mobile App: Detailed information on absence was shown\" released in OWS7 8.5.0(2022-05-31)_Build1489738\nThis has been improved.\n\nTest hint(s):\n- Verify that schedule information is displayed correctly in ORTEC ESS Mobile App\n - Verify that shift open for bidding are displayed correctly in ORTEC ESS Mobile App- Verify that shift information on swapping shifts is displayed correctly in ORTEC ESS Mobile App","",4487,"14.444.436"]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7\\MS Reporting",null,null,null,"Improved grouping of shifts for report 'Attendance list per department'","In the 'Attendance list per department' report the grouping of shifts could be unclear for realizations.\r\nThis has been improved.\r\nWhen grouping shifts the activity name is now included, next to shift begin/end time.\r\n\r\nTest hint(s)\r\nVerify the 'Attendance list per department' report shows the expected data.","","3023",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7\\BI support",null,null,null,"BI - HDM Property views only showed the latest revision of departments of employees","BI - HDM Property views only showed the latest revision of departments of employees.\nThis has been fixed,\n\nTest hint(s):\nVerify that correct department and employees are shown in FACT_NL_Medewerker_Kenmerk, FACT_NL_Roostergroep_Kenmerk, FACT_US_Employee_Property and FACT_US_Department_Property tables.","","3025",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7\\MS Reporting",null,null,null,"When minimizing a report window, it was possible that the OWS client session could become unusable","When minimizing a report window, it was possible that the OWS client session could become unusable\r\nThis has been improved.\r\nThe workaround was to adjust the setting 'MULTIPLEREPORTS' to True. The default value for new users for the setting 'MULTIPLEREPORTS' has been changed to True.\r\n\r\nTest hint(s):\r\nNone","For this solution to become available, the ORTEC WS Win32 client must be installed.","3030",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7\\MS Reporting",null,null,null,"Some parameters in the report 'Overview shifts' were not filled in by default","Some parameters in the report 'Overview shifts' were not filled in by default. To be specific, the parameters 'Show employee as' and 'Show duty color'.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nOpen report 'overview shifts' \r\n Verify all parameters have a default value","","3032","13.732.719"]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7",null,null,null,"Added a new monitoring query, CheckServerUpdateBacklogCount","Added a new monitoring query, CheckServerUpdateBacklogCount. This query returns the number of records in ROS_SERVER_UPDATES, ROS_QUEUE_UPDATES and ROS_SKILL_MATCHING_UPDATES\r\ntables.\r\n\r\nTest hint(s):\r\nVerify the monitoring query, CheckServerUpdateBacklogCount returns the correct number of records in ROS_SERVER_UPDATES, ROS_QUEUE_UPDATES and ROS_SKILL_MATCHING_UPDATES\r\ntables.","","3035",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7",null,null,null,"Too many shifts were loaded during central department rotation unit lines conversion","Too many shifts were loaded during central department rotation unit lines conversion. This has been improved.\r\n\r\nTest hint(s):\r\nVerify that  central department rotation unit lines conversion runs during server startup. Please note that, central department rotation unit lines conversion needs to be done once. If the conversion has already occurred, nothing else needs to be done.","","3036",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Employees could be borrowed and shifts could be subcontracted without permission through shift proposal window in ORTEC WS Win32 client","Employees could be borrowed and shifts could be subcontracted without permission through shift proposal window in ORTEC WS Win32 client. This has been fixed.\r\nNow the permissions are checked: EMPLOYEE_TRANSFER_IN , SHIFT_SUBCONTRACT_TO, SHIFT_SUBCONTR_PLANCONCEPT\r\nand SHIFT_SUBCONTR_PLANFINAL.\r\n\r\nTest hint(s):\r\nVerify that when a user does not have permission, cannot borrow employee or subcontract shifts using the shift proposal window.","For this solution to become available, the ORTEC WS Win32 client must be upgraded.","3037",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7\\Workstation planning",null,null,null,"Manually increasing the demand of a workstation on a specific date did not work for night shifts","Manually increasing the demand of a workstation on a specific date did not work for night shifts.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nCreate a workstation demand from 22:00 to 06:00 on every day of the week Manually increase it on any day through the workstation planning Verify the correct demand is updated","","3038","13.887.977"]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7",null,null,null,"Shifts with status plan were visible in ESS7 app","Shifts with status plan were visible in the ESS7 App in case part of the schedule was published and the employee did not have the permission to view planned shifts.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nVerify that shifts with status plan are not visible in ESS7 App when the employee does not have permissions for viewing planned shifts (self scheduling excluded).","","3105",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWSforManagers",null,null,null,"The Insights section in WS For managers will only show account entries booked on the requested department(s).","The MSS Insights section shows its values (account entries) differently than before. \n \nPreviously, the Insights section showed all account entries for the employees assigned to the requested department(s). In case employees were working for multiple departments, account entries of the other departments were also shown. This made it hard for a manager to evaluate the 'performance' of their department(s). In addition, it led to some inconsistencies in the different detail levels. \n \nThis has been improved. Now, the Insights section only shows account entries booked on the requested department(s). In addition, it will also show account entries of other departments for the period an employee was lent out to that department from the requested department(s). This is to support a Flexpool-like case for which its employees only work for other departments. \n \nFor now, the inclusion of these entries is default behavior but will be made into a user setting in an upcoming MSS front-end change.","","4035",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Viewing old clockings in ORTEC WS Win32 client has been made dependent on an Access Control permission and a server setting","Viewing old clockings in ORTEC WS Win32 client has been made dependent on an Access Control permission and a server setting for performance improvement.\r\nWith this change, users with the newly created Access Control permission, VIEW_OLD_CLOCKINGS granted are allowed to view any clocking, irrespective of how old the clocking is.\r\nWhen the permission VIEW_OLD_CLOCKINGS is not granted, the user is only allowed to view clockings based on a newly created server setting, MAXNOFDAYSINPASTTOOPENCLOCKINGOVERVIEW.\r\nThe user is then not allowed to view any clocking, whose begin date is older than MAXNOFDAYSINPASTTOOPENCLOCKINGOVERVIEW days from the current date.\r\nThe default value of MAXNOFDAYSINPASTTOOPENCLOCKINGOVERVIEW is set to 365. This setting has been created in OWSSettingsManager/Users = Server/Clocking.\r\n\r\nTest hint(s):\r\nVerify that there exists a permission, VIEW_OLD_CLOCKINGS in Access Control and a server setting MAXNOFDAYSINPASTTOOPENCLOCKINGOVERVIEW in OWSSettingsManager/Users = Server/Clocking. Verify that when the permission VIEW_OLD_CLOCKINGS is granted, the user is allowed to view any clocking. Verify that when the permission VIEW_OLD_CLOCKINGS is not granted, the user is only allowed to view clockings not older than MAXNOFDAYSINPASTTOOPENCLOCKINGOVERVIEW.","For this solution to become available, the ORTEC WS Win32 client must be upgraded.","4457",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7",null,null,null,"Shift options could not be retrieved for self-rostering when there was a subcontracted shift in the schedule and feature toggle USEINDIVIDUALROSTERSFORSELFROSTERINGOPTIONS was true","Shift options could not be retrieved for self-rostering when there was a subcontracted shift in the schedule and feature toggle USEINDIVIDUALROSTERSFORSELFROSTERINGOPTIONS was true. This has been fixed.\r\n\r\nTest hint(s): Verify that shift options can be retrieved for self-rostering","","4557",""]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7",null,null,null,"Several OWS Backend translations added for German","Several translations have been added for German.\r\n\r\nTest hint(s):\r\nNone","","4588","14.513.151"]
[null,null,1504019,"2022-08-25",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Several translations added for German","Several translations have been added for German.\r\n\r\nTest hint(s):\r\nNone","","4598",""]
[null,null,1505668,"2022-09-02",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Deleting grouped correction bookings was possible on an account with only READ permissions","It was possible to delete running account correction lines without write permissions. \r\nIn case a grouping was applied in the form, one could select the group category and the delete button would be visible when one of the bookings was not approved. \r\nThis has been fixed. \r\nIn case one does not have write permissions on the running account, the delete button will always be disabled.\r\n\r\nTest hint(s): \r\n1. Verify that no running account bookings can be deleted when only read permissions have been granted.","For this solution to become available, the ORTEC WS Win32 client must be installed","3810","14311408"]
[null,null,1505668,"2022-09-02",null,"Development\\OWSforAdHocPlanners",null,null,null,"ShiftOffering - Prevent unexpected copies of shifts","A shift that was offered and after that picked by an employee very fast, could be copied to the vacant shifts sometimes.  \r\nThis has been fixed.\r\n\r\nTest hint(s):\r\n- Open a shift for bidding in OWS Client \r\n- Pick the shift using Employee Self Service, or assign it using OWS Client \r\n- Verify that no copy is made of the shift","","4283",""]
[null,null,1505668,"2022-09-02",null,"Development\\OWS7",null,null,null,"The 'code' field of a physical location in ORTEC WS Win32 client was limited to 20 characters","The 'code' field of a physical location in ORTEC WS Win32 Client was limited to 20 characters.  \r\nIt has now been extended to 200 characters to be consistent with imported physical location and database model.\r\n\r\nTest hint(s): \r\n1. Verify that a new physical location can be created in ORTEC WS Win32 Client with the 'code' field having a length of up to 200 characters.","For this solution to become available, the ORTEC WS Win32 client must be installed.","4373","14.430.153"]
[null,null,1505668,"2022-09-02",null,"Development\\OWS7 ",null,null,null,"Added a consistency check that verifies the duration of activities: the duration should be smaller than or equal to 24 hours  ","Added a consistency check that verifies the duration of activities: the duration should be smaller than or equal to 24 hours\nThe added consistency check prohibits entering activities with a duration larger than 24 hours.\n\nThe functionality of the consistency check is implemented behind OWS Setting: CONSISTENCYCHECKS\\ACTIVITYDURATIONCHECK\\ENABLED.\nA script has been added such that the consistency check is turned on by default only for customers that do not have any activities with a duration larger than 24 hours.\n\nA monitoring queries about to collect information on activities and their durations and the configured consistency checks used:\nSystemMonitoring/CMHS/Weekly/DataAmounts/CountActivitiesPerDurationCategory  \nSystemMonitoring/CMHS/Daily/Settings/ConsistencyChecks\n\nNOTE: When running a dbupdate the following warning already was shown when any activity existed that is longer than 24 hours:\n'The database contains activities with a duration longer than 24 hours. This is not supported by the (labor) rules.'\nThis warning means that to avoid possible issues those activities should be examined and fixed, to avoid issues in (labor) rules.\n\nTest hint(s): \n1. Verify that realizations in OWS client can be entered","","4952","14543452"]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7",null,null,null,"Warning on more than 100.000 cost centers was written every few seconds","In case of more than 100.000 cost centers, a warning was written in the logging and in the event viewer every few seconds, i.e. when importing cost center. This flooded the logging and event viewer.\r\nThis has been improved.\r\nNow the check for 'more than 100.000 cost centers' is in a DBUpdate script. The warnings in the logging and event viewer will no longer be written.\r\n\r\nTest hint(s):\r\nVerify DBUpdate runs correctly","",3099]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7\\OWS for Employees",null,null,null,"Creating a realization on a shift causes more schedule changes than necessary in ORTEC WS for Employees ","Creating a realization on a shift caused more schedule changes than necessary in ORTEC WS for Employees.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nVerify that when a realization is created for a shift in ORTEC WS Win32 client, only 1 schedule change is shown in ORTEC WS for Employees","",3522]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7",null,null,null,"Unused swap request permissions removed from \"ORTEC WS for Employees\" category in Access Control","Unused swap request permissions are removed from \"ORTEC WS for Employees\" category in Access Control. The following permissions were removed:\r\nAcceptExchangeRequestAction\r\nCancelExchangeRequestAction\r\nCreateExchangeRequest\r\nDeclineExchangeRequestAction \r\nPlease note that these permissions still exist in \"Employee Self Service (deprecated)\" category in Access Control.\r\n\r\nTest hint(s):\r\nVerify the permissions do not exist in \"ORTEC WS for Employees\" category in Access Control. Verify the permissions exist in \"Employee Self Service (deprecated)\" category in Access Control.","",4963]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7",null,null,null,"Http status code changed from 500 to 400 in Back-end API routes when certain exceptions occur in OWS Back-end ","There was no difference in the HTTP status code between different exceptions that could occur when OWS Back-end API communicates with a CWSS Server or Interface worker via command handlers. For all exceptions a HTTP status code 500 was returned.This has been improved.For non-system and non-retriable exceptions a HTTP status code 400 will be returned. For all other exceptions the HTTP status code 500 will still be returned.\r\n\r\nTest hint(s):\r\nNone","",4964]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7",null,null,null,"Several translations added for German","Several translations have been added for German for recent functional changes.\r\n\r\nTest hint(s):  None","",5094,14579882]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7",null,null,null,"Turn on feature toggle AlwaysQueryTransactionDataObject by default","The setting: FEATURETOGGLES\\ALWAYSQUERYTRANSACTIONDATAOBJECT is now by default enabled (introduced in OSDCOMMAIN-11459) \r\nIn Release OWS 7 8.5.0(2022-01-20)_Build1464524 in OSDCOMMAIN-13811 we added additional logging behind this feature toggle.\r\n\r\nTest hint(s):\r\n- verify queue exports succeed as expected","",5102]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Several translations added for Danish and Finnish","Several translations have been added for Danish and Finnish for recent functional changes.\r\n\r\nTest hint(s):  None","",5140]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7",null,null,null,"Added resource name and employee number on failed employee import interface messages","A failed interface message did not show the employee name and employee number when an employment terms group code was imported using an unexpected but allowed xml structure.\r\nThis has been fixed.\r\nIn general we will now always try to show resource name and employee number in the messages form during failures on importing any subfield in an employee import.\r\n\r\nTest hint(s):\r\n1. Verify that a failed employee import now shows the employee name and number in a failed interface message\r\n2. Verify that an employee can be imported.","",5216]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7",null,null,null,"A 'fixed' vacant shift caused an error when the schedule optimizer was run with feature toggle 'USEDAYSHIFTPLANNER' on","A 'fixed' vacant shift caused an error when the schedule optimizer was run with feature toggle 'USEDAYSHIFTPLANNER' on.\r\nThis has been fixed.\r\nThe issue was introduced with the update  8.5.0(2022-06-09)_Build1491589.\r\n\r\nTest hint(s):\r\nVerify that the schedule optimizer can be run without error when there are fixed vacant shifts in a schedule.","",5273,14622486]
[null,null,1507552,"2022-09-16",null,"Development\\OWS7",null,null,null," Set Feature toggle USEDAYSHIFTPLANNER by default False","The setting: FEATURETOGGLES\\USEDAYSHIFTPLANNER is now by default disabled (introduced in DEVELOPMENT-3367)\nWe have received information that the optimizer does not always respect created violations correct during optimization when the feature toggle is turned on.\nThis functionality will be disabled by default until further notice.\n\nTest hint(s):\nNone","",5290]
[null,null,1510266,"2022-10-03",null,"Development\\OWS7\\Interfacing",null,null,null,"Added employee name and number to interface message in IdentifyCOMTECShift ExtraXMLCreator","When a shift realization import check in the 'IdentifyCOMTECShift' ExtraXMLCreator failed due to the current shift status being higher than published, the employee name and number were not added to the failed interface message.\r\nThis has been fixed.\r\n\r\nTest hint(s)\r\n1. Verify that a failed interface message on shift status errors on importing shift realizations display employee name and employee number when 'IdentifyCOMTECShift' ExtraXMLCreator is used.",null,3107,14074895]
[null,null,1510266,"2022-10-03",null,"Development\\OWS7\\Workstation planning",null,null,null,"When entering a realization, changing a workstation to (None), but using the same address did not save it","When entering a realization, changing a workstation to (None), but using the same address did not save it.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nCreate a shift with a workstation and address that belongs to the workstation Enter a realization where you remove the workstation but add the same address back Verify the realization still has the correct address",null,3790,14304063]
[null,null,1510266,"2022-10-03",null,"Development\\OWS7",null,null,null,"Shift remarks changed when replacing a duty","Shift remarks changed when replacing a duty. Note that for this bug to occur featuretoggle CREATEDUTYFROMEXISTINGDUTYINDUTYSETFORM had to be true. Furthermore replacing refers to the 'replace' button in the dutyset duty window in ORTEC WS Win32 client.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nTurn on feature toggle CREATEDUTYFROMEXISTINGDUTYINDUTYSETFORM\r\n Create a duty set duty A with a description and a shift with that duty\r\n Replace the duty in the duty set form Verify remark on the shift is still empty",null,4376]
[null,null,1510266,"2022-10-03",null,"Development\\OWS7\\Basic functionalities",null,null,null,"ORTEC Identity Gateway support has been removed from ORTEC Workforce product","ORTEC Identity Gateway support as OIDC (OpenID Connect) provider has been removed from ORTEC Workforce product\r\n\r\nTest hint(s):\r\n1. Verify ORTEC WS for Employees and/or ORTEC WS for Managers can still be accessed","This update immediately affects access to ORTEC WS for Employees, ORTEC WS for Managers, Firebase Mobile API  (for notifications OWS Mobile App) for customers that have the ORTEC Identity Gateway as provider and resource provider in the OIDC configuration:\r\nThey should have moved to a different supported provider before using this update!\r\nSupported provider types: Active Directory Federated Services, AzureAD or any other supported custom OIDC provider.",5032]
[null,null,1510266,"2022-10-03",null,"Development\\OWS7",null,null,null,"Added a retry mechanism in Back-end API for setting retrieval in case of a SQL deadlock","SQL deadlock could cause Back-end API to not start.\r\nThis has been improved.\r\nA retry mechanism has been added in Back-end API for setting retrieval in case of a SQL deadlock\r\n\r\nTest hint(s):\r\nNone",null,5201,14618115]
[null,null,1510266,"2022-10-03",null,"Development\\OWS7",null,null,null," Shift counters per shift only showed one shift when multiple shifts had the same name","Shift counters per shift only showed one shift when multiple shifts had the same name.\r\nThe issue was introduced in OSDCOMMAIN-13773 / 8.5.0(2021-12-16)_Build1457935.\r\nThis has been fixed.\r\nNow the shifts with the same name but different demands are shown separately.\r\n\r\nTest hint(s):\r\nSet up a shift counter to use faction shifts Create multiple shifts with the same name All shifts should be visible in the shift counter",null,5202,14558891]
[null,null,1510266,"2022-10-03",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Create weekly monitoring query to count all cost centers","Added a monitoring query CountCostCenters in order to weekly track the number of cost centers in the database.\r\n\r\nTest hint(s):\r\nVerify uploading queries in CSCS goes ok",null,5226,13626576]
[null,null,1510266,"2022-10-03",null,"Development\\OWSforTeamSchedulers",null,null,null,"The duration of an optimizer should be limited to e.g. 24 hours","The maximum duration of an optimization run is set to 24 hours",null,5289]
[null,null,1510266,"2022-10-03",null,"Development\\OWS7",null,null,null,"Plan board component 'Shift counters' checked a setting too much which could cause performance decline","Plan board component 'Shift counters' checked a setting too much which could cause performance decline.\r\n\r\nThe performance could decline when using a high number of plan boards. \r\nThis was introduced in 8.5.0(2022-03-25)_Build1477295.\r\nThis has been improved.\r\nNow the setting is only checked once for a 'Shift counters' plan board component when doing a (full) refresh of a plan board.\r\n\r\nTest hint(s):\r\nVerify that a configured 'Shift counters' plan board component shows the expected values in OWS Win32 Client","For this change to become available, the OWS Win32\r\nclient needs to be updated.",5467,14655396]
[null,null,1510266,"2022-10-03",null,"Development\\OWSforTeamSchedulers",null,null,null,"Account entries were missing inORTEC WS for EmployeesESS accounts in case department has no schedule","Earlier this year (in OWS7 1485063 and higher) a change was done to the way account entries were retrieved for ORTEC WS for Employees. \r\nThis change made it easier and more robust to determine if an employee is allowed to see account entries based on status Plan or Published.\r\nInstead of only the frontend determining what the cutoff dates are to retrieve published account entries, the backend also does an (extra) check.\r\nThis improved situations of employees working for multiple departments having different published until dates.\r\n\r\n\r\nHowever, account entries belonging to a department that had no schedule on the day of the entry were not shown in case the employee is not allowed to see entries in status Plan.\r\nThis resulted in entries not being visible anymore for (old) departments that stopped scheduling. This was not desired.\r\nNow these entries are shown in case the last schedule of that department is in status Published or higher.\r\nWe also introduced a feature toggle FilterAccountEntriesInStatusPlanForESSHandler with default value \"Y\". \r\nSetting this to \"N\" (not recommended, especially not with the ESS7 app) the behaviour is the same as before update 1485063.",null,5485]
[null,null,1511266,"2022-10-06",null,"Development\\OWS7\\BI support",null,null,null,"Added option to start BI runs with a triggerfile on a fileshare","An option was added to trigger a BI run in case a consultant does not have access to the database server.\nAn empty 'start.txt' file can be placed in a shared folder on the database server. A frequently scheduled task will detect this file and trigger a BI run.\nA default daily BI run time can also be scheduled. In case a BI run was not manually triggered in the last 24 hours, BI will start on that time.\nIMPORTANT NOTE: It is advised to only set this up for Incremental Loads. An accidentally triggered Historical Load on an environment where Incremental Loads have been run will cause a corrupted BI database!\n\nNote that the date notation for the BI logfile has been changed for more consistency across our products.\nThe date notation has been changed from day_%d-MM-yyyy_%H-%m-ss (e.g. mon_1-8-2022_9-9-32) to yyyy-MM-dd_HH-mm-ss (e.g. 2022-08-01_mon_09-09-32)\n\nTest hint(s): \n1. Verify that BI still runs when this new functionality is not used \n2. Verify the trigger mechanism triggers BI when configured","If this new trigger mechanism is not to be used, no action is required. You can leave the current config and tasks the way they are. \r\nTo enable the new trigger mechanism:\r\n1. The file 'BI_With_Manual_Trigger.ps1' needs to be added to the commands folder (next to BI.ps1 and BI_CONFIG_xxx.ps1)\r\n2. Three new variables in the BI_CONFIG file need to be used\r\n   - $ManualTriggerPath = '#TriggerFile_Path#', The path / fileshare where trigger files will be placed\r\n   - $RuntimeWithoutTrigger = '02:00', The time a BI run will be started on a daily basis (when BI has not started for 24 hours)\r\n    - $BIPowershellPath = '#BI_CommandsPath#\\BI.ps1', The location of the BI.ps1 file\r\n3. Adjust the BI_IL task in the Windows Task Scheduler\r\n   - Call: D:\\<Path>\\BI_With_Manual_Trigger.ps1 'D:\\<Path>\\BI_CONFIG_xxx.ps1'  instead of D:\\<Path>\\BI.ps1 'D:\\<Path>\\BI_CONFIG_xxx.ps1'\r\n   - Adjust the trigger of the task run run more frequent. E.g. every 10 minutes\r\n4. Create an empty 'start.txt' file in the shared folder ('#TriggerFile_Path#) and The Bi run should start at the time the scheduled task is scheduled",3021,"14026327"]
[null,null,1511266,"2022-10-06",null,"Development\\OWS7",null,null,null,"Upgraded to Microsoft .NET Framework 4.8 and enabled support for TLS 1.2","This update includes an upgrade of OWS binaries to support Microsoft .NET Framework 4.8  (https://support.microsoft.com/en-us/topic/microsoft-net-framework-4-8-offline-installer-for-windows-9d23f658-3b97-68ab-d013-aa3c3e7495e0). \n\nVersion 4.8 is the last or 'completed' version of the framework and follows the Lifecycle Policy of the parent OS. The framework will continue to be serviced with monthly security and reliability bug fixes. Additionally, it will continue to be included with Windows, with no plans to remove it. \nMicrosoft recommends customers to use .NET Framework 4.8 to receive the highest level of performance, reliability and security.     \n\nOne of the main reasons to upgrade to .NET Framework 4.8 was to better support TLS 1.2 and future TLS changes in all components of ORTEC Workforce Scheduling. TLS (Transport Layer Security) is responsible for preventing eavesdroppers, hackers and other cyber criminals from accessing sensitive data as it moves through the internet, using cryptography protocols. Version 1.2 is currently the agreed upon standard regarding encryption of internet connections. \nAs of this upgrade, ORTEC Workforce Scheduling supports TLS 1.2.\n\nTest hint(s):\nMake sure .NET Framework 4.8 is installed Verify ORTEC Workforce Scheduling CPMS processes can start","To run ORTEC Workforce Scheduling after this update, .NET Framework 4.8 is added as a system requirement. \nThe .NET Framework 4.8 is automatically included and installed from Windows 10 May 2019 update and Windows Server 2022 onward, older versions will have to manually install it. For more information on installing it, see https://learn.microsoft.com/en-us/dotnet/framework/install/on-windows-10.      \n\nTo determine whether .NET 4.8 is already installed use the following Windows Powershell command:     # Returns 'True' if .NET4.8 is installed   \n (Get-ItemProperty \"HKLM:\\SOFTWARE\\Microsoft\\NET Framework Setup\\NDP\\v4\\Full\").Release -ge 528040   \n\nIf UnattendedUpdates is used, .NET Framework 4.8 will be automatically installed. See release note of issue 5383 for more details.  \n\nIt is not necessary to update the ORTEC Workforce Scheduling Win32 client for this update, it is not affected by this upgrade. \nPlease note that when the Win32 client is updated, .NET 4.8 also needs to be installed on Client machines. \n \nWe have updated the ORTEC Reporting Services Extensions to support TLS 1.2. To have these changes it is necessary to use the installer to install them.",3097,""]
[null,null,1511266,"2022-10-06",null,"Development\\OWS7\\Interfacing",null,null,null,"Added employee name and number to interface message in IdentifyCOMTECShift ExtraXMLCreator - Part 2","A shift realization import check in the 'IdentifyCOMTECShift' ExtraXMLCreator did not provide the employee name and number in case: - The current department status being higher than published. - A shift in another department could not be removed due to it being fixed (When importing without a dpt_code, OWS determines the main department of the employee. If an existing shift was planned in another department, this shift will be removed. If that shift was fixed an error is raised).  These have been fixed.\n\nTest hint(s):\n1. Verify that a failed interface message on department status errors on importing shift realizations displays employee name and employee number when 'IdentifyCOMTECShift' ExtraXMLCreator is used. \n2. Verify that a failed interface message on not being able to delete a fixed shift displays the employee name and employee number when 'IdentifyCOMTECShift' ExtraXMLCreator is used.","",4489,"14.444.451"]
[null,null,1511266,"2022-10-06",null,"Development\\OWS7",null,null,null,"Several translations changed for German","Some German translations have been changed.\r\n\r\nTest hint(s):\r\nNone","",5623,"14696817"]
[null,null,1511266,"2022-10-06",null,"Development\\OWS7",null,null,null,"Install .NET 4.8 in UnattendedUpdates","Due to a .NET 4.8 upgrade for ORTEC Workforce Scheduling, UnattendedUpdates will check whether .NET4.8 is installed and install it if necessary.\n\nThis will be performed on the following servers configured in the UnattendedUpdates config file:\n- Main application server\n- Role servers\n- Terminal Servers\n\nPlease note that installing .NET 4.8 requires Windows to be restarted.","The installation of .NET 4.8 requires a reboot of Windows on all relevant servers.\n\nUnattendedUpdates can restart the concerning Windows machines automatically when <scriptMayRestartWindows> is set to Y in the UnattendedUpdates config file.\nWhen <scriptMayRestartWindows> is set to N, the script will raise a warning that all servers needs to be restarted manually in the final confirmation email\n\nNote the Windows restart is a mandatory step and not all CPMS processes will start when the .NET update has not been fully applied!",5383]
[null,null,1512223,"2022-10-14",null,"Development\\OWS7",null,null,null,"Some stylesheets delivered with ORTEC Workforce Scheduling still used outdated Microsoft XML Parser version 4","Some stylesheets delivered with ORTEC Workforce Scheduling still used outdated Microsoft XML Parser version 4.\r\nThis has been improved.\r\nIt now uses the most current version, Microsoft XML Parser version 6.\r\n\r\nTest hint(s):\r\nVerify interface library stylesheets are still working","We updated library functions wherever needed. We did not upgrade interfaces maintained by the business, these probably need changes as well if the customer wants to be totally MSXML 4.0 free. To upgrade these business interfaces, please replace the following function calls with calls to one from our library:\r\nms:format-date\r\n\r\nms:format-time\r\nPlease copy these library files to your stylesheet location since we have added/updated them:\r\ndate.format-date.template.xsl\r\ndate.functions.xsl\r\n\r\nstr.padding.template.xsl\r\n\r\nXML2Text.xsl\r\nXML2TextUTF16.xsl  XMLToInsertQuery.xsl","3102","13800627"]
[null,null,1512223,"2022-10-14",null,"Development\\OWS7",null,null,null,"Error when using candidates for shift functionality for a subcontracted shift","When using candidates for a shift, a subcontracted shift could not be planned when the target employee already had a shift planned.\r\nThis has been fixed.\r\nThe planned shift now becomes unassigned, and the new shift is planned.\r\n\r\nTest hint(s):\r\nVerify that, when using candidates for a shift, a subcontracted shift can be planned when the target employee already has a shift planned.","","4468","14337953"]
[null,null,1512223,"2022-10-14",null,"Development\\OWS7",null,null,null,"Added the possibility for FirebaseAPI installation on other location than Default Web Site","The FirebaseAPI can now be installed in (or updated to) a different location than the standard Default Web Site. In the InstallFirebaseAPIl.xml you can change the value of the tag <websitePath> to a desired location. E.g. <websitePath>D:\\Program Files(x86)\\ORTEC\\</websitePath> When the tag <websitePath> remains unchanged, the FirebaseAPI will still be installed under the Default Web Site.  Notes:  - Please do not install in the <installDir>\\ORTEC\\Workforce Scheduling\\ folder!    That can obstruct a correct execution of the PatchUtility. - Please do not make the <websitePath> longer than 255 characters.\r\n\r\nTest hint(s):\r\nNone","When you move the FirebaseAPI from c:\\inetpub\\wwwroot to a different location, the previous installation files under c:\\inetpub\\wwwroot\\<websiteName> are not removed. Removing these files is considered to be a one-time manual operation.","4488",14444230]
[null,null,1512223,"2022-10-14",null,"Development\\OWS7",null,null,null,"Activity properties in template duties sometimes showed wrong value when no permission on all activity properties","Activity properties in template duties sometimes showed the wrong value, when no permission on all activity properties.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nCreate two activity properties Verify in template duties if you update an activity properties value it shows the correct value","For this solution to become available, the ORTEC WS Win32 client must be installed.","5558",""]
[null,null,1512223,"2022-10-14",null,"Development\\OWS7",null,null,null,"Determination whether .NET4.8 needs installation in UnattendedUpdates could be incorrect","UnattendedUpdates could use an incorrect build number during a check whether in the supplied updates have a build number equal to or higher than 1511266 (update to .NET4.8 release).\r\nThis caused the .NET4.8 prerequisite not to be installed while it should have been.\r\nThis has been fixed\r\n\r\nTest hint(s)\r\n- Verify the unattended updates script has installed .NET 4.8 during an update to 1511266 or higher when .NET 4.8 is not yet present on the server(s).\r\nNote that installation of .NET4.8 requires a Windows restart.","","5696",""]
[null,null,1512223,"2022-10-14",null,"Development\\OWS7",null,null,null,"DBupdate error when running update script that checks the number of cost centers and having more then 100.000 cost centers","A DBUpdate script, that raises a warning when more than 100.000 cost centers exist, caused an interpretation error when the condition was met.\r\nThis has been fixed.\r\n\r\nTest hint(s)\r\n- Verify that the DBUpdate runs without errors when more than 100.000 cost centers exist in the OWS database","","5866","14733724"]
[null,null,1514209,"2022-10-27",null,"Development\\OWS7","Impossible to delete shift after import","When importing shifts with feature toggle CreateExchangesWhenImportingShifts enabled, the created exchanges (in database or internal) would cause importing the deletion (<action>DELETE</action>) of a shift to fail.\nThis has been improved. Similar to the behavior of the planboard, importing a shifts deletion will first try to delete the shift, but set it to removed when deletion is not possible due to linked objects (like exchanges, illness, leave etc.)\nNote that when a shift has been removed it cannot be replanned through import when the exact shift is targeted (identified by id or code)\n\nTest hint(s)\n - Verify that a shift can also be deleted or removed by import when feature toggle CreateExchangesWhenImportingShifts is enabled","","Impossible to delete shift after import","When importing shifts with feature toggle CreateExchangesWhenImportingShifts enabled, the created exchanges (in database or internal) would cause importing the deletion (<action>DELETE</action>) of a shift to fail.\nThis has been improved. Similar to the behavior of the planboard, importing a shifts deletion will first try to delete the shift, but set it to removed when deletion is not possible due to linked objects (like exchanges, illness, leave etc.)\nNote that when a shift has been removed it cannot be replanned through import when the exact shift is targeted (identified by id or code)\n\nTest hint(s)\n - Verify that a shift can also be deleted or removed by import when feature toggle CreateExchangesWhenImportingShifts is enabled","",3101,"13226610"]
[null,null,1514209,"2022-10-27",null,"Development\\OWS7","The default end date of an account on the WS for Employees Insight page had the wrong value if all schedules of a department were at least published","The default end date of an account on the WS for Employees Insight page had the wrong value if all schedules of a department were at least published. This could lead to more calculations being shown than expected.\nThis has been fixed.\n\nTest hint(s):\n- Verify that the correct overview is shown if all schedules are published and opening an account in WS for Employees","","The default end date of an account on the WS for Employees Insight page had the wrong value if all schedules of a department were at least published","The default end date of an account on the WS for Employees Insight page had the wrong value if all schedules of a department were at least published. This could lead to more calculations being shown than expected.\nThis has been fixed.\n\nTest hint(s):\n- Verify that the correct overview is shown if all schedules are published and opening an account in WS for Employees","",3104,"13928242"]
[null,null,1514209,"2022-10-27",null,"Development\\OWSforTeamSchedulers","[BDA] Team Scheduler - RefreshHorizontalCalculationsCache fails: BadRequest when retrieving horizontal calculations from BDA","In very specific cases, due to corrupt data, the horizontal calculations were not refreshed every 24 hours. This has been fixed. The corrupt data will be removed.",null,"[BDA] Team Scheduler - RefreshHorizontalCalculationsCache fails: BadRequest when retrieving horizontal calculations from BDA","In very specific cases, due to corrupt data, the horizontal calculations were not refreshed every 24 hours. This has been fixed. The corrupt data will be removed.",null,4982,""]
[null,null,1514209,"2022-10-27",null,"Development\\OWS7","Realizations in WS for Employees did not always show the correct begin and end time","Realizations in WS for Employees did not always show the correct begin and end time, when they were waiting for an approval of a manager.\nThis has been fixed.\n\nTest hint(s):\n- Verify entering a realization in WS for Employees shows the correct begin and end time","","Realizations in WS for Employees did not always show the correct begin and end time","Realizations in WS for Employees did not always show the correct begin and end time, when they were waiting for an approval of a manager.\nThis has been fixed.\n\nTest hint(s):\n- Verify entering a realization in WS for Employees shows the correct begin and end time","",5298,"14628217"]
[null,null,1514209,"2022-10-27",null,"Development\\OWS7","ClockTimes window export to excel (csv) was not saved with filetype csv by default","ClockTimes window export to excel (csv) was not saved with filetype csv as default\nThis has been improved.\n\nTest hint(s)\n- Verify when exporting clockings to csv the default extension csv is used.","For this change to become available, the OWS Win32 client needs to be updated","ClockTimes window export to excel (csv) was not saved with filetype csv by default","ClockTimes window export to excel (csv) was not saved with filetype csv as default\nThis has been improved.\n\nTest hint(s)\n- Verify when exporting clockings to csv the default extension csv is used.","For this change to become available, the OWS Win32 client needs to be updated",5323,"14628627"]
[null,null,1514209,"2022-10-27",null,"Development\\OWS7\\Basic functionalities","Opening Access Control as dual client window caused ORTEC Workforce Scheduling Win32 client to be resized","Opening Access Control as dual client window caused ORTEC Workforce Scheduling Win32 client to be resized.\nA new feature toggle setting has been introduced: FEATURETOGGLES\\CWGSCUASFORMSTYLENORMAL and is by default enabled.\nWhen the feature toggle is enabled the Access Control dual window is opened outside the ORTEC Workforce Scheduling Win32 client.\n\nTest hint(s):\n- Verify opening Access Control in ORTEC Workforce Scheduling Win32 client does not resize the screen","","Opening Access Control as dual client window caused ORTEC Workforce Scheduling Win32 client to be resized","Opening Access Control as dual client window caused ORTEC Workforce Scheduling Win32 client to be resized.\nA new feature toggle setting has been introduced: FEATURETOGGLES\\CWGSCUASFORMSTYLENORMAL and is by default enabled.\nWhen the feature toggle is enabled the Access Control dual window is opened outside the ORTEC Workforce Scheduling Win32 client.\n\nTest hint(s):\n- Verify opening Access Control in ORTEC Workforce Scheduling Win32 client does not resize the screen","",5401,""]
[null,null,1514209,"2022-10-27",null,"Development\\OWS7","When two shifts in a published schedule were exchanged, the 'Overview shift reassignments' form of one of the shifts did not show the correct corresponding activity types","When two shifts in a published schedule were exchanged, the 'Overview shift reassignments' form of one of the shifts did not show the correct corresponding activity types.\nThis has been improved.\n\nTest hint(s):\n- Exchange two shifts in a published schedule and verify that the 'Overview shift reassignments' form shows the correct corresponding activities.","For this solution to become available, the ORTEC WS Win32 client must be installed.","When two shifts in a published schedule were exchanged, the 'Overview shift reassignments' form of one of the shifts did not show the correct corresponding activity types","When two shifts in a published schedule were exchanged, the 'Overview shift reassignments' form of one of the shifts did not show the correct corresponding activity types.\nThis has been improved.\n\nTest hint(s):\n- Exchange two shifts in a published schedule and verify that the 'Overview shift reassignments' form shows the correct corresponding activities.","For this solution to become available, the ORTEC WS Win32 client must be installed.",5421,"14640912"]
[null,null,1514209,"2022-10-27",null,"Development\\OWS7","Schedule optimizer created violations in the future for labor rule 'Weekly rest'","The schedule optimizer created violations in the future for labor rule 'Weekly rest'. This has been improved in certain cases (see below).\nIn general, the schedule optimizer assumes that the planning is \nmade chronologically, starting from an empty planning. It does not consider already planned shifts in future periods and violations can occur because of this. \nChanging this requires an overhaul of the optimizer code. However, we can do certain checks in the algorithm's pre-processing steps, but this is limited to single shifts and not combinations of shifts. We have added such a pre-processing check for this rule as well.\nAn individual shift planned by the optimizer will no longer \ncreate a violation because of shifts outside of the optimized period. However, a violation might still occur due to a combination of shifts \nplanned by the optimizer. \nWe expect this fix will improve certain situations for the 'Weekly rest' rule, but definitely not all.\nThis functionality is behind a feature toggle, CheckFutureViolationsForRestPerWeekReq. The default value of the feature toggle is 'N'.\nNote: Please note that the exceptions mentioned in the 'Weekly rest' rule are not taken into account in this pre-processing improvement.\n\nTest Hint(s):\n- Verify no violations in the future for labor rule 'Weekly rest' will be created when running the schedule optimizer.","","Schedule optimizer created violations in the future for labor rule 'Weekly rest'","The schedule optimizer created violations in the future for labor rule 'Weekly rest'. This has been improved in certain cases (see below).\nIn general, the schedule optimizer assumes that the planning is \nmade chronologically, starting from an empty planning. It does not consider already planned shifts in future periods and violations can occur because of this. \nChanging this requires an overhaul of the optimizer code. However, we can do certain checks in the algorithm's pre-processing steps, but this is limited to single shifts and not combinations of shifts. We have added such a pre-processing check for this rule as well.\nAn individual shift planned by the optimizer will no longer \ncreate a violation because of shifts outside of the optimized period. However, a violation might still occur due to a combination of shifts \nplanned by the optimizer. \nWe expect this fix will improve certain situations for the 'Weekly rest' rule, but definitely not all.\nThis functionality is behind a feature toggle, CheckFutureViolationsForRestPerWeekReq. The default value of the feature toggle is 'N'.\nNote: Please note that the exceptions mentioned in the 'Weekly rest' rule are not taken into account in this pre-processing improvement.\n\nTest Hint(s):\n- Verify no violations in the future for labor rule 'Weekly rest' will be created when running the schedule optimizer.","",5522,""]
[null,null,1514209,"2022-10-27",null,"Development\\OWS7","Terminate OWS Win32 Client automatically after a maximum number of unrecoverable errors have occurred","A large number of exceptions within one minute caused the OWS Win32 client not to shutdown properly. \nThis has been improved.\nNow, when the number of exceptions within a minute reaches the added server setting (see below), the OWS Win32 Client is terminated.\nAdded Server setting: MaxNumberOfUnrecoverableErrorsPerMinuteInOWSClient with default value 200.\n\nTest hint(s):\n- None","","Terminate OWS Win32 Client automatically after a maximum number of unrecoverable errors have occurred","A large number of exceptions within one minute caused the OWS Win32 client not to shutdown properly. \nThis has been improved.\nNow, when the number of exceptions within a minute reaches the added server setting (see below), the OWS Win32 Client is terminated.\nAdded Server setting: MaxNumberOfUnrecoverableErrorsPerMinuteInOWSClient with default value 200.\n\nTest hint(s):\n- None","",5799,"14.655.410"]
[null,null,1514209,"2022-10-27",null,"Development\\OWS7\\Basic functionalities","Interfaceworker with role SkillDemandOptimization could halt if a schedule was deleted while it was busy or not running","An Interfaceworker with role SkillDemandOptimization could halt if a schedule was deleted while it was busy or not running.\nThis has been fixed.\n\nTest hint(s):\n- Verify skill demands are correctly calculated when deleting a schedule","","Interfaceworker with role SkillDemandOptimization could halt if a schedule was deleted while it was busy or not running","An Interfaceworker with role SkillDemandOptimization could halt if a schedule was deleted while it was busy or not running.\nThis has been fixed.\n\nTest hint(s):\n- Verify skill demands are correctly calculated when deleting a schedule","",5801,14730537]
[null,null,1514209,"2022-10-27",null,"Development\\OWSforTeamSchedulers","[BDA] Team scheduler does not show calculations","It was not possible to retrieve horizontal calculations when setting 'UseHideTransferredEmployeesOnRunningAccount' was set to 'true'.\nThis has been fixed.\n\n\nTest hints:\n- Open a schedule view in the Team Scheduler application and verify that horizontal calculation results show up (Note: This can take a while.) In the schedule view, (un)plan a shift and verify that the horizontal calculation of the involved employee is updated.","","[BDA] Team scheduler does not show calculations","It was not possible to retrieve horizontal calculations when setting 'UseHideTransferredEmployeesOnRunningAccount' was set to 'true'.\nThis has been fixed.\n\n\nTest hints:\n- Open a schedule view in the Team Scheduler application and verify that horizontal calculation results show up (Note: This can take a while.) In the schedule view, (un)plan a shift and verify that the horizontal calculation of the involved employee is updated.","",5844,14732759]
[null,null,1516666,"2022-11-11",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - Added extra information to confirmation email","Extra information has been added to the confirmation email after a successful unattendedUpdates run.\n- The email subject will now display the value of the <customer><environment> tag after the <customer><name> tag defined in UnattendedUpdate_Config.xml.\n- When mentioning the environment(s) have been updated from version x to y, the comtec environment names are now also mentioned.\n- When a Windows restart is needed after a prerequisite installation and the script may not perform the restart, the relevant servernames are now mentioned.\n\nTest hint(s):\n1. Use unattended update and check the confirmation email is complete","",5015]
[null,null,1516666,"2022-11-11",null,"Development\\OWS7\\Technical improvements",null,null,null,"UnattendedUpdates - Script to check for main application server could return a false positive","When UnattandedUpdates checks whether the script is run on the main application server, an incorrect value for the serverType (dependent/independent) is sometimes stored in registry. \r\nIn such a case, this led to an incorrect error that the script was not run on the main application server\r\nThis has been improved.\r\nNow the existence of the Environments registry key is checked instead of serverType.\r\n\r\nTest hint(s)\r\n1. Verify that UnattandedUpdates starts without errors when run on a main application server.","",5017]
[null,null,1516666,"2022-11-11",null,"Development\\OWS7\\Technical improvements",null,null,null,"UnattendedUpdates - Empty DBUpdateConsole output did not raise an error","When a crash in the DBUpdateConsole occurred when running UnattendedUpdates, no output was returned.\r\nWhen checking the DBUpdateConsole output this scenario was not taken into account and UnattendedUpdates continued without raising an error.\r\nThis has been fixed. \r\nUnattendedUpdates will now stop when no output is returned.\r\n\r\nTest hint(s)\r\n1. Verify that UnattendedUpdates Performs DBUpdates without issues. DBUpdate output can be checked in a logfile in the <PatchUtility>\\UnattendedUpdates\\Log\\DBUpdate folder.","",5018]
[null,null,1516666,"2022-11-11",null,"Development\\OWSforTeamSchedulers",null,null,null,"Retrieving a schedule without employees in ORTEC WS for Team Schedulers gave internal server error  ","Opening a planboard for a department without employees in ORTEC WS for Team Schedulers doesn't show an error anymore\n\nTest hint(s):\n1. None","",5391]
[null,null,1516666,"2022-11-11",null,"Development\\OWS7",null,null,null,"Added option to stop a CMHS network in case a critical error has occurred","Added option to stop a CMHS network in case a critical error has occurred\r\nIn the CPMS configuration of a CMHS process you can select the action that should be taken when one of the networks in the process has a critical error.Value 'none' is the default and indicates that the network should not stop. Value 'stop all networks' was added and indicates that a CPMS process running the configured (checked) CMHS networks will be terminated on a critical error.\r\n\r\nTest hint(s)\r\n\r\n1.  Verify that configured CPMS processes that run one or more CMHS network still function.","",5914]
[null,null,1516666,"2022-11-11",null,"Development\\OWS7\\Technical improvements",null,null,null,"UnattendedUpdates  - Stop processing OWS updates when prerequisite install requires manual Windows reboot","UnattendedUpdates could install Windows prerequisites and continue to install all ORTEC WS updates.\nWhen an installed prerequisite required a Windows restart and UnattendedUpdates was not allowed to restart Windows for you, this could cause ORTEC WS to not function properly when the Windows restart as stated in the final confirmation email was not followed up.\nThis has been improved.\nUnattendedUpdates will stop processing ORTEC WS updates when:\n- An installed prerequisite needs a Windows restart.\n- UnattendedUpdates is not allowed to restart Windows for you.\nThe COMTEC Starter Service will be started, and an email will be sent that a Windows restart is needed before ORTEC WS updates can be processed  \n\n\nNote: when the UnattendedUpdates script is run from the Windows PowerShell ISE, we consider the script to run attended.\nIn this case the script will continue processing ORTEC WS updates, and the final confirmation email will state that a Windows restart is needed.\n\nTest hint(s)\n1. Verify the UnattendedUpdates script runs normally and reacts to installed prerequisites as described.","",5947]
[null,null,1516666,"2022-11-11",null,"Development\\OWS7",null,null,null,"A worker responsible for processing skill matching calculations could halt","A worker responsible for processing skill matching calculations could halt. This could happen when entities were deleted while the worker was down.\nThis has been fixed.\nThis fix was introduced behind a feature toggle FEATURETOGGLES\\REDUCELOCKINGINSKILLMATCHINGUPDATEHANDLER, which by default is turned on.  \n\nTest hint(s):\n1. Verify skill matching calculations are still done correctly","",6090,14755741]
[null,null,1516666,"2022-11-11",null,"Development\\OWSforTeamSchedulers",null,null,null,"Preparation for ORTEC WS for Team Schedulers features","Preparations for upcoming features in ORTEC WS for Team Schedulers regarding workstations & cost centers on activity level\n\nTest hint(s):\n1. None","",4304]
[null,null,1516666,"2022-11-11",null,"Development\\OWS7",null,null,null,"Remove feature toggle DoNotLoadRemovedAndUnassignedShiftsForPersonalSchedule","Removed feature toggle DoNotLoadRemovedAndUnassignedShiftsForPersonalSchedule. We now never load removed and unsassigned shifts for a personal schedule.\n\nTest hint(s):\n1. None","",6225]
[null,null,1517628,"2022-11-17",null,"Development\\OWS7",null,null,null,"UnattendedUpdates sent an email on each warning","Unattended updates would send an email stating the script has stopped on every non-critical exception, even though the script would continue running.\r\nThis has been improved.\r\nWarnings are now gathered and displayed in the final confirmation email upon completion.\r\n\r\nTest hint(s):\r\nVerify unattended updates runs correctly","","5016",""]
[null,null,1517628,"2022-11-17",null,"Development\\OWS7",null,null,null,"Installing the BackendAPI and FirebaseAPI would fail if run from a folder with a space in the name","Installing the BackendAPI and FirebaseAPI would fail if the install script was run from a folder with a space in the name.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nVerify installing BackendAPI and FirebaseAPI works correctly","","5022",""]
[null,null,1517628,"2022-11-17",null,"Development\\OWS7",null,null,null,"A notice is added to Unattended Updates when XMLDefinitions or Stylesheets updates are rolled out","A notice is added to Unattended Updates when XMLDefinitions or Stylesheets updates are rolled out.\r\nThis makes it clearer that a manual action has to be taken when a non-default location is used to store XMLDefinitions or Stylesheets.\r\n\r\nTest hint(s):\r\nVerify a notice if given if Interfaces or Stylesheets are updated using Unattended Updates","","5023",""]
[null,null,1517628,"2022-11-17",null,"Development\\OWSforAdHocPlanners",null,null,null,"ORTEC WS for AdHocPlanners: Oops page due to v2/shifts/by-department call on 2100+ shifts","In Ad Hoc Planning, the schedule could not be opened in case there were more than 2100 shifts in it. Also, the list with finished offers could not be shown in case there were more than 2100 finished offers.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nOpen a schedule containing more than 2100 shifts Open a finished offers list when there are more that 2100 shifts in the past period","","5690",""]
[null,null,1517628,"2022-11-17",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS for TeamSchedulers: Schedule hangs when labor rule violations with no contributing shifts","When retrieving violations, the violations caused by \"Daily rest after shift (labor period)\" were placed at every employee on the day of the violation.\r\n\r\n\r\nTest hints:\r\nCreate a violation of the rule \"Daily rest after shift (labor period)\". When opening the schedule in Team Scheduler, this violation should only be visible at the employee it belongs to","","5950",""]
[null,null,1517628,"2022-11-17",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS for TeamSchedulers: Error when retrieving details of an approved swap request","It was not possible to open an approved swap request.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nOpen a swap request in the PROCESSED tab.","","6359",""]
[null,null,1517628,"2022-11-17",null,"Development\\OWS7",null,null,null,"Monitoring stylesheets did not work correctly after 8.5.0(2022-10-14)_Build1512223","CMHS based monitoring stylesheets did not work correctly after update 8.5.0(2022-10-14)_Build1512223. This resulted in query-based monitoring data no longer being sent. \nIn that specific update, two additional stylesheets were introduced which are now used in one of the existing stylesheets (date.functions.xsl). \nThe changed, existing stylesheet was replaced by the patch utility in the following CMHS monitoring location: Server\\Utilities\\MonitorConfiguration\\CMHSNetwork\\Stylesheets\\Libraries\nHowever, the new stylesheets were not added to that same location resulting in a dependency failure when loading the CMHS network.\n\nThis has been fixed and the new stylesheets are now also added to that specific CMHS monitoring location. \n\nNote: A manual workaround is to copy the date.format-date.template.xsl and str.padding.template.xsl stylesheets manually from Server\\Interfaces\\Stylesheets\\Libraries to Server\\Utilities\\MonitorConfiguration\\CMHSNetwork\\Stylesheets\\Libraries\n\nTest hint(s):\nNone","","6731","14848498"]
[null,null,1518817,"2022-11-24",null,"Development\\OWS7\\Basic functionalities",null,null,null,"A wrongly entered WebServer folder in the Unattended Update configuration could result in failures","A wrongly entered WebServer folder in the Unattended Update configuration could result in failures. \r\nThis has been fixed. \r\nA prescript check was added to raise an error the configured path is does not exist.\r\n\r\nTest hint(s): \r\n- Verify Unattended Updates can correctly install a manual WebServer update",null,5020]
[null,null,1518817,"2022-11-24",null,"Development\\OWS7",null,null,null,"Unattended Updates did not stop/start additional BackendDomainsApi websites","Unattended Updates would not stop/start additional BackendDomainsAPI websites (created on hosted consolidation environments) that had a Physical Path without a trailing '\\'. \r\nThis could cause updating the BackendDomainsApi to fail. \r\nThis has been fixed. \r\nIt now searches for sites with and without the trailing '\\' and stops/starts both.\r\n\r\nTest hint(s): \r\n- Verify updating the BackendDomainsApi goes ok using Unattended Updates",null,5024]
[null,null,1518817,"2022-11-24",null,"Development\\OWS7",null,null,null,"Determining first editable date of a planboard was calculated too many times which could degrade performance of opening planboards ","The first date a plan board is editable was calculated too many times. \nThis could degrade performance of opening planboards, in particular for (larger) plan boards covering multiple scheduling periods. \nThis has been improved.\n\nNow this is only calculated once while opening a plan board.\n\nTest hint(s): \n- Verify opening a plan board in OWS win32 client succeeds.",null,6197]
[null,null,1518817,"2022-11-24",null,"Development\\OWS7",null,null,null,"UnattendedUpdate process could stall when FirebaseMobileAPI silently installed an IIS feature  ","UnattendedUpdate process waited for user input when the FirebaseMobileAPI silently (re)installed the IIS feature 'Application Initialization'.\n\nThis has been improved. \n\nAs the IIS feature 'Application Initialization' is a prerequisite to ensure correct operation of the FirebaseMobileAPI, a pre-update check has been added to verify whether this feature is already installed\n\nTest hint(s): \n- None",null,6210,14765330]
[null,null,1518817,"2022-11-24",null,"Development\\OWSforTeamSchedulers",null,null,null,"[BDA] Error when retrieving details of an approved swap request","It was not possible to open an approved swap request. \r\nThis has been fixed.\r\n\r\nTest hint(s):\r\n- Open a swap request in the PROCESSED tab.",null,6359]
[null,null,1518817,"2022-11-24",null,"Development\\OWSforTeamSchedulers",null,null,null,"Publish schedule sometimes not possible in Team Scheduler ","When the interface worker and the server did not have the same default language, changing the status of a roster period was not possible. \n\nAdded feature toggle Server setting: FeatureToggles\\USEENGLISHFORSTATUSCONVERSION and is by default enabled.\n\nTest hint(s):\nVerify that changing the status of a roster period is still possible",null,6448]
[null,null,1518817,"2022-11-24",null,"Development\\OWS7",null,null,null,"Windows 2022 is supported","Deploying OWS 7 on Windows 2022 is supported.",null,6893]
[null,null,1521163,"2022-12-09",null,"Development\\OWS7",null,null,null,"Unattended Updates - added option to retrieve updates from file location instead of EFT","An option has been added to Unattended Updates to retrieve ORTEC WS update files from a file location.\nThis can accommodate the following scenarios:\n- Updates that have been rolled out on a test environment are backed up (UnattendedUpdate_Config.xml -> <locations><backupLatestUpdateFolder>). When testing has finished, a production environment can retrieve the updates from this folder to apply the same updates to production.\n- Updates can be retrieved from a server without an internet connection.\n- Updates can be stored or downloaded to a central file server to reduce internet overhead on e.g. Hosting or customers with multiple environments running on multiple servers.\n\nTest hint(s):\n- Verify Unattended Updates still works as before when the new parameters have not been set Verify Unattended Updates can retrieve update files from a local or network folder.","In order to enable this fuctionality two new parameters need to be added to the UnattendedUpdate_Config.xml in C:\\ProgramData\\Ortec\\ORTEC Workforce Scheduling\\UnattendedUpdates\r\n1. Create node <downloadMethod>FileLocation</downloadMethod> under <scriptOptions>\r\n  - Allowed values are 'EFT' and 'FileLocation' (case sensitive)\r\n  - When the node does not exist or left empty, EFT will be set as the default values\r\n \r\n2. Create node <getUpdatesFromFileLocationFolder></getUpdatesFromFileLocationFolder> under <locations> and set the value to a folder location.\r\n  This can be a local folder (e.g. C:/temp/OWSUpdates) or a unc path to a shared folder (e.g. \\\\<servername>\\OWSUpdates)\r\nNotes:\r\n  - Make sure read permissions on the folder are granted for the user that runs the UnattenedUpdates process\r\n  - The parameter getUpdatesFromFileLocationFolder may not be left empty when <downloadMethod> has been set to 'FileLocation'\r\n  - The only relevant files for this process are \r\n    - Manual_Update_*.zip files\r\n    - Update_*.zip files\r\n    - Cumulative_ReleaseNotes_OWS7.csv (not mandatory, but recommended)\r\nFor reference, the new parameters have been added to the Template_UnattendedUpdate_Config.xml","5019",""]
[null,null,1521163,"2022-12-09",null,"Development\\OWS7",null,null,null,"Unattended Update process could stall when utility programs were still open","The Unattended Update process could stall when ORTEC WS related processes like CCDSCommand or DBUpdateWizard were still open or running as these processes could not be updated.\r\nThis has been improved.\r\nIn addition to CSCS, Settings Manager and Win-32 Client, the script will also stop instances of: ComtecConfig, CCDSCommand, CCDSRecorder, DBAnonymize, DBAnonymizeConsole, DBUpdate, DBUpdateWizard, DBUpdateCOnsole, PostInstall, ReplacePassword,  TranslationManager and PatchUtilConsole.\r\n\r\nTest hint(s):\r\nNone","","5021",""]
[null,null,1521163,"2022-12-09",null,"Development\\OWS7",null,null,null,"When something went wrong with the server responsible for skill requirement optimization calculations, it was hard to make sure that all skill requirement optimization calculations were up to date","When something went wrong with the server responsible for skill requirement optimization calculations, it was hard to make sure that all skill requirement optimization calculations were up to date. \r\nThis has been improved.\r\nA command handler, /hmy/server/CRecalculateSkillDemandOptimizationResults, has been created to recalculate the skill demand optimization results for input departments and periods.\r\n\r\nTest hint(s):\r\nNone","","6454",""]
[null,null,1521163,"2022-12-09",null,"Development\\OWS7",null,null,null,"Creating a date specific duty demand copies the skill requirements from the recurring duty demand on that day if applicable","When creating a date specific duty demand, the skill requirements are now copied from the recurring duty demand on that day if applicable.\nPreviously the user had to recreate the skill requirements for the date specific duty demand, which was a lot of work.\nThis functionality is behind a general setting called UseCopySkillRequirementsDateSpecificDutyDemand.\n\nNotes:\nIf the date specific duty demand is lower than the number of the \nto-be-copied skill requirements, the user will get an error message \nindicating the minimum duty demand that has to be entered.\nThe user has to create this minimum date specific duty demand, then remove a\n number of (copied) skill requirements after which the date specific \nduty demand can be lowered accordingly. This functionality is also applied when increasing or decreasing the duty demand from the shift counter grid in the planboard.\n\nTest hint(s):\nNone","","6742",""]
[null,null,1521163,"2022-12-09",null,"Development\\OWS7",null,null,null,"ORTEC WS - ORTEC Web Server installer was removed","ORTEC WS - ORTEC Web Server installer was removed\nThe Web Server installer could be used to install the deprecated ESS and MSS websites (ie. for on-premises installations)\nThey have been replaced by ORTEC for Employees and ORTEC for Managers cloud front ends.\n\nTest hint(s):\nNone","","6863",""]
[null,null,1521163,"2022-12-09",null,"Development\\OWS7\\Technical improvements",null,null,null,"'Forbidden activity type' rule could be slow if configured to check an employee property","'Forbidden activity type' rule could be slow if configured to check an employee property.\r\nEspecially when checking employee properties that have permissions configured.\r\n This has been improved.\r\nPer shift first the activity type is checked, then for the date of the shift the configured age/salary group and employee property are checked.\r\n\r\nTest hint(s):\r\n- verify that the 'Forbidden activity type' rule works as expected.","","6947",""]
[null,null,1521163,"2022-12-09",null,"Development\\OWS7\\Technical improvements",null,null,null,"Rules checked employee properties, age and salary group given the rule configuration","Rules checked employee properties, age and salary group given the rule configuration. \nThis has been improved.\nThe rule checks the age and salary group first and then the employee properties checks, because this is more efficient.\n\nTest hint(s):\nNone","","6958",""]
[null,null,1521163,"2022-12-09",null,"Development\\OWS7\\Technical improvements",null,null,null,"A race condition in protecting reads on objects in memory could cause situation not releasing locks that eventually could halt a CWSS interface worker process ","A race condition in protecting reads on objects in memory could cause situation not releasing locks that eventually could halt an CWSS interface worker process \n This has been improved\n\nAdded feature toggle: FeatureToggles\\ImproveMultiReadExclusiveWriteTimeOutSyncForReads and is by default enabled.\n\nTest hint(s):\n- verify that OWS win 32 clients can work and process plan board changes simultaneously\n- verify that a CWSSServer worker designated for handling ORTEC WS for Employees or Manager calls can handle that traffic","","7138","14837360"]
[null,null,1525753,"2023-01-05",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - added progress tracking on multi-step updates","When running the Unattended Updates script again after an error, it did not know that some update steps potentially still needed to be performed.\r\n\r\n- If a CVIS update zip was already rolled out and removed and then DBUpdate itself failed, the script did not know that DBUpdate still needed to run on one or more environments.\r\n- In the same case a Client update zip could have already been processed and removed. The script did not know that the Client still needed to be copied to one or more terminal servers.\r\nThis has been improved.\r\nThe script will now keep track of:\r\n- Environments for which the DBUpdate still needs to run.\r\n- Terminal servers to which the Client needs to be copied to.\r\nWhen the script runs into a DBUpdate error which needs to be fixed. The script can be restarted after fixing the error.\r\nWhen it has detected that DBUpdate or Client steps are still not finished from a previous run, it will start in a mode that will skip downloading (when configured) and preparing updates so it can finish the unfinished steps.\r\nWhen unfinished steps are all finished, the progress will be marked as complete and a next run of the script will start normally again, starting with downloading (when configured) and preparing updates.\r\n\r\nTest hint(s):\r\n1. Verify that UnattenedUpdates finishes normally when errors do not occur\r\n2. In case an error has occurred, verify that UnattendedUpdates:\r\n    - Starts without downloading updates again\r\n    - Finishes all remaining steps when errors have been resolved\r\n    - Starts normally on the next run of the script","This functionality can be turned on or off in C:\\ProgramData\\Ortec\\ORTEC Workforce Scheduling\\UnattendedUpdates\\UnattendedUpdate_Config.xml\r\nThe following node can be inserted between </scriptOptions> and <eMail>:\r\n  <featureToggles>\r\n    <useProgressTracking>Y</useProgressTracking>\r\n  </featureToggles>\r\nSee Template_UnattendedUpdate_Config.xml in the UnattendedUpdates scripts folder for an example\r\nNote that it is active by default, also when the entry does not exist.","6185",""]
[null,null,1525753,"2023-01-05",null,"Development\\OWS7",null,null,null,"Removed feature toggle PlanActivityDoesNotUnplanOverlappingShiftsFromOtherDepartment","Feature toggle PlanActivityDoesNotUnplanOverlappingShiftsFromOtherDepartment was removed. \nThis was introduced in OSDCOMMAIN-13482 A shift from another department was planned out when planning an activity type overlapping that shift\n\nTest hint(s):\n- Plan in an activity or disturbance type over a shift from a lending department. This should show an informative error and do not perform any planning or remove any shifts.","","6564",""]
[null,null,1525753,"2023-01-05",null,"Development\\OWS7\\OWS for Employees",null,null,null,"A technical change was done in preparation for supporting overnight employee realisations in ESS7","A technical change was done in preparation for supporting overnight employee realisations in the ESS7 app.\r\n\r\nThis change makes it possible to create an employee realization that started a day earlier than the planned shift.\r\n\r\n\r\n\r\nThe new functionality can be activated by the general setting UseOvernightShiftEmployeeRealisation, which by default is turned off\r\nThis new general setting is dependent on the setting UseApproveRealisations and can only be activated when UseApproveRealisations is activated.\r\n\r\n\r\nPlease note that the ESS7 frontend also needs to be adjusted for this change to become effective.  More details will be provided when this part is developed.","","6834",""]
[null,null,1525753,"2023-01-05",null,"Development\\OWS7",null,null,null,"OWS Server Installer was updated","OWS Server Installer was updated.\nThe dependencies for the COMTEC Access Web Api were removed from the installer \nThe dependencies for the ORTEC Identity Gateway were removed earlier in issue \"5032 - ORTEC Identity Gateway support has been removed from ORTEC Workforce product\"\n\nTest hint(s)\n- Verify that the ORTEC Server Installer successfully installs OWS Server binaries","","6865",""]
[null,null,1525753,"2023-01-05",null,"Development\\OWSforTeamSchedulers",null,null,null,"Employee requests not correct with >1 weekly patterns  ","Employee requests with a weekly or monthly recurrence pattern were not shown correctly.\r\nThis has been fixed.\r\nTesthint(s):\r\n - Create an employee request  with a weekly or monthly recurrence pattern. Check that the requests are shown correctly in OWS for Team Schedulers","",6921]
[null,null,1525753,"2023-01-05",null,"Development\\OWSforTeamSchedulers",null,null,null,"Stopping optimizer did not work when interfaceworker handles Backend Domains Api requests","When the requests from the Backend Domains Api are handled by an interfaceworker, the optimizer could not be stopped before the maximum time had passed.\r\nThis has been fixed. Now, the request to stop the optimizer is handled by the main server regardless the value of the CWWS/Servernumber setting, and the optimizer stops.\r\n\r\nTest hint(s):\r\nStart the optimizer and stop it before the maximum time is over. Verify that the optimizer actually stops.","",6945]
[null,null,1525753,"2023-01-05",null,"Development\\OWS7",null,null,null,"ORTEC WS - ORTEC Reporting Services Extensions (x86) installer was removed","ORTEC WS - ORTEC Reporting Services Extensions (x86) installer was removed.\r\nORTEC Reporting Services Extensions (x86) is not used since all supported SQL Server versions are x64. ORTEC WS - ORTEC Reporting Services Extensions (x64) installer should be used.\r\n\r\nTest hint(s):\r\nNone","",7152]
[null,null,1525753,"2023-01-05",null,"Development\\OWS7",null,null,null,"When opening a personal schedule with begin and end date in the same week, an access violation occurred","When opening a personal schedule with begin and end date in the same week, an access violation occurred.\r\nThis has been fixed.\r\nNow the personal schedule of the week in which both dates fall is opened.\r\n\r\nTest hint(s):\r\nIn General - Plan board Settings - Display settings, set the Personal schedule in the used display setting to \"One week per row\".  Open a personal schedule with begin and end date in the same week. Verify that the personal schedule of that week is opened.","For this solution to become available, the ORTEC WS Win32 client must be installed.",7331,14951316]
[null,null,1525753,"2023-01-05",null,"Development\\OWS7",null,null,null,"Added translation for German","A translation has been added for German for recent functional changes.\r\n\r\nTest hint(s):\r\nNone","",7614]
[null,null,1525753,"2023-01-05",null,"Development\\OWS7",null,null,null,"OWS Win32 Client: Access Control can be opened as dual client window - functionality is enabled by default","Feature toggle EnableAccessControlInDualClient has been turned on by default   This feature toggle was added in issue OSDOWSD-4464 \"OWS Win32 Client: Access Control can be opened as dual client window\" (OWS 7 8.5.0(2021-12-23)_Build1459598)  Using access control through the win32 client is the safer alternative compared to using it through your browser. For this to work, update the OWS Settings manager setting CWGSACCESSCONTROLBASEURL with the location to access control website i.e. https://localhost/accesscontrol/.\nThe user(s) that should be allowed to access control must have the CUASMANAGEMENTCONFIG permission.\n\nTest hint(s): \n- Verify access control can be opened from the win32 client","","7912",""]
[null,null,1528349,"2023-01-19",null,"Development\\OWS7",null,null,null,"Mailbox messages did not support round brackets in the mailbox name","Mailbox messages did not support round brackets in the mailbox name.\r\nThis has been improved.\r\n\r\nTest hint(s):\r\nVerify the mailbox name and number of unread messages is correct in the Messages screen","For this solution to become available, the ORTEC WS Win32 client must be installed.",5621,14667426]
[null,null,1528349,"2023-01-19",null,"Development\\OWS7",null,null,null,"The backendAPI would return parent costcenters for a requested department while realizing in the ESS7 App and WS for Employees","The backendAPI would return parent costcenters for a requested department while realizing in the ESS7 App and WS for Employees.\r\nThis has been fixed.\r\nThe backendAPI will now only return leaf costcenters\r\n\r\nTest hint(s):\r\n1. Verify that only leaf costcenters are selectable when changing an activities cost center during a realization in the ESS7 App or WS for Employees",null,5622,14667459]
[null,null,1528349,"2023-01-19",null,"Development\\OWS7",null,null,null,"Replace by workstation with activity type None led to incorrect activity types","When replacing (part of) a shift by a workstation with activity type None, this led to incorrect activity types.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nCreate a shift with activity type A and replace this shift by a workstation with no activity type Verify that the shift still has activity type A",null,5744]
[null,null,1528349,"2023-01-19",null,"Development\\OWS7",null,null,null,"OWS Win32 Client: an about to expire license warning could be shown when multiple clients retrieved license information simultaneously","In OWS Win32 Client: an about to expire license warning could be shown when multiple clients retrieved license information simultaneously.\r\nThis has been improved.\r\n\r\nTest hint\r\nverify a user can login OWS 7 using OWS Win32 Client application",null,6050,14746848]
[null,null,1528349,"2023-01-19",null,"Development\\OWS7\\Technical improvements",null,null,null,"Remove feature toggle USEIMPROVEDSELFROSTERGETSHIFTOPTIONS","In issue #3659 a feature toggle was added to improve self rostering.\r\nThis improvement was implemented behind a feature toggle.\r\nThe feature toggle has been removed.\r\n\r\n",null,6452]
[null,null,1528349,"2023-01-19",null,"Development\\OWS7",null,null,null,"Removed feature toggle ImproveLockingForCleanUpRemovedShifts ","Removed feature toggle ImproveLockingForCleanUpRemovedShifts\r\nThe functionality added in \"3039 Technical change to command handler CCleanUpRemovedShifts to prevent panic exceptions\" behind this toggle is now implemented by default.\r\n\r\nTest hint(s): Verify that calling CCleanUpRemovedShifts command handler to clean up removed shifts succeeds.",null,6605]
[null,null,1528349,"2023-01-19",null,"Development\\OWS7",null,null,null,"Replace by leave of absence did not have an 'all shifts' option for multiple shifts on one day","When there were multiple shifts on one day, It was not possible to select all shifts with the planboard option 'Replace by leave of absence'.\r\nThis has been improved.\r\nIt is now possible to select all shifts on one day when using 'Replace by leave of absence'\r\n\r\nTest hint(s):\r\n1. Verify that the (All) option can be used to replace al shifts on one day.\r\n2. Verify that you can still chose a single shift.","For this solution to become available, the ORTEC WS Win32 client must be installed.",7332,14951755]
[null,null,1528349,"2023-01-19",null,"Development\\OWSforAdHocPlanners",null,null,null,"Added originating system to user session logging","The acLoginSessionLogOWSApplication table contains the originating system (app) for the user that is logged in (session). Now, this is also done for users of ORTEC WS Ad Hoc Planning and ORTEC WS for Team Schedulers.\r\nThis information can be used by the ORTEC monitoring system to track the number of logins per app.",null,7524]
[null,null,1528349,"2023-01-19",null,"Development\\OWS7",null,null,null,"Handling access violation errors in planboards was changed.","When an access violation in the planboard occurred, the customer could not open planboards.\r\nThis has been improved.\r\nWhen an access violation occurs the planboard is marked as defective and closed.\r\n\r\n",null,7568,{"$f":"M102814962271","v":{"$error":"#NAME?"}}]
[null,null,1528349,"2023-01-19",null,"Development\\OWS7",null,null,null,"UnattendedUpdates: Backup of manual updates considered non-existing files to backup","In case files were removed from a WebServer of WebSite update, UnattendedUpdates would raise an error during the backup stage as it considered non-existing files to backup.\r\nThis has been fixed.\r\nUnattendedUpdates will now backup the full installation folder.\r\nAfter backup, it will also clear the installation folder before rolling out the new files to facilitate the removal of the on-premise (2013) versions of ESS, MSS and TeamRostering\r\nNote that the ApplConfig.xml in the webServer locations is never removed as that stores the customers configuration.\r\n\r\nTest hint(s):\r\nVerify a full backup is made for WebServer and WebConfig updates. Verify that DualClient and Access Control websites work.",null,8207]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7",null,null,null,"BI package FACT_Assigned_Activity deleted to many activities ","In case of night shifts on the previous day of the BI IL start date, the package FACT_Assigned_Activity would delete the activities after midnight belonging to those shifts.\nAs a shift on the previous day of the BI IL start date is not reloaded, those activities were lost.\nThis has been fixed.\n\nThe activities after midnight belonging to a shift starting on the previous day of the BI IL start date will not be deleted during an IL run,\n\nTest hint(s):\n1. Verify the activities after midnight belonging to a shift starting on the previous day of the BI IL start date will not be deleted during an IL run,","",5620,"14659444"]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7",null,null,null,"Add log and handle exception for Access violation when opening schedule","Additional logging was added for access violations while accessing user properties.\nThis change was implemented behind a feature toggle LogAccessViolationInUserProperty with default value N.\n\nTest hint(s):\nNone","",5868,""]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7",null,null,null,"A subcontracted night shift could not be set back to concept on the last day of department availability","When the status of a subcontracted overnight shift was set to Final planning and the corresponding employee was not available on the second day of the night shift, the status could not be set back to concept anymore.\nThis has been fixed.\nAdded feature toggle setting: EnableOvernightShiftStatusBackToConceptForUnavailableEmployee and is by default enabled\n\nTest hint(s):\n1. Create an overnight shift, subcontract it to another department, plan it at an employee and set the status to Final planning Set the end date of the availability of the employee to the second day of the overnight shift and verify that the status of the overnight shift can be set back to concept","",5952,"14736277"]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7\\Technical improvements",null,null,null,"A technical improvement was made to improve the performance of retrieving cost centers for a department in an interval","A technical improvement was made to improve the performance of retrieving cost centers for a department in an interval.\r\n\r\nTest hint(s):\r\nNone","",6051,""]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7",null,null,null,"Added extra information when validity period of a duty and a cost center mismatch error is raised during cost center import ","When importing a cost center validity period that does not match with the validity period of a duty the cost center was linked to, a consistency check fails as expected.\r\nThe raised error did not display specific information about the concerning cost center or duty to be able to take action.\r\nThis has been improved.\r\nThe import will now display the name code of the cost center as well as the name and duty set name (when applicable) of a concerning duty.\r\n\r\nTest hint(s):\r\n1. Verify the import of cost centers functions\r\n2. Verify changing attributes of a cost center in the win32 Client functions.","",6535,"14837564"]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7",null,null,null,"Added a monitoring query to detect nonRecurringDuties with a validity period of more than one day","Added a monitoring query to detect nonRecurringDuties with a validity period of more than one day\n\nTest hint(s):\nNone","",6788,""]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7",null,null,null,"Some self scheduling permissions were not visible in the 'ORTEC WS for Employees' category in Access Control","Several access control permissions for selfrostering in WS for Employees were located in the 'Employee Self Service (deprecated)', but were not visible in the 'ORTEC WS for Employees' category.\r\nThis has been improved.\r\nThe following permissions have also been added to the ORTEC WS for Employees' category.\r\n- guiactions.ows.UnplanShift\r\n- guiactions.ows.PlanDuty\r\n\r\n- guiactions.ows.ScheduleView.DutiesInDutyGroupAction- guiactions.ows.ScheduleView.ShiftDetailsAndOptionsAction\r\n\r\nTest hint(s):\r\n1. Verify the mentioned permissions are visible in Access Control under: ORTEC WS for Employees/Self Scheduling","",7513,14958928]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7",null,null,null,"Hint text was incomplete after replacing shift with activity type","A shifts hint text only showed the name of the original shift when it was replaced by activity type and  setting OPTIONS\\PLANBOARD\\REPLACEALLWITHACTIVITYTYPE\\SAVESHIFTBEFORELEAVEWHENREPLACEACTIVITYTYPEININTERVAL was enabled.This has been fixed.\n\nThe hint text will now display the name of the original shift and other configured elements.\n\nTest hint(s):\n1. Verify the hint text of a shift has all configured elements after replacing a shift by activity type.","",7624,14974585]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7",null,null,null,"Minimum rest time for a series of relief days does not violate on the last day of a rosterperiod","The labor rule \"minimum rest time for a series of relief day shifts\" did not show a violation when the relief day was planned on the last day of a schedule and the interval to the next work shift was smaller than specified in the rule. \nThis has been fixed.\n\nTest hint(s):\n1. Create a labor rule in which the minimum rest time for a series of relief day shifts is specified. \n2. Plan a work shift, day-off shift and work shift consecutively, where the day-off shift is planned on the last day of a schedule and such that the relief time is shorter than specified in the labor rule. \n3. Verify that a violation is shown on the last work shift.","",7793,""]
[null,null,1530916,"2023-02-02",null,"Development\\OWS7",null,null,null,"UnattendedUpdates: Rolling out manual updates failed for _ClientCEF.zip","UnattendedUpdates would raise an error on file deletion during rollout of a _ClientCEF update.\nThis has been fixed.\nRolling out a ClientCEF, WebServer and WebConfig update will no longer delete the existing files before placing the updated ones, but overwrite them.\nNote this issue was introduced in  8.5.0-1528349 (2023-01-19)\n\nTest hint(s):\n1. Verify that rolling out a ClientCEF, WebServer and WebConfig update does not raise errors.","",8420,15067538]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"ORTEC WS for Managers displayed leave requests without an end date ","Requests for (special) leave without an end date were shown in ORTEC WS for Managers.\r\nThis has been improved.\r\nORTEC WS for Managers will only show requests with an end date.\r\nNote that such requests were entered by the AbsenceFlow interface and not by regular usage of the Win-32 Client or WS for Employees\r\n\r\nTest hint(s):\r\n1. Verify that only leave requests with an end date are shown in WS for Managers.","","5294",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"Cancelled double subcontracted shift was not removed visually from vacant shifts after being moved to planboard","When cancelling a double subcontracted shift and then planning it to an employee, the shift was still shown in the vacant shifts section.\nThis has been fixed.\n\nTest hint(s):\n1. Subcontract a shift from department A to department B and then from department B to department C \n2. Cancel the double subcontracted shift in department A and plan it to an employee. \n3. Verify that the shift is planned and not visible in the vacant shifts anymore.","","5670",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"Added Department Id to Ros_Optimizer_Runs table","Added Department Id to Ros_Optimizer_Runs table\n\nTest hint(s):\n1. Verify that Ros_Optimizer_Runs table has a column DPT_ID. \n2. Verify that after new optimizer runs, entries in Ros_Optimizer_Runs also include the department id in the DPT_ID column.","","5873",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"Replace by leave of absence did not work for subcontracted shifts","The option 'Replace by leave of absence' did not work for a subcontracted shift.\nThis has been fixed.\nNow a subcontracted shift can be replaced by leave of absence by the planner of the department the shift has been subcontracted to.\nAdded feature toggle ReplaceByLeaveOfAbsenceSubcontractedShift which is enabled by default.\n\nTest hint(s):\n1. Subcontract a shift from one department to another and then plan it. \n2. Select this shift, choose 'Replace by leave of absence' and verify that the subcontracted shift is unplanned and replaced by a leave shift.","","6057","14736513"]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"Firebase mobile API - Permissions could not always be verified to create shift bidding notifications","Permissions could not always be verified to create shift bidding notifications using the firebase mobile api.\nThis has been improved.\n\nTest hint(s):\n1. Verify command handler CGetEmployeesThatCanBidOnShifts still works","","6337",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"Forbidden violations were possible in Realizations of Approved shifts","When realizing an approved shift, it was possible to create a forbidden violation even though the user had no authorization to do this (ALLOW_VIOLATION_101632_JUST Create violation in status justified or higher).\nThis has been fixed.\nNow the user gets an error telling it is not possible to create a violation in the realization of an approved shift.\nAdded feature toggle CHECKAUTHORIZATIONFORCREATINGVIOLATIONINREALIZATIONOFAPPROVEDSHIFT and is enabled by default.\n\nTest hint(s):\n1. Plan a shift to an employee and set the schedule status to Processed \n2. Create a realization for the shift in which the workstation is set to a workstation for which the employee does not have the required skills. In the Employee form (tab Employment Conditions), set 'Entries for approved schedules known until date' to a date after the shift \n3. Approve the realization and verify that an error is shown telling the user it does not have the authorization to create a violation in the realization of an approved shift","","6783",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7\\Technical improvements",null,null,null,"Access Control: the performance of a query that is used to load data for access control management was improved. ","Access Control: the performance of a query that is used to load data for access control management was improved.\n\nTest hint(s)\n1. Use Access Control to administer permissions","","6787","14852544"]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7\\Technical improvements",null,null,null,"A performance improvement was implemented for self rostering","A performance improvement was implemented for self rostering. This change was done behind a feature toggle REDUCEHIERARCHICCRITERIACALCULATIONS, which is enabled by default.\r\n\r\nTest hint(s):\r\nNone","","7218",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - warnings from previous unsuccessful runs were not displayed in final success mail","When a warning was raised and the UnattendedUpdates script failed afterwards, the next successful script run would not mention the warning (i.e. a DBUpdate warning) from the failed run in the final email.\nThis has been improved.\nWarnings are now stored in the UpdateProgress.xml file. When the script finishes successfully, warnings from previous failed runs will be mentioned in the final success email.\nNote: this only applies for the script option 'useProgressTracking', which is enabled by default.\n\nTest hint(s):\nNone","","7374",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"MaxLabourTimeSaldoReq first calculates violations, then checks employee properties","Before doing the calculations of the labor rule 'Maximum labour-time based on account balance', the checks on employee properties, salary group and age are now checked first to determine whether the calculations need to be done. This can improve the performance of this labor rule.\r\nAdded feature toggle CheckEmployeePropertiesBeforeCalculatingMaxLabourTimeSaldoReq and is by default enabled.\r\n\r\nTest hint(s):\r\nNone","","7570",14962368]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"Overlapping requests were sometimes shown only once when they are violated in ORTEC WS Win32 client planboard","Overlapping requests are sometimes shown only once when they are violated in ORTEC WS Win32 client planboard. \nThis has been fixed.\nPlease note that in the following cases, only one violation will still be shown:\ni. When a (No) work during a period request overlaps with a recurring request.\nii. When a duty request overlaps with a recurring shift request on the same duty name/type.\nThis change is behind feature toggle AllowWorkInIntervalWishandWishWithShiftToCreateMultipleViolationsIfNeeded which is enabled by default.\n\nTest hint(s):\n1. Verify that all violations of overlapping requests are shown in ORTEC WS Win32 client planboard except for the cases mentioned above.","","7591","14872084"]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7\\OWS for Employees",null,null,null,"ORTEC WS for Employees: Shiftbidding showed wrong results for night shifts using labor rule 'Maximum/minimum labor time of shifts'","Shiftbidding in ORTEC WS for Employees showed wrong results for night shifts using labor rule 'Maximum/minimum labor time of shifts'.\nThis has been improved.\nThe violations being calculated for this rule now correctly consider the day shift length, night shift length and the other shift length.\nNote: the exception to this rule (to ignore this maximum x times a year) is not supported when using shift bidding through ORTEC WS for Employees. This was already the case and has not been changed.\n\nTest hint(s):\n1. Verify shift bidding options in ORTEC WS for Employees are correctly shown when using night shifts and labor rule 'Maximum/minimum labor time of shifts'","","7650",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7\\Technical improvements",null,null,null,"ORTEC WS for Employees: Planning an alternative in Self Scheduling in Round 2 could give a \"Something went wrong\" message","ORTEC WS for Employees: Planning an alternative in Self Scheduling in Round 2 could give a \"Something went wrong\" message\nThe analysis of issue #7330 found that the cause was most probable was a wrong protection of the internal resources involved in this functionality under a high load.\nThis has been improved.\n\n\nThis change is behind feature toggle ImproveSelfRosterUnPlanShiftPlanDutyLocks which is enabled by default.\n\nTest hint(s)\n1. Verify that during Self Scheduling in Round 2 alternatives can be planned in.","","7728",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"Added feature toggle for future improvement","In preparation for future improvement 8384, added feature toggle ReduceMemoryUsageWhenVerticalCalculationsAreCollapsed which will be enabled by default.\n\nTest hint(s);\nNone","","8383",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7\\Technical improvements",null,null,null,"Some settings of the chromium component were made configurable","Some settings of the chromium component were made configurable in Registry.\r\nHKEY_LOCAL_MACHINE\\Software\\WOW6432Node\\ORTEC\\Comtec\\CWGS\\EnableCEFSafeBrowsing\r\nThis can be enabled to add enable Googles Safe-Browsing feature. Since we only connect to local, known websites, this is disabled by default.\r\nHKEY_LOCAL_MACHINE\\Software\\WOW6432Node\\ORTEC\\Comtec\\CWGS\\EnableCEFLogSeverityDebug\r\nThis can be enabled to add additional logging output from the chromium component, this is disabled by default.\r\nIf they are not provided in the registry, both will default to False.\r\n\r\nThe values can be added in the registry in order to change them.\r\nAdd the mentioned registry settings as type REG_SZ with value True or False. \r\n\r\n\r\nNote these settings should be added on the client machine.\r\n\r\nTest hint(s):\r\nNone","For this solution to become available, the ORTEC WS Win32 client must be installed.","8460",""]
[null,null,1533112,"2023-02-16",null,"Development\\OWS7",null,null,null,"Overview shift reassignments could not be opened for two shifts on same date for different departments","When opening the \"Overview shift reassignments\" for two shifts of different departments on the same date, an error occurred.\nThis has been fixed.\n\nTest hint(s):\n1. Have an employee X attached to two departments A and B and plan a shift to employee X in department A \n2. Plan a second shift to another employee in department B on the same date with non-overlapping times and set the status of this schedule to Published \n3. Move the second shift to employee X and verify that \"Overview shift assignments\" can be opened for the two shifts on the same day","","8765",15168201]
[null,null,1535556,"2023-03-02",null,{"$f":"F1120","v":"Development\\OWSforTeamSchedulers"},null,null,null,"[OWS] BackendEventPublisher: Clean up settings","Removed the following redundant settings:\r\nBackendEventPublisher\\URLs\\ReschedulingIntegrationServiceURL BackendEventPublisher\\CloudTenantNames\\ReschedulingIntegrationServiceCloudTenantName  \r\nRemoved logic that was using these settings.","","4756",""]
[null,null,1535556,"2023-03-02",null,"Development\\OWS7",null,null,null,"Overlap was checked for employees linked to a department during loading data which could cause a slow CWSS Server process startup","Overlap of rotation unit lines was checked on startup of CWSS server process, causing it to be slow. This has been improved.\r\nOverlap of rotation unit lines is now only checked when adding new lines.\r\n\r\nIt is possible to still enable the overlap check on startup using a newly introduced setting UseCheckRotationUnitLineOverlapOnLoad, default 'False'.\r\nNote: The server startup time can improve significantly for customers with many rotation unit lines","","8123",""]
[null,null,1535556,"2023-03-02",null,"Development\\OWS7",null,null,null,"Performance of opening planboard was improved when having collapsed vertical calculations ","Performance of opening planboard was improved when having collapsed vertical calculation\r\nFunctionality was implemented behind a feature toggle ReduceMemoryUsageWhenVerticalCalculationsAreCollapsed, which will be enabled by default.\r\n\r\nTest hint(s):\r\nVerify (collapsed) vertical calculations in a planboard work as expected","","8384",""]
[null,null,1535556,"2023-03-02",null,"Development\\OWS7",null,null,null,"Addresses of employees were shown when not necessary","Addresses of employees were shown when not necessary.\r\nThis has been improved.\r\nAddresses that belong to an employee are now only visible when assigning an address to an employee.\r\n\r\nTest hint(s):\r\nVerify addresses belonging to an employee are visible when assigning an address to an employee. Verify addresses belonging to an employee are not visible when assigning an address to a duty, organization or physical location.","For this solution to become available, the ORTEC WS Win32 client must be installed.","8588",""]
[null,null,1535556,"2023-03-02",null,"Development\\OWS7",null,null,null,"Queries on contracts in the backend API are sometimes slow","Queries on contracts in the backend API were sometimes slow.\r\nThis has been improved.\r\n\r\nTest hint(s):\r\nNone","","8603",15094540]
[null,null,1535556,"2023-03-02",null,"Development\\OWSforTeamSchedulers",null,null,null,"Team Scheduler - When dutyset duties were not valid for the entire scheduling period, it was impossible to change the shift demands.\nThis has been fixed.","When dutyset duties were not valid for the entire scheduling period, it was impossible to change the shift demands.\nThis has been fixed.","","8736",15166556]
[null,null,1535556,"2023-03-02",null,"Development\\OWS7",null,null,null,"Queries on shifts through the EMSS backend API were sometimes slow","Queries on shifts through the EMSS backend API were sometimes slow\r\nThis has been improved\r\n\r\nTest hint(s):\r\nNone","","8875",15174635]
[null,null,1535556,"2023-03-02",null,"Development\\AUTH0",null,null,null,"With the previous patch (1533112), an issue was introduced causing that users were not synchronized to Auth0 anymore.\nThis has been fixed.","With the previous patch (1533112), an issue was introduced causing that users were not synchronized to Auth0 anymore.\nThis has been fixed. Now, users that are added in Access Control with authentication method 'Auth0 user database', will be synchronized to Auth0 again.\n\nTest hint(s):\nAdd a user in Access Control with authentication method 'Auth0 user database'. Verify that the user receives an email from Auth0.","","9238",15209772]
[null,null,1535556,"2023-03-02",null,"Development\\OWS7",null,null,null,"Several small performance improvements have been implemented within ORTEC WS. ","Several small performance improvements have been implemented within ORTEC WS. For example:\n- Improvements in several plan board grids (e.g. shift counter grid)\n- Improvements in opening a planboard and retrieving violations\n- Improvements in client-server communication \n- Improvements in server startup time\n- Improved handling of planboard updates in case there are no open planboards (e.g. in interfaceworkers)\n\nPlease note that these are small improvements which, individually, might not be directly noticeable for everyone.\nAll together they will have a beneficial effect on the performance of ORTEC WS and it is advised to apply this update at all customers that face a performance risk.\n\nThis is part one of a larger performance improvement package. Part two will be included in the next ORTEC WS update.",null,"6188, 6189, 6190, 6191, 6192, 6193, 6194, 6195, 6196, 6751, 8075, 9088"]
[null,null,1537826,"2023-03-16",null,"Development\\OWS7",null,null,null,"ORTEC WS for Employees: Improved performance for duty proposal when labor period rules are involved. ","ORTEC WS for Employees: Improved performance for duty proposal when labor period rules are involved.\r\nThe duty proposal that is returned to the backend API and front end calculated the violation text.\r\nThis has been improved \r\nThe violation text is not used/displayed in the front end, so it us no longer calculated during a duty proposal calculation for the front end.","","6404",""]
[null,null,1537826,"2023-03-16",null,"Development\\OWS7",null,null,null,"Checking same permissions multiple times during single transaction could degrade performance","Checking same permissions multiple times during single transaction could degrade performance\r\nA performance improvement has been implemented to avoid checking a permission multiple times during a single transaction.\r\nThis improvement was added behind feature toggle \"FeatureToggles\\CachePermissionCheckCallsForDescriptions\" and is by default enabled,\r\n\r\nTest Hint(s)\r\n- Very opening a planboard in OWS Win32 Client works as expected","","6988",""]
[null,null,1537826,"2023-03-16",null,"Development\\OWSforTeamSchedulers",null,null,null," ORTEC WS for Team Schedulers: Access Control permissions have been added","New Access Control permissions have been added for ORTEC WS for Team Schedulers. They can be found in the ORTEC WS for Team Schedulers permission category.\nThe new permissions are:\nApprove leave requests - Without this permission it is not possible to approve or decline leave requests in the leave requests dashboard tile. Approve swap requests - Without this permission it is not possible to approve or decline swap requests in the swap requests dashboard tile. Replace with sick leave shifts - Without this permission it is not possible to replace shifts with sick leave in the sick leave dashboard tile. Publish schedules - Without this permission it is not possible to set the status of a schedule to Published. Close schedules - Without this permission it is not possible to set the status of a schedule to Closed.\n Edit schedules - Without this permission it is not possible to do any mutations in the schedule view.  Note: The existing Team Schedulers permission \"Allowed to start Optimizer\" now also needs the \"Edit schedules\" permission.","These new permissions are automatically checked after the BDA is updated. If the ORTEC WS for Team Scheduler frontend is not yet deployed (which hides certain menu options and buttons based on the permissions), this could mean that the user still has the option in the UI but gets an error message after performing the action.\r\nTo prevent this potential issue and to prevent backwards compatibility, Access Control user groups that had the general \"Team scheduler (departments)\" permission will automatically receive these new permissions when the BDA is updated.",8599,""]
[null,null,1537826,"2023-03-16",null,"Development\\OWS7",null,null,null,"The schedule optimizer in the ORTEC WS Win32 client could create violations when shift sequences are used","The schedule optimizer could create violations when shift sequences were used.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nVerify that schedule optimizer does not create any violations when shift sequences are used.","","8608","https://ortec.link/Request?HID=15096430"]
[null,null,1537826,"2023-03-16",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS for Team Schedulers: Added translations for Access Control","For team scheduling permissions translations are added for the German language.\n\nTest hint(s):\nNone","","8610",""]
[null,null,1537826,"2023-03-16",null,"Development\\OWS7",null,null,null,"Added option to filter out shifts with certain treatments from swap options in BackendAPI","Added the option to filter out shifts which contain a certain treatment from the swap options in WS for Employees and ESS7 App (backendAPI)\r\nThis has been done for illness and leave shifts which would be replaced with an AbsenceCode in other forms.\r\nAs such shifts are normally not eligible for a swap request, they will be filtered out.\r\nAn OWS Settings Manager setting has been added to configure what treatments are used to filter out shifts.\r\nOptions - CommandHandlers - TGetExchangeOptions: TREATMENTSTOEXCLUDEFROMEXCHANGEOPTIONS\r\nDefault value: 'ADV, DAYOFF, COMPDAYOFF, COMPLEAVE, ILLNESS, ILLNESSNL, ILLNESSNLNR, ILLNESSNW, ILLNESSNWNR, LEAVE, VACATION, VACATIONNL, VACATIONNW'\r\nWhen a shift contains any activity for which the treatment is configured in this setting, the shift is no longer shown as a swap option.\r\nThe treatmentlist in this setting can be adjusted to suit the customers needs. I.e. When swapping with a DayOff shift should be allowed, DAYOFF can be removed from the treatmentlist.\r\nWhen the setting is emptied, no filtering will be applied as was the case before this change.\r\n\r\nTest hint(s):\r\n1. Verify that shifts containing a treatment configured in setting TREATMENTSTOEXCLUDEFROMEXCHANGEOPTIONS are no longer shown as a swap option in WS for Employee and ESS7 App (BackendAPI)","","8733",""]
[null,null,1537826,"2023-03-16",null,"Development\\OWS7",null,null,null,"Several translations added for German","Several translations have been added for German for recent functional changes.\n\nTest hints:\nNone","","9285","https://ortec.link/Request?HID=15220518"]
[null,null,1537826,"2023-03-16",null,"Development\\OWS7",null,null,null,"First installation of BackendAPI did not set the SSL certificate on website binding","In case the website binding option 'Require Server Name Indication' was configured (default), the BackendApi installation script would not set the certificate on first installation. This has been fixed.  The installation script will now follow normal IIS certificate behavior. - In case Require Server Name Indication is enabled, the certificate will only be set to the installed website binding. - In case Require Server Name Indication is disabled, the certificate will be set to all website bindings which also have Require Server Name Indication disabled and have the same combination of port and ip address.  Also improved. The script could set an invalid certificate (expired or future). The script will now only link valid certificates. In case multiple valid certificates exist with the same common name, the certificate with the longest validity will be used.\r\n\r\nTest hint(s):\r\n1. Verify the script will add the desired certificate to the website binding.\r\n2. Verify that the certificate with the longest validity is used in case multiple valid certificates exist.","","9290","https://ortec.link/Request?HID=15220666"]
[null,null,1537826,"2023-03-16",null,"Development\\OWS7",null,null,null,"German translations added for accounts","ORTEC WS Win32 Client: For the accounts export to excel , the 2 time columns (From/Till) are now correctly translated to the user's language\r\n\r\nTest hint(s):\r\nORTEC WS Win32 Client: Export account to excel (eg. Annual hours) and verify that the header of the 2 time columns (From/Till, Van Tot in Dutch) are now correctly translated to the user's language","For this change to become available, the OWS Win32 client needs to be updated","9296","https://ortec.link/Request?HID=15221824"]
[null,null,1537826,"2023-03-16",null,"Development\\OWS7",null,null,null,"Forbidden Violations still possible in Approved Schedule after new release","When realizing an approved shift, it was possible to create a forbidden violation even though the user had no authorization to do this (permission ALLOW_VIOLATION_101632_JUST Create violation in status justified or higher). This has been fixed. Now the user gets an error telling it is not possible to create a violation in the realization of an approved shift. \r\n \r\n This issue was introduced earlier during 6783, release 8.5.0(2023-02-16)_Build1533112.\r\n\r\nTest hint(s): Create a labor of type \"Cost center of activity\". Plan a shift with a cost center added to the activity to an employee and set the schedule status to Approved Create a realization for the shift in which the cost center is set to (none) Approve the realization and verify that an error is shown telling the user it does not have the authorization to create a violation in the realization of an approved shift","","9398","https://ortec.link/Request?HID=15275551"]
[null,null,1537826,"2023-03-16",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS for Team Schedulers: Performance of checking permissions has been improved","Improved performance by adding permission checks to a cache. This cache has an expiration time of 15 minutes.\r\nUpdating permissions could take up to 15 minutes for being processed.\r\nTest hint:\r\nUpdate permissions and see it being processed within 15 minutes.","","9633",""]
[null,null,1538813,"2023-03-22",null,"Development\\OWS7",null,null,null,"When checking the validity of the activity type of an imported leave failed it could could halt an interface worker.","When checking the validity of the activity type of an imported leave failed it could could halt an interface worker.\r\nIf an imported leave wish did not have a valid activity type within validity period of the leave wish i.e. by not including an ate_code in the import, this could halt the worker.\r\nThis has been improved.\r\n When a leave wish without a valid activity type is imported the import will show an error and will continue.\r\n\r\nTest hint(s)\r\nimport a leave wish and verify it is imported correctly","","8782","https://ortec.link/Request?HID=15169274"]
[null,null,1538813,"2023-03-22",null,"Development\\OWS7",null,null,null," Make shift remarks available in the workstation planboard and in the workstation employee proposal screen","Shift remarks are now available in the workstation planboard and in the workstation employee proposal screen\r\n\r\nTest hints:\r\nVerify that it is possible to add/update shift remarks In the workstation planboard  (similar to doing so in the regular planboard) Verify that these shift remarks are also shown in the employee proposal window in the remarks section.","For this solution to become available, the ORTEC WS Win32 client must be installed","9068",""]
[null,null,1538813,"2023-03-22",null,"Development\\OWS7",null,null,null,"Account(s) not visible in drop down menu","When opening the ORTEC WS Win32 Client without opening a planboard, not all available accounts were visible in the Accounts drop down menu.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nAdd a new account and restart the client. Open the client without opening a planboard and verify that the new account is visible in the Accounts drop down menu","For this solution to become available, the ORTEC WS Win32 client must be installed","9074","https://ortec.link/Request?HID=15189380"]
[null,null,1538813,"2023-03-22",null,"Development\\OWS7",null,null,null,"Error in handling and recording changes in auditing tables could cause CWSSServer process to stop responding ","Error in handling and recording changes in auditing tables could cause CWSSServer process to stop responding  \r\nThis was introduced by issue #6196 releases in #9049 \r\nThis issue reverts these changes.\r\n\r\nTest hint(s)\r\nverify auditing tables are processed correctly when configured","","9778","https://ortec.link/Request?HID=15311982"]
[null,null,1541079,"2023-03-31",null,"Development\\OWSforAdHocPlanners",null,null,null,"[AHP] Added functionality to add and edit the shift remark in Ad Hoc Planning","Added functionality to add and edit the shift remark in Ad Hoc Planning. This can be done via the shift details in the schedule, and when offering a shift.\n\nTest hint(s):\nOpen the shift details, and add or edit the shift remark Offer a shift. Add or edit the shift remark in the dialog where the details of the shift to offer can be edited.","","7705",""]
[null,null,1541079,"2023-03-31",null,"Development\\OWS7",null,null,null,"Demanded duty skills were not taken into account when requesting swap options for a shift","When an employee requested swap options for a shift, the recently delivered functionality of demanded duty skills was not taken into account. \nThis means that employees could create or worsen missing skill requirements by swapping shifts.\nThis has been improved.\nORTEC WS for Employees and all ESS App versions will no longer propose an employee for a swap if the swap would create or worsen a missing skill requirement when using demanded duty skills.\n\nTest hint(s): \n Verify that ORTEC WS for Employees and the ESS App will no longer propose an employee for a swap if the swap would create or worsen a missing skill requirement when using demanded duty skills.","","9286",""]
[null,null,1541079,"2023-03-31",null,"Development\\OWSforAdHocPlanners",null,null,null,"Translations for Finnish","Several translations have been added for Finnish for using Ad Hoc Planning.\n\nTest hint(s):  \nNone","","9379",""]
[null,null,1541079,"2023-03-31",null,"Development\\OWS7",null,null,null,"For a customer with many cost centers,  opening a shift was slow","For customers with a large amount of costcenters that need to be shown in a treeview in the shift form, opening this form from the plan board for the first time could take some time.\n\nThis is only relevant when the setting COSTCENTER\\SHOWCOSTCENTERSINTREE = TRUE and there are many costcenters, \nThis has been improved.\n\nTest hint(s):\nVerify that opening a shift from a plan board the first time now has a shorter waiting time.","For this solution to become available, the ORTEC WS Win32 client must be installed.","9402","https://ortec.link/Request?HID=15275679"]
[null,null,1541079,"2023-03-31",null,"Development\\OWS7",null,null,null,"Added additional logging in CGetDutyDemand command handler for analysis purposes","Additional logging was added to better analyze the CGetDutyDemand command handler call.\n\nTest hint(s):\nNone","","9644","https://ortec.link/Request?HID=15295900"]
[null,null,1541079,"2023-03-31",null,"Development\\OWS7",null,null,null,"Improve visual feedback on loading for forms by showing a waiting cursor during the loading of those forms","Small improvement to show waiting cursor while opening some forms e.g. the shift form\r\n\r\nTest hint(s):\r\nOpen a shift from the plan board. Verify the waiting cursor is show while the form is opening.","For this solution to become available, the ORTEC WS Win32 client must be installed.","9672",""]
[null,null,1543005,"2023-04-13",null,"Development\\OWS7",null,null,null,"Labor time and work agreement rules are extended with extra checkbox to filter on contract hours","A checkbox has been added to all existing labor time rules/work agreements, which makes it possible to apply the rule (only) to employees with certain contract hours (employment condition hours). It works similar to the existing checkboxes for age and employee property. The values for the contract hours parameter can be between 0 and 168 hours.\n\nPlease note that if multiple instances of a labor rule are configured for different contract hour ranges, all instances of the rule will still be checked for all employees.\nThis is because ORTEC WS first calculates violations and only afterwards applies the checkbox\n filters to decide if the violation should actually be shown/thrown. \nCreating multiple instances will therefore increase the total violation calculation time, albeit for many labor rules this is negligible. This was already the case for the existing checkboxes for age and employee property.\n\nTest hint(s) :\n1. Open labor time or work agreement rules and verify that you can now set an extra checkbox so the rule only applies to employees with contract hours between the set range","For this solution to become available, the ORTEC WS Win32 client must be installed.",10175,""]
[null,null,1543005,"2023-04-13",null,"Development\\OWSforTeamSchedulers",null,null,null,"Planboards in Teamscheduler won't open","Retrieving shift data was very slow when the database contained a lot subcontract data.\nThis has been improved.\n\nTest hint(s):\n1. Open the schedule for a department Open shift details","",10181,"https://ortec.link/Request?HID=15336154"]
[null,null,1543005,"2023-04-13",null,"Development\\OWS7",null,null,null,"Module modBasic could not be viewed and toggled on/off in OWS Settings manager","Module modBasic could not be viewed and toggled on/off in OWS Settings manager. It would show an error that a setting did not exist.\nThis has been fixed.\nNote this issue was introduced in version OWS 7 update 1541079 (2023-03-31).\n\nTest hint(s):\n1. Verify that viewing ModBasic in the OWS Settings Manager does not return an error.","",10216,""]
[null,null,1543005,"2023-04-13",null,"Development\\OWS7",null,null,null,"Missing cost centers in duty window when the cost center tree view was used","Incorrect cost centers were shown in the cost center tree on the Activity and Description tabs of duty forms when an incorrect validity period for the selected duty was used to check the available cost centers.\nThe issue has been resolved. \nA feature toggle 'LoadAllCostCentersInTreeView', disabled by default, has been added to toggle between the current (fixed) behavior when it is disabled and the behavior from before the performance improvements when it is enabled.\n\nThis is only relevant for configurations that have the OWS Setting COSTCENTER\\SHOWCOSTCENTERSINTREE enabled.\n\nNote this issue was introduced in issue 9402 in OWS 7 update 1541079 (2023-03-31)\n\nTest hint(s):\n1. Verify that the shift form shows the correct cost centers in the tree when opening different shifts.","For this solution to become available, the ORTEC WS Win32 client must be installed.",10254,"https://ortec.link/Request?HID=15401326"]
[null,null,1544616,"2023-04-26",null,"Development\\OWSforTeamSchedulers",null,null,null,"Subcontracted shifts cannot be changed in TS in case schedules have different statuses","Subcontracted shifts could not be changed in case the schedules had different statuses.\nThis has been fixed. Now, the status of the shift is lowered to the status of the original department, instead of to the status of the current department.\n\nTest hint(s):\nEdit a shift that is subcontracted to another department","",10243,"https://ortec.link/Request?HID=15395728"]
[null,null,1544616,"2023-04-26",null,"Development\\OWS7",null,null,null,"Several translations added for German","Several translations added for German\r\n\r\nTest hint(s):\r\nNone","",10405,"https://ortec.link/Request?HID=15410774"]
[null,null,1544616,"2023-04-26",null,"Development\\OWS7",null,null,null,"Feature toggle UseEnglishForStatusConversion has been removed","Feature toggle USEENGLISHFORSTATUSCONVERSION has been removed\r\n\r\nTest hint(s):\r\nNone","",6785,""]
[null,null,1544616,"2023-04-26",null,"Development\\OWS7",null,null,null,"Scaling issues in the ORTEC WS Win32 Client after opening Data Management or Access Control","Opening the Access Control or Data Management form could rescale the win32 client if the new Chromium component was used and the monitor was scaled to more than 100% in the Windows display settings.\r\nThis could lead to a mix of scaling in some win32 client forms and their contents after Data Management or Access Control was opened, causing not all form contents to be within the forms boundaries.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\n- Verify that the win32 client does not rescale when opening Access Control or Data Management forms.\r\n- Verify that the win32 client forms and their contents have the same scaling after opening Access Control or Data Management forms.","For this solution to become available, the ORTEC WS Win32 client must be installed.",9133,"https://ortec.link/Request?HID=15199142"]
[null,null,1546767,"2023-05-12",null,"Development\\OWS7",null,null,null,"In the workstation planboard, it is now possible to show skill violations in the bottom section of the planboard","In the workstation planboard, it is now possible to show skill \nviolations in the bottom section of the planboard (as a border color on \nworkstation items).\nCombined with the staffing information \nshown in the same section, this makes it easier to see at a glance if \nthere are any issues in the occupation of workstations.\nTo\n show the skill violations, a new display option has been added called \n\"Skill violations\" which can be added to the Workstation item border \ncolor settings.\n\nTest hint(s):\nCreate the labor rule of type Skills and create a skill violation on a shift.  Go\n to the workstation planboard and verify that the created skill \nviolation is shown in both screens with a border around the shift","For this solution to become available, the ORTEC WS Win32 client must be installed.",10258,""]
[null,null,1546767,"2023-05-12",null,"Development\\OWS7",null,null,null,"Added index on column CODE in ROS_COST_CENTERS","Querying costcenters could be slow when having a large amount of costcenters.\nThis has been improved.\nAn index is added on the column CODE in ROS_COST_CENTERS\n\nTest hint(s)\n- None","",10300,"https://ortec.link/Request?HID=15403825"]
[null,null,1546767,"2023-05-12",null,"Development\\OWS7",null,null,null,"Added index on column CODE in ROS_SHIFTS","Querying shifts could be slow when having a large amount of shifts. This has been improved. An index is added on the column CODE in ROS_SHIFTS\n\nTest hint(s)\n- None","",10301,"https://ortec.link/Request?HID=15403829"]
[null,null,1546767,"2023-05-12",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS for Team Schedulers: An 'Internal Server Error' happened when a user tried to update or delete a non-existing shift ","An 'Internal Server Error' happened when a user tried to update or delete a non-existing shift for ORTEC WS for Team Schedulers.\r\nThis has now been fixed.\r\nTest hints:\r\n1. Update a shift\r\n2. Delete a shift","",10710,""]
[null,null,1546767,"2023-05-12",null,"Development\\OWS7",null,null,null,"Several translations improved for German","Several german translations have been improved for module duty generator.\r\n\r\nTest hint(s):\r\nNone","",10721,"https://ortec.link/Request?HID=15462003"]
[null,null,1546767,"2023-05-12",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS for Team Schedulers: Fix access violation in CIncreaseOrDecreaseRequiredAmountForDuty handler","Increasing shift demands failed with a 500 response in case the related duty set did not have a demand configured.\r\nThis has now been changed.\r\nA 400 response is now returned as it is still not allowed to change the shift demand when there is no demand configured.\r\n\r\nTest hint(s):\r\nIncrease the shift demand of a duty set without a configured demand.","",10724,""]
[null,null,1546767,"2023-05-12",null,"Development\\OWS7",null,null,null,"Added calculation list information to logline when switching horizontal calculation list","To improve the analysis of performance, the logging of TCOServerHorizontalStatisticGridManager.GetPropertiesForCells has been extended.\nThe calculation list name, id and classname have been added to the logline.\n\nTest hint(s):\n- None","",8052,"https://ortec.link/Request?HID=15037548"]
[null,null,1546767,"2023-05-12",null,"Development\\OWS7",null,null,null,"Unattended Update returned error in case the environment was already up to date","When Unattended Updates determined that OWS was already up to date and nothing needed to be done, this was incorrectly marked as an exception and emailed to the email recipients for exceptions. \r\nThis has been fixed.\r\nWhen Unattended Updates filters out update files that are already installed and no update files remain after this step, the script will stop and send a more friendly message to the email recipients for success.\r\nThis will state that the environment is up to date and the update process has been skipped.\r\nMail subject: \"Automatic update process skipped for customer X\"\r\nMail body: \"Notification at step: Preparation before update - Update file preparation and filtering. No relevant updates are left after filtering. This environment is up to date. Script finished\"\r\n\r\n\r\nNote that an exception will still be raised when no update files are present before the filter updates step.\r\nAs this might indicate:\r\n- An error during update file retrieval\r\n- Download updates being disabled and updates have not been supplied manually\r\n\r\nTest hint(s)\r\n- Verify that when running unattended updates on a system that is already up-to-date, that the mail indicating there are no updates required has changed to a more friendly notification and is no longer sent to the email recipients for exceptions.","",8323,"https://ortec.link/Request?HID=15062736"]
[null,null,1546767,"2023-05-12",null,"Development\\OWS7",null,null,null,"Added error message when importing property value that's not Y/N/True/False","Importing user property values that are not Y/N/True/False were imported as N by default, leading to unexpected imported values.\r\nThis has been fixed.\r\nNow, an error is shown and importing the user property value will fail if it is not Y/N/True/False.\r\n\r\nThis change has been added behind feature toggle CHECKBOOLEANSWHENIMPORTINGUSERPROPERTYVALUES and enabled by default.\r\n\r\nTest hint(s)\r\n- Verify that feature toggle CHECKBOOLEANSWHENIMPORTINGUSERPROPERTYVALUES is turned on.\r\n- Verify that importing an unsupported user property value will fail and show an error.","",8401,"https://ortec.link/Request?HID=15063976"]
[null,null,1546767,"2023-05-12",null,"Development\\OWS7",null,null,null,"Added support for multiple recipients for BI success or failed emails","BI could only send an email to one recipient in case of success or failed.\r\nThis has been improved.\r\n\r\n\r\nIt is now possible configure the BI_CONFIG file to:\r\n- Accept multiple email recipients\r\n- Configure separate email recipient lists for failure or success emails\r\n\r\nTest hint(s) \r\nVerify that BI emails are delivered to the configured people both for success and for failure emails","To make use of this change, be sure to:\r\n\r\n1. Replace the BI.ps1 file\r\n2. Adjust the customers BI_config file\r\n  a. Add the following lines under [string]$MailTo = \r\n     [array]$MailToFAILED = \"\"               #Only required when $MailFAILED is set to $true. Multiple receivers can be added like \"receiver1@example.com\",\"receiver2@example.com\" etc.\r\n \r\n     [array]$MailToSUCCESS = \"\"           #Only required when $MailSUCCES is set to $true. Multiple receivers can be added like \"receiver1@example.com\",\"receiver2@example.com\" etc\r\n \r\n  b. Fill the new variables with the appropriate email addresses\r\n  c. Remove the line: [string]$MailTo = ''                    #Only required when $MailFAILED or $MailSUCCES is set to $true\r\nFor an example see: BI_Conifg_Template.ps1 \r\n\r\n\r\nNote: when BI.ps1 has been updated, but the BI_Config has not been adjusted, the script is backwards compatible and will use the recipient in the $MailTo variable for both success and failure emails",8522,"https://ortec.link/Request?HID=15078111"]
[null,null,1548532,"2023-05-25",null,"Development\\OWS7",null,null,null,"It is now possible to import an accounting line with type duration if the Registration functionality is activated","It is now possible to import an accounting line with type duration \nif the Registration functionality is activated. Previously it was only \npossible to import accounting lines with type amount.\nAn import of accounting lines with duration is only possible in a shift realization import using the TFillFieldsOfCOMTECShift ExtraXMLCreator.\nThe import can be achieved by adding the following subnodes to a <TLVNLDuty> within a realization import.\n\n<TAccountingLines>\n  <TAccountingLine>\n    <CCR_ID></CCR_ID>\n    <DURATION></DURATION>\n  </TAccountingLine>\n</TAccountingLines>\n\nIn order to allow the import, the following setting needs to be turned on (off by default):\nINTERFACES\\EXTRAXMLCREATORS\\FILLFIELDSOFCOMTECSHIFT\\ALLOWIMPORTACCOUNTINGLINEDURATION\n\nPlease note that the same checks apply to the import as performed in the \nClient on an accounting line with type duration \n(e.g. CHECKREGISTRATIONTIMEEQUALSWORKTIME)\n\nTest hint(s):\n- Verify accounting line durations can be imported by realisation import.","",10259,""]
[null,null,1548532,"2023-05-25",null,"Development\\OWS7",null,null,null,"Could not view account in WS for Employees due to incorrect published until date","When retrieving accounts in WS for Employees, the minimum date for which accounts can be retrieved (minimum published until date of the departments the employee is/was linked to) was determined incorrectly in case an employee had a link to a department that was not used anymore.\r\nThis has been fixed.\r\nSimilar to the MS report 'Account for Employee ESS', the BackendAPI will only look for linked departments in the period for which the accounts are requested.\r\nNote the underlying query has been revised. \r\nAdded feature toggle in: FeatureToggles\\UseImprovedQueryForEmployeePublishedUntil and is by default enabled.\r\nFurthermore, the exception message has been improved in case the user is not allowed to see account entries in the requested period. The name and published until date of the concerning department raising the exception have been added.\r\n\r\nTest hint(s):\r\n- Verify that the correct overview is shown if all schedules are published and opening an account on the Insights page of WS for Employees.","",10307,"https://ortec.link/Request?HID=15404092"]
[null,null,1548532,"2023-05-25",null,"Development\\OWS7",null,null,null,"Additional logging was added to analyze locking problems","Additional logging was added to analyze locking problems, more specifically for:\n- Time to enter FHandleSingleUpdateLock \n- Sleep time between handling updates  \n\nThe logging for 'Sleep time between handling updates' was implemented behind setting UpdateHandlerReceiveThreadSleepLogging, default value True.\n\nTest hint(s):\nNone","",10708,"https://ortec.link/Request?HID=15441180"]
[null,null,1548532,"2023-05-25",null,"Development\\OWS7",null,null,null,"Requests did not show properly upon opening the workstation planboard","When using Display settings with 'Visible days' and 'Visible interval', requests where sometimes displayed at incorrect times. Also sometimes an error message \"No overlapping intervals found\" was shown when refreshing the workstation planboard.\nThis has been fixed.\n\nTest hint(s): \n- Verify that requests are displayed correctly when opening a workstation planboard","For this solution to become available, the ORTEC WS Win32 client must be installed.",10709,"https://ortec.link/Request?HID=15441186"]
[null,null,1548532,"2023-05-25",null,"Development\\OWS7",null,null,null,"Filtered (conditional) index on ROS_SHIFTS has been added","In update 8.5.0(2023-03-02)_Build1535556 a filtered (conditional) index on ROS_SHIFTS was added. However, this was not added to OWS data model meaning the change was undone after the database update ran. \r\n\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nNone","",11268,"https://ortec.link/Request?HID=15519962"]
[null,null,1548532,"2023-05-25",null,"Development\\OWS7",null,null,null,"Skill demand calculation gave error when applying cyclical schedule with fixed shifts","Skill demand calculation gave error when applying cyclical schedule with fixed shifts.\nThis has been fixed.\n\nTest hint(s):\n- Check a cyclical schedule with fixed shifts can be rolled out.","",8710,""]
[null,null,1548532,"2023-05-25",null,"Development\\OWS7",null,null,null,"Candidates for a shift shows employee that has already been assigned another requested shift when 'Request to work and duty requests' is used as a shift proposal criteria ","Candidates for a shift shows employee that has already been assigned another requested shift when 'Request to work and duty requests' is used as a shift proposal criteria.\nThis has been fixed.\nPlease note that due to this fix, candidates for a shift cannot take a duty wish with multiple duty names into account. This fix is under the feature toggle, ConsiderCurrentShiftOnlyForDutyWishForRequestToWorkAndDutyRequests, which by default is turned on.\n\nTest hint(s)\n- Verify that Candidates for a shift shows correct employees in ORTEC WS Win32 client planboard when 'Request to work and duty requests' is used in shift proposal criteria.","",8766,"https://ortec.link/Request?HID=15168210"]
[null,null,1550417,"2023-06-08",null,"Development\\OWSforTeamSchedulers",null,null,null,"Added new permission for use in WS for Team Schedulers","Added a permission to AccessControl: Apply cyclical schedule & shift demands. This permission will be initially granted for users with the existing permission \"Edit schedules\".\nThis permission will be used in a new feature in OWS for Team Schedulers where the visibility of the action \"Apply cyclical schedule & shift demands\" will depend on the permission of the user.\n\nTest hint(s):\nVerify that the new permission \"Apply cyclical schedule & shift demands\" is visible in AccessControl.",null,"10068",""]
[null,null,1550417,"2023-06-08",null,"Development\\OWS7",null,null,null,"Technical change in locking mechanism","A technical change was made in the locking mechanism of ORTEC Workforce Scheduling.\r\nAmongst others, some logging was added.\r\nThis change was implemented behind a feature toggle CriticalSectionLockTryEnter, default value True.\r\n\r\nTest hint(s):\r\nNone",null,"10542",""]
[null,null,1550417,"2023-06-08",null,"Development\\OWSforTeamSchedulers",null,null,null,"Added additional logging to the Backend Domains API","Added extra logging to the Backend Domains API to be able to investigate non responsive or slow calls. The following information is now logged:\nThread usage, Slow queries, Slow command handler calls",null,"11130","https://ortec.link/Request?HID=15504428"]
[null,null,1550417,"2023-06-08",null,"Development\\OWS7",null,null,null,"Feature toggle MarkPlanboardAsDefectiveWhenAccessViolationOccurs was removed","Feature toggle MarkPlanboardAsDefectiveWhenAccessViolationOccurs was removed.\r\nPlanboards are now always marked as defective when an access violation occurs.\r\n\r\nTest hint(s):\r\nNone",null,"8143",""]
[null,null,1550417,"2023-06-08",null,"Development\\OWS7",null,null,null,"Incorrect period in the violation message of \"Number of free days on a weekday\" rule","When using a \"Number of free days on a weekday\" rule with the violation period set to a number of weeks, the violation message showed a violation period that started one day earlier than expected.\r\nThis has been fixed.\r\n\r\nTest hint(s)\r\n1. Verify that when \"Number of free days on a weekday\" is set to a number of weeks and that rule is violated, the shown violation message is stating the expected violation period",null,"8246","https://ortec.link/Request?HID=15059832"]
[null,null,1550417,"2023-06-08",null,"Development\\OWSforTeamSchedulers",null,null,null,"Added support to send shifts to their central department to the Backend Domains API","Added support in the Backend Domains API to send shifts to their central department.\nShifts cannot be sent when they are offered, subcontracted or already sent to the central department.\nThis functionality will only be enabled if setting 'UseCentralDepartments' is enabled.\nA permission has been added to Access Control for use in ORTEC for Team Schedulers: Edit shifts that are sent to a central department. This permission is revoked by default.\n\nTest hint(s):\n1. Enable setting 'UseCentralDepartments' and verify that shifts can be send to their central department. \n2. Open Access Control. Verify that the new permission \"Edit shifts that are sent to a central department\" is present in the ORTEC for Team Schedulers section.",null,"9337",""]
[null,null,1553220,"2023-06-22",null,"Development\\OWS7",null,null,null,"Removed unused parameter from 'Account for employee ESS'","The report 'Account for Employee ESS' used in WS for Employees contained a parameter (ID_Department) that was not actually used nor was it visible.\r\nTo accommodate a change for the future ESS7 Web version, this parameter has been removed.\r\n\r\nTest hint(s):\r\n1. Verify that the report 'Account for Employee ESS' can be opened and data is retrieved as dictated by the chosen parameter settings.","",10919,""]
[null,null,1553220,"2023-06-22",null,"Development\\OWS7",null,null,null,"Added isFixed attribute to BackendAPI shift routes","For a future development for ESS7, the existing backend API routes to retrieve shifts and defaultshifts have been extended. They now also return the IsFixed attribute.\r\n\r\ntest hint(s)\r\nnone","",11146,""]
[null,null,1553220,"2023-06-22",null,"Development\\OWS7",null,null,null,"Requesting account entries in WS for Employees could lead to an error for an employee without a department assignment","In OWS 7 update 1548532 (2023-05-25) an improved query was introduced to determine the published_until date of the employee when requesting account entries in WS for Employees.\r\nThis could lead to an exception in WS for Employees in case the employee did not have a department assignment in the default period of the account.\r\nThis has been fixed.\r\n\r\n\r\nWhen a customer has experienced this error and has turned off feature toggle UseImprovedQueryForEmployeePublishedUntil because of this. please re-enable the feature toggle.\r\n\r\nTest hint(s)\r\nVerify that requesting account entries in WS for Employees  for an employee that is not assigned to a department for the requested period, a correct published until date is returned.","",11664,"https://ortec.link/Request?HID=15604484"]
[null,null,1553220,"2023-06-22",null,"Development\\OWS7",null,null,null,"Report 'Employee Schedule Planner' could contain duplicates in the employee selection list","The employee selection list in the report ''Employee Schedule Planner'' could contain duplicates.\r\nThis has been fixed.\r\n\r\nTest hint(s)\r\nVerify that when opening report 'Employee Schedule Planner', there are no duplicate employees in the employee selection list. Specifically in the case when an employee was lend/borrowed to/from another department.","",8238,"https://ortec.link/Request?HID=15059550"]
[null,null,1553220,"2023-06-22",null,"Development\\OWS7",null,null,null,"Violation period for \"Working hours per period (general)\" was not displayed correctly","A violation of the labor rule \"Working hours per period (general)\"  would not correctly show the configured period in which the violation occurred. This has been fixed   The message now clearly states begin and end date of the period in which the violation occurred.\r\n\r\nTest hint(s)\r\nCreate a violation for rule \"Working hours per period (general)\"  and verify if the period mentioned in the violation message is correct.","",8335,"https://ortec.link/Request?HID=15062966"]
[null,null,1553220,"2023-06-22",null,"Development\\OWS7",null,null,null,"Feature toggle EnableOvernightShiftStatusBackToConceptForUnavailableEmployee has been removed","Feature toggle EnableOvernightShiftStatusBackToConceptForUnavailableEmployee has been removed.\r\nThis was added in 5952. Night shifts can now always be set back to concept on the last day of department availability.\r\n\r\nTest hint(s):\r\nCreate an overnight shift, subcontract it to another department, plan it at an employee and set the status to Final planning Set\r\n the end date of the availability of the employee to the second day of \r\nthe overnight shift and verify that the status of the overnight shift \r\ncan be set back to concept",null,8372,""]
[null,null,1553220,"2023-06-22",null,"Development\\OWS7",null,null,null,"Added options to limit the period to request account entries in the ORTEC WS Win32 Client","It was possible for a user to set the period for requesting a running account in the  ORTEC WS Win32 Client longer than desired, which could lead to bad performance or cause an Out of Memory exception. This has been improved. Two new settings have been added : OPTIONS/RUNNINGACCOUNTS/MAXNOFDAYSINPASTTOOPENRUNNINGACCOUNT (default value 400) OPTIONS/RUNNINGACCOUNTS/MAXNOFDAYSSHOWNINRUNNINGACCOUNT (default value 366)  With these default values, a user can now go up to 400 days in the past, and the requested period can have a total duration of 366 days.  A new authorization OWS/HMY/EXCEED_MAX_RUNNINGACCOUNT_PERIOD has been added to be able to overrule this limitation.  Note that the period for requesting a running account for a parent department is still limited to a year\r\n\r\nTest hint(s)\r\nverify that the new authorization is available in Access Control Verify that the 2 added settings are available in Settings Manager Verify that the set (or default) values are applied when setting the period in an account card filter.","For this solution to become available, the ORTEC WS Win32 client must be installed.",8754,"https://ortec.link/Request?HID=15167729"]
[null,null,1553220,"2023-06-22",null,"Development\\OWSforTeamSchedulers",null,null,null,"Preparations for new ORTEC WS for Team Schedulers feature \"Shift Offering\"","Preparations for new ORTEC WS for Team Schedulers feature \"Shift Offering\"",null,6003]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","Vacant shift was not correct after concept planned shifts","The amount of vacant shifts after applying duty demand was not correct when a shift was subcontracted to another department and planned there.\nThis has been fixed.\nThis change is behind the feature toggle IncludeSubContractedShiftsInNumberOfAssignedShifts, which is enabled by default.\n\nTest hint(s):\n- Verify that when applying duty demand again on a schedule when one of the shifts was subcontracted and planned on another department, the correct amount of vacant shifts are created.","","Vacant shift was not correct after concept planned shifts","The amount of vacant shifts after applying duty demand was not correct when a shift was subcontracted to another department and planned there.\nThis has been fixed.\nThis change is behind the feature toggle IncludeSubContractedShiftsInNumberOfAssignedShifts, which is enabled by default.\n\nTest hint(s):\n- Verify that when applying duty demand again on a schedule when one of the shifts was subcontracted and planned on another department, the correct amount of vacant shifts are created.","","10445","https://ortec.link/Request?HID=15413518"]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","New routes for Employee Self Service 7 front end are available in ORTEC WS Backend API to support new reporting functionality","New routes for Employee Self Service 7 front end are available in ORTEC WS Backend API to support upcoming reporting functionality\n\nTest hint(s):\n- None","","New routes for Employee Self Service 7 front end are available in ORTEC WS Backend API to support new reporting functionality ","New routes for Employee Self Service 7 front end are available in ORTEC WS Backend API to support upcoming reporting functionality\n\nTest hint(s):\n- None","In order to use reports with Employee Self Service 7 it is necessary to allow for larger requests in the Report Server.\nThis can be done in the web.config of the Report Server.\n- On the machine running Report Server, open file C:\\Program Files\\Microsoft SQL Server Reporting Services\\SSRS\\ReportServer\\web.config (drive or path may differ)\n- Find the line <httpRuntime executionTimeout=\"9000\" requestValidationMode=\"2.0\"/> \n- Replace with <httpRuntime executionTimeout=\"9000\" requestValidationMode=\"2.0\" maxQueryStringLength=\"16384\" /> \n- Save the web.config \n- Restart the service 'SQL Server Reporting Services'\n\nNote: It is possible that the value of maxQueryStringLength 16384 is not large enough, depending on the environment. In this case the event viewer will show an error \"The length of the query string for this request exceeds the configured maxQueryStringLength value.\"","11061",""]
[null,null,1556752,"2023-07-14",null,"Development\\OWSforTeamSchedulers","teamscheduling/CAddRealization: No matching duty properties could be found for existing activity","An error would be shown when a user tried to edit a shift in OWS for Team Schedulers, when that shift also has a declined employee realization.\nThis has been fixed. Now, the declined employee realization will be removed when the user edits a shift.\n\nTest hint(s):\nEdit a shift in OWS for Team Schedulers","","teamscheduling/CAddRealization: No matching duty properties could be found for existing activity","An error would be shown when a user tried to edit a shift in OWS for Team Schedulers, when that shift also has a declined employee realization.\nThis has been fixed. Now, the declined employee realization will be removed when the user edits a shift.\n\nTest hint(s):\nEdit a shift in OWS for Team Schedulers","","11129","https://ortec.link/Request?HID=15504373"]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","Cannot select main address in client, no future proof workaround","To comply with GDPR, functionality has been added in OWS 7 update 1534456 (2023-03-02) to hide employee addresses in the following win32 Client forms\n\n- Maintenance > Organization > Properties > Address\n- Maintenance > Locations and workstations > Properties > Address\n- Any Duty form -> Address\nFor customers using the same address form employees and organization, this could cause addresses that could not be selected.\nThis has been improved.\nIt is now possible to show employee addresses by setting OPTIONS\\ADDRESS\\SHOWEMPLOYEEADDRESSESINSEARCHFORMS to Y in the OWS Settings Manager (Refresh Settings required).\nThe default value for this setting is N.\n\nTest hint(s):\n- Verify that employee addresses are not visible in the mentioned forms when SHOWEMPLOYEEADDRESSESINSEARCHFORMS is set to N\n- Verify that employee addresses are visible in the mentioned forms when SHOWEMPLOYEEADDRESSESINSEARCHFORMS is set to Y","For this solution to become available, the ORTEC WS Win32 client must be installed.","Cannot select main address in client, no future proof workaround","To comply with GDPR, functionality has been added in OWS 7 update 1534456 (2023-03-02) to hide employee addresses in the following win32 Client forms\n\n- Maintenance > Organization > Properties > Address\n- Maintenance > Locations and workstations > Properties > Address\n- Any Duty form -> Address\nFor customers using the same address form employees and organization, this could cause addresses that could not be selected.\nThis has been improved.\nIt is now possible to show employee addresses by setting OPTIONS\\ADDRESS\\SHOWEMPLOYEEADDRESSESINSEARCHFORMS to Y in the OWS Settings Manager (Refresh Settings required).\nThe default value for this setting is N.\n\nTest hint(s):\n- Verify that employee addresses are not visible in the mentioned forms when SHOWEMPLOYEEADDRESSESINSEARCHFORMS is set to N\n- Verify that employee addresses are visible in the mentioned forms when SHOWEMPLOYEEADDRESSESINSEARCHFORMS is set to Y","For this solution to become available, the ORTEC WS Win32 client must be installed.","11364","https://ortec.link/Request?HID=15531554"]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","CCDS session(s) were not closed when a CMHS process was stopped","CCDS session(s) were not closed when a CMHS process was stopped.\nThis has been improved.\nAny open CCDS session(s) are now closed when stopping a CMHS CPMS process.\nA CMHS CPMS process is stopped when an exception occurs in CCDSConsumer with the option to stop all networks in the process is enabled.\n\nTest hint(s):\n- None","","CCDS session(s) were not closed when a CMHS process was stopped","CCDS session(s) were not closed when a CMHS process was stopped.\nThis has been improved.\nAny open CCDS session(s) are now closed when stopping a CMHS CPMS process.\nA CMHS CPMS process is stopped when an exception occurs in CCDSConsumer with the option to stop all networks in the process is enabled.\n\nTest hint(s):\n- None","","11414",""]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7\\Basic functionalities","Several translations added for German","Several translations have been added for German for recent functional changes.\n\nTest hint(s):\n- None","","Several translations added for German","Several translations have been added for German for recent functional changes.\n\nTest hint(s):\n- None","","12002",""]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","Sorting on calculation based on other calculations resulted in a wrong sort order and a subsequent refresh in a planboard could cause an exception","Calculation based on Calculations were sorted as a string instead of the actual type (duration or float) resulting in negative numbers displaying incorrectly (eg -40 above -50).\nAlso, when refreshing the planboard, the corresponding employees were not retrieved, showing an error message: \"TCalculation.CalculateEx: horizontal calculations can only be calculated per resource...\".\n This has been fixed.\n\ntest hint(s)\n- Verify that a calculation based on other calculations now sorts correctly and that a subsequent refresh of the planboard does show the employees.","","Sorting on calculation based on other calculations resulted in a wrong sort order and a subsequent refresh in a planboard could cause an exception","Calculation based on Calculations were sorted as a string instead of the actual type (duration or float) resulting in negative numbers displaying incorrectly (eg -40 above -50).\nAlso, when refreshing the planboard, the corresponding employees were not retrieved, showing an error message: \"TCalculation.CalculateEx: horizontal calculations can only be calculated per resource...\".\n This has been fixed.\n\ntest hint(s)\n- Verify that a calculation based on other calculations now sorts correctly and that a subsequent refresh of the planboard does show the employees.","","8213",""]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","A registration in the accounting tab of a shift for a single employee produced multiple account entries in case of an employee with multiple contracts","A registration in the registration tab of a shift for a single employee produced multiple account entries in case of an employee with multiple contracts. Though only one employee had the actual shift, both contracts got the accounting bookings.\nThis has been fixed.\nThis change is behind the feature toggle ExcludeLinkedResourcesFromAccountinglinesRem, which is enabled by default.\n\nTest hint(s):\nOnly valid when settings AccountingLinesRem and UseAccounting are active and employment conditions with compensation rule 'Duty registration' on an account exists.\n- Create/use an employee with two contracts ( /1 , /2) with the employment conditions containing compensation rule 'Duty registration'. \n- Give one of the contracts a shift Register the hours of the shift using the registration tab of the shift \n- Verify that only the employee with the shift has an entry, and that the linked employee does not.","","A registration in the accounting tab of a shift for a single employee produced multiple account entries in case of an employee with multiple contracts","A registration in the registration tab of a shift for a single employee produced multiple account entries in case of an employee with multiple contracts. Though only one employee had the actual shift, both contracts got the accounting bookings.\nThis has been fixed.\nThis change is behind the feature toggle ExcludeLinkedResourcesFromAccountinglinesRem, which is enabled by default.\n\nTest hint(s):\nOnly valid when settings AccountingLinesRem and UseAccounting are active and employment conditions with compensation rule 'Duty registration' on an account exists.\n- Create/use an employee with two contracts ( /1 , /2) with the employment conditions containing compensation rule 'Duty registration'. \n- Give one of the contracts a shift Register the hours of the shift using the registration tab of the shift \n- Verify that only the employee with the shift has an entry, and that the linked employee does not.","","8689","https://ortec.link/Request?HID=15163890"]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","Shifts were loaded when changing the status of a schedule to check violations when it was not necessary to do so","Shifts were loaded when changing the status of a schedule to check violations when it was not necessary to do so.\nThis has been improved.\nThis change was made behind feature toggle ReduceShiftLoadingWhenChangingScheduleStatus, enabled by default.\n\nTest hint(s):\n- None","","Shifts were loaded when changing the status of a schedule to check violations when it was not necessary to do so","Shifts were loaded when changing the status of a schedule to check violations when it was not necessary to do so.\nThis has been improved.\nThis change was made behind feature toggle ReduceShiftLoadingWhenChangingScheduleStatus, enabled by default.\n\nTest hint(s):\n- None","","8874",""]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","When an optimizer could not start due to entities being locked, the client could become unusable","When an optimizer could not start due to resources being locked, the client could become unusable.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nVerify optimizer plans in shifts and shows no errors","For this solution to become available, the ORTEC WS Win32 client must be installed.","When an optimizer could not start due to entities being locked, the client could become unusable","When an optimizer could not start due to resources being locked, the client could become unusable.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nVerify optimizer plans in shifts and shows no errors","For this solution to become available, the ORTEC WS Win32 client must be installed.","8999",""]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","The flexpool statistics report could take a long time to produce a result","The flexpool statistics report (standard report) could take a (very) long time to produce a result.\nThis has been improved.\n\nTest hint(s):\n- Open a Flexpool statistics report and check if the content is correct.","","The flexpool statistics report could take a long time to produce a result","The flexpool statistics report (standard report) could take a (very) long time to produce a result.\nThis has been improved.\n\nTest hint(s):\n- Open a Flexpool statistics report and check if the content is correct.","","9073","https://ortec.link/Request?HID=15189374"]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","Labor rule 'Rest per week for shift with certain activity kind' sometimes checked the wrong period in combination with ATW-rest shifts","Labor rule 'Rest per week for shift with certain activity kind' sometimes checked the wrong period leading to incorrect violations. In the past shifts with only ATW-rest were also used to determine the start of the period to check. This has been fixed. Now the shifts with treatment type ATW-rest are ignored for determining the period. \nThis functionality is behind feature toggle IgnoreRestPeriodsPreceedingShiftsOnRestPerWeekWithActivityKind and is default True.\n\nTest hint(s):\n- Verify labor rule 'Rest per week for shift with certain activity kind' ignores the ATW-rest shift in a period with enough rest.","","Labor rule 'Rest per week for shift with certain activity kind' sometimes checked the wrong period in combination with ATW-rest shifts","Labor rule 'Rest per week for shift with certain activity kind' sometimes checked the wrong period leading to incorrect violations. In the past shifts with only ATW-rest were also used to determine the start of the period to check. This has been fixed. Now the shifts with treatment type ATW-rest are ignored for determining the period. \nThis functionality is behind feature toggle IgnoreRestPeriodsPreceedingShiftsOnRestPerWeekWithActivityKind and is default True.\n\nTest hint(s):\n- Verify labor rule 'Rest per week for shift with certain activity kind' ignores the ATW-rest shift in a period with enough rest.","","9091","https://ortec.link/Request?HID=15195243"]
[null,null,1556752,"2023-07-14",null,"Development\\OWS7","BI enhancement for pro-active monitoring purposes","Added functionality to copy the Logging and LoggingErrors tables from the HDM_Stage to the OWS database.\nThe rows for the active BI run will be copied to the BI_Logging and BI_LoggingErrors tables in the OWS DB at the end of the BI run.\nAdditionally, an extra record is inserted in the BI_Logging table in the OWS database to indicate the state of the BI run\n- At start of the BI run a record with package name 'Ortec BI Process' will be inserted with a start_time and finished = N. This indicates an active BI run\n- On an error, this record will be updated to have an end_time and finished = N. This indicates a failed BI run\n- On a successful BI run, this record will be updated to have an end_time and finished = Y. This indicates the BI run has successfully finished\n\nPlease note that this change requires writing to the OWS database. \nIn case the sql account used for the OWS database during the BI run only has read rights, the BI run will fail (reason mentioned in the BI logfile).\n\nThis functionality is enabled by default, but can be disabled by adding the following setting to the BI_Config file(s)\n[boolean]$CopyLogTablesToOwsDatabase = $false\n\nNote when this setting does not exist, it will default to $true\nSee the new BI_Config_Template.ps1 for an example.\n\nTest hint(s):\n- Verify a BI run does not raise unexpected errors\n- Verify the records from the HDM_Stage Logging and LoggingErrors tables for the concerning BI run are copied to the OWS database tables BI_logging and BI_LogigngErrors","Please note the following:\r\n1. The OWS database requires a DBUpdate\r\n2. The sql account used by BI for the OWS database needs write permissions\r\n3. The BI.ps1 file should be updated in the folder where the BI process is run","BI enhancement for pro-active monitoring purposes","Added functionality to copy the Logging and LoggingErrors tables from the HDM_Stage to the OWS database.\nThe rows for the active BI run will be copied to the BI_Logging and BI_LoggingErrors tables in the OWS DB at the end of the BI run.\nAdditionally, an extra record is inserted in the BI_Logging table in the OWS database to indicate the state of the BI run\n- At start of the BI run a record with package name 'Ortec BI Process' will be inserted with a start_time and finished = N. This indicates an active BI run\n- On an error, this record will be updated to have an end_time and finished = N. This indicates a failed BI run\n- On a successful BI run, this record will be updated to have an end_time and finished = Y. This indicates the BI run has successfully finished\n\nPlease note that this change requires writing to the OWS database. \nIn case the sql account used for the OWS database during the BI run only has read rights, the BI run will fail (reason mentioned in the BI logfile).\n\nThis functionality is enabled by default, but can be disabled by adding the following setting to the BI_Config file(s)\n[boolean]$CopyLogTablesToOwsDatabase = $false\n\nNote when this setting does not exist, it will default to $true\nSee the new BI_Config_Template.ps1 for an example.\n\nTest hint(s):\n- Verify a BI run does not raise unexpected errors\n- Verify the records from the HDM_Stage Logging and LoggingErrors tables for the concerning BI run are copied to the OWS database tables BI_logging and BI_LogigngErrors","Please note the following:\n1. The OWS database requires a DBUpdate\n2. Make sure the sql account configured for $SSIS_OWS_OLTP_connectDB in BI_Config_IL/HL has write permissions on the OWS database\n3. The BI.ps1 file should be updated in the folder where the BI process is run","9546","https://ortec.link/Request?HID=15287268"]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Upgraded packages Newtonsoft Json and Microsoft Owin","Technical change to update the following packages\n\n- Newtonsoft Json \n- Microsoft Owin and dependent packages\n\nTest hint(s):\n- None.","",10052,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Added database logging to monitor the progress of the External Planner","To facilitate analyzing the progress of a current or previous run of the external planner, 2 new tables (ROS_EXTERNAL_PLANNER_RUNNING and  ROS_EXTERNAL_PLANNER_LOG) have been added to the database.Two new settings are added:\n- PLANNER\\NOFDAYSTOKEEPEXTERNALPLANNERDBLOGGING to indicate how long the records in this new table are kept. Default value: 60\n- PLANNER\\TIMEBETWEENEXTERNALPLANNERDBLOGGINGINSECONDS to indicate the interval used to log progress. Default value: 60\n\nTest hint(s):\n- Run the external planner and verify that records are added to the new tables ROS_EXTERNAL_PLANNER_RUNNING and ROS_EXTERNAL_PLANNER_LOG  to indicate planner-progress.","",11040,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Added option to send a message to a specific user in commandHandler CSendMessageToUsers","The existing commandHandler CSendMessageToUsers has been extended to allow sending a message to a single specific user. \nAn optional extra parameter UserName can be added containing the userName as known in Access Control to send a message to that specific user.\nWhen this parameter is not provided, or left empty, the message will be send to all users as before. When a non existing or non active user is provided, the message will not be send.\n\nTest hint(s):\n- Send a message to all users using the commandHandler CSendMessageToUsers and verify that all users received the message send a message to a specific user using the commandHandler CSendMessageToUsers, providing the added parameter UserName and verify that only that user receives the message","",11147,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Added version number in OWS Settingsmanager","To accommodate a future change, the OWS version number and date have been added to the OWS Setting manager. This is displayed on the miscellaneous tab.\n\nTest hint(s):\n- Verify that version number and date modified is now visible in the miscellaneous of OWS Settings Manager.","",12987,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Added the CloudMapService process for future functionality","Technical change containing preparations for a new process CloudMapService.\nThis introduces a new process CloudMapService, that is disabled by default, and should stay disabled for now.\nNone of this functionality is in use yet.\n\nTest hint(s):\n- None.","",13010,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Add description and example button for C# command handlers (Integration of OSDORDENH-17)","Improvement: for C# CommandHandlers also a description and a command example can be shown in CSCS Command Sender.When available a description is shown and a command example can be requested if available after selecting a command handler in CSCS Command Sender.\n\nTest hint(s):\n- None.","",13012,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Improved the error message when generating a report from ESS 7 and the configured maxQueryStringLength of Reporting Services is too small","Improved the error message when generating a report from ESS 7 and the configured maxQueryStringLength of Reporting Services is too small\nIf the maxQueryStringLength is configured is too small, an error message like the following will be displayed in the event viewer:\n\nError generating report 'Master schedule ESS'. The report server encountered an unhandled exception in HttpApplication. (rsUnhandledHttpApplicationError)\nThe length of the query string for this request exceeds the configured maxQueryStringLength value. The length of the query string used: xxxx\"\n\nTest hint(s):\n- None.","",13178,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWSforAdHocPlanners",null,null,null,"AhP not indicating violations when expected   --> On our own normal database proper repro","The shift offer functionality possibly sent the shift to too many employees due to missing violations.\nThis has been fixed.\nThe violation message for the weekly work time rule could show incorrect dates.\nThis has been fixed.\n\nTest hint(s):\n1. Don't use CWSS for violations\n2. Construct a schedule where an employee is close to the weekly work time limit. Another shift in that week (on Wednesday) would violate the weekly work time rule. Verify that the shift is not offered to this employee.\n3. Let an employee violate the weekly work time rule. Verify that the error contain correct dates.","",13516,"https://ortec.link/Request?HID=15744026"]
[null,null,1561992,"2023-08-30",null,"Development\\OWSforTeamSchedulers",null,null,null,"It was not possible to open or edit a shift when it had multiple subcontracts","When a shift was subcontracted multiple times, it was not possible to open or edit the shift in Ortec WS for TeamSchedulers anymore.\nThis has been fixed.\nNote that it is not possible to subcontract a shift multiple times using Ortec WS for TeamSchedulers, but only using the OWS Win32 Client.\n\nTest hint(s):\n- Subcontract a shift multiple times.\n- Edit the shift in Ortec WS for Team Schedulers.","",13543,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Added two new permissions to be used in ESS7","Added two new permissions to Access Control and the BackendAPI for future use in ESS7\n- In category ORTEC WS for Employees/reports: gui.workspace.ess.reports (to see reports in the new reporting functionality)\n- In category ORTEC WS for Employees/Personal schedule/Actions: guiactions.ess.calendar.sync (to turn synchronizing the calendar with your device on or off)\nNote: as the functionality behind guiactions.ess.calendar.sync was already enabled in the ESS7 App by default, this new permission will be automatically granted to each usergroup for which the permission gui.workspace.ess.personalroster is granted (in category ORTEC WS for Employees/Personal schedule/Workspace).\n\nTest hint(s):\n- Verify that the permission gui.workspace.ess.reports has been added to AccessControl in category ORTEC WS for Employees/reports.\n- Verify that the permission guiactions.ess.calendar.sync has been added to AccessControl in category ORTEC WS for Employees/Personal schedule/Actions.\n- Verify that the permission guiactions.ess.calendar.sync has been granted to each usergroup for which the permission gui.workspace.ess.personalroster (in category ORTEC WS for Employees/Personal schedule/Workspace) is granted.","",13761,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Removed the Microsoft .NET Framework 3.5 SP 1 prerequisite from the OWS Win32 Client installer","Microsoft .NET Framework3.5 SP 1 prerequisite has been removed from OWS client installer\n\nTest hint(s):\n- Verify that reports can be viewed in OWS Win32 Client","",13805,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWSforTeamSchedulers",null,null,null,"[OWS] Small change in teamscheduling\\CGetViolations handler","In Ortec WS for Team Schedulers, violations of custom violation types were not shown. \nThis has been fixed. Now, such violations are shown and visualized the same way as labor rule violations.\n\nTest hint(s):\n- Open a schedule in Ortec WS for Team Schedulers.\n- Verify that shifts with a custom type violation show a red corner.","",14039,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWSforTeamSchedulers",null,null,null,"[BDA] Team Scheduler: future scheduling periods not visible","In case a roster period had scenario's, future schedules could not be opened in ORTEC WS for Team Schedulers. \nThis has been fixed.\n\nTest hint(s):\n- Verify that roster periods can be opened in ORTEC WS for Team Schedulers. Also in case there is a scenario present in the Win32 Client.","",14105,"https://ortec.link/Request?HID=15830674"]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7\\Technical improvements",null,null,null,"When an Access Violation occurs during handling of a transaction additional information is included in the translog xml","When an Access Violation occurs during handling of a transaction, additional information is included in the translog xml.   This is for analysis purposes.\n\nTest hint(s)\n- None","",14269,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Outdated nuget package Microsoft.Owin (and dependencies) are updated","The package Microsoft.Owin was outdated, which caused a security risk.\nThis has been improved.\n\nTest hint(s):\n- None","",7119,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Updating a duty wish simultaneously by two users could cause a PANIC in main CWSS Server process","Updating a duty wish simultaneously by two users could cause a PANIC in the main CWSS Server process This has been improved.The duty wish and associated wish message are better protected with locks to prevent this concurrency issue.This change is behind the feature toggle ImproveLockingForWishMessages, which is enabled by default.\r\n\r\nTest hint(s):\r\n- Verify processing wish messages succeed.","",8051,"https://ortec.link/Request?HID=15037454"]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Memory usage was inefficient for temporary calculations during in TRunningAccountExportSelector","Memory usage was inefficient for temporary calculations during in TRunningAccountExportSelector. This could lead to big spikes in memory usage while running an export.\nThis has been improved.\nThe memory of temporary calculations that are not needed anymore are is now gradually freed during the calculation instead of all at once at the end.\nExample:\nWhen running account B is exported, calculations from running account A are needed to calculate B\nThe calculations from A are not needed anymore when B is calculated for a resource and calculated values for A are released from memory before bookings for the next employee are retrieved.\nThis change was implemented behind feature toggle FreeRunningAccountsPerObjectWhileExporting, default Y.\n\nTest hint(s):\n- Verify exports using TRunningAccountExportSelector still return the expected results","",8778,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"The plugin Comtec.Workbench.Project.Common.Exchange is now delivered with ORTEC WS","The (services) plugin Comtec.Workbench.Project.Common.Exchange is now included in the ORTEC WS delivery by default. \nWe have decided to include the most commonly used services plugins to prevent problems with incompatible versions and library dependencies.\nFrom now on, one can be sure that the plugin and ORTEC WS are compatible.\nPlease note the plugin is included as-is. We will monitor the need for additional information and act accordingly. \nPlease don't hesitate to reach out to product support in case of questions.\n\nTest hint(s):\n- Verify process Comtec.Workbench.Project.Common.Exchange is working and handlers correctly return values","Having the Exchange plugin in the OWS installation folder results in the following event viewer error when starting CAIS: \"Could not locate assembly: Microsoft.IdentityModel.Extensions,\". This one-time message at CAIS startup is harmless and is caused by CAIS trying to load irrelevant libraries (in this case the Exchange libraries). This will be fixed in a later update. ",9788,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"The plugin Comtec.Workbench.Project.Common.Http is now delivered with ORTEC WS","The (services) plugin Comtec.Workbench.Project.Common.Http is now included in the ORTEC WS delivery by default.  We have decided to include the most commonly used services plugins to prevent problems with incompatible versions and library dependencies. From now on, one can be sure that the plugin and ORTEC WS are compatible. \n For this delivery, we used the latest version of the standard service plugin and included a specific change regarding certificates that was done in the past for ORTEC WS. In the standard service plugin the certificate has to be placed in the CurrentUser store (of the user running the CPMS plugin). In the change done for ORTEC WS the certificate has to be placed in the LocalMachine store. This solved a problem that the certificate sometimes could not be found in the CurrentUser store (usually after an ORTEC WS restart),   We have now combined these two options; the version in this delivery will first look into the LocalMachine store and if the certificate can not be found there, it will look into the CurrentUser store.  \n General information about the plugin can be found at: https://wiki.ortec.intranet/osd/Projects/Common/ComtecWorkbenchProjectCommonHttp\n We will monitor the need for additional information and act accordingly. \n Please don't hesitate to reach out to product support in case of questions.\n\nTest hint(s):\n- Verify process Comtec.Workbench.Project.Common.Http is working and handler correctly returns values","",9789,""]
[null,null,1561992,"2023-08-30",null,"Development\\OWS7",null,null,null,"Windows 11 is now supported for the ORTEC WS Client","Windows 11 is now supported for the ORTEC WS Client\n\nTest hint(s):\n- None",null,8322]
[null,null,1564089,"2023-09-15",null,"Development\\OWS7","Added route to BackendApi to retrieve activity details of a shift in the Team Schedule","In preparation for a future change in ESS7, a new route has been added to the BackendAPI to retrieve the activities of a shift on the Team Schedule page. \n  For GDPR compliance, the name of the activityType will be replaced by the GeneralAbsenceName when the treatment is configured in the TreatmensReplacedByGeneralAbsenceCode setting in CSCS -Settings Manager - Comtec.Workforce.Backend - Portals   \n\nAdded new permission to Access Control: \n- In category ORTEC WS for Employees/Team schedule/workspace: \n  - gui.workspace.ess.teamschedule.details (to show or hide  all activities of Team schedule shifts) \n- In category ORTEC WS for Employees/Team schedule: \n  - guiactions.ows.ess.teamschedule.address (to show or hide the address of an activity in Team Schedule)\n  - guiactions.ows.ess.teamschedule.costcenter (to show or hide the cost center of an activity in Team Schedule)\n  - guiactions.ows.ess.teamschedule.workstation (to show or hide the workstation of an activity in Team Schedule)\n\nTest hint(s):\n1. Verify mentioned permissions are available in Access Control","","Added route to BackendApi to retrieve activity details of a shift in the Team Schedule","In preparation for a future change in ESS7, a new route has been added to the BackendAPI to retrieve the activities of a shift on the Team Schedule page. \n  For GDPR compliance, the name of the activityType will be replaced by the GeneralAbsenceName when the treatment is configured in the TreatmensReplacedByGeneralAbsenceCode setting in CSCS -Settings Manager - Comtec.Workforce.Backend - Portals   \n\nAdded new permission to Access Control: \n- In category ORTEC WS for Employees/Team schedule/workspace: \n  - gui.workspace.ess.teamschedule.details (to show or hide  all activities of Team schedule shifts) \n- In category ORTEC WS for Employees/Team schedule: \n  - guiactions.ows.ess.teamschedule.address (to show or hide the address of an activity in Team Schedule)\n  - guiactions.ows.ess.teamschedule.costcenter (to show or hide the cost center of an activity in Team Schedule)\n  - guiactions.ows.ess.teamschedule.workstation (to show or hide the workstation of an activity in Team Schedule)\n\nTest hint(s):\n1. Verify mentioned permissions are available in Access Control","","11646",""]
[null,null,1564089,"2023-09-15",null,"Development\\OWS7","ORTEC WS for Managers: Technical change containing preparations to include workstation and costcenter information for approving realisations","ORTEC WS for Managers: Technical change containing preparations to include workstation and costcenter information for approving realisations\n\nTest hint(s)\n1. Verify realisation can be approved in ORTEC WS for Managers","","ORTEC WS for Managers: Technical change containing preparations to include workstation and costcenter information for approving realisations","ORTEC WS for Managers: Technical change containing preparations to include workstation and costcenter information for approving realisations\n\nTest hint(s)\n1. Verify realisation can be approved in ORTEC WS for Managers","","13455",""]
[null,null,1564089,"2023-09-15",null,"Development\\OWS7","German translations have been improved","Some German translations have been updated.\r\n\r\nTest hint(s):\r\nNone","","German translations have been improved","Some German translations have been updated.\r\n\r\nTest hint(s):\r\nNone","","13775","https://ortec.link/Request?HID=15807715"]
[null,null,1564089,"2023-09-15",null,"Development\\OWS7","Simultaneous updates involving duty property values could cause an access violation in CWSS Server process","Simultaneous updates involving duty property values could cause an access violation in CWSS Server process.\nTo release locks that were not released as result of such access violation, a restart of the CWSS Server was required.\nThis has been improved.\nSimultaneous updates on duty property values and user properties in general has improved by better protecting this simultaneous access.\n\nA feature toggle 'FeatureToggleImproveLockingForWishMessages', enabled by default, has been added to toggle between the current (fixed) behavior when it is enabled and the behavior from before the improvements when it is disabled.\n\nTest hint(s)\n1. Verify that duty/activity/department properties can be changed from their default to a non-default value","","Simultaneous updates involving duty property values could cause an access violation in CWSS Server process","Simultaneous updates involving duty property values could cause an access violation in CWSS Server process.\nTo release locks that were not released as result of such access violation, a restart of the CWSS Server was required.\nThis has been improved.\nSimultaneous updates on duty property values and user properties in general has improved by better protecting this simultaneous access.\n\nA feature toggle 'IMPROVELOCKINGFORUSERPROPERTIES', enabled by default, has been added to toggle between the current (fixed) behavior when it is enabled and the behavior from before the improvements when it is disabled.\n\nTest hint(s)\n1. Verify that duty/activity/department properties can be changed from their default to a non-default value","","14029","https://ortec.link/Request?HID=15823671"]
[null,null,1564089,"2023-09-15",null,"Development\\OWS7\\Basic functionalities","Several translations added for german","Several translations have been added for German for recent functional changes.\r\n\r\nTest hint(s):  None","","Several translations added for german","Several translations have been added for German for recent functional changes.\r\n\r\nTest hint(s):  None","","14482",""]
[null,null,1564089,"2023-09-15",null,"Development\\OWS7","Application Integration process loaded unnecessary dll's","The CPMS process Application Integration (CAIS) loaded all dll's in the ..\\ORTEC\\Workforce Scheduling\\Server folder unnecessarily.\nThis could raise (ignorable) exceptions in the event viewer.\nThis has been fixed.\n\nThe Application Integration process will now only load the dll's it needs.\n\nTest hint(s)\n1. Verify that an interface or Mobile App using CAIS works as expected","","Application Integration process loaded unnecessary dll's","The CPMS process Application Integration (CAIS) loaded all dll's in the ..\\ORTEC\\Workforce Scheduling\\Server folder unnecessarily.\nThis could raise (ignorable) exceptions in the event viewer.\nThis has been fixed.\n\nThe Application Integration process will now only load the dll's it needs.\n\nTest hint(s)\n1. Verify that an interface or Mobile App using CAIS works as expected","","14573",""]
[null,null,1564089,"2023-09-15",null,"Development\\OWS7","The plugin Comtec.Workbench.Project.Common.CMHS.MessageInMetadata is now delivered with ORTEC WS","The (services) plugin Comtec.Workbench.Project.Common.CMHS.MessageInMetadata is now included in the ORTEC WS delivery by default.  We have decided to include the most commonly used services plugins to prevent problems with incompatible versions and library dependencies. From now on, one can be sure that the plugin and ORTEC WS are compatible.  For this delivery, we used the latest version of the standard service plugin\r\n\r\nTest hint(s):\r\n1. When the CMHSMessageInMetadata plugin is already used in a CMHS network, verify that CMHS network still delivers the expected results","","The plugin Comtec.Workbench.Project.Common.CMHS.MessageInMetadata is now delivered with ORTEC WS","The (services) plugin Comtec.Workbench.Project.Common.CMHS.MessageInMetadata is now included in the ORTEC WS delivery by default.  We have decided to include the most commonly used services plugins to prevent problems with incompatible versions and library dependencies. From now on, one can be sure that the plugin and ORTEC WS are compatible.  For this delivery, we used the latest version of the standard service plugin\r\n\r\nTest hint(s):\r\n1. When the CMHSMessageInMetadata plugin is already used in a CMHS network, verify that CMHS network still delivers the expected results","","9785",""]
[null,null,1565900,"2023-09-27",null,"Development\\OWS7","Several reports showed a '+' in the shift name when there was no instructor shift anymore","When an instructor shift was unmarked as instructor shift or the student shift was removed, several reports still showed the display character for an instructor shift (+) after a shifts name.\n\nThis has been fixed.\nThe following reports now use the display characters, as determined by ORTEC Workforce Scheduling, instead of being determined by logic in the report itself.\n- Atendancelist per Department\n- Employee Schedule ESS\n- Employee Schedule Planner\n- Master Schedule ESS\n- Master Schedule Planner\n- Overview Shifts\n- Year Roster\n\nTest hint(s):\n1. Verify that a '+' is no longer added to the shift name for a shift that was unmarked as an instructor shift in the mentioned reports.","","Several reports showed a '+' in the shift name when there was no instructor shift anymore","When an instructor shift was unmarked as instructor shift or the student shift was removed, several reports still showed the display character for an instructor shift (+) after a shifts name.\n\nThis has been fixed.\nThe following reports now use the display characters, as determined by ORTEC Workforce Scheduling, instead of being determined by logic in the report itself.\n- Atendancelist per Department\n- Employee Schedule ESS\n- Employee Schedule Planner\n- Master Schedule ESS\n- Master Schedule Planner\n- Overview Shifts\n- Year Roster\n\nTest hint(s):\n1. Verify that a '+' is no longer added to the shift name for a shift that was unmarked as an instructor shift in the mentioned reports.",null,"10055","https://ortec.link/Request?HID=15330119"]
[null,null,1565900,"2023-09-27",null,"Development\\OWS7","BI loaded too many duties and activities in the staging phase","The BI package Stage_Activity caused loading too many activities and duties.\r\nAlthough the derived data in the Fact tables was correct, efficiency and memory and storage were affected.\r\nThis has been improved.\r\nNow only duties and activities relevant for the BI load interval are read in the staging phase.\r\n\r\nTest hint(s):\r\n1. Verify that the Fact_..._Activity and Fact_..._Shift tables contain entries relevant for the BI Load interval.","","BI loaded too many duties and activities in the staging phase","The BI package Stage_Activity caused loading too many activities and duties.\r\nAlthough the derived data in the Fact tables was correct, efficiency and memory and storage were affected.\r\nThis has been improved.\r\nNow only duties and activities relevant for the BI load interval are read in the staging phase.\r\n\r\nTest hint(s):\r\n1. Verify that the Fact_..._Activity and Fact_..._Shift tables contain entries relevant for the BI Load interval.",null,"10303","https://ortec.link/Request?HID=15403832"]
[null,null,1565900,"2023-09-27",null,"Development\\OWSforTeamSchedulers","Technical preparation for the new vertical calculations feature in ORTEC WS for Team Schedulers.","Technical preparation for the new vertical calculations feature in ORTEC WS for Team Schedulers.\n\nTest hint(s):\n1. Verify that vertical calculations are shown in ORTEC WS for Team Schedulers","","Technical preparation for the new vertical calculations feature in ORTEC WS for Team Schedulers.","Technical preparation for the new vertical calculations feature in ORTEC WS for Team Schedulers.\n\nTest hint(s):\n1. Verify that vertical calculations are shown in ORTEC WS for Team Schedulers",null,"10817",""]
[null,null,1565900,"2023-09-27",null,"Development\\OWS7\\Technical improvements","Added a primary key to ROS_SUB_TRANS_SHIFTS","The ROS_SUB_TRANS_SHIFTS table didn't have a Primary Key.\r\nThis has been added to accommodate SQL change tracking mechanism.\r\n\r\nTest hint(s):\r\nNone","","Added a primary key to ROS_SUB_TRANS_SHIFTS","The ROS_SUB_TRANS_SHIFTS table didn't have a Primary Key.\r\nThis has been added to accommodate SQL change tracking mechanism.\r\n\r\nTest hint(s):\r\nNone",null,"14246",""]
[null,null,1565900,"2023-09-27",null,"Development\\OWS7","Added ESS7 and OWS for Employees permission for viewing Team Schedule shifts in the past","In ESS7 and OWS for Employees it was possible to see Team Schedule shifts in the past. This was not always desired.\nA new permission \"gui.workspace.ess.teamschedule.allowedtoseeshiftsinthepast\" has been added to restrict access to Team Schedule shifts in the past.\nThe new permission will be granted by default to user groups that already have the workspace.ess.teamschedule permission, to ensure the default behavior stays the same as before. \nWhen the new permission is revoked for users in OWS for Employees, the user will get the default message when viewing the team schedule in the past: 'There are no shifts planned on this day.'\n\nTest hint(s):\n1. Verify that when the permission to see Team Schedule shifts in the past is revoked, only active and future shifts can be retrieved.","","Added ESS7 and OWS for Employees permission for viewing Team Schedule shifts in the past","In ESS7 and OWS for Employees it was possible to see Team Schedule shifts in the past. This was not always desired.\nA new permission \"gui.workspace.ess.teamschedule.allowedtoseeshiftsinthepast\" has been added to restrict access to Team Schedule shifts in the past.\nThe new permission will be granted by default to user groups that already have the workspace.ess.teamschedule permission, to ensure the default behavior stays the same as before. \nWhen the new permission is revoked for users in OWS for Employees, the user will get the default message when viewing the team schedule in the past: 'There are no shifts planned on this day.'\n\nTest hint(s):\n1. Verify that when the permission to see Team Schedule shifts in the past is revoked, only active and future shifts can be retrieved.",null,"14304",""]
[null,null,1565900,"2023-09-27",null,"Development\\OWS7","Report Requests did not show recurring requests when request starts before selected period","The 'wish type' picker in MS Report Requests only showed wish types that have a validity period inside the selected report interval.\r\nThis caused recurring wishes not to be selectable when the begin date of a recurring wish lies before the selected report interval while the end date of the wish lies in or past that interval.\r\nThis has been fixed.\r\n\r\n\r\nWhen a recurring wish exists before, in or past the selected report interval, the recurring wish type will be selectable.\r\n\r\nTest hint(s):\r\n1. Verify that the recurring wish type can be selected in the report parameters when a recurring wish exists.","","Report Requests did not show recurring requests when request starts before selected period","The 'wish type' picker in MS Report Requests only showed wish types that have a validity period inside the selected report interval.\r\nThis caused recurring wishes not to be selectable when the begin date of a recurring wish lies before the selected report interval while the end date of the wish lies in or past that interval.\r\nThis has been fixed.\r\n\r\n\r\nWhen a recurring wish exists before, in or past the selected report interval, the recurring wish type will be selectable.\r\n\r\nTest hint(s):\r\n1. Verify that the recurring wish type can be selected in the report parameters when a recurring wish exists.",null,"9297","https://ortec.link/Request?HID=15221917"]
[null,null,1565900,"2023-09-27",null,"Development\\OWS7","Workstation planning Report grouped employees with the same firstname when parameter \"Show employee name\" was set to \"Firstname\"","Workstation planning Report grouped employees with the same firstname when parameter \"Show employee name\" was set to \"Firstname\".\nThis has been fixed.\n\nTest hint(s):\n1. Open a Workstation planning report, set parameter \"Show employee name\" to \"Firstname\", and verify that when 2 employees have the same firstname, 2 records are shown.","","Workstation planning Report grouped employees with the same firstname when parameter \"Show employee name\" was set to \"Firstname\"","Workstation planning Report grouped employees with the same firstname when parameter \"Show employee name\" was set to \"Firstname\".\nThis has been fixed.\n\nTest hint(s):\n1. Open a Workstation planning report, set parameter \"Show employee name\" to \"Firstname\", and verify that when 2 employees have the same firstname, 2 records are shown.",null,"9548","https://ortec.link/Request?HID=15287280"]
[null,null,1565900,"2023-09-27",null,"Development\\OWS7","The plugin Comtec.Workbench.Project.Common.Email is now delivered with ORTEC WS","The (services) plugin Comtec.Workbench.Project.Common.Email is now included in the ORTEC WS delivery by default. \nWe\n have decided to include the most commonly used services plugins to \nprevent problems with incompatible versions and library dependencies.\nFrom now on, one can be sure that the plugin and ORTEC WS are compatible.\nGeneral information about the plugin can be found at: https://wiki.ortec.intranet/osd/Projects/Common/ComtecWorkbenchProjectCommonEmail\n \nPlease note the plugin is included as-is. We will monitor the need for additional information and act accordingly. \nPlease don't hesitate to reach out to product support in case of questions.\n\nTest hint(s):\n1. Verify process Comtec.Workbench.Project.Common.Email is working and handler correctly returns values","","The plugin Comtec.Workbench.Project.Common.Email is now delivered with ORTEC WS","The (services) plugin Comtec.Workbench.Project.Common.Email is now included in the ORTEC WS delivery by default. \nWe\n have decided to include the most commonly used services plugins to \nprevent problems with incompatible versions and library dependencies.\nFrom now on, one can be sure that the plugin and ORTEC WS are compatible.\nGeneral information about the plugin can be found at: https://wiki.ortec.intranet/osd/Projects/Common/ComtecWorkbenchProjectCommonEmail\n \nPlease note the plugin is included as-is. We will monitor the need for additional information and act accordingly. \nPlease don't hesitate to reach out to product support in case of questions.\n\nTest hint(s):\n1. Verify process Comtec.Workbench.Project.Common.Email is working and handler correctly returns values",null,"9786",""]
[null,null,1567656,"2023-10-12",null,"Development\\OWS7",null,null,null,"Interface imported duplicate address after correction","Importing addresses could result in duplicate addresses when the existing address contained Statename, and the imported address did not, and all other fields where equal.\nThis has been improved: when no Statename element is available in the importfile and all other address-fields are equal, the imported address is now seen as identical to the existing address, and does not result in the creation of a new address. \nnote : when the Statename field is available is the importfile (even when empty) the compare does take this field into account, and could as such still create a new address, even if all other address fields are identical\n\nTest hint(s):\nEnter an address in OWS with Statename filled in. Then import that same address without statename. Verify that this import no longer results in a duplicate address.","","10053","https://ortec.link/Request?HID=15329949"]
[null,null,1567656,"2023-10-12",null,"Development\\OWS7",null,null,null,"Using command handler CChangeRosterStatus could give a timeout which could lead to a server halt","Using command handler CChangeRosterStatus could give a timeout which could lead to a server halt.\nThis has been improved.\n\nInstead of a static value, we now determine the expected calculation time needed for this command handler based upon the amount of shifts involved in the change.\n\nThis improvement was added behind feature toggle FeatureToggles\\IncludeCheckIntervalForViolationCalculationInResourceViolationsXMLCreator and is by default enabled.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\nVerify CChangeRosterStatus can correctly change the status of a roster period, especially when a large amount of shifts is involved","","10057","https://ortec.link/Request?HID=15330185"]
[null,null,1567656,"2023-10-12",null,"Development\\OWS7",null,null,null,"BackendAPI install script could fail starting the website","In some cases the BackendAPI install/update script could throw an error that the website could not be found while trying to start the BackendAPI website.\r\nThis seems to be caused by the web.config file not being fully freed by an external process like a virus scanner.\r\nThis has been improved.\r\nThe BackendAPI install script will now retry starting the website with a 5 second delay after an error occurred.\r\nAlso improved: any errors thrown by the BackendAPI install script will now be mentioned by Unattended Updates\r\n\r\nTest hints):\r\nNone","","10493","https://ortec.link/Request?HID=15420380"]
[null,null,1567656,"2023-10-12",null,"Development\\OWS7",null,null,null,"Technical preparations for using ORTEC Cloud Map Services for travel distance calculations","Technical preparations for using ORTEC Cloud Map Services for travel distance calculations.\r\nMore detailed information will follow when the functionality is released.","","14060",""]
[null,null,1567656,"2023-10-12",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Several translations added for Danish, German and Finnish","Several translations have been added for Danish, German and Finnish for recent functional changes.\r\n\r\nTest hint(s): \r\nNone","","18328",""]
[null,null,1567656,"2023-10-12",null,"Development\\OWS7",null,null,null,"The xsd file for the Comtec.Workbench.Project.Common.Email plugin was not delivered","In OWS 7 update 1565900 (2023-09-27), the Comtec.Workbench.Project.Common.Email plugin was released as part of OWS.\r\nThe XML schema definition: Comtec.Workbench.Project.Common.Email.xsd is now also delivered.\r\n\r\nTest hint(s):\r\nNone","","18458",""]
[null,null,1567656,"2023-10-12",null,"Development\\OWS7",null,null,null,"OWS Back-end API: New reporting routes used wrong report name translation token","Technical change in new reporting routes to use the correct translation token.","","18505",""]
[null,null,1567656,"2023-10-12",null,"Development\\OWS7",null,null,null,"BackendAPI checked too many access modes for new permissions ","When logging in OWS for Employees or ESS7 App a session is created and permissions are verified.\r\nThis added three unnecessary event log entries.\r\nThis has been improved.\r\n \r\n Note this was introduced in OWS 7 Update 1564089 (2023-09-14) by issue 11646\r\n\r\nTest hint(s)\r\nNone.","","21759",""]
[null,null,1567656,"2023-10-12",null,"Development\\OWS7\\Technical improvements",null,null,null,"The GETRESOURCEVIOLATIONS(BI) SQL functions could result in double violation information","When employees linked to multiple departments with different schedule intervals, the GETRESOURCEVIOLATIONS(_BI) SQL functions could result in double violation information.\nThis has been improved.\n\nThis improvement was added behind feature toggle FeatureToggles\\CRosterStatusDynamicTransactionTimeout and is by default enabled.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\nVerify the \"Overview of violations\" report shows the expected violation information","","8474","https://ortec.link/Request?HID=15062625"]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"A subcontracted shift was still open for bidding when the subcontracted shift got cancelled.","A shift that was subcontracted and that was set open for bidding by the subcontracting department remained open for bidding, even if the subcontracting department declined the shift, or if the initial department cancelled the subcontract. \nThis has been fixed.\n\nTest hint(s):\n1. Add a shift to department-roster, subcontract to other department in other department, set shift open for bidding -> cancel subcontract in 1st department : verify that shift is no longer be open for bidding in 1st department  \n2. Add a shift to department-roster, subcontract to other departmentin other department, set shift open for bidding-> decline subcontract in 2nd department : verify that shift is no longer be open for bidding in 1st department","",10082,"https://ortec.link/Request?HID=15330696"]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"'Number of night shifts, deduction for lost days' rule, could not show violation at the end of a schedule","When using a small period (e.g. max x shifts every 4 days) in 'Number of night shifts, deduction for lost days' rule, it could occur that a violation was not shown at the end of the schedule.\nThis has been improved.\nViolations will be calculated for the full schedule.\n\nTest hint(s):\n1. Verify that violations on number of night shift type rules ae shown where expected","","10246","https://ortec.link/Request?HID=15397780"]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"Employee number and name missing in failed user import message","Importing an employee with a username that was already allocated to another employee will raise a valid error.\nHowever, the interface message did not contain enough information about the failing record to act on.\nThis has been changed.\nThe employee numbers are now mentioned in the interface message and logging.\n\nTest hint(s):\n1. Verify that a failed employee import now shows the employee number in a failed interface message\n2. Verify that an employee can be imported.","","10330","https://ortec.link/Request?HID=15408094"]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"Expiration date could not be set for interface messages","The setting NofDaysBeforeExpiring had no effect for Interface messages (type: HtmlMessage) and such messages were removed after 366 days\nAs a large number of interface messages can still be impactful, this has been improved.\n\nIt is now possible to create the setting Options/Messages/HtmlMessage/NofDaysBeforeExpiring with a custom value.\nIf the setting does not exist, a default value of 366 days will be used\n\nNote that the value is restricted by settings:\n- Options/Messages/MinimumNofDaysBeforeExpiring\n- Options/Messages/MaximumNofDaysBeforeExpiring\n\nTest hint(s):\n1. Verify that new interface messages will have an expiration of 366 days or the number of days as set in Options/Messages/HtmlMessage/NofDaysBeforeExpiring","","10494","https://ortec.link/Request?HID=15420553"]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"Timewindow violation ignored for shift ending after last day of schedule","The labor rule ShiftInTimeWindowReq (Check shift times with time window) did not raise a violation when there was no matching Time Window for a shift ending after the last day of the schedule.\nThis has been fixed.\n\nTest hint(s): \n1. Verify that a shift ending after the schedule will raise a violation when no time window exists.","","10774","https://ortec.link/Request?HID=15484542"]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7\\Technical improvements",null,null,null,"A system monitoring query NumberOfPlannedContractsPerMonth was added","A system monitoring query NumberOfPlannedContractsPerMonth was added.\r\nThe query collects the number of planned contracts on a daily level.","","11076","https://ortec.link/Request?HID=15500736"]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"Functionality 'Replace by activity type' emptied shift remark","When using the functionality 'Replace by activity type' the shift remark was not retained in case the entire shift got replaced.\nThis has been fixed.\n\nTest hint(s):\n 1. Plan a shift and enter a shift remark. Replace activitytype for the entire shift.\n Verify that the remark is retained on the newly created shift","","11079","https://ortec.link/Request?HID=15501187"]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"Technical change to support asynchronous retrieval of reports through the BackendAPI","Technical change to support asynchronous retrieval of reports through the BackendAPI.","","21869",""]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"TeamSchedule details were no longer visible with allowedtoseeshiftsinthepast permission","In card 14304, a new permission 'allowedtoseeshiftsinthepast'  was added to show or hide Team Schedule shifts in the past in ESS7\nThis worked as expected. However, when determining whether the activities of past Team Schedule shifts could be shown, the permission was evaluated incorrectly, causing past activates not to be shown.\nThis has been fixed.\nNote this was introduced in OWS 7 update 1565900 (2023-09-27)\n\nTest hint(s):\n1. Verify ESS7 displays Team schedule details in the past when the permission allowedtoseeshiftsinthepast is granted.","","22434",""]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"Memory improvement in temporary calculations during in TRunningAccountExportSelector could cause an Access Violation","Memory improvement in temporary calculations during in TRunningAccountExportSelector could cause an Access Violation\nThis could occur when in the selection of departments the exported the bookings for an employee linked to multiple departments were being calculated. \nThis issue was introduced in issue 8778 \"Memory usage was inefficient for temporary calculations during in TRunningAccountExportSelector\" in OWS7 8.5.0(2023-08-30)_Build1561992.\n\nAnd was reported in issue 25629\nTo prevent until 25629 is resolved and released the feature toggle issue 8778 was resolved will be turned off  \nThe FreeRunningAccountsPerObjectWhileExporting will be set to default N\n\nTest hint(s):\nNone","",25970,""]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"The ExtraXMLCreator for a UserImport sometimes wrongfully removed permissions from users","The ExtraXMLCreator for a UserImport sometimes wrongfully removed permissions from users. This specifically happened when updateStrategy was set to overwrite and the cases were not matching.\nThis has been fixed.\nAn additional bug was discovered where permissions were removed in a similar fashion when setting UseMultiLang was on. This has been fixed behind feature toggle DoNotTranslateUserGroupNamesInUserImport, default Y.\nWe have also removed feature toggle UseImprovedUserImport. This feature toggle had a default value of Y, which is now default behavior.\n\nTest hint(s):\n Have a role called \"Manager Planning\" (with a P, not a p). Use the ExtraXMLCreator UserImport to assign a role 'Manager planning' to a user. \n1. Check that the user is properly assigned to the role Repeat \n2. Check that the user is still properly assigned to the role","","8149","https://ortec.link/Request?HID=15054912"]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"DBUpdate - improved performance of correcting datamodel","Added a DBUdpate(Wizard/Console) feature that when the datamodel needs to be corrected, only the incorrect object will be lifted instead of all dependencies on a table. This can save time when a larger table needs to be changed or corrected. This holds true for non-column objects like keys and indexes. When a column needs to be changed it is still needed to drop and create all dependencies on a table.  \nThis functionality is turned on by default. It can be disabled by checking 'Full drop and create' \nIn the DBUpdateWizard, this can be done on the page prior to conversion\nIn the DBUpdate, this can be done on the tab 'Advanced Options' \nFor the DBUpdateConsole, it is disabled by default. It can be enabled in the DBUpdateConsole by adding the switch /OptimizedDropAndCreate\n\nTest hint(s): \n1. Verify the DBUpdate(Wizard/Console) runs normally and corrects the datamodel where necessary","","8154",""]
[null,null,1569177,"2023-10-26",null,"Development\\OWS7",null,null,null,"Memory of CWSS Server processes is logged every 30 seconds instead of 15 minutes","Memory of CWSS Server processes was logged every 15 minutes by default.\nThis has been changed to every 30 seconds.\nMemory will also be logged upon switching logfile.\nNote the default will only change for customers which still have the old default of 15 minutes.\nOther values will not be overwritten.\n\nTest hint(s):\nNone","","9356","https://ortec.link/Request?HID=15258827"]
[null,null,1571075,"2023-11-09",null,"Development\\OWS7",null,null,null,"Skills were not included when replacing duty in duty set","When replacing a duty in a duty set and feature toggle CREATEDUTYFROMEXISTINGDUTYINDUTYSETFORM enabled, the skill of the original duty was not included in the new replaced duty. \nThis has been fixed.\n\nTest hint(s):\n- Verify that when replacing a duty in a duty set the skills of the original duty are included in the new replaced duty.\n- Verify that when replacing a duty in a duty set the removed skills of the original duty are not included in the new replaced duty.","","10245","https://ortec.link/Request?HID=15397779"]
[null,null,1571075,"2023-11-09",null,"Development\\OWS7",null,null,null,"When importing an employee property value failed, the error did not show the employee number","When importing user property values failed for an employee failed, the employee number of the failing record was not shown in the logging.\nThis has been improved.\nThe logging now also mentions the employee number.\n\nTest hint(s):\n- Import xml file with employee with unknown username Verify that the logging now shows the employee number related to the failing record.","","10444","https://ortec.link/Request?HID=15413513"]
[null,null,1571075,"2023-11-09",null,"Development\\OWS7",null,null,null,"Leave requests overview can also be opened from schedule management","The form 'Leave requests' in menu 'Overview' can only be opened with a fixed department (last department for which a schedule has been opened).\nThis has been improved.\nOne can now also open the form 'Leave requests' from schedule management (schedule periods tab, Requests groupbox).\nIn this case the selected department is used to open the Leave requests form.\nNote that the Leave requests form opens with the default period of the upcoming year. \nA selected schedule period is not considered.\n\nTest hint(s):\n- Verify that the 'Leave requests' form can be opened from either schedule management or the 'Overview' menu. When opening from from schedule management, the selected department is used to open the from.","For this solution to become available, the ORTEC WS Win32 client must be installed.",14450,""]
[null,null,1571075,"2023-11-09",null,"Development\\OWS7",null,null,null,"Recurring wishes could cause the optimizer to create a schedule with violations","Despite of the fact a recurring wish to 'not work' on a day existed, the optimizer would plan a shift on that day, when that shift continued the day after the day of the wish, resulting in a violation.\nThis has been fixed.\n\nTest hint(s):\n- Verify that a wish not to work is respected by the optimizer, even if the shift to be scheduled continues on the day after the day of the wish.","","18292","https://ortec.link/Request?HID=15945745"]
[null,null,1571075,"2023-11-09",null,"Development\\OWSforAdHocPlanners",null,null,null,"[BDA] East environment opens but is stuck / locking (linked resources for overlapping shifts)","When offering a shift in Ad Hoc Planning, the environment could get stuck when an available employee already had a shift for another contract.\nThis has been fixed. Now, other contracts of employees are considered when determining to whom a shift can be offered.\n\nTest hint(s):\n- Offer a shift. Verify that the expected employees receive a notification about that.","","18382","https://ortec.link/Request?HID=15950869"]
[null,null,1571075,"2023-11-09",null,"Development\\OWSforTeamSchedulers",null,null,null,"Added functionality to ORTEC WS for Team Schedulers to show shifts from other contracts in the schedule","Added functionality to ORTEC WS for Team Schedulers to show shifts from other contracts in the schedule. Before, only the shifts assigned to the current contract were shown, but now, also the shifts from contracts in other departments are shown. Note that shifts from other contracts in other departments are shown only once in the schedule, so for only one of the contracts if the employee has multiple contracts in the same department.\n\nTest hint(s):\n- Open the schedule in ORTEC WS for Team Schedulers. \nVerify that all shifts of both contracts are shown in case an employee has a second contract in another department.","","26118",""]
[null,null,1571075,"2023-11-09",null,"Development\\OWS7",null,null,null,"ORTEC WS for Employees: When requesting simultaneous alternative shifts for different employees in Selfrostering access violations could occur","ORTEC WS for Employees: When requesting simultaneous alternative shifts for different employees in Selfrostering access violations could occur.\nA shared internal resource for the employees (when in the same department) was not protected correctly. \nThis protection has been improved.\nThe protection is applied on the worker handling Back-end API calls as dictated by the CSMS setting: Comtec.Workforce.BackendAPI\\Portals\\InterfaceServerNumber\nWhen updating this settings workers with changed server numbers involved should be restarted.\n\nThis functionality is behind added feature toggle: FEATURETOGGLE\\ProtectShiftsListInDutyInstances and is by default disabled!\n NOTE: an ORTEC consultant is only allowed to change this setting after consulting the Maintenance department\n\nTest hint(s):\n- None","","27147","https://ortec.link/Request?HID=16132006"]
[null,null,1571075,"2023-11-09",null,"Development\\OWS7",null,null,null,"BI Support: added option to switch off certain packages","To reduce the time of a BI run, an option has been added to skip BI packages that use the HTTPServer in case they are not needed by the customer. One can now skip packages related to violations, requests, duty/activity demands and cyclic shifts/activities.  \n\nTo configure what packages will be skipped, a new setting has been created in CSCS - Settings Manager - CBIS - Dataloads: PACKAGES_TO_SKIP \nThe following values are valid:\n- Violation        (skips STAGE_Violation and FACT_Employee_Violation) \n- Request         (skips STAGE_Request and FACT_Employee_Request) \n- DutyDemand (skips STAGE_Duty_Demand, FACT_Shift_Demand and FACT_Activity_Demand) \n- CyclicShift      (skips STAGE_Cyclic_Shift, FACT_Cyclic_Shift and FACT_Cyclic_Activity)  \nThese can be entered as a comma separated string (in any order).  E.g: Violation, Request, CyclicShift, DutyDemand\n\nTest hint(s):\n1. Verify BI runs as expected when setting is not filled.\n2. Verify that mentioned packages can be skipped when desired.","","9547","https://ortec.link/Request?HID=15287270"]
[null,null,1572321,"2023-11-23",null,"Development\\OWSforAdHocPlanners",null,null,null,"The employee proposal functionality in Ad Hoc Planner was slow","The employee proposal functionality in Adhocplanning was slow. This could result in gateway time-outs, resulting in the functionality being unusable.\nThis has been improved. \n\nTest hint(s):\n1. Verify the employee proposal in Ad Hoc Planner still works","",26188,"https://ortec.link/Request?HID=16061725"]
[null,null,1572321,"2023-11-23",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Several translations added for Danish, French & Finnish","Several translations have been added for Danish, French & Finnish \n\nTest hint(s):  None","",27124,""]
[null,null,1572321,"2023-11-23",null,"Development\\OWS7",null,null,null,"External Planner process could halt immediately after starting","External Planner process could halt immediately after starting\nThis has been resolved. \n\nNote: this was introduced in OWS 7 8.5.0(2023-11-09)_Build1571075.\n\nTest hint(s):\n1. Verify external planner service process can be started and finishes correctly","",28306,"https://ortec.link/Request?HID=16148388"]
[null,null,1575619,"2023-12-07",null,"Development\\OWS7","Labor rule MaxDurationLaborPeriodNightReq could load to much shifts","To calculate exceptions, the rule 'Duration of a night shift (labor period)' (MaxDurationLaborPeriodNightReq) could load shifts as far back as the MaxScheduleAge setting would allow.\nThis has been improved.\n\nThe rule will only load shifts from as far back as the beginning of the schedule minus the maximum exception period.\n\nTest hint(s):\nNone","","Labor rule MaxDurationLaborPeriodNightReq could load too many shifts","To calculate exceptions, the rule 'Duration of a night shift (labor period)' (MaxDurationLaborPeriodNightReq) could load shifts as far back as the MaxScheduleAge setting would allow.\nThis has been improved.\n\nThe rule will only load shifts from as far back as the beginning of the schedule minus the maximum exception period.\n\nTest hint(s):\nNone",null,13017,"https://ortec.link/Request?HID=15658465"]
[null,null,1575619,"2023-12-07",null,"Development\\OWS7","Changing leave request status from Approved to Concept Approved or Open could remove realization of shifts not containing the leave type of the request","Changing leave request status from Approved to Concept Approved or Open, could remove realization of shifts not containing the treatment of the leave request.\nThis has been improved.\n\nAdded feature toggle FeatureToggles\\KeepRealisationOfShiftWithoutActivityTypeOfWishWhenUndoingLeaveWish and is by default enabled.NOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\n1.  Verify changing status of leave requests with and without a pre-existing shift in the period of the the leave request.","","Changing leave request status from Approved to Concept Approved or Open could remove realization of shifts not containing the leave type of the request","Changing leave request status from Approved to Concept Approved or Open, could remove realization of shifts not containing the treatment of the leave request.\nThis has been improved.\n\nAdded feature toggle FeatureToggles\\KeepRealisationOfShiftWithoutActivityTypeOfWishWhenUndoingLeaveWish and is by default enabled.NOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\n1.  Verify changing status of leave requests with and without a pre-existing shift in the period of the the leave request.",null,13535,"https://ortec.link/Request?HID=15745385"]
[null,null,1575619,"2023-12-07",null,"Development\\OWS7\\Technical improvements","ESS7: technical change to include additional information on absence when retrieving the default shifts","Technical change in the BackendAPI to include additional information on absence when retrieving the default shifts for ESS7\r\n\r\nTest hint(s):\r\nNone.","","ESS7: technical change to include additional information on absence when retrieving the default shifts","Technical change in the BackendAPI to include additional information on absence when retrieving the default shifts for ESS7\n\n\n\nTest hint(s):\n\nNone.","",22311]
[null,null,1575619,"2023-12-07",null,"Development\\OWS7","Registration hours are updated automatically when changing shift times","Registration hours are updated automatically when changing shift times.\nWhen the total number of workhours is changed when applying a (employee) realization, the registration hours are updated automatically.\n\nThis functionality is behind the following settings:\nExisting global setting UseAccounting needs to be enabled \nServer setting Options/Accounting/ThreeLevelCostCentersForAccounting needs to be set to N.\nAdded server setting Options/Accounting/UpdateAccountingLinesForWorkHours with default value N needs to be changed to Y\n\nTest hint(s):\n1. Verify applying shift realisations \n2. Verify approving employee realisations","","Registration hours are updated automatically when changing shift times","Registration hours are updated automatically when changing shift times.\nWhen the total number of workhours is changed when applying a (employee) realization, the registration hours are updated automatically.\n\nThis functionality is behind the following settings:\nExisting global setting UseAccounting needs to be enabled \nServer setting Options/Accounting/ThreeLevelCostCentersForAccounting needs to be set to N.\nAdded server setting Options/Accounting/UpdateAccountingLinesForWorkHours with default value N needs to be changed to Y\n\nTest hint(s):\n1. Verify applying shift realisations \n2. Verify approving employee realisations","",27140]
[null,null,1575619,"2023-12-07",null,"Development\\OWS7\\Technical improvements","Index changes to improve query performance of Workstation planboard","To improve performance of loading data for the Workstation planboard:\r\nAn index has been improved in ROS_ACTIVITIES\r\nAn index has been added to ROS_SHIFTS\r\n\r\nTest hint(s):\r\nNone","","Index changes to improve query performance of Workstation planboard","To improve performance of loading data for the Workstation planboard:\n\nAn index has been improved in ROS_ACTIVITIES\n\nAn index has been added to ROS_SHIFTS\n\n\n\nTest hint(s):\n\nNone","",29775]
[null,null,1577453,"2023-12-21",null,"Development\\OWSforTeamSchedulers",null,null,null,"Added functionality to unassign multiple shifts in one action by using the selection mode in ORTEC WS for Team Schedulers","Added functionality to unassign multiple shifts in one action by using the selection mode in ORTEC WS for Team Schedulers.\n\nTest hint(s):\n1. Select multiple assigned shifts and unassign them using the unassign option in the action menu","",11912,""]
[null,null,1577453,"2023-12-21",null,"Development\\OWS7",null,null,null,"Schedule Optimizer did not take wildcard wishes into account","Schedule Optimizer did not take wildcard wishes into account.\nThis has been improved.\n\nTest hint(s):\n1. Verify that the optimizer respects wildcard wishes","",13084,"https://ortec.link/Request?HID=15702232"]
[null,null,1577453,"2023-12-21",null,"Development\\OWS7",null,null,null,"Shift bidding notifications were sent to employees in case of potential violations","Shift bidding notifications were sent to employees in case of potential violations.\nThis has been improved.\nWhen the employees that can bid on shifts are collected using the command handler CGetEmployeesThatCanBidOnShifts additionally the potential violations are checked for all labor rules.Employees are excluded when the picking a shift would lead to a violation.\nAdded feature toggle setting: FeatureToggles\\CheckAllLaborRulesForViolationDifferencesInGetEmployeesThatCanBidOnShifts and is by default enabledNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\n1. Verify that employees can bid on shifts when they are opened for bidding and that notifications are only sent to the right employees","",18324,""]
[null,null,1577453,"2023-12-21",null,"Development\\OWS7",null,null,null,"Memory usage was inefficient for temporary calculations using TRunningAccountExportSelector - Revisited","Memory usage was inefficient for temporary calculations using TRunningAccountExportSelector. This could lead to big spikes in memory usage while running an export. \nThis was been improved in issue \"8778 Memory usage was inefficient for temporary calculations during in TRunningAccountExportSelector\" delivered in OWS7 8.5.0(2023-08-30)_Build1561992.\nBut in certain cases an access violation could occur during the export.\nTo avoid this the improvement was temporarily disabled in OWS7 - 8.5.0(2023-10-26)_Build1569177.\n\nThe issue with the access violations has been fixed and the feature toggle FreeRunningAccountsPerObjectWhileExporting re-enabled by default again.\n\nTest hint(s): \n1. Verify exports using TRunningAccountExportSelector still return the expected results \n2. Verify \"Overview account entries\" report","",25629,"https://ortec.link/Request?HID=16033905"]
[null,null,1577453,"2023-12-21",null,"Development\\OWSforAdHocPlanners",null,null,null,"Ad Hoc Planner could not handle employees with an employee number that ends with a '/'","Ad Hoc Planner could not handle employees with an employee number that ends with a '/'.\nThis has been fixed. Now, an employee with a number ending with '/' is considered to have no contracts.\n\nTest hint(s):\n1. Have an employee with an employee number ending with a '/' character Assign a shift to that employee Verify that the schedule can be opened in Ad Hoc Planner","",26272,"https://ortec.link/Request?HID=16094226"]
[null,null,1578886,"2024-01-04",null,"Development\\OWS7",null,null,null,"Bookings with nested calculations were sometimes calculated wrong","In certain cases, account entries with nested calculations were calculated incorrectly, resulting in incorrect values that were noticed when transferring balances.\nA significant change was done in the account entry calculation code that influences how nested calculations and their periods are handled. This fixes the issues reported in the OPS tickets and we are confident that it is the right fix.\n\nHowever, based on several tests on other customer configurations, it turns out that this fix can have severe consequences if the existing configuration is not 100% correct (e.g. when cycles are present, or when remuneration rules are set-up very inefficiently).\nThe observed consequences are: much slower calculations, errors when calculating an account and \"double bookings\".\nAs these consequences can be very severe - and we saw them at almost every existing customer configuration - we have decided to not enable the change by default and we will not do so in the future.\n\nBecause the change does have benefits for new configurations, we decided to keep the change in code and put it behind a feature toggle.\nThe feature toggle is called IMPROVEBOOKINGSWITHNESTEDCALCULATIONS and is turned off by default.\n\nIt is advised to turn the feature toggle on for new remuneration configurations. In those cases the change has several benefits: more reliable account entries and an earlier notification if something is wrong in the configuration.\nIt is strongly advised to not to turn it on for existing configurations in a production environment.","Test hint(s):\nVerify bookings are correct",9958,"https://ortec.link/Request?HID=15325280"]
[null,null,1578886,"2024-01-04",null,"Development\\OWS7",null,null,null,"OWS Backend-API could return status code 500 when retrieving schedule data with inconsistent subcontracting information","OWS Backend-API could return status code 500 when retrieving schedule data with inconsistent subcontracting information\r\nIt was possible for the command handler CSubcontractShiftsToDepartment to create invalid subcontract data.\r\nThis could occur when a shift belonging to dpt A was subcontracted from dpt B to dpt C (without being subcontracted from dpt A to dpt B first)\r\nOn such data, the BackendAPI raised an incomprehensible error when requesting TeamSchedule data.\r\nThis has been improved.\r\n\r\n\r\n- The command handler CSubcontractShiftsToDepartment will not allow the subcontracting when the provided fromDepartment does not match the current department of the shift.\r\nWhen multiple shifts are provided the command handler will subcontract valid data and raise an errormessage on the invalid shifts.\r\nPlease check the response in your CMHS networks.\r\n\r\n\r\n- The BackendAPI will now raise a more comprehensible error on existing invalid data.\r\n\r\nTest hint(s):\r\nVerify CMHS networks using the command handler CSubcontractShiftsToDepartment will process valid subcontract input.","The output of the command handler CSubcontractShiftsToDepartment can hold error messages that certain shifts could not be subcontracted. \r\nPlease adjust your CMHS networks to check for errors.",11945,"https://ortec.link/Request?HID=15623599"]
[null,null,1578886,"2024-01-04",null,"Development\\OWSforAdHocPlanners",null,null,null,"A new CSCS setting has been added for Ad Hoc Planning AdhocPlanning/General/MaxNofDepartmentsInDashboard","A new CSCS setting has been added for Ad Hoc Planning AdhocPlanning/General/MaxNofDepartmentsInDashboard. The default value for this setting is 10.\r\nThis\r\n setting is related to a change in Ad Hoc Planning to limit the number \r\nof departments for which the information in the dashboard is shown, due \r\nto performance reasons.","",28560,""]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7",null,null,null,"The import definitions using ExtraXMLCreators TFillFieldsOfIllness and TIllnessAfterImportStandardActions only created required exchanges when replacing shifts","The import definitions using ExtraXMLCreators TFillFieldsOfIllness and TIllnessAfterImportStandardActions only created required exchanges when replacing shifts. It is now possible to add an extra parameter to an importdefinition file, such that when importing Illness the ExchangeKind for replaced duties can be set to REQUESTED instead of the currently only existing option REQUIRED  the format for this extra (optional) parameter is<Param><Name>ExchangeKindForReplacedDuties</Name> <Show>N</Show> <Label>Mutatiesoort voor ziektediensten</Label> <Type>string</Type> <Value>REQUESTED</Value> </Param>  if the value <> REQUESTED or the parameter does not exist, the exchangekind will always be REQUIRED as it was before this change.\n\nTest hint(s): \nImport an Illness and verify that it's exchangekind is Required. Add an extra parameter ExchangeKindForReplacedDuties to your importdefinition and set it's value to REQUESTED. Verify that the Exchanges do indeed have exchangekind Requested when importing Illness.","","11666","https://ortec.link/Request?HID=15604627"]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7",null,null,null,"Subcontracted shift does not raise violation for MaxLabourTimeDuringHolidaysReq rule","The labor rule 'Maximum working time on and around public holidays' (MaxLabourTimeDuringHolidaysReq) did not create a violation for (central) subcontracted shifts.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\n1. Verify that the labor rule 'Maximum working time on and around public holidays' will create a violation on a subcontracted shift if needed.","","12021","https://ortec.link/Request?HID=15630069"]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7\\Technical improvements",null,null,null,"Access Control: query that inserts and updates login sessions could block other queries under heavy load","Access Control: query that inserts and updates login sessions could block other queries under heavy load\nThe query has been improved.\n\nTest hint(s):\nVerify OWS Win32 Client can be logged into","","13085","https://ortec.link/Request?HID=15702249"]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7",null,null,null,"BI load after patching - DateTime conversion failed and caused issue with the logging","BI load after patching - DateTime conversion failed for certain locales and caused issue with the logging.\nThis has been fixed\n\nTest hint(s):\nRun BI.ps1 and verify that the BI_Logging table contains new records","","13444","https://ortec.link/Request?HID=15741663"]
[null,null,1580730,"2024-01-18",null,"Development\\OWSforTeamSchedulers",null,null,null,"[BDA]Send prefix with employee information  ","The prefix of the employee name is now made available to the routes that send the employee name. This is used in ORTEC WS for Team Schedulers, for these locations:\nSickness tile + details Swap requests + details Leave requests tile + details + staffing popover Schedule overview Shift details popover Shift edit screen Employee details  Note: this only makes this information available, the UI will start showing this in a later update.\n\nTest hint(s): None","","13482",""]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7",null,null,null,"Candidates for shift does not correctly consider employees with a pending update","The 'candidates for shift' functionality could raise an error when an employee which was assigned to a shift with a pending update.\nThis has been fixed.\n\nTest hint(s):\nVerify the candidates for shift functionality no longer raises an error when employees are assigned to a pending update.","","13545","https://ortec.link/Request?HID=15748021"]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7",null,null,null,"External Optimizer could fail because of an unnecessary permission check while calculating violations during optimizations with 'Registration' rule involved","External Optimizer could fail because of an unnecessary permission check while calculating violations during optimizations with 'Registration' rule (BookKeepingReq) involved\r\nThis has improved.\r\n\r\nTest hint(s):\r\nVerify external optimizer succeeds when labor rules set with a rule 'Registration' is involved in the to be optimized schedule.","","13816","https://ortec.link/Request?HID=15816289"]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7",null,null,null,"Unattended Updates - Added check for environments that skipped or failed PostInstall","When an active environment was not selected in the PatchUtility configuration, it could lead to PostInstall not being run for that environment.\r\nNor were any errors during the PostInstall step detected.\r\nThis has been improved.\r\n- A pre-script check has been added to look for active environments that are not selected in the PatchUtility configuration in CSCS.\r\n- Besides checking the output of the PatchUtilConsole, it's logfile is now also is checked for known errors during PostInstall. \r\nNote: as such an error does not block updating other environments, this is treated as a non-critical error. The script will continue and a warning will be shown in the confirmation email.\r\n\r\nTest hint(s):\r\n1. Verify updates are rolled out without false warnings","","14101",""]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - Added detection of corrupt data in database before starting update process","When a CVIS update is present, UnattendedUpdates will now check the OWS database(s) for corrupt data before the actual update process starts.\r\nThis is done by running the following scripts:\r\n- 10000: Detect user- 1999999: Detect corrupt data - 9999999: Detect corrupt data (after conversion) \r\n The databases of all environments will be checked first. When any of them return corrupt data, the script will stop before shutting down the Starter Service and applying updates. \r\n Do note that checking the corrupt data scripts additionally does take extra time, especially on larger databases. The check can be disabled if desired (see upgrade notes).\r\n\r\nTest hint(s):\r\n1. Verify script will stop when an OWS database contains corrupt data.","Note: in order to use this functionality, it is necessary that this update is installed first as DBUpdateConsole.exe needs to be updated. The check will be skipped when the DBUpdateConsole is not yet updated.\r\n\r\n\r\nThis functionality is enabled by default, but can be disabled by adding a setting to the UnattendedUpdate_Config.xml located in C:\\ProgramData\\Ortec\\ORTEC Workforce Scheduling\\UnattendedUpdates \r\nIn the <scriptOptions> node add <testOwsDatabaseForCorruptDataBeforeUpdate>N</testOwsDatabaseForCorruptDataBeforeUpdate>\r\nSee Template_UnattendedUpdate_Config.xml for an example","15561",""]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - Support cusfile for Ortec routing products ","To increase DBUpdate support for Ortec routing products in UnattendedUpdates, the name of the cus file is no longer set hard-coded to OWSDatamodelPatches.cus, but determined dynamically.\r\n\r\nTest hint(s):\r\nNone","","21743",""]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - Improved DBUpdate output handling","In UnattendedUpdates, verifying the success of the DBUpdate process was done by interpreting the output text.\r\nThis has been improved.\r\nThe lastExitCode from the DBUpdateConsole process is also used to verify success or failure, making evaluation less dependent on interpreting plain text.\r\n\r\nTest hint(s):\r\n1. Verify that UnattendedUpdates interprets the DBUpdate results correctly. See DBUpdate log file for verification.","","21895",""]
[null,null,1580730,"2024-01-18",null,"Development\\OWS7\\OWS for Employees",null,null,null,"Backend-API: A new setting ShowCustomActivityProperties was added for ESS7 app","Backend-API: A new setting ShowCustomActivityProperties was added for ESS7 app with a default value of False.\n\nTest hint(s):\nOWS for Employees: verify application can be logged into ESS7 App: verify application can be logged into",null,"28572",""]
[null,null,1580730,"2024-01-18",null,"Development\\OWSforTeamSchedulers",null,null,null,"Backend Domains API logging was not split per environment ","Backend Domains API logging was not split per environment.\nThis has been improved.\n\nIt is now possible to split logging into different files based on the \nenvironment name. If the environment name is not available given the context of the call, we still log to a single general file.\nThis means that there will always be at least 2 files: WebApiLog-xxx.txt and WebApiLog-{tenant_name}_xxx.txt.\nThe location that these files are written to have not changed.  For instance, the default \"%PROGRAMDATA%\\\\Ortec\\\\ORTEC Workforce Scheduling Backend API\\\\Logs\\\\WebApiLog-xxx.txt\" would now also have a file \"......\\\\WebApiLog-default-xxx-.txt\".\nThis change impacts both the Team Scheduler and Ad Hoc Planning applications.\nSome examples to clarify in which cases where an environment name is or is not available.\nThe following lines will end up in the general file\n2023-12-15 09:52:52.691 1: Starting web host\n2023-12-15 09:52:52.827 1: Version: OWS-0 Built: 2023-09-27T16:22:48+02:00\nThe following lines will end up in the environment specific file\n2023-12-15 10:05:01.122 +01:00 [INF] Tenant academy : HTTP GET /teamscheduling/api/v1/toggles responded 200 in 198.4640 ms\n2023-12-15 10:05:03.927 +01:00 [ERR] Tenant academy : The service is currently not able to process this request.\nThis functionality is disabled by default. It can be turned on using the BDA Postinstall (BackendDomainApisWebSite.Configuration.UI) using the checkbox \"Split logfiles by environment name\".\n\nTest hint(s):\nVerify logging is now split per OWS environment after enabling this functionality.","","29847",""]
[null,null,1583033,"2024-02-01",null,"Development\\OWS7",null,null,null,"It was possible to pick a shift using Ortec WS for Employees/ESS Mobile App  on the last day of a schedule that created a violation on first day of the next schedule","It was possible to pick a shift using Ortec WS for Employees/ESS Mobile App on the last day of a schedule that created a violation on first day of the next schedule.\r\nThis has been resolved, picking such a shift is no longer possible and will now correctly return a proper violation message.\r\n\r\nTest hint(s):\r\nTry to pick a shift using Ortec WS for Employees/ESS Mobile App  that would create a violation in the next schedule and verify this is no longer allowed","","10081"]
[null,null,1583033,"2024-02-01",null,"Development\\OWS7",null,null,null,"After replace by activity type of class 'Leave of absence' the hint text did not show name of original shift anymore","A shifts hint text did not show the name of the original shift when it was replaced by activity type leave of absence. This has been fixed.  The hint text will now display the name of the original shift and other configured elements.\n\nTest hint(s): \nVerify the hint text of a shift has all configured elements after replacing a shift by activity type leave of absence.","","11326"]
[null,null,1583033,"2024-02-01",null,"Development\\OWS7",null,null,null,"Trying to open the messages form multiple times could cause an exception","Trying to open the messages form multiple times could cause an exception\nThis has been improved.\n\nTest hint(s):\nVerify if clicking (several consecutive times) on the \"number of messages\" indication in the status bar of the ORTEC WS Win32 client shows or refreshes the messages form.","For this solution to become available, the ORTEC WS Win32 client must be installed.","11623"]
[null,null,1583033,"2024-02-01",null,"Development\\OWS7",null,null,null,"Access Control: In the management tab the \"system\", \"temp\" and \"unknown\" users were shown.","In the management tab in Access Control the \"system\", \"temp\" and \"unknown\" users were shown. \n\nThis has been improved.\nThese users will not be visible anymore; the user of Access Control cannot accidently change or remove these users.\n\nTest hint(s):\nVerify user list and search in Access Control no longer shows \"system\", \"temp\" and \"unknown\" users","","12996"]
[null,null,1583033,"2024-02-01",null,"Development\\OWS7",null,null,null,"Default value of setting CompensationRulesAllowedNumberOfDaysToLookForward has changed","The default value of setting CompensationRulesAllowedNumberOfDaysToLookForward has changed from 1 to 400.\n\nTest hint(s):\nVerify (in OWS-Settingsmanager) that the value of setting PERFORMANCE\\COMPENSATIONRULES\\COMPENSATIONRULESALLOWEDNUMBEROFDAYSTOLOOKFORWARD is set to 400 when it still had the default value of 1","","13680"]
[null,null,1583033,"2024-02-01",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - Added option to run additional scripts before update","To accommodate synchronizing database change tracking data to the Big Data Portal, functionality has been added to call external Powershell scripts during the UnattendedUpdate process. These will be called after the Starter Service has been shut down and before updates are applied.  Scripts can be configured by adding an extra node at the bottom of the UnattendedUpdate_Config.xml.  <customScripts> \n   <customScript>\n        <description>ScriptIdentifier</description>\n        <scriptPath>D:\\path\\Scriptname.ps1</scriptPath>\n        <scriptParams>\n            <scriptParam name=\"param1\" value=\"paramValue 1\"/>\n            <scriptParam name=\"param2\" value=\"paramValue 2\"/>\n        </scriptParams>\n    </customScript> \t\n</customScripts>  \n\nMultiple scripts can defined by adding extra  <customScript> nodes. Parameters can be added or removed with the <scriptParam> tag \nSee Template_UnattendedUpdate_Config.xml for an example. \nAny failures in an external script will stop the UnattendedUpdate process\n\nTest hint(s):\nVerify that correctly configured scripts are executed.","Note: as external scripts may contain unverified code, it is advised to revisit the access permissions to UnattendedUpdate_Config.xml in C:\\ProgramData\\Ortec\\ORTEC Workforce Scheduling\\UnattendedUpdates","14180"]
[null,null,1583033,"2024-02-01",null,"Development\\OWS7\\Technical improvements",null,null,null,"Used binaries were vulnerable for CVE-2024-21319 - Microsoft Identity Denial of Service","Used binaries were vulnerable for CVE-2024-21319 - Microsoft Identity Denial of Service\nThis has been mitigated by upgrading the binaries to a newer version.\n\nFor reference:\nCVE-2024-21319 - Security Update Guide - Microsoft - Microsoft Identity Denial of service vulnerability\n\nTest hint(s):\nNone","","31065"]
[null,null,1585598,"2024-02-15",null,"Development\\OWS7",null,null,null,"Replace by leave could behave inconsistently when there were multiple activities in a shift","Replace by leave in case of full-day leave requests could behave inconsistently, depending on the contents of the shift.  \nIf a shift fully consists of activity types that are considered labour but also rest (e.g. certain absence shifts), no activities were replaced by leave.  \nIf a shift partially consisted of those activity types, the labour activities were replaced regardless if they are also considered as rest.  \nThis has been improved. \nNow only activities that are considered labour and no rest are replaced by leave in case of full-day leave requests. \nAdded feature toggle: FEATURETOGGLES\\REPLACEWITHLEAVEWITHINSHIFTONLYATWLABOURANDNORESTTIMEACTIVITIES which is enabled by default.\n\nTest hint(s):\nVerify that for a shift with multiple activities, including an activity that is considered labour and no rest,  the activity that is considered labour and no rest is not replaced by the leave activity type when approving leave wish.","","11142","https://ortec.link/Request?HID=15505919"]
[null,null,1585598,"2024-02-15",null,"Development\\OWS7",null,null,null,"Importing an Illness for an employee with 0 contract hours was not possible and creating an illness in the ORTEC WS Win32 client was not consistent","Importing an Illness for an employee with 0 contract hours was not possible and creating an illness in the ORTEC WS Win32 client was not consistent. This has been improved. \n Importing an Illness for an employee with 0 contract hours will now generate a warning and will create the Illness. Replaceable shifts are now always unplanned when creating an illness in the ORTEC WS Win32 client, illness shifts are not created for zero hour contract days, and are now always created for non-zero hour contract days. \nAdded feature toggle: FEATURETOGGLES\\IMPROVEILLNESSPROCESSORFORZEROHOURCONTRACTS and is by default enabled.\n\nTest hint(s): \nVerify that Importing an Illness for an employee with 0 contract does create an Illness. Verify that when creating an illness in the ORTEC WS Win32 client, shifts are unplanned, and ilness shifts are created where needed.","","11213","https://ortec.link/Request?HID=15513577"]
[null,null,1585598,"2024-02-15",null,"Development\\OWS7",null,null,null,"OWS for Employees: Removing availabilities in bulk could block other actions","OWS for Employees: Removing availabilities in bulk could block other actions\n\nThis has been improved.\nOn the back-end the commands were queued and could block other actions.\nThe cause of this \"queuing\" has been removed such that concurrency should improve.\n\nAdded feature toggle FeatureToggles\\ImproveDeleteWishCommand and is by default enabledNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\nVerify updating / removing availabilities in OWS for Employees","","11757","https://ortec.link/Request?HID=15612159"]
[null,null,1585598,"2024-02-15",null,"Development\\OWS7",null,null,null,"Candidates for shift plans out shift instead of swapping them","It was no longer possible to swap shifts with an employee proposed by the candidates for shift functionality.\nThe shift of the proposed employee was unplanned since OWS 7 update 1512223 (2022-10-14)\nThis has been improved.\n\nIt is again possible to swap shifts with an employee proposed by the candidates for shift functionality. \nNote a swap will only take place when the proposed employee is in the same department as the proposal shift.\nWhen the proposed employee belongs to a proposal department, any overlapping shifts will be planned out.\n\nTest hint(s):\n1. When using candidates for shift on a planned shift A to plan it at an employee in the same department who already has has a shift B assigned. Verify that when selecting that employee, the shifts are swapped instead of shift B being unplanned.\n2. When using candidates for shift on a planned shift A to plan it at an employee in a proposal department who already has has a shift C assigned. Verify that when selecting that employee, the shift A is planned at the proposed employee with shift C being unplanned","","11863","https://ortec.link/Request?HID=15617633"]
[null,null,1585598,"2024-02-15",null,"Development\\OWSforTeamSchedulers",null,null,null,"[BDA]Send prefix with employee information  ","The prefix of the employee name is now made available to the routes that send the employee name. This is used in ORTEC WS for Team Schedulers, for these locations:\r\nSickness tile + details Swap requests + details Leave requests tile + details + staffing popover Schedule overview Shift details popover Shift edit screen Employee details  Note: this only makes this information available, the UI will start showing this in a later update.\r\n\r\nTest hint(s): None","","13482",""]
[null,null,1585598,"2024-02-15",null,"Development\\OWS7\\Technical improvements",null,null,null,"An event viewer warning has been added when the status of a CPMS process is set to unknown","An event viewer warning has been added when the status of a CPMS process is set to unknown.\n\nTest hint(s):\nNone","","13533","https://ortec.link/Request?HID=15745382"]
[null,null,1585598,"2024-02-15",null,"Development\\OWS7",null,null,null,"Ortec Relevance App: sending notifications to a large group of employees (+1000) could fail","Ortec Relevance App: sending notifications to a large group of employees (more than 1000) could fail.\nThis has been fixed.\n\nTest hint(s):\nVerify that you can send a notification to more than 1000 employees.","","14481","https://ortec.link/Request?HID=15862462"]
[null,null,1585598,"2024-02-15",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for the new employee proposal feature in ORTEC WS for Team Schedulers","Technical preparation for the new employee proposal feature in ORTEC WS for Team\nSchedulers.","","26126",""]
[null,null,1585598,"2024-02-15",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to improve the performance of retrieving scheduling periods","Technical change to improve the performance of retrieving scheduling periods through the BackendDomainsApi.\n\nTest hint(s):\nNone","","31544",""]
[null,null,1585598,"2024-02-15",null,"Development\\OWSforTeamSchedulers",null,null,null,"The BackendDomainsApi only logged a line whenever an HTTP request was finished","The BackendDomainsApi only logged a line whenever an HTTP request was finished. This made analysis of problems difficult in some cases, especially when trying to identify large amounts of incoming traffic.\nThis has been improved. We now also log a line whenever we start processing an HTTP request.\nThis logging has the following format. A 6 character identifier has been added to match requests from the same http call.\n2024-02-02 09:37:39.753 7: \"4c2fec\" Tenant \"some-tenant\" : HTTP \"GET\" \"/general/api/v1/versioninfo\" start processing\n\nTest hint(s):\nNone","","31551",""]
[null,null,1585598,"2024-02-15",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to improve the performance of several API calls for Team Schedulers","Technical change to improve the performance of several API calls for Team Schedulers\n\nTest hint(s):\nNone","","31675",""]
[null,null,1585598,"2024-02-15",null,"Development\\OWS7",null,null,null,"Sending shift picking notifications to all potential candidates could fail on unavailability of one employee","Sending shift picking notifications to employees could fail. This\r\nwas the case when an employee was unavailable within the department on the day of the shift opened for bidding and the feature toggle CheckAllLaborRulesForViolationDifferencesInGetEmployeesThatCanBidOnShifts\r\nwas enabled.  \r\nThis has been fixed. \r\nShift picking notifications will be sent out to\r\npotential candidates, even when there is an absent employee within the\r\ndepartment on the day(s) of the shift(s).\r\n\r\nTest hint(s):\r\nVerify when setting a shift open for bidding, a notification is sent to all employees that are able to do the shift.","","31727","https://ortec.link/Request?HID=16455862"]
[null,null,1587683,"2024-02-29",null,"Development\\OWS7",null,null,null,"Opening workstation planboard could show message stating length of interval should be at least 1 day","Opening the workstation plan board could show a message stating \"the length of given interval should be at least 1 day\".  This has been fixed.\r\n\r\nTest hint(s):\r\nNone","","14425","https://ortec.link/Request?HID=15858356"]
[null,null,1587683,"2024-02-29",null,"Development\\OWS7",null,null,null,"Locks were not freed when using linefeed in an exchange remark","When entering an exchange remark (dependent on UseRemarkExchanges) with invalid characters or line feeds, this could cause a panic exception with unreleased locks as a result.\nThis has been improved.\nThe text entered for an exchange remark is now checked for invalid and non-displayable characters and corrected when needed.\n\nTest hint(s):\nVerify that entering an exchange remark will not raise an error.","","18413","https://ortec.link/Request?HID=15954748"]
[null,null,1587683,"2024-02-29",null,"Development\\OWS7",null,null,null,"ORTEC WS Win32 Client: Opening duty view on published schedule required permission ROSTER_PLAN_READ","ORTEC WS Win32 Client: Opening a duty view on published schedule for a period that is crossing the month line without permission ROSTER_PLAN_READ failed.\nThis has been fixed.\n\nTest hint(s):\nVerify that when a user has the permission ROSTER_PUB_READ  the duty view from a published schedule for a period that is crossing the month-line can be opened","For this solution to become available, the ORTEC WS Win32 client must be installed.","18414","https://ortec.link/Request?HID=15954767"]
[null,null,1587683,"2024-02-29",null,"Development\\OWS7",null,null,null,"The query to load workstation planboard data could cause a delay","The query to load workstation planboard data could cause a delay.\r\nThis has been improved.\r\nThe query is called less times and with less data, which makes the overall performance better when loading data for the Workstation planboard.\r\n\r\nTest hint(s):\r\nNone","","25933","https://ortec.link/Request?HID=16047105"]
[null,null,1587683,"2024-02-29",null,"Development\\OWS7\\Technical improvements",null,null,null,"Waiting too long on a blocked thread could halt a server process","Waiting too long on a blocked thread could halt a server process in some cases.\nThis has been improved.\nWhen two threads are suspect of being deadlocked (on a critical section lock), the blocked thread will be receive an exception and locks will be released. This will allow the other thread to continue\nNote this is dependent on the existing feature toggle CriticalSectionLockTryEnter being enabled\n\nTest hint(s):\nNone","","28492","https://ortec.link/Request?HID=16160144"]
[null,null,1587683,"2024-02-29",null,"Development\\OWS7",null,null,null,"OWS Back-end API returned an error when more than 2100 workstations were available for a department","OWS Back-end API returned an error when more than 2100 workstations were available for a department\r\nWhen realizing a shift in ORTEC WS for Employees, ESS7 App or the mobile app, there could be an error when there are more than 2100 workstations valid for the department.\r\nThis has been fixed.\r\nRetrieving workstations will be done in chunks of 1000 when necessary.\r\n\r\nTest hint(s):\r\nVerify that entering a realization using ORTEC WS for Employees, the responsive web app or the mobile app for a department with +1000 Workstations succeeds.","","29444","https://ortec.link/Request?HID=16176463"]
[null,null,1587683,"2024-02-29",null,"Development\\OWS7",null,null,null,"Database functions to retrieve cyclical shifts could unnecessarily increase the GLOBAL_ID counter","The database functions to retrieve cyclical shifts (i.e. GETCYCLICSHIFTSFORDPTS_BI) could cause a rise in the GLOBAL_ID SequenceCounter in the sequence table.\r\nThis has been improved.\r\nThese functions will now use internal id's to export the cyclical shift data.\r\nAdded feature toggle: FeatureToggles\\CopyDutiesAsInternalObjectForInternalShifts which is enabled by default.\r\n\r\nTest hint(s):\r\nNone","","29447","https://ortec.link/Request?HID=16176534"]
[null,null,1587683,"2024-02-29",null,"Development\\OWS7",null,null,null,"New Client permission for changing activity times while subcontracting","A new permission SHIFT_SUBCONTR_CHANGE_ACTIVITY_BEGIN_END has been added to AccessControl (Ortec WS for Windows\\Planboard) to allow/disallow the user to change the begin / end time of an activity when subcontracting a shift.\nThis permission will automatically be granted to usergroups already allowed the permission SHIFT_SUBCONTRACT_TO\n \nNote that in previous versions it was possible to change the begin or end time of an activity when subcontracting a shift even when the permission to realize a shift was not granted. This has been fixed.\n\nTest hint(s):\nVerify that permissions SHIFT_SUBCONTR_CHANGE_ACTIVITY_BEGIN_END and SHIFT_REALISATION_WRITE for relevant status are both needed to change the activity begin/end times when subcontracting a shift","For this solution to become available, the ORTEC WS Win32 client must be installed.","31803",""]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7",null,null,null,"Remuneration definition \"Overtime: fixed in regard to publication\" could give unexpected overtime","Remuneration definition \"Overtime: fixed in regard to publication\" could give unexpected overtime.\nWhen adding shift before an existing shift in publication and realizing that added shift adjacent after this existing shift this could give could give unexpected overtime.\nThis has been improved.\n\nThis improvement is behind feature toggle ImproveGetIntervalsAndWorkIndicatorsInOvertimeDefCompareSchedulesRem and by default False.\n\nTest hint(s):\nNone","","12071","https://ortec.link/Request?HID=15635421"]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7",null,null,null,"Recalculate bookings from import only triggered on a change in employment terms interval.","Recalculate bookings from employee import only triggered on a change in employment terms interval.\nThis has been improved.\nA change in availability or EmploymentTermsGroup will now also trigger a recalculation on import if the setting RECALCULATESAVEDBOOKINGSONIMPORT is set to Y.\n\nTest hint(s):\n1. With the setting RECALCULATESAVEDBOOKINGSONIMPORT on Y, import a EmploymentTerms update with only a change in availability. Verify that this has lead to a recalculation of the saved bookings \n2. With the setting RECALCULATESAVEDBOOKINGSONIMPORT on Y, import a \nEmploymentTerms update with only a change in employment terms group. Verify that \nthis has lead to a recalculation of the saved bookings","","13123","https://ortec.link/Request?HID=15712293"]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7",null,null,null,"It was not possible to turn of the notification sound effect when a new mailbox message was available.","It was not possible to turn off the notification sound effect that sounds when a new mailbox message is available.\nThis has been improved.\n\nA new user setting '\\PLAYREMINDERSOUND' is made available to toggle the notification sound effect. Its default value is TRUE and will play a sound when receiving a new message.\nSet user setting '\\PLAYREMINDERSOUND' to value FALSE in the setting manager, refresh settings and restart the client. This is also available for the DEFAULT_USR.\n\nTest hint(s):\n1. After setting '\\PLAYREMINDERSOUND' to FALSE, do an action that causes a message in the message box and verify there is no sound when the message is received.","For this solution to become available, the ORTEC WS Win32 client must be installed.","18452","https://ortec.link/Request?HID=15955889"]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7",null,null,null,"Include German helpfile in OWS update","A German helpfile has been added to the win32 Client.\r\nThis file is placed by the win32 Client installer and also by a new update zip (Update_xxxxxxx_Help.zip)\r\n\r\nTest hint(s):\r\n1. Verify that the helpfile is now displayed in German when language if the win32 Client language is set to German","For this solution to become available, the ORTEC WS Win32 client must be installed.","22408","https://ortec.link/Request?HID=16029803"]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7",null,null,null,"Picking two subcontracted nightshifts in a row by an employee in a proposal department failed","Picking two subcontracted nightshifts in a row by an employee in a proposal department failed with the message \"The employee is not available for the lending department during the whole interval\"  \nThis has been improved.\n\nTest hint(s):\n1. Verify that an employee from a proposal department can pick two subcontracted nightshifts in a row is possible.","","26044","https://ortec.link/Request?HID=16055454"]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7",null,null,null,"The DbUpdate process could produce false-positive warnings regarding cost-centers.","The DbUpdate process could produce false-positive warnings regarding cost-centers when no cost-centers are defined.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nNone","","28276","https://synergy.ortec.com/Synergy/docs/WflRequest.aspx?BCAction=1&ID=%7ba5c2b607-dbea-4669-b142-bb0930e918ed%7d"]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7",null,null,null,"Modifying a leave request in OWS Win32 Client could result in a Panic exception","Modifying a leave request in OWS Win32 Client could result in a Panic exception when an incorrect date was provided.\nThis has been fixed.\n\nTest hint(s):\n1. Verify leave request can be entered and changed Verify shifts can be planned in/out on a planboard.","","29669","https://ortec.link/Request?HID=16210428"]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7",null,null,null,"The skill requirements counter showed the wrong totals when night shifts are involved","The skill requirements counter showed the wrong totals when night shifts are involved\nThis has been fixed\n\nTest hint(s):\n1. Verify that the Skill requirement counters are correct when planning night shifts with skill requirement(s).","","31180","https://ortec.link/Request?HID=16363352"]
[null,null,1590101,"2024-03-14",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for self scheduling points in the employee proposal in ORTEC WS for Team Schedulers","Technical preparation for self scheduling points in the employee proposal in ORTEC WS for Team Schedulers","",31356,""]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7\\Technical improvements",null,null,null,"A transaction rollback did not have detailed logging of what changes of a fragment were rolled back.","A transaction rollback did not have detailed logging of what changes of a fragment were rolled back.\r\nThis has been improved.\r\nSome additional logging was added for future investigations.\r\n\r\nTest hint(s):\r\nNone","","31430",""]
[null,null,1590101,"2024-03-14",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for self scheduling support in ORTEC WS for Team Schedulers","Technical preparation for self scheduling support in ORTEC WS for Team Schedulers","","32135",""]
[null,null,1590101,"2024-03-14",null,"Development\\OWS7",null,null,null,"Subcontracting the same shift via teamscheduler/command handler and via OWS Client leads to inconsistent CURRENT_DPT_ID","Subcontracting the same shift via teamscheduler/command handler and via OWS Client leads to inconsistent CURRENT_DPT_ID and non-chronological subcontract ID\r\nThis has been fixed.\r\nWhen a new subcontract is created, it is assigned an ID which is higher then previous active subcontracts of the associated shifts.\r\n\r\nTest hint(s):\r\n1. subcontract a shift via an interface worker. Subcontract the same shift to another department using the client. Verify the current department of the shift after restarting the client.","","32407","https://ortec.link/Request?HID=16492663"]
[null,null,1590101,"2024-03-14",null,"Development\\OWSforAdHocPlanners",null,null,null,"AdHoc inefficient query causing timeouts","Reverted change \"The employee proposal functionality in Ad Hoc Planner was slow\" which was  released in ORTEC Workforce Scheduling 7 Update 1572321.\nIt turns out that in certain environments (with lots of employee data in the database) this change significantly worsens the overall performance of the Ad Hoc Planner.\nThe original issue will be investigated again to find a different solution.","","32828","https://ortec.link/Request?HID=16552109"]
[null,null,1592068,"2024-03-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"Backend preparation for the functionality to to visualize one-time shift wishes and the wildcards (also called \"jokers\") in ORTEC WS for Team Schedulers","Backend preparation for the functionality to to visualize one-time shift wishes and the wildcards (also called \"jokers\") in ORTEC WS for Team Schedulers.",null,32313]
[null,null,1592068,"2024-03-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"Backend preparation for the functionality to show self scheduling points in the schedule in ORTEC WS for Team Schedulers","Backend preparation for the functionality to show self scheduling points in the schedule in ORTEC WS for Team Schedulers",null,32690]
[null,null,1592068,"2024-03-29",null,"Development\\OWS7",null,null,null,"Added CMHS plugin DBLogWriterConsumer","A new CMHS plugin DBLogWriterConsumer is now included in the ORTEC WS delivery.\n\nThis plugin allows for text or xml data in a CMHS network to be written to the database for storage and analysis.\n\nTwo new tables (MessageLogHub and MessageLogHubArchive) and two stored procedures (sp_messageHubLog_moveToArchive, sp_messageHubLogArchive_search) have been added.\n\nThis change also includes a CJSS configuration that calls sp_messageHubLog_moveToArchive every 5 minutes to clean the table MessageLogHub, once CJSS variables are filled. \n\nThis job is disabled by default and should be turned on when this plugin is used.\n\n\n\nImportant! Querying this data should only be done on the MessageLogHubArchive table to ensure the stability of the CMHS networks.\n\nFor more information on this functionality, see ORD consultant help: https://consultanthelp.ortec.com/ORD/12/Release-Implementation-Paper/Functional-Improvements/Message-Hub.htm#MessageHub\n\n\n\nTest hint(s):\n\n1. Verify that plugin DBLogWriterConsumer is available in the CMHS network editor","A CJSS job has been added to move log records from the MessageLogHub table to the MessageLogHubArchive table. This is disabled by default and will trigger every 5 minutes.\n\nIn order for the task to work, two task variables that need to be filled: %DATABASESERVER% and %OPERATIONAL_DB%",32984]
[null,null,1592068,"2024-03-29",null,"Development\\OWSforTeamSchedulers",null,null,null,"Backend preparation for the functionality to show violations of types 'constraint' and 'wishes' in ORTEC WS for Team Schedulers","Backend preparation for the functionality to show violations of types 'constraint' and 'wishes' in ORTEC WS for Team Schedulers.",null,33092]
[null,null,1592068,"2024-03-29",null,"Development\\OWS7\\Technical improvements",null,null,null,"Improved memory usage of the employment condition groups an employee belongs to","Improved memory usage of the employment condition groups an employee belongs to.\n\nThe memory usage for each line in an employment condition group (in memory) was reduced by 4 bytes.\n\n\n\nTest hint(s):\n\nNone",null,33121]
[null,null,1594243,"2024-04-12",null,"Development\\OWS7",null,null,null,"Removed warning from the event log for loading shifts for internal schedules.","A warning was written to the Event log when shifts were loaded for internal schedules. This could flood the event log at customers using self rostering.\n\nThis has been improved.\n\nA notification on loading shifts for internal schedules will only be written to the server log.\n\nTest hint(s):\n\nNone",null,18136,"https://ortec.link/Request?HID=15937208"]
[null,null,1594243,"2024-04-12",null,"Development\\OWS7\\Technical improvements",null,null,null,"A logfile and event log could get flooded with messages with the text \"evaluating begin date of expression resulted in a value <= 0\" ","A logfile and event log could get flooded with messages with the text \"evaluating begin date of expression resulted in a value <= 0\"\n\nThis has been improved.\n\nThis warning message is now only logged to the logfile and event viewer when the pre-existing setting for logging account category line information, LogAclInfo, is enabled. \n\nThis settings should only be used in single user environment with the purpose to analyze bookings, by default this settings is off.\n\n\n\nTest hint(s):\n\nNone",null,18137,"https://ortec.link/Request?HID=15937210"]
[null,null,1594243,"2024-04-12",null,"Development\\OWS7",null,null,null,"RecalculateSavedBookingsOnImport could lead to excess recalculations of saved bookings when importing multiple terms group lines","RecalculateSavedBookingsOnImport could lead to excess recalculations of saved bookings when importing multiple terms group lines.\nThis has been improved.\nImplemented a new method behind setting RecalculateSavedBookingsOnImport that imports all terms group lines, checks if there are any changes in terms group lines, and recalculates saved bookings once from the begindate of the changes.\nAdded feature toggle Server setting: FeatureToggles\\ImproveRecalculateSavedBookingsOnImport which is enabled by default.\n\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\n1. Verify that bookings are (only) recalculated on import with setting \\Interfaces\\XMLImp\\RecalculateSavedBookingsOnImport enabled.\n2. Verify that saved bookings are calculated as expected",null,29433,"https://ortec.link/Request?HID=16175412"]
[null,null,1594243,"2024-04-12",null,"Development\\OWS7",null,null,null,"Workstations that are not valid were shown in ORTEC WS Win32 Client","Workstations that are not valid can no longer be selected in the duty form of the ORTEC WS Win32 Client.\n\nThe general setting UseValidPeriodForWorkstation should be activated.\n\n\n\n\n\nThis is checked differently, depending on the place where the duty form is opened/used:\n\nRegular shifts (master schedule); the begin date of the shift is taken as the reference date. Cyclical schedule shifts: the start date of the cyclical schedule + day / week the shift is assigned to is taken as the reference date.  Duty set / special duties: The valid from date of the workstation should fall within the validity period of the duty. Note; This means the validity end date of a workstation is not checked.  \n\nIn case an invalid workstation was already present in an existing duty / shift, it will remain there. Once another workstation is saved in the activity, the invalid workstation will disappear from the list.\n\nThe scope of this change was kept small, which means workstation validity periods are not checked throughout all of ORTEC WS (e.g. not in ESS7 nor are there any consistency checks).\n\nThe purpose of this change is to make it much less likely a planner selects an invalid workstation, but also to clean the workstation dropdown list with invalid workstations.\n\n\n\nTest hint(s): \n\n1. Verify when realizing a shift,\n\nonly workstations can be chosen that are valid on that day. \n\n2. Verify when defining a duty set\n\nduty, only workstations can be chosen that have a ???valid from??? date within the\n\nvalidity period of the duty.","For this solution to become available, the ORTEC WS Win32 client must be installed.",32472]
[null,null,1594243,"2024-04-12",null,"Development\\OWS7",null,null,null,"Transferring calculated entries using 'Carry over balance' could lead to incorrect calculated entries","Using a 'Transferbooking based upon an expression' (=Transfer) rule could sometimes lead to incorrect calculated entries when the rule was set to \"per entry\", \"per entry day\" or per \"equal properties\".\nThis could happen in very specific situations:\nIf the result of the Transfer rule was carried over with a \"Carry over balance\" type of rule that booked to a secondary account and the secondary account was then transferred back to the first account (close to a cycle, but separated by time) And, if the first account was requested for a period longer than the period defined in the \"Carry over balance\" rule.  \nThis has been improved.\nA new Feature Toggle IMPROVETRANSFERBOOKINGCALCULATIONS has been added and is set to disabled by default.\nThis change also needs Feature Toggle IMPROVEBOOKINGSWITHNESTEDCALCULATIONS to be enabled. Otherwise it won't have any effect.. \nAs mentioned in \"9958 - Bookings with nested calculations were sometimes calculated wrong\" the feature toggle IMPROVEBOOKINGSWITHNESTEDCALCULATIONS has risks for existing configurations and is therefore by default off. It is advised to turn on both feature toggles for new remuneration configurations. \n It is strongly advised to not to turn on both feature toggles for existing configurations in a production environment.\n\nTest hint(s):\nVerify that transferring calculated entries using 'Transferbooking based upon an expression'  shows correct entry calculations, specifically over a multi-year period and with carry over \"per entry\", \"per entry day\" or per \"equal properties\".",null,32517]
[null,null,1594243,"2024-04-12",null,"Development\\OWS7",null,null,null,"Added support for SQL Server 2022 and MSOLEDBSQL19 provider","Support has been added for use of SQL Server 2022 with OWS 7\nSupport has also been added for use of the 'Microsoft OLE DB Driver 19for SQL Server' provider (MSOLEDBSQL19(.1)).\n\nNotes on SQL Server 2022\nMicrosoft has removed the 'SQL Server Native Client' provider from SQL Server Management Studio 19 and  SQL Server 2022 and recommend to use 'Microsoft OLE DB Driver 19for SQL Server'.\nSee: https://learn.microsoft.com/en-us/sql/relational-databases/native-client/sql-server-native-client?view=sql-server-ver15\nHowever, it is still possible to add the 'SQL Server Native Client' provider and use this with OWS 7.\n\nNotes when using MSOLEDBSQL19(.1) driver for SQL connection\n- This provider has encryption options that are mandatory by default, but can be set to 'Optional' on the Advanced tab in the Data Link Properties form.\n\n- OWS Settings Manager \n  - When OWS Settings Manager is opened with params 'ServerName' and 'Catalog' filled in (needed when opening on another server than the main application server), the encryption option in the driver cannot be used\n  - When opening on the main application server, only the param 'ServerName' (and in case of multiple active environments, 'Environment' ) should be used. \n\n- BISupport\n  - Make sure to add the following attribute to the connectionstrings: Use Encryption for Data=Optional\n\nGeneric changes:\n- The DBUpdate script 'Detect compatibility level' will now expect that the compatibility level is set to a minimum of 130 (SQL Server 2016)\n- Improved message when an error occurred during retrieval of MultiLang translation in MS Reports, the database password would be shown in the error message. The password has been removed.\n\nTest hint(s):\n1. Verify that OWS can be configured and used with SQL Server 2022","Components that need attention during update: \n- To prevent the database password being shown when an error occurred during retrieval of multiLang translation in reports, the ReportServer installer should be uninstalled and reinstalled on the reportserver. - To use BI Support with MSOLEDBSQL19, BI.ps1 needs to be updated on the database server. \nIt is recommended to set the compatibility level of the OWS and BI databases to the highest possible level. In order to set it to 2022, version 19 of SQL Server Management Studio is required.\n\nIn order to use 'Microsoft OLE DB Driver 19 for SQL Server':\n- The provider must be installed. This can be downloaded from: https://learn.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver16\n- An installation prerequisite is a recent version of both the 32-bit as the 64-bit versions of the Visual C++ Redistributables (>= 14.34). These can be downloaded from: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version\n\nSee the encryption settings on the Advanced tab in the Data Link Properties form. If an encryption error is raised, either set the Connection encryption parameter to 'Optional' or provide a certificate and use the FQDN of the server hosting the SQL Server database.",32682]
[null,null,1594243,"2024-04-12",null,"Development\\OWS7",null,null,null,"Added command handler Omrp/CAdjustDutyDemandOnDay ","Added command handler Omrp/CAdjustDutyDemandOnDay \n\n This was copied from the /teamscheduling/CAdjustDutyDemandOnDay command handler.\n\n\n\nTest hint(s):\n\nNone",null,33271]
[null,null,1594243,"2024-04-12",null,"Development\\OWS7",null,null,null,"Extend logging during transaction rollback","For analysis purposes, additional logging has been added in case a transaction rollback should fail.\n\n\n\nTest hint(s):\n\nNone",null,33541]
[null,null,1594243,"2024-04-12",null,"Development\\OWSforTeamSchedulers",null,null,null,"Added some Finnish, Danish and French translations for Team Scheduling permissions in AccessControl","Added some Finnish, Danish and French translations for Team Scheduling permissions in AccessControl.",null,9408]
[null,null,1594243,"2024-04-12",null,"Development\\OWS7\\Technical improvements",null,null,null,"Waiting for DTC transactions when handling queries could slow down query processing on SQL Server 2022","Waiting for DTC transactions when handling queries could slow down query processing on SQL Server 2022\nIn the past we noticed that sometimes for snapshot transaction involved in DTC transaction on SQL Server the snapshotted data was inconsistent.\nA special query was called to add and wait for a correct state of the DTC transaction. \nFor reference see OSDCOMMAIN-9486 and OSDCOMMAIN-9470\nFor SQL Server 2022 this wait is no longer needed.\n\nFor OWS environments with a database running on SQL Server 2022 instances the StartSnapshotTransaction_WaitForDtcCommits will be turned off when running DBUpdate.\nFor OWS environments with a database running on SQL Server instances with a version < 2022 the StartSnapshotTransaction_WaitForDtcCommits will be turned when running DBUpdate.\nA warning will be shown if the StartSnapshotTransaction_WaitForDtcCommits setting was changed.\n\nTest hint(s):\n1.Verify transaction between CWSS main process and Interface workers are handled and finish correctly",null,32050]
[null,null,1597363,"2024-04-23",null,"Development\\OWS7",null,null,null,"Access Control from the client could sometimes open the windows (partly) outside of the display. ","Access Control from the client could sometimes open the windows (partly) outside of the display.\n\nThis has been improved.\n\nA check had been added to ensure the Access Control window always opens within the display.\n\n\n\nTest hints:\n\n1. Open access control from the client. Move the windows partly outside of your display and close the window. Open access control again and verify that the windows opens fully within the display.","For this solution to become available, the ORTEC WS Win32 client must be installed.",29674,"https://ortec.link/Request?HID=16212198"]
[null,null,1597363,"2024-04-23",null,"Development\\OWS7",null,null,null,"Added logging on locking exceptions","For analysis purposes, logging has been added in case adding description locks fails due to an exception.\n\nThe classname and id of the failing object will be logged in the CWSSServer log file.\n\nAdded Server setting FeatureToggles\\LogDescriptionInfoOnDescriptionLockException which is enabled by default.\n\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\n\n\nTest hint(s):\n\nNone",null,32588]
[null,null,1597363,"2024-04-23",null,"Development\\OWS7",null,null,null,"Transferring calculated entries using 'Carry over balance' could lead to errors when feature toggle IMPROVETRANSFERBOOKINGCALCULATIONS was enabled","Transferring calculated entries using 'Carry over balance' could lead to errors when feature toggle IMPROVETRANSFERBOOKINGCALCULATIONS (default disabled) was enabled.\nThis has been improved.\nThis feature toggle and code behind it is removed such that this cannot occur anymore.\nA new issue is planned to investigate wrong bookings using 'Carry over balance'.\n\nTest hint(s):\n1. Verify transferring calculated entries using 'Carry over balance' rule succeed.",null,34056]
[null,null,1597363,"2024-04-23",null,"Development\\OWS7",null,null,null,"UnattendedUpdates: Updated WinSCP to version 6.3.3","WinSCP used in UnattendedUpdates is updated to version 6.3.3\n\nTest hint(s)\n1. Verify that UnattendedUpdates can download files when during the update process.",null,34155]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7",null,null,null,"Added option to identify employees as non-binary","It was not possible to identify employees as non-binary.\nThis has been changed.\nAn additional option \"Non-binary\" has been added to the Gender selection dropdown.\nThe value of non-binary is stored as and can be imported as 'X'\n\nTest hint(s):\n1. Verify that it is now possible to identify an employee as \"Non-binary\", next to the already existing options \"Male\" and \"Female\".","For this solution to become available, the ORTEC WS Win32 client must be installed.\n\nNote: not updating the Client will cause: \n- An imported gender value of non-binary to be shown as one of the former value options of a previously selected employee\n- An imported gender value of non-binary to be overwritten with one of the former value options when opening the gender dropdown",28356]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Setting MinimumATWRestToEndShiftSeriesInHours was read for each possible shift in a series","Setting MinimumATWRestToEndShiftSeriesInHours was read for each possible shift in a series.\n\nThis has been improved. \n\nMinimumATWRestToEndShiftSeriesInHours will only be read when starting the server process or refreshing settings.\n\n\n\nTest hint(s): None",null,30361]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7",null,null,null,"Self rostering commands checked skill demand optimization results  even when UseDemandedDutySkills is disabled","Self rostering commands checked skill demand optimization results even when UseDemandedDutySkills is disabled.\n\nThis has been improved.\n\nSkill demand optimization results are no longer checked when UseDemandedDutySkills is disabled.\n\n\n\nTest hint(s): None",null,31810]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7",null,null,null,"Language codes were shown in the violation text of shift wish violations when Multilang module enabled","Language codes were shown in the violation text of shift wish violations when Multilang module enabled.  This has been improved.\nAdded feature toggle NoMultilangLanguageLabelsInViolationTextShiftWishViolation which is enabled by default.\n\nTest hint(s):  \n1. Verify multilang labels are not present in violation text of a shift wish violation when feature toggle NoMultilangLanguageLabelsInViolationTextShiftWishViolation is enabled.  \n2. Verify multilang labels are present in violation text of a shift wish violation when feature toggle NoMultilangLanguageLabelsInViolationTextShiftWishViolation is disabled.",null,33330]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7",null,null,null,"A new queue filter 'ShiftEmployeePropertyQueueFilter' has been added.","A new queue filter 'ShiftEmployeePropertyQueueFilter' has been added.\n\nThis filter works on shift changes for employees having a Yes value for a configured employee property valid on the shift date\n\nTo configure add the following filter to a shift queue export definition:\n\n<ShiftEmployeePropertyQueueFilter employeePropertyNames=\"booleanEmplProp1,booleanEmplProp2\"/>\n\nThe configured properties must be an employee property and of the type Yes/No.\n\nMultiple employee properties can be defined (separated by a comma).\n\nThe export triggers on shift changes in the following condition:\n\nThe (or one of the) employee(s) must have the value Yes for one of the configured employee properties valid on the (old or new) begin date of the shift\n\n\n\nTest hint(s):\n\n1. Verify the queue export filters on mentioned conditions",null,33359]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7",null,null,null,"Retrieving the Workstation or ActivityType data for the Dutyform activities tab was called twice on each click","When clicking on Workstation or Activity type control in Dutyform, the methods to retrieve the data to show in the dropdown were called twice on each click.\n\nThis has been fixed.\n\n\n\nTest hint(s): None",null,33520]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7",null,null,null,"ORTEC OWS for Employees: all valid duties in a dutyset and all valid special duties could be selected when adding a shift","ORTEC WS for Employees: all valid duties in a duty set and all valid special duties could be selected when adding a shift.\n\nThis has been improved.\n\nIn the ORTEC WS Win32 client a new checkbox has been added to the properties tab in the duty form of duty set duties and in the special duties form. This checkbox 'The shift can be added via ESS' allows the planner to decide whether it is possible for an employee to add the duty to their schedule in ESS. Default this checkbox will be on for the existing and new duties.\n\nFrom this update, only duties that have this checkbox checked will be available in ORTEC WS for Employees and ESS7 for adding shifts.\n\n\n\nTest hint(s):\n\n1. Verify that a shift can be added in ORTEC WS for Employees and ESS7 when the checkbox The shift can be added via ESS' for that duty is checked.\n\n2. Verify that a shift can not be added in ORTEC WS for Employees and ESS7 when the checkbox The shift can be added via ESS' for that duty is not checked.","For this solution to become available, the ORTEC WS Win32 client must be installed.",34078]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7",null,null,null,"DBAnonymize did not clear department remarks","DBAnonymize did not clear department remarks\n\nThis has been fixed.\n\n\n\nTest hint(s):\n\n1. Verify that after running the anonymisation script, the department remarks are changed to '--'","DBAnonymize has been updated. Requested databases should be anonymized\n\nusing this new version.",34258,"https://ortec.link/Request?HID=16598956"]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7",null,null,null,"ZipCode and CountryCode were not included in command to cloud map service","ZipCode and CountryCode were not included in command to cloud map service.\nThese have been added.\nZipCode and CountryCode can be used for alternative map service endpoint.\n\nExample command:\n<CPairs>\n<pair Reference=\"2904779_2904780_0\">\n  <origin CountryCode=\"NL\" Latitude=\"52.3893\" Longitude=\"4.8516\" ZipCode=\"1014 AN\"/>\n  <destination CountryCode=\"NL\" Latitude=\"52.04583\" Longitude=\"4.4732\" ZipCode=\"2718 EA\"/>\n</pair>\n</CPairs>\n\nTest hint(s):\nCloudMapService must be configured and running, and UseDistanceFromCloudMapService=True \n1. Open an account that requires distance calculation Verify the calculated distances",null,34717]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7\\Technical improvements",null,null,null,"When copying a shift in some cases the (translated) name and description of the shift were used unnecessarily","Superfluous steps were done when determining alternatives in self scheduling and when creating illness shifts. \nThis has been improved.\n\nTest hint(s):\n1. In ORTEC WS for Employees or ESS7: verify retrieving alternatives in self scheduling.\n2. In ORTEC WS Win32 Client: verify creating illness shifts of an employee.",null,35829]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7\\Technical improvements",null,null,null,"Improved memory usage of both department and resource instances","Improved memory usage of both department and resource instances\nThe size of the instances has been reduced by 4 bytes + 76 bytes that was allocated by an internal list that was never used in production code in those instances.\n\nTest hint(s): None",null,8134]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7\\Technical improvements",null,null,null,"Improved CWSS Server memory usage for TeamRotationUnitLines","Improved CWSS Server memory usage for TeamRotationUnitLines.\n\nTest hint(s): None",null,8135]
[null,null,1600173,"2024-05-17",null,"Development\\OWS7",null,null,null,"Improved memory usage of costcenter instances","Improved memory usage of costcenter instances.\nThis is done by only creating internal lists for duties and/or costcenters when needed, and freeing the list(s) when empty.\nAdded setting featuretoggles/ImproveMemoryUsageCostCenter which is enabled by default.\n\nTest hint(s): None",null,8386]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7\\Technical improvements",null,null,null,"The internal mechanism for session validation caused unnecessary database access","The internal mechanism for login session validation caused one or more database queries on each validation. \n\nEspecially the BackendAPI could do many consecutive validation calls, causing many database queries.\nThis has been improved.\n \n Login sessions are now cached in order to validate from memory most of the time.\nThe login session is cached for one minute, then it will be refreshed from the database.\n\nTest hint(s):\n1. Verify one can login to the OWS win32 Client and cloud applications.","",13906,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7",null,null,null,"Opening the 'Master Schedule ESS' report for an ESS or central department could result in a 'You are not authorized for provided 'ID_Department' parameter' error. ","Opening the 'Master Schedule ESS' report for an ESS department or central department could result in a 'You are not authorized for provided 'ID_Department' parameter' error.\r\nThis has been fixed. \r\nESS departments are now properly checked without errors and central departments have been removed from the department option list in the report.\r\n\r\nTest hint(s):\r\n1. Verify that a ESS department can be used as a department parameter in an ESS report.","",26256,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7",null,null,null,"When applying rules over a period for which an employee has multiple employment terms, an exception was shown and the account or requested planboard would not open correctly.","When applying rules over a period for which an employee has multiple employment terms, an exception was shown and the account or requested planboard would not open correctly.\nThis has been fixed. \n\nAdded FeatureToggle ImproveApplyRulesOverPeriod which is enabled by default.\n\nTest hint(s):\n1. Verify that rules are applied correctly by opening an account or a planboard in a scenario where an employee has multiple employment terms for the requested period.","",28422,"https://ortec.link/Request?HID=16156230"]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7",null,null,null,"BI: FACT_ASSIGNED_ACTIVITY table would show duplicates of the activities of a one time duty linked to multiple shifts","The BI table FACT_ASSIGNED_ACTIVITY would show duplicate activities in case a one time duty was linked to multiple shifts (by using plan in activity type on multiple selected days).\nThis has been fixed.\nThe activities of a one time duty linked to multiple shifts will now only show once.\n\nTest hint(s):\n1. Verify that the activities of a one time duty linked to multiple shifts will now only show once in the FACT_ASSIGNED_ACTIVITY table and associated views.","",30407,"https://ortec.link/Request?HID=16296723"]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7",null,null,null,"Importing a new shift with ExtraXMLCreator TIdentifyCOMTECShift planned out non-overlapping shifts and did not create an exchange ","When the ExtraXMLCreator TIdentifyCOMTECShift is setup to identify based on code, all non-overlapping shifts were planned out on import of a new shift and no exchange was created.\nThis has been improved.\nOnly shifts overlapping with the imported shift are unplanned by the ExtraXMLCreator TIdentifyCOMTECShift and will now trigger an exchange to be created when appropriate.\n\n\nCreating an exchange on unplanning shifts depends on FeatureToggle CreateExchangesWhenImportingShifts\nIf all shifts on the day of the import shift need to be unplanned, this is still possible by adding the node <PLANOUTEXISTING>ALLDAY</PLANOUTEXISTING> under <TLVNLShift> in the importfile.\n\nTest hint(s):\n1. Verify that only overlapping shifts are unplanned when a new shift is imported with ExtraXMLCreator TIdentifyCOMTECShift without adding node PLANOUTEXISTING with value ALLDAY to the import file. \n2. Verify that an exchange is created for unplanned shifts in case FeatureToggle CreateExchangesWhenImportingShifts is enabled.","",32442,"https://ortec.link/Request?HID=16493079"]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7\\Technical improvements",null,null,null,"After handling an update a server did not always immediately check for new updates","After handling an update, a server did not always immediately check for new updates.\nWhen a server was taking more time to load and handle updates than a configured wait time to re-query for pending updates, a worker would still use that configured wait time to wait before handling these pending updates. \nThis has been improved.\n\nA server will now immediately check for new updates when handling the previous update took more time than the configured wait time.\n\nTest hint(s): \nNone.","",33778,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7\\Technical improvements",null,null,null,"Improved logging for time out exception to provide more detailed information","Improved logging for time out exception to provide more detailed information.  \n\nThe logging now includes the thread and timestamp of the current lock in place. \nTime out exceptions occurring via command handler are included in the logging.\n\nTest hint(s):\n1. Verify thread and timestamp are included in logging when time out exception is raised.","",34606,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7",null,null,null,"When applying rules over a period ... an exception was shown and the account or requested planboard would not open correctly.","When applying rules over a period for which an employee has no employment conditions or the employee's active employment condition has no compensation rules an exception was shown and the account or requested planboard would not open correctly. \nThis has been fixed. \nAdded FeatureToggle ImproveApplyRulesOverPeriod which is enabled by default.\n\nTest hint(s): \nNone.","",36983,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7",null,null,null,"Access Control read configuration for OIDC and OutboundProxy on every login causing unnecessary database access","Access Control read configuration for OIDC and OutboundProxy on every login caused unnecessary frequent database access, slowing down other processes.\nThis has been improved.\nAs the following CSCS settings are not prone to frequent change, they are now cached (refreshed every 30 minutes)\n- CUASFW - OIDC - ResourceServerConfiguration\n- SharedCFW - Network - OutboundProxyConfiguration\n\nTest hint(s):\n1. Verify OWS Win32 Client can be logged into.\n2. Verify cloud applications can be logged into.","When changing the mentioned settings, the user has to wait a maximum of 30 \r\nminutes or restart the concerning application you are logging in to for the changes to take effect.\r\nI.e. a restart of the BackendAPI, BackendDomainsAPI or FirebaseAPI",37003,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7",null,null,null,"Access Control read userData on every login validation caused unnecessary frequent database access","Access Control read configuration for userData on every login and login validation caused unnecessary frequent database access, slowing down other processes.\nThis has been improved.\n\nTest hint(s):\n1. Verify OWS Win32 Client can be logged into.\n2. Verify cloud applications can be logged into.","",37004,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7\\Basic functionalities",null,null,null,"Several translations added for French, German, Danish, Finnish","Several translations have been added for [French, German, Danish and Finnish] for recent functional changes.\n\nTest hint(s):\nNone","",37095,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7\\Technical improvements",null,null,null,"Improved handling updates using a client side cursor querying the transaction data","Improved handling updates using a client side cursor querying the transaction data.\n  When using a server side cursor to query data while handling updates in CWSS process it was observed that SQL transactions and sessions could be blocked which was noticed and related to open FETCH API_CURSOR functionality. By using a client side cursor this FETCH API_CURSOR behavior is absent and should result in improved handling of transactions in CWSS processes \nThis has been evaluated at several customers and deemed ready to enable at all customers.  \n This functionality is behind added feature toggle: FeatureToggle\\ImproveHandlingUpdatesUsingClientSideCursor and is enabled by default.\n\nTest hint(s):\nNone.","",37177,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7",null,null,null,"When feature toggle CopyDutiesAsInternalObjectForInternalShifts is enabled a BI run could fail or show unexpected memory growth ","When feature toggle CopyDutiesAsInternalObjectForInternalShifts is enabled a BI run could fail or show unexpected memory growth.\n This has improved.\nFeature toggle CopyDutiesAsInternalObjectForInternalShifts introduced in 29447 \"Database functions to retrieve cyclical shifts could unnecessarily increase the GLOBAL_ID counter\" is turned off as a precaution.\nTwo issues have been reported related to this issue (37331 and 34048) that will be investigated.\n\nTest hint(s):\n1. Verify a BI load succeeds.","",37347,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7\\Technical improvements",null,null,null,"Internal structure for the administration of the shifts associated to duty set duties has changed","Internal structure for the administration of the shifts associated to duty set duties has changed.\nThe structure has changed to be better protected during (possible) concurrent access.\n\nTest hint(s):\nNone.","",9057,""]
[null,null,1602133,"2024-05-30",null,"Development\\OWS7",null,null,null,"Updates that were not relevant for a plan-board were evaluated and sent to all opened plan-boards (which could slow down main OWS Server)","Updates that were not relevant for a plan-board were evaluated and sent to all opened plan-boards(which could slow down main OWS Server).\nThis has been improved.\n\nAdded feature toggle setting: FeatureToggles\\UseClassBasedFilteringOnPlanDataViewEventHandler which is enabled by default.\n\nTest hint(s):\n1. Verify that opened planboards still receive updates when needed.","",9385,""]
[null,null,1603811,"2024-06-13",null,"Development\\OWS7\\Technical improvements",null,null,null,"Memory usage of subcontracts, positions in physical location and workstations has been improved","Memory usage of subcontracts, positions in physical location and workstations been improved.\nThe internal sizes has been reduced for several entities with the OWS application like subcontracts, positions in physical locations, workstation, workstation planner profiles and entry causes.\n\nTest hint(s):\n1. Verify subcontracting of shifts\n2. Verify entering/updating positions associated to physical locations (if configured)\n3. Verify entering/updating positions associated to workstations (if configured)\n4. Verify entering/updating workstation planner profiles\n5. Verify entering/updating entry causes (if configured)","","18325",""]
[null,null,1603811,"2024-06-13",null,"Development\\OWS7",null,null,null,"Dates & times were not always formatted correctly in ESS7 reports","Dates and times shown in ESS7 system reports were not always formatted according to the selected user language. This has been fixed.\r\nPlease note that non-ESS system reports were also changed as a preparation for Reporting functionality in Team Scheduler later this year.\r\n\r\nTest hint(s)\r\n1. Verify that dates & times are formatted for generated reports in OWS for employees, OWS Win 32 client and ESS7 App","","32405","https://ortec.link/Request?HID=16492635"]
[null,null,1603811,"2024-06-13",null,"Development\\OWS7\\Technical improvements",null,null,null,"Additional information is logged based on whether changes to the planboard are applied by workers","Additional information has been added to the logging based on whether changes to the planboard are applied by workers. \r\nAdded logging on invalid typecast exception regarding shift containers. \r\nThis has been done for analysis purposes.\r\n\r\nTest hint(s):\r\nNone","","32854",""]
[null,null,1603811,"2024-06-13",null,"Development\\OWS7",null,null,null,"SkillDemandOptimization could load unnecessary shifts","The SkillDemandOptimization interface worker could load unnecessary shifts for skill demand calculations potentially leading to a server halt. \nThis has been improved. \nTo guarantee that the required schedules are read on startup, we recommend setting the interface worker parameter ReadHistoryForAllDepartments=True.\n\nTest hint(s):\n1. Verify that making a few changes in an recent schedule in quick succession leads to correct skill demand calculations.\n2. Verify that making a few changes in an cyclical schedule in quick succession leads to no skill demand calculations and no worker halt.","","33222","https://ortec.link/Request?HID=16567751"]
[null,null,1603811,"2024-06-13",null,"Development\\OWS7",null,null,null,"The column 'ProcessGUID' was never filled when using DBLogWriterConsumer in a network","The column 'ProcessGUID' was never filled when using DBLogWriterConsumer in a network.\r\nThis has been fixed.\r\nA GUID is generated for each network on startup and can be used in BDLogWriterConsumer and FileWriter.\r\n\r\nTest hint(s):\r\n1. Start a network that uses DBLogWriterConsumer and feed it some input, verify that the column 'processGUID' is filled.\r\n2. Start a network that uses FileWrite with the parameter UseGUID set to true, verify that the exported filename contains a GUID.","","37060",""]
[null,null,1603811,"2024-06-13",null,"Development\\OWS7",null,null,null,"The configuration for auditing was read from the settings manager for each transaction.","The configuration for auditing was read from the settings manager for each transaction. \nThis has been improved. \nAs a performance improvement, the setting is now only read at startup and when refresh settings is used. \nAdded feature toggle setting featuretoggles/UseImprovedAuditHandler which is enabled by default.\nAfter updating the auditing configuration the workers need to be restarted to reload the changed auditing configuration.\n\nTest hint(s): \n1. Verify data changes for configured tables are recorded in the ros_auditing table.","","9799",""]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7\\Technical improvements",null,null,null,"When processing and realizing shifts using the TFillFieldsOfCOMTECShift extra XML creator the shift field data to be imported was examined too often","When processing and realizing shifts using the TFillFieldsOfCOMTECShift extra XML creator the shift field data to be imported was examined too often.\n\nThis has improved.\nThe shift field data to be imported is examined less during processing, this should improve processing and realizing shifts performance to some extent\n\nTest hint(s):  \n1.Verify that an import based on Shift/Department Code/Name still functions as expected",null,13998]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7\\Technical improvements",null,null,null,"Loading (shift) data did not use the database collation and indexes properly because of uppercase statement in the used queries","Loading (shift) data did not use the database collation and indexes properly because of uppercase statement in the used queries.\nThis has improved.\nThere is some improved performance of loading the (shift) data by taking advantage of the case insensitivity in the database of the Code, Name, and Description columns and omitting the transformation to uppercase when querying the shift IDs.\n\nTest hint(s):\n1. Verify that an import based on Shift/Department Code/Name still functions as expected",null,13999]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"The performance of identifying descriptions by code during import could be improved","When importing data there is an option to identify descriptions by code (e.g. shift, activity, costcenter, workstation). During import these codes are searched to retrieve the corresponding object.  The performance of this search has been improved. \n\n A Featuretoggle UseGlobalIndexOnCode has been added, this is default False\n\n\n\nTest hint(s):\n\n1. Verify that import by code works as expected.",null,18046]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"OWS Back-end API Improved error message handling on Reporting errors.","On some errors thrown by the ReportServer the error message could not be parsed correctly for ESS7 and a generic error message was shown.\n\nThis has been improved\n\nAdded an extra parsing method for ReportServer error messages such that more information in the error message\n\n\n\nTest hint(s):\n\nNone",null,30236]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"Added extra options for BI IL period settings","Two new period options for the BI incremental load have been added to the CSCS settings manager.\n- The setting IL_START_PERIOD now allows the value MinMonthsOrFirstOfYear: Minimum date of a rolling window of setting IL_START_VALUE months or the first day of the year. For example, A value of -4 would take the earlier date of the first day of this year OR the first day of 4 months ago. \n- The setting IL_END_PERIOD now allows the value MaxMonthsOrFirstOfNextYear: Maximum date of a rolling window of setting IL_END_VALUE months or the first day of the year. For example, A value of 4 would the the later date of the first day of next year OR the first day of 4 months in the future.\n\nTest hint(s):\n1. Verify that the new settings are available in the CSCS settingsmanager.\n2. Verify that the IL interval in HMY_BISETTINGS changes to the new calculated dates.",null,30242,"https://ortec.link/Request?HID=16284438"]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"All employees were locked when exporting data through a Queue Export","All employees were locked when exporting data through a Queue Export which led to undesired waiting times.\n\nThis has been improved.\n\nWith this change only data related to the export will be locked. \n\nThis change can be enabled/disabled using the newly introduced FeatureToggle ImproveLockingDescriptionsWhileExporting which is enabled by default.\n\n\n\nTest hint(s):\n\n1. Verify queue exports work as expected with FeatureToggle ImproveLockingDescriptionsWhileExporting enabled.",null,31040,"https://ortec.link/Request?HID=16358348"]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"Interfaces using TQueryExportSelector could still lock all employees","Interfaces using TQueryExportSelector could lock all employees.\n\nThis has been improved.\n\nNow the export will only lock the data needed for the export.\n\n\n\nTest hint(s):\n\n1. Verify that exporting using interfaces that have a TQueryExportSelector in the configuration still returns the expected results.",null,31041,"https://ortec.link/Request?HID=16358349"]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"Added consistency check on user property value deletion","For analysis purposes, an additional consistency check has been added on deletion of user property values.\n\nThis has been added behind existing feature toggle LogAccessViolationInUserProperty, which is disabled by default\n\n\n\nTest hint(s):\n\nNone","See feature toggle report in monitoring for customers that have this feature toggle already enabled.\n\nIf after upgrading any performance degradation is noticed, turning the toggle off is one of the first mitigation.",32403]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7\\Technical improvements",null,null,null,"When CWSS Server process started loading and verifying employee numbers it took up considerable amount of time when number of employees in database had become large","When CWSS Server process started loading and verifying employee numbers it took up considerable amount of time when number of employees in database had become large.\n\nThis has been improved.\n\nThe step to verify employeenumbers is skipped when loading data and UseCopyDataForSameEmployees is True.\n\n\n\nTest hint(s):\n\n1. Verify that importing employee data still works as expected.",null,32648,"https://ortec.link/Request?HID=16510668"]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"Enabling feature toggle CopyDutiesAsInternalObjectForInternalShifts could lead to access violations and memory leaks","Enabling feature toggle CopyDutiesAsInternalObjectForInternalShifts could lead to access violations and memory leaks\n  The database functions to retrieve cyclical shifts (i.e. GETCYCLICSHIFTSFORDPTS_BI) uses internal id's to export the cyclical shift data. This could lead to access violation and memory leaks. It was found this issue could occur when a realisation on one or more shifts existed in the cyclical shift data.\nThis has been improved.  \nThe existing feature toggle CopyDutiesAsInternalObjectForInternalShifts is enabled again.\nIt was disabled in issue 37347 in release 8.5.0(2024-05-30)_Build1602133\n\nTest hint(s): \nNone",null,34048,"https://ortec.link/Request?HID=16593536"]
[null,null,1605853,"2024-06-27",null,"Development\\OWSforTeamSchedulers",null,null,null,"Backend preparation for showing reports in ORTEC WS for Team Schedulers","Backend preparation for showing reports in ORTEC WS for Team Schedulers.",null,34339]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"Access violation could occur during an export using multiple TRunningAccountExportSelectors on running accounts with bookings originating and transferred from a shared running account ","Access violation could occur during an export using multiple TRunningAccountExportSelectors on running accounts with bookings originating and transferred from a shared running account\nThis has been improved.\n\nThe improvement done is behind feature toggle FreeRunningAccountsPerObjectWhileExporting. \nThe impact has been reduced by only clearing/freeing the calculated running account lines when a single TRunningAccountExportSelector is used in the definition. (i.e. for the definitions used in the BI runs)\n\nTest hint(s):\nNone","For customers having this feature toggle off because of this issue, it is advised to turn the feature toggle back on as it reduces memory usage / allocation during exports with large amounts of bookings involving (transferred) bookings on running accounts that are transferred as bookings on the running accounts that are exported.",35840,"https://ortec.link/Request?HID=16614566"]
[null,null,1605853,"2024-06-27",null,"Development\\OWSforTeamSchedulers",null,null,null,"The 'publish' and 'close' buttons were sometimes not shown in the schedule","In ORTEC Workforce for Team Schedulers, the 'publish' and 'close' buttons were sometimes not shown in the schedule.\nThis specifically happened for departments that did not have a closed period yet, but did have a cyclical schedule.\nThis has been fixed.",null,36884,"https://ortec.link/Request?HID=16618680"]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"Added a new command handler /OMRP/CNewShiftExistingDuty that can plan a new shift based on an existing duty.","Added a new command handler /OMRP/CNewShiftExistingDuty that can plan a new shift based on an existing duty.\n\nThe handler requires a given resource, department (with existing schedule), duty set duty, begin- and end-time.\n\nThe new shift will take the duty set duty as a base, but starting at the given begin time. The last activity will be shortened / extended to the given end time, and deleted if the duration falls outside of the new shift interval.\n\nIf the new given end time is less then the new given begin time, the new shift will  continue past 23:59 to the next day.\n\n\n\nTest hint(s):\n\n1. Verify the new commandhandler omrp/CNewShiftExistingDuty is available and able to plan in a new shift.",null,37368]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"ShiftEmployeePropertyFilter could not verify the correct date of a shift that was initially copied and then subsequently undone","ShiftEmployeePropertyFilter could not verify the correct date of a shift that was initially copied and then subsequently undone.\n\nThis has been improved.\n\nIn this scenario, the ShiftEmployeePropertyFilter now obtains the correct date, enabling the export of the desired files.\n\n\n\nTest hint(s):\n\n1. Verify the queue filter export of ShiftEmployeePropertyFilter when copying a shift (from one day to another) and undoing this action (Ctrl+Z)",null,37491]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7\\Technical improvements",null,null,null,"An empty TAccountingLines tag in import xml using the ExtraXMLCreator TFillFieldsOfCOMTECShift showed the error message \"No field for index -1\"","An empty TAccountingLines tag in import xml using the ExtraXMLCreator TFillFieldsOfCOMTECShift showed the error message \"No field for index -1\".\nThis has been improved.\n\nTest hint(s): \n1.Verify that an import based on Shift/Department Code/Name still functions as expected.",null,41768]
[null,null,1605853,"2024-06-27",null,"Development\\OWSforTeamSchedulers",null,null,null,"Issue with certain reports with -1 values in multiselect parameters.","A technical change was done in the \"Attendance list per department\" and \"Overview shifts\" reports. The dataset for retrieving activity type parameter values has been split into a dataset for the valid values and a dataset for the default values.\n\nEarlier, these were combined in one dataset, where -1 values were used to exclude unwanted activity types in the default values. This resulted in default values (-1) that were not in the valid values list.\n\nThis does not work well for reports that are opened in cloud apps (ESS, Team Scheduler).\n\nFunctionally there is no difference in the behavior of the reports. Performance has been tested and no major differences are observed in the retrieval of parameter values.",null,45957]
[null,null,1605853,"2024-06-27",null,"Development\\OWSforTeamSchedulers",null,null,null,"Block old scheduling periods in GetRosterPeriodsForDepartmentAsync","The nightly process to refresh the calculations for ORTEC for Team Schedulers could require too much memory. This could be the case when there are departments for which the last rosterperiod is a long time ago, which triggers a long period of calculations. \n\nThis has been improved by discarding rosterperiods that start more days ago than the value of the new MaximumScheduleAgeInDays setting in CSCS. These old rosterperiods will also not be shown in the dashboard anymore. \n\nThe new setting TeamScheduling/Dashboard/MaximumScheduleAgeInDays has been added with default value 365 days.",null,46093]
[null,null,1605853,"2024-06-27",null,"Development\\OWS7",null,null,null,"It is now possible to use the buffered history of running accounts instead of the global buffered history for interface workers","It is now possible to use the buffered history of running accounts instead of the global buffered history for interface workers.\n\nThis previously was only available on the main worker.\n\nTo use this new functionality, the process needs to be configured with an additional startup parameter UseBufferedHistoryOfRunningAccounts=True in system configuration\n\nWhen using this parameter in a worker process and there is an account with a larger buffered history than that of the worker process, please make sure that stored account entries on that account do not reference any plan data. Otherwise there is a risk of the worker needing to load referenced plan data during startup which could severely degrade worker startup time.\n\nTest hint(s):\n\nNone",null,46150]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle ConsiderCurrentShiftOnlyForDutyWishForRequestToWorkAndDutyRequests has been removed","Feature toggle ConsiderCurrentShiftOnlyForDutyWishForRequestToWorkAndDutyRequests has been removed.\nThis feature toggle was introduced in update 1548532 (2023-05-25).\n\nTest hint(s):\nNone",null,11139]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle ExcludeLinkedResourcesFromAccountingLinesRem has been removed","Feature toggle ExcludeLinkedResourcesFromAccountingLinesRem has been removed. \nThis feature toggle was introduced in update 1556752 (2023-07-14).\n\nTest hint(s): \nNone",null,11979]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle: IncludeSubContractedShiftsInNumberOfAssignedShifts has been removed.","Feature toggle IncludeSubContractedShiftsInNumberOfAssignedShifts has been removed.\nThis feature toggle was introduced in 10445 in update 1556852 (2023-07-14).\n\nTest hint(s):\nNone",null,12000]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle: IgnoreRestPeriodsPreceedingShiftsOnRestPerWeekWithActivityKind has been removed","Feature toggle IgnoreRestPeriodsPreceedingShiftsOnRestPerWeekWithActivityKind has been removed. \nThis feature toggle was introduced in 9091 in update 1556852 (2023-07-14).\n\nTest hint(s):\nNone",null,12959]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle UseFloatCheckingForUnequalStringFields has been removed","Feature toggle UseFloatCheckingForUnequalStringFields has been removed.\nThis feature toggle was introduced in update 1044087 (January 2018).\n\nTest hint(s): \nNone",null,3047]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle DetermineApprovedUntilDateBasedOnResourceWhenAddingResourceToDepartment has been removed","Feature toggle DetermineApprovedUntilDateBasedOnResourceWhenAddingResourceToDepartment has been removed.\nThis feature toggle was introduced in update 1057488 (2018-02-15).\n\nTest hint(s):\nNone",null,3050]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle AllowLoadingOfDutyWhenApplyingDutyChanges has been removed.","Feature toggle AllowLoadingOfDutyWhenApplyingDutyChanges has been removed.\nThis feature toggle was introduced in update 1081014 (2018-04-26).\n\nTest hint(s):\nNone",null,3055]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle CheckRemunerationsForTooManyNestedCalculations has been removed","Feature toggle CheckRemunerationsForTooManyNestedCalculations has been removed. \nThis feature toggle was introduced in update 1072598 (2018-03-29).\n\nTest hint(s):\nNone",null,3058]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle ImproveTransactionErrorHandling has been removed","Feature toggle ImproveTransactionErrorHandling has been removed.\nThis feature toggle was introduced in update 1084864 (2018-05-11).\n\nTest hint(s):\nNone",null,3059]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle CheckWholeDayForFirstDayOfIllnessExpression has been removed","Feature toggle CheckWholeDayForFirstDayOfIllnessExpression has been removed.        \nThis feature toggle was introduced in update 1089040 (2018-05-24).\n\nTest hint(s):\nNone",null,3061]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"The default value of feature toggle UseBreakOnCall has been set to True","The default value of feature toggle UseBreakOnCall has been set to True.\nThis make the new treatment Break (On call) available for all customers by default.            \nThis feature toggle was introduced in update 1159551 (2019-01-31).\n\nTest hint(s):\nNone",null,3062]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle RecalculateOnlyIfDateEarlierThanApprovedUntilDate has been removed","Feature toggle RecalculateOnlyIfDateEarlierThanApprovedUntilDate has been removed.      \nThis feature toggle was introduced in update 1556752 (2023-07-14).\n\nTest hint(s):\nNone",null,3066]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle UseRestOutsideLaborPeriodForRestPerNumberOfHoursLaborPeriodReq has been removed","Feature toggle UseRestOutsideLaborPeriodForRestPerNumberOfHoursLaborPeriodReq has been removed.           \nThis feature toggle was introduced in update 1498030 (2022-07-14).\n\nTest hint(s):\nNone",null,31472]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7\\Technical improvements",null,null,null,"Feature toggle ImproveSelfRosterUnPlanShiftPlanDutyLocks has been removed.","Feature toggle ImproveSelfRosterUnPlanShiftPlanDutyLocks has been removed.\n\nThis feature toggle was introduced in 8.5.0-1533112 (2023-02-16).\n\n\n\nTest hint(s):\n\nNone",null,33965]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7\\Technical improvements",null,null,null,"Feature toggle UseIndividualRostersForSelfRosteringOptions has been removed.","Feature toggle UseIndividualRostersForSelfRosteringOptions has been removed.\nThis feature toggle was introduced in 8.5.0-1496687 (2022-07-07).\n\nTest hint(s):\nNone",null,33966]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7\\Technical improvements",null,null,null,"The performance of creating a recordset and putting the employee calculation information in it has been improved","The performance of creating a recordset and putting the employee calculation information in it has been improved.\n\n\n\nTest hint(s): None",null,33967]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7\\Technical improvements",null,null,null,"Unnecessary information was processed when determining employee calculations for self scheduling","Unnecessary information was processed when determining employee calculations for self scheduling.\nThis has been improved.\nOnly relevant information is processed when determining employee calculations.\n\nTest hint(s):\n1. Verify employee calculations are in correct for self scheduling in ESS7 or WS for Employees.",null,33968]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7\\Technical improvements",null,null,null,"When an employee starts self scheduling, a copy is made from the original schedule, and all shifts were loaded during this process","When an employee starts self scheduling, a copy is made from the original schedule, and all shifts were loaded during this process.\nThis has been improved.\nAll shifts in the original schedule are already loaded, making it unnecessarily to reload the shifts.\n\nTest hint(s):\n1. Verify employee roster in self scheduling is a correct copy of the original schedule in ESS7 or WS for Employees.",null,33969]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7\\Technical improvements",null,null,null,"All Selfscheduling calls were offloaded to the interfaceworker configured in Comtec.Workforce.BackendApi.Portals.InterfaceServerNumber","All Selfscheduling calls were offloaded to the interfaceworker configured in Comtec.Workforce.BackendApi.Portals.InterfaceServerNumber.\nThis has been changed.\nA new CSCS Setting Comtec.Workforce.BackendAPI\\Portals\\SelfSchedulingWorkerCCDSNames has been added to allow offloading Selfscheduling calls to dedicated Selfscheduling worker(s).\nThe default behaviour to offload Selfscheduling calls to the interfaceworker remains active.\n\nTest hint(s):\n1. Verify that a frontend call to selfScheduling/calculationResults is processed correctly by the server (number) dictated by Comtec.Workforce.BackendApi.Portals.InterfaceServerNumber when the new setting  Comtec.Workforce.BackendAPI\\Portals\\SelfSchedulingWorkerCCDSNames is empty or \"0\".\n2. Verify that a frontend call to selfScheduling/calculationResults is processed correctly by the server (number) dictated by Comtec.Workforce.BackendAPI\\Portals\\SelfSchedulingWorkerCCDSNames  when the new setting  Comtec.Workforce.BackendAPI\\Portals\\SelfSchedulingWorkerCCDSNames  contains a valid servername. 3.. Verify that a frontend call to selfScheduling/calculationResults is NOT processed correctly by the server (number) dictated by Comtec.Workforce.BackendAPI\\Portals\\SelfSchedulingWorkerCCDSNames  when the new setting  Comtec.Workforce.BackendAPI\\Portals\\SelfSchedulingWorkerCCDSNames  contains an invalid servername.",null,33974]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"The selfroster command handlers CSetJoker / CPlanDuty / CGetShiftOptions / CGetDutiesWhenUnplanShift / CUnplanShiftPlanDuty locked too many objects or used too strict locks, resulting in blocked actions or longer wait times. ","Multiple locking-related improvements have been made to increase the performance of the self scheduling process.\nThe selfroster command handlers CGetShiftOptions / CGetDutiesWhenUnplanShift / CUnplanShiftPlanDuty locked too many objects or used too strict locks, resulting in blocked actions or longer wait times. \nThe commandhandler selfroster/CSetJoker used to write-lock all current and previous departments of the employee setting the joker, blocking other actions.\nThe command handler selfroster/CPlanDuty imposed write-locks on all current and previous departments of the employee planning the duty, resulting in blocked actions.\nThis has been improved.  \nThe departments are now read-locked to reduce locking issues with other actions. In command handlers where duties are used, the duty itself is write-locked. \nThis functionality is behind feature toggle ImproveLockingSelfSchedulingCommands which is enabled by default\n\nTest hint(s):\nNone",null,37196]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"To determine the list of duties when unplanning a shift for selfrostering, an internal copy of the schedule was made","To determine the list of duties when unplanning a shift for selfrostering, an internal copy of the schedule was made.     \nThis has been improved. An internal employee roster is now generated instead of creating a copy of the schedule.\n \nThis improvement is done behind feature toggle ImproveLockingSelfSchedulingCommands which is enabled by default.\n\nTest hint(s): \n1. Verify employee is given correct list of duties when unplanning a shift during self scheduling in ESS7 or WS for Employees",null,37197]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"When using \"replace by\" break (on call) was not replaced by leave-of-absence","When using \"replace by\" break (on call) was not replaced by leave-of-absence in the case that feature toggle REPLACEWITHLEAVEWITHINSHIFTONLYATWLABOURANDNORESTTIMEACTIVITIES was enabled.\n\nThis has been changed.\n\nUsing \"replace by\" break (on call) is now always replaced by leave-of-absence unless the shift consists fully of rest activities, then the break (on call) will not be replaced (as was already the case).\n\n\n\nTest hint(s):\n\n1. For a shift that contains more than only rest activities, verify that when using \"Replace by\" and feature toggle REPLACEWITHLEAVEWITHINSHIFTONLYATWLABOURANDNORESTTIMEACTIVITIES is enabled, treatment \"Break (On Call)\" is replaced by leave of absence.\n\n2. For a shift that only contains rest activities, verify that when using \"Replace by\" and feature toggle REPLACEWITHLEAVEWITHINSHIFTONLYATWLABOURANDNORESTTIMEACTIVITIES is enabled, treatment \"Break (On Call)\" is not replaced.","Customers that had feature toggle REPLACEWITHLEAVEWITHINSHIFTONLYATWLABOURANDNORESTTIMEACTIVITIES disabled because of this issue are advised to re-enable the feature toggle.",37266,"https://ortec.link/Request?HID=16627917"]
[null,null,1607763,"2024-07-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"In ORTEC WS for TeamSchedulers rolling out a cyclical schedule sometimes did not work","In ORTEC WS for TeamSchedulers rolling out a cyclical schedule sometimes did not work.\n\nThis happened specifically in the case where you have violations that require a permissions to create.\n\nThis has been fixed.",null,37391,"https://ortec.link/Request?HID=16633909"]
[null,null,1607763,"2024-07-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"Show absence of linked resources in schedule view","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.",null,46082]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle ReduceLockingInSkillMatchingUpdateHandler has been removed","Feature toggle ReduceLockingInSkillMatchingUpdateHandler has been removed.              \nThis feature toggle was introduced in update 1516666 (2022-11-11).\n\nTest hint(s):\nNone",null,46590]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle FilterAccountEntriesInStatusPlanForESSHandler has been removed","Feature toggle FilterAccountEntriesInStatusPlanForESSHandler has been removed.               \nThis feature toggle was introduced in update 1510084 (2022-09-30).\n\nTest hint(s):\nNone",null,46591]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle UseFirstValidContractForEmployeeQuery has been removed","Feature toggle UseFirstValidContractForEmployeeQuery has been removed.               \nThis feature toggle was introduced in update 1485063 (2022-05-05).\n\nTest hint(s):\nNone",null,46592]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle CopyActivityPropertiesInWorkstationOptimizer has been removed","Feature toggle CopyActivityPropertiesInWorkstationOptimizer has been removed.              \n This feature toggle was introduced in update 1386678 (2021-01-07).\n\nTest hint(s):\nNone",null,46594]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle RespawnJobThreadAfterTerminatedOnSystemError has been removed","Feature toggle RespawnJobThreadAfterTerminatedOnSystemError has been removed.              \n This feature toggle was introduced in update 1464524 (2022-01-20).\n\nTest hint(s):\nNone",null,46596]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"The default value of feature toggle ImproveHandlingSubcontractedShiftsWhenDeletingSchedule has been set to True again","The default value of feature toggle ImproveHandlingSubcontractedShiftsWhenDeletingSchedule has been set to True again.                \nThis feature toggle was introduced in update 1361657 (2020-10-01).\n\nTest hint(s):\nNone",null,46652]
[null,null,1607763,"2024-07-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"Custom reports without a translation for parameter prompts did not work as expected","In ORTEC WS for Team Schedulers, reports without a translation for parameter prompts did not work as expected.\n\nThis has been fixed.",null,46694]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle DoNotRemovePartOfUserNameInCOMClientInformation has been removed","Feature toggle DoNotRemovePartOfUserNameInCOMClientInformation has been removed.      \nThis feature toggle was introduced in update 1341658 (2020-07-16).\n\nTest hint(s):\nNone",null,6510]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle ImproveMultiReadExclusiveWriteTimeOutSyncForReads has been removed","Feature toggle ImproveMultiReadExclusiveWriteTimeOutSyncForReads has been removed.         \nThis feature toggle was introduced in update 1521163 in (2022-12-08).\n\nTest hint(s):\nNone",null,7220]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle ReplaceByLeaveOfAbsenceSubcontractedShift has been removed","Feature toggle ReplaceByLeaveOfAbsenceSubcontractedShift has been removed.       \nThis feature toggle was introduced in update 1533112 (2023-02-16).\n\nTest hint(s):\nNone",null,8614]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle CheckEmployeePropertiesBeforeCalculatingMaxLabourTimeSaldoReq has been removed","Feature toggle CheckEmployeePropertiesBeforeCalculatingMaxLabourTimeSaldoReq has been removed.          \nThis feature toggle was introduced in update 1533112 (2023-02-16).\n\nTest hint(s):\nNone",null,8683]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle ReduceHierarchicCriteriaCalculations has been removed","Feature toggle ReduceHierarchicCriteriaCalculations has been removed.          \n This feature toggle was introduced in update 1533112 (2023-02-16).\n\nTest hint(s):\nNone",null,9001]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle CheckAuthorizationForCreatingViolationInRealizationOfApprovedShift has been removed","Feature toggle CheckAuthorizationForCreatingViolationInRealizationOfApprovedShift has been removed.         \n This feature toggle was introduced in update 1533112 (2023-02-16).\n\nTest hint(s):\nNone",null,9014]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle ReduceMemoryUsageWhenVerticalCalculationsAreCollapsed has been removed","Feature toggle ReduceMemoryUsageWhenVerticalCalculationsAreCollapsed has been removed.         \n This feature toggle was introduced in update 1533112 (2023-02-16).\n\nTest hint(s):\nNone",null,9015]
[null,null,1607763,"2024-07-10",null,"Development\\OWS7",null,null,null,"Feature toggle CachePermissionCheckCallsForDescriptions has been removed","Feature toggle CachePermissionCheckCallsForDescriptions has been removed.             \nThis feature toggle was introduced in update 1537826 (2023-03-16).\n\nTest hint(s):\nNone",null,9384]
[null,null,1609523,"2024-07-24",null,"Development\\OWSforTeamSchedulers",null,null,null,"Backend preparation for creating sick leaves in ORTEC WS for Team Schedulers","Technical preparation has been done in the BackendDomainsAPI  for creating sick leaves in ORTEC WS for Team Schedulers",null,37235]
[null,null,1609523,"2024-07-24",null,"Development\\OWSforTeamSchedulers",null,null,null,"The sickness tile did not show absences for linked resources","Absences marked as \"for all contracts\" are now shown in the sickness tile for all contracts of an employee, instead of only the contract the absence was reported for.",null,46083]
[null,null,1609523,"2024-07-24",null,"Development\\OWS7",null,null,null,"An interface worker could halt when an ESS user requested swap options where the same skill is demanded twice","A swap request action could stall when an ESS user requests swap options in a department where the same skill is demanded twice (with different levels) and the resource has the higher skill level.\n\nThis could keep the employee locked indefinitely, potentially leading to a server halt.\n\nThis has been fixed.\n\n\n\nTest hint(s):\n\n1. Verify that ESS users can request a swap in a department with the same skill demanded twice (with different levels)",null,46640]
[null,null,1609523,"2024-07-24",null,"Development\\OWS7",null,null,null,"Memory leak related to USECLASSBASEDFILTERINGONPLANDATAVIEWEVENTHANDLER","In OWS 7 Update 1602133 (30-05-2024), we introduced new functionality that evaluates every update to check if it is relevant before the planboards were updated.\nUnfortunately, this contained a memory leak.\nThis has been fixed.\nIn case the concerning feature toggle UseClassBasedFilteringOnPlanDataViewEventHandler was disabled, it will be re-enabled by the DBUpdate\n\nTest hint(s):\n1. Make sure memory of the CWSS server processes does not rise more than expected.",null,46956,"https://ortec.link/Request?HID=16676956"]
[null,null,1611779,"2024-08-14",null,"Development\\OWS7",null,null,null,"CMHS process was not stopped on (SQL) error at startup","A CMHS process was not stopped on (SQL) error at startup.\r\nThis has been improved. \r\nA CMHS or CPMS processes will no longer start if a network component generates an error during initialization.\r\n\r\nTest hint(s):\r\nNone","",31275,"https://ortec.link/Request?HID=16366046"]
[null,null,1611779,"2024-08-14",null,"Development\\OWS7",null,null,null,"Violations regarding the ATB rule 'Labor time per day for specified kind' were sometimes incorrectly overlooked ","Violations regarding the ATB rule 'Labor time per day for specified kind' were sometimes\nincorrectly overlooked in specific cases.  \nThis has been fixed.  \nThis rule now accurately shows the violations.\n\nTest hint(s):\nNone","",31505,"https://ortec.link/Request?HID=16387607"]
[null,null,1611779,"2024-08-14",null,"Development\\OWS7",null,null,null,"Moving shift horizontally could result in an access violation when those shifts had already been moved by another user","Moving shift horizontally could result in an access violation when those shifts had already been moved by another user.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\n1. Verify that moving a shift horizontally using 2 clients moving the same shift works as expected.","",31728,"https://ortec.link/Request?HID=16455871"]
[null,null,1611779,"2024-08-14",null,"Development\\OWS7",null,null,null,"Feature toggle ImproveDeleteWishCommand has been removed","Feature toggle ImproveDeleteWishCommand has been removed. \nThis feature toggle was introduced in update  8.5.0-1585598 (2024-02-15).\n\nTest hint(s): \nNone","",31756,""]
[null,null,1611779,"2024-08-14",null,"Development\\OWS7",null,null,null,"Translations 09-02-2024 OWS Backend","Several translations have been added for German.\n\nTest hint(s):  \nNone","",31846,"https://ortec.link/Request?HID=16459910"]
[null,null,1611779,"2024-08-14",null,"Development\\OWS7",null,null,null,"The default displayer settings in the Client could be overwritten by a user without permission via the plan board","The default displayer settings in the Client could be overwritten  via the plan board by a user without permission.\r\nThis has been fixed.\r\nUser without permission to change default display setting can only save their personal plan board settings.\r\n\r\nTest hint(s):\r\nVerify that users can save (personal) plan board settings in Client.","For this solution to become available, the ORTEC WS Win32 client must be installed.",32189,"https://ortec.link/Request?HID=16477735"]
[null,null,1611779,"2024-08-14",null,"Development\\OWS7",null,null,null,"Calling /omrp/CNewShiftExistingDuty could result in '... removed and assigned .... at the same time' error.","Calling command handler /omrp/CNewShiftExistingDuty with setting DoNotDeleteUnnecessaryShifts off resulted in 'A shift cannot be removed and assigned to an employee at the same time' error.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\n1 Verify that command handler /omrp/CNewShiftExistingDuty can plan a valid shift with the setting CheckDutiesAgainstDemandedDutiesInShiftForm turned off.","",46725,"https://ortec.link/Request?HID=16665354"]
[null,null,1611779,"2024-08-14",null,"Development\\OWS7",null,null,null,"ReadHistoryForAllDepartments=true was not the default for Workers","ReadHistoryForAllDepartments=true was not the default for Workers, while this value is required for interface workers.\r\nThis has been improved.\r\nReadHistoryForAllDepartments is now true by default and can be turned off by giving the command line parameter the value 'False', 'N', or 'No' (case insensitive).\r\nAny other value will not change the value of ReadHistoryForAllDepartments from true.\r\n\r\nTest hint(s):\r\nNone","",47184,"https://ortec.link/Request?HID=16680968"]
[null,null,1611779,"2024-08-14",null,"Development\\OWSforTeamSchedulers",null,null,null,"Preparation for ORTEC WS for Team Schedulers related to showing employee realizations in the schedule.","Preparation for ORTEC WS for Team Schedulers related to showing employee realizations in the schedule.","",47338,""]
[null,null,1611779,"2024-08-14",null,"Development\\OWS7",null,null,null,"Self scheduling not possible with empty value of SelfSchedulingWorkerCCDSNames when interfaceworker has ccdsname","Self scheduling in ESS resulted in an error if setting SelfSchedulingWorkerCCDSNames is empty and the dedicated interfaceworker has a ccdsname.\nThis has been fixed.\n\nThis was introduced in issue 33974 releases in OWS 7 update 1607763 (2024-07-11)\n\nTest hint(s):\nVerify that an ESS users can perform a self scheduling action","",47951,"https://ortec.link/Request?HID=16711886"]
[null,null,1611779,"2024-08-14",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS for Team Schedulers: Sick leave tile no longer showed correct shift number for \"now +7d shifts\"","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.\nDue to a recent change this was no longer the case and it showed shifts for a longer period. \nThis has been fixed.","",48041,""]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7",null,null,null,"When using copy/paste on an overlapping shift, it got unplanned without a warning message","When using\ncopy/paste on an overlapping shift, it got unplanned without a warning message.  \nThis has been improved. \nNow using copy/paste over a planned shift\nresults in a warning message and the planned shift is not unplanned.  \nThe copy/paste functionality now\nhandles copying over planned shift the same way as when adding a new shift over\na planned shift.  \nThe cut/paste functionality is not changed.\n\nTest hint(s):\n1. Verify that an overlapping shift using copy/paste results in a warning message and the planned shift is not unplanned.",null,14040,"https://ortec.link/Request?HID=15824793"]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7",null,null,null,"Employees were not sorted correctly when using a rule of type \"Calculation based on other calculations\" with \"Display hours in decimals\" enabled","Employees were not sorted correctly in the planboard when using a rule of type \"Calculation based on other calculations\" with \"Display hours in decimals\" enabled.\nThis has been fixed.\nEmployees are now sorted correctly when using a rule of type \"Calculation based on other calculations\".\n\n\n\nTest hint(s):\n1. Verify employees are sorted correctly when using a rule of type \"Calculation based on other calculations\" with \"Display hours in decimals\" enabled.",null,32188,"https://ortec.link/Request?HID=16477729"]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7\\Technical improvements",null,null,null,"Added a new settings to prepare for web-based helpfile support","A new settings CWGSHELPFILEBASEURL has been added to prepare for a web-based Helpfile that will be provided for hosting.\n\nTest hint(s):\nNone","DBAnonymize has been updated. Requested databases should be anonymized using this new version",33773]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7\\Technical improvements",null,null,null,"Small performance improvement when loading user properties and values.\n\n","Small performance improvement when loading user properties and values.\n\nTest hint(s):\nNone",null,34728]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7",null,null,null,"(Required) workstation rules where not taken into account at shifts with already assigned workstation","(Required) workstation rules where not taken into account at shifts with already assigned workstation.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that the optimizer no longer plans not workstations that are not allowed given the set required rules when there is already an assigned workstation in the shift.",null,37388,"https://ortec.link/Request?HID=16633619"]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7",null,null,null,"Added new notification type for shift changes","A new notification type called \"Shift change\" has been introduced. To achieve this, the notification functionality and data model has been reworked. This also allows for easier addition of new notification types in the future. \n  \nIn the following scenarios, the new \"Shift change\" notification is sent to the employee in ESS7: \n- When a published shift is added to the employee's\nschedule*.\n- When a published shift is unassigned from an employee*.\n- When a published shift is exchanged with another\nshift. \n- When the times of a published shift are modified. \n* Note that sending notifications based on an actual (central) subcontract status (e.g. final planning) does not yet work and will be solved in a later update.\n  \nThe notification indicates that there is a schedule change on a certain date or between multiple dates (in case of multiple changes). It does not include details of the change itself.  \n \nThe following settings influence the new notification type: \n- OrtecRelevancePushNotificationSender\\ShiftChangeNotification\\SendShiftChangeNotification\nWith this new setting the new notification type can be turned on or off. By default it is turned off.\n- OrtecRelevancePushNotificationSender\\ShiftChangeNotification\\MaximumNumberOfDaysInFutureToSendShiftChangeNotification\nThis new setting specifies the number of\ndays in the future for which shift change notifications are sent. The default value is set to 7 days. This means a change to a shift scheduled 10 days from now will not trigger a notification. \n- OrtecRelevancePushNotificationSender\\TimeBetweenProcessingNotificationInSeconds. \nTo enhance the overall user experience and prevent\nnotification overload, all notifications for a single employee are bundled\ntogether within a specified time interval. This ensures that only one\nnotification is sent, regardless of the number of changes. This time interval is determined by the (existing) setting mentioned above. Please note that this setting is also used for other notification types.   \n\nIn the same change, for consistency sake, we also introduced a new activation setting for the existing shift offer notification type: OrtecRelevancePushNotificationSender\\ShiftOfferNotification\\SendShiftOfferNotification\nBy default this is turned on (for backwards compatibility). Please note that if the cloud app Shift Offering is used, this setting has no effect because shift offer notifications are sent from the cloud app instead.",null,46613]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7",null,null,null,"Microsoft Excel application was required next to OWS Win32 Client to export clocking and running account information","In order to export to Excel from a running account or clocking form, a Microsoft Excel instance had to be installed on the machine where the OWS Win32 Client runs. \nWithout this prerequisite, exporting to Excel would result in an error. This has been improved.\nThe OWS Win32 Client now supports exporting to Excel without having an actual Microsoft Excel instance installed.\n\nThis is available behind feature toggle USEHARMONYFLEXCELREPORT and is, for now, turned off by default. \n\nThe following, existing OWS Settings Manager settings should be turned on to be able to use this new functionality:\n- OPTIONS\\CLOCKINGS\\EXPORTTOEXCEL=Y - for using the new functionality to export clocking information \n- OPTIONS\\RUNNINGACCOUNTS\\EXPORTTOEXCEL=Y - for using the new functionality to export running account information\n\nWhen enabling the new functionality also be aware of the DEFAULT_USR\\INTERFACE\\EXCEL settings, although this was already relevant in the existing Excel export.\nA DateFormat, NumberFormat, TimeFormat and SumFormula should be present and equal to the regional settings of the user(s) generating the Excel file.\nPlease be aware that the standard Numer Format needs to be changed to #,##0.00 to make sure Excel is displaying the decimals correctly when using the new Excel export.\nIf formatting settings are incompatible, the Excel report will still be generated, but an error might occur when the Excel file is opened in Microsoft Excel.","For this solution to become\n\navailable, the ORTEC WS Win32 client must be installed.",46888]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7",null,null,null,"ESS7: New permission for swap option: giving away shift ","Added access control permission /CWGS/OWS/ESS/GetExchangeRequestOptionsGiveAway in preparation for an ESS change.\nThis new permission in automatically granted if the usergroup already has the permission /CWGS/OWS/ESS/GetExchangeRequestOptions\n\nTest hint(s):\n1. Verify that the new right /CWGS/OWS/ESS/GetExchangeRequestOptionsGiveAway is available in access control and automatically assigned to usergroups with the permission /CWGS/OWS/ESS/GetExchangeRequestOptions",null,47870,"https://ortec.link/Request?HID=16711845"]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7",null,null,null,"Translations OWS Backend","Several translations have been added for German.\n\nTest hint(s):  None",null,47948]
[null,null,1614627,"2024-09-06",null,"Development\\OWS7",null,null,null,"Interval pool could not be configured per CWSS worker process","Interval pool could not be configured per CWSS worker process\nThis has been improved\nIn OWS Settings Manager the existing setting IntervalPool\\MAXNUMBEROFINTERVALSINPOOL can be overridden per CWSS server using the servernr\nI.e. by adding IntervalPool\\Server40\\MAXNUMBEROFINTERVALSINPOOL the value set for CWSS Server process with server number 40\n\nAn addition by setting the value to 0 the usage of the intervalpool can be disabled.\nThus when the following settings are in OWS Settings Manager- IntervalPool\\Server40\\MAXNUMBEROFINTERVALSINPOOL = 0 - IntervalPool\\MAXNUMBEROFINTERVALSINPOOL = 200000\n\nThe interval pool CWSS Server process with server number 40 it is disabled, and for all other CWSS Server processes it size is 200000.\n\nAfter a setting has changed the CWSS Server processes affected by the changed setting should be restarted.\n\nNOTE: The size of interval pool used has effect on performance and memory usage. A higher value for the interval pool causes the lower bound of memory usage to increase.\nUsing a higher value for the interval pool can have performance gains, but lowering the default value to preserve memory can be required.\n\nTest hint(s)\nVerify opening a planboard in OWS Win32 Client  Verify calculations done on an OWS CWSS worker process handling horizontal/vertical calculations",null,48179]
[null,null,1614627,"2024-09-06",null,"Development\\OWSforTeamSchedulers",null,null,null,"ORTEC WS for Team Schedulers vertical calculations can be offloaded to a separate interface worker","Technical change to make it possible to configure the vertical calculation requests coming from ORTEC WS for Team Schedulers to a separate interface worker. This can significantly lower the amount of load of the main server, which makes all other actions faster.\n\nA new setting has been added: TeamScheduling\\VerticalCalculations\\ServerNumber.\n\nThis setting has a default value of 0. A value of 0 indicates that no separate interface worker is used for the vertical calculations.\n\n\n\nTest hint(s):\n\nConfigure an interface worker \n\n Edit this setting so that vertical calculation requests are sent to it: TeamScheduling\\VerticalCalculations\\ServerNumber Verify through the CSCS command dispatcher that the vertical calculation requests are sent to the configured interface worker",null,48502]
[null,null,1614627,"2024-09-06",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation to skip vertical calculations for central departments","Technical preparation to skip vertical calculations for central departments.\n\nA new setting has been added: TeamScheduling\\VerticalCalculations\\ExcludeCentralDepartments, default false.",null,48669]
[null,null,1616090,"2024-09-13",null,"Development\\OWS7",null,null,null,"Added the possibility to replace the legacy OWSClient helpfile with a webbased alternative.","A setting CwgsHelpfileBaseUrl has been added to allow replacing the legacy OWSClient helpfile with a webbased alternative.  The default value of CwgsHelpfileBaseUrl is an empty string which means the legacy help file is used. In order to use the webbased help, CwgsHelpfileBaseUrl should a valid URL to the website hosting the help.\n\nTest hint(s):\n1. When on hosting platform, set the value of CwgsHelpfileBaseUrl to the correct URL and verify the correct page opens when clicking F1 in OWSClient.","For this solution to become available, the ORTEC WS Win32 client must be installed.",33774]
[null,null,1616090,"2024-09-13",null,"Development\\OWS7",null,null,null,"Issue with NumberOfDaysToShowPlannedShifts in schedule that is partially published","In ESS, partially published schedules showed shifts beyond the published until date + NumberOfDaysToShowPlannedShifts if setting NumberOfDaysToShowPlannedShifts has a value larger than 0.\nThis has been been fixed.\n\nTest hint(s):\n1. Open a partly published schedule in ESS whilie setting NumberOfDaysToShowPlannedShifts is larger than 0. Verify that you cannot see shifts past the publication date + NumberOfDaysToShowPlannedShifts .",null,48374]
[null,null,1616090,"2024-09-13",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for approving a schedule in Team Schedulers","Technical preparation for approving a schedule in Team Schedulers.\nA new permission has been added in AccessControl: ORTEC WS for TeamSchedulers > Allowed to approve schedules",null,48379]
[null,null,1616090,"2024-09-13",null,"Development\\OWS7",null,null,null,"Calculating reporting and/or invoice rules could cause the main CWSS server process to go out of memory ","Calculating reporting or invoice rules could cause the main CWSS server process to go out of memory\nEspecially when employment terms is complex and opening planboards with large number of employees and/or opening a planboard using multiple scheduling periods this could escalate quickly.\nThis has been improved.\nThe cause of this specific growth of memory was found and mitigated.\n\nThis was introduced in issue 36983 in OWS7 - 8.5.0(2024-05-30)_Build1602133\nThis functionality was introduced behind feature toggle IMPROVEAPPLYRULESOVERPERIOD which was enabled by default.\n\nTest hint(s):\n1. Verify memory of the server process does not rise disproportionality when reporting and/or invoice rules are used.","If feature toggle IMPROVEAPPLYRULESOVERPERIOD was disabled, it will be enabled again.",48781,"https://ortec.link/Request?HID=16737452"]
[null,null,1617924,"2024-09-26",null,"Development\\OWS7",null,null,null,"Entries for shift on account category in shift proposal were not correct for employees in proposal departments when searching candidates for a shift. ","Entries for 'shift on account category' in shift proposal were not correct for employees in proposal departments when searching candidates for a shift.\n\nThis has been fixed.\n\n\n\nTest hint(s):\n\n1. Verify that entries for shift on account category show the correct value for employees of proposal departments when searching candidates for a shift.",null,14130]
[null,null,1617924,"2024-09-26",null,"Development\\OWS7",null,null,null," Opening a running account only checked 'To' date when check if interval is too large for setting MAXNOFDAYSSHOWNINRUNNINGACCOUNT.","It was possible to refresh the running account form with an interval larger than MAXNOFDAYSSHOWNINRUNNINGACCOUNT when changing the from date.\n\nThis has been fixed.\n\n\n\nTest hint(s):\n\n1. Open a running account and move the from date to some point in the past (outside the MAXNOFDAYSSHOWNINRUNNINGACCOUNT). Verify that you receive an warning message, and the to date is set to the maximum allowed end date","For this solution to become available, the ORTEC WS Win32 client must be installed.",31729,"https://ortec.link/Request?HID=16455895"]
[null,null,1617924,"2024-09-26",null,"Development\\OWS7",null,null,null,"Consistency check on activities larger than 24 hours has been turned on by default","The existing consistency check on activities larger than 24 hours has been turned on by default.\n\nAdditionally 2 new settings have been added :\n\nConsistencyCheckActivityDurationCheckEnabledOnLoadingDescriptions to enable this consistency check while loading activities, disabled by default. When enabled a line will be added to the server logging for each activity loaded that has a duration larger than 24 hours.\n\nConsistencyCheckActivityDurationCheckRaisesException, enabled by default when no activities with a duration longer than 24 hours are present in the database, disabled when these do exist. When ConsistencyCheckActivityDurationCheckRaisesException is enabled an exception will be raised, when disabled a line will be added to the server logging when trying to add an activity that has a duration larger than 24 hours.\n\n\n\nTest hint(s):\n\n1. Verify that when ConsistencyCheckActivityDurationCheckRaisesException is enabled an exception is raised when trying to import an activity that has a duration larger than 24H.",null,33376]
[null,null,1617924,"2024-09-26",null,"Development\\OWS7",null,null,null,"Unattended updates custom script did not allow for boolean parameters.","Running a custom Powershell script in Unattended updates did not allow for boolean parameters as input\n\nThis has been fixed.\n\nIf a parameter has a value of True/False in the UnattendedUpdate_Config.xml it will be interpreted as a boolean parameter for the script.\n\nIf a customers configuration uses string parameters with a value of true/false in a script, this script will need to be adjusted to prevent this.\n\nSwitch parameters (parameters which presence triggers the true condition) should be assigned a value true in config file.\n\n\n\nTest hint(s):\n\n1. Verify that a script with boolean parameters can be run during unattended update using the custom scripts section of Unattended update config\n\n2. Verify that not giving a name/variable or giving an empty string as name/variable will result in an error message",null,48300,"https://ortec.link/Request?HID=16718416"]
[null,null,1617924,"2024-09-26",null,"Development\\OWS7",null,null,null,"When an ETimeOutLockMutexTimeOut was raised it did not show the correct thread id in the logging","When an ETimeOutLockMutexTimeOut was raised the wrong thread ID was logged.\n\nThis has been fixed.\n\n\n\nTest hint(s):\n\nNone",null,48600,"https://ortec.link/Request?HID=16729437"]
[null,null,1617924,"2024-09-26",null,"Development\\OWS7",null,null,null,"Added possibility to filter out nonEmployeeAddresses with description in ESS realisations","A new BackendAPI setting UseOnlyAddressesWithDescription (in comtec.workforce.BackendAPI/Portals) has been added to only show addresses that have a filled in description when making a realization in ESS.\n\nNote this setting only works in combination with the existing setting UseNonEmployeeAddresses enabled.\n\n\n\nTest hint(s):\n\n1. Verify that when enabling settings UseNonEmployeeAddresses and UseOnlyAddressesWithDescription, only non-employee addresses with a filled description field are shown when making a realization in ESS.",null,48601,"https://ortec.link/Request?HID=16729443"]
[null,null,1617924,"2024-09-26",null,"Development\\OWS7",null,null,null,"Using CCleanUpRemovedShifts on a worker could cause Access Violation error in main CWSS Server process","When a shift with a non-default duty property value was cleaned using CCleanUpRemovedShifts on a worker it could cause Access Violation error in main CWSS Server process\n\nThis has been improved.\n\nThis issue occurred when the date of such shift was before the date regarding the BUFFEREDHISTORY used on the CWSS Server process handling the update (usually the main worker)\n\nThe resolution of this issue has been implemented behind feature toggle ImproveApplyIncomingDescriptionDeleteOfUserPropertyValue, which is enabled by default\n\n\n\nTest hint(s):\n\nNone","Recommended to push this to customers using the CCleanUpRemovedShifts command handler that have (or have had) issues in the past with this command handler.",48838]
[null,null,1620193,"2024-10-10",null,"Development\\OWS7",null,null,null,"CMHS CANBEPAUSED functionality was not enabled by default","CMHS CANBEPAUSED functionality was not enabled by default.\nThis has been improved.\nIt is no longer needed to set property 'CanBePaused' in CMHS configurations.\nNetworks will automatically be paused if one of its components is not ready AND the producer is capable of pausing. \nAs a result: \n- Networks with a FileReader, MSMQReaderPolling or FTPProducer will now automatically pause if one of its components is not ready.\n- Networks with a CCDSProducer of CRBSSubscriber will never pause, since they can't.\n- No configuration is needed anymore to get this working.\n\nTest hint(s)\n- Verify that CMHS network configurations work.",null,14556,"https://ortec.link/Request?HID=15878388"]
[null,null,1620193,"2024-10-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation to edit sick leaves","Technical preparation to edit sick leaves in Team Schedulers.",null,47852]
[null,null,1620193,"2024-10-10",null,"Development\\OWS7",null,null,null,"It was not possible to revert to the default value for a user property without an interval when importing the user property as subfield","It was not possible to revert to the default value for a user property without an interval when importing the user property as subfield.\n\nThis has been fixed.\n\n\n\nTest hint(s):\n\nNone",null,48140,"https://ortec.link/Request?HID=16714149"]
[null,null,1620193,"2024-10-10",null,"Development\\OWS7",null,null,null,"In the \"Add Shift\" window, duty types with long names were not fully visible","In the \"Add Shift\" window, duty types with long names were not fully visible.\n\nThis has been fixed.  \n\nThe width of the columns for both Shifts and Special Shifts is increased to display 30 characters.","For this solution to become available, the ORTEC WS Win32 client must be installed",48458]
[null,null,1620193,"2024-10-10",null,"Development\\OWS7",null,null,null,"[Backend API] Added new property \"ChoicesLimitedByStaffingCrit\" to selfschedulinginfo","As preparation for a future ESS7 change, added a property to the self-scheduling info call to enable future differentiation in shift selection to ensure relevant dialogs are shown only when necessary.\n\n\n\nTest hint(s):\n\nNone",null,48588]
[null,null,1620193,"2024-10-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for employee realization approval from schedule","Technical preparation for employee realization approval from schedule in Team Schedulers.",null,48776]
[null,null,1620658,"2024-10-14",null,"Development\\OWS7",null,null,null,"Added a check to employee realizations for a pending update overlapping with other (pending) shifts","Added a check to the CEmployeeRealisation commandHandler used by WS for Employee and ESS7 for a pending update overlapping with other (pending) shifts when they would be approved.\n\nWhen an employee enters a pending employee realization the entered pending update and adjacent pending updates will be 'trial-approved' to see whether overlap with any shift will occur after approval.\n\nAn error will be raised when overlap is detected.\n\nThis check will be performed for pending updates with status New or ConceptApproved (not Draft).\n\nThe interval for which pending updates are checked is: all shifts in the range of 24 hours before and after the entered pending update\n\nThis is available behind feature toggle CheckPotentialOverlapForEmployeeRealisations and is enabled by default.\n\n\n\nTest hint(s):\n\n1. With feature toggle CheckPotentialOverlapForEmployeeRealisations enabled, verify you can no longer enter a realisation in WS for Employees or ESS7 when the realization would cause overlap with other shifts or realization when they would be approved. An error will appear that shifts overlap.",null,29670]
[null,null,1620658,"2024-10-14",null,"Development\\OWS7",null,null,null,"The begin-/enddates of an existing skill/grouplabel were not updated if the new begindate lies after the current begindate or the new enddate lies before the current enddate","The begin-/enddates of an existing skill/grouplabel were not updated if the new begindate lies after the current begindate or the new enddate lies before the current enddate, regardless of the settings REMOVEINTERVALAFTERIMPORTEDENDDATE and REMOVEINTERVALBEFOREIMPORTEDBEGINDATE.\n\nThis has been fixed.\n\nWith the settings REMOVEINTERVALAFTERIMPORTEDENDDATE or REMOVEINTERVALBEFOREIMPORTEDBEGINDATE = Y, the existing begin-/enddate of an overlapping skill/grouplabel will be replaced by the new begin-/enddate.\n\n\n\nTest hint(s):\n\n1. With setting REMOVEINTERVALAFTERIMPORTEDENDDATE = Y, verify that the enddate is updated when importing an update to the existing skill/grouplabel with an earlier enddate than the existing enddate.\n\n2. With setting REMOVEINTERVALBEFOREIMPORTEDBEGINDATE = Y, verify that the beginddate is updated when importing an update to the existing skill/grouplabel with a later begindate than the existing begindate.",null,31502,"https://ortec.link/Request?HID=16387227"]
[null,null,1620658,"2024-10-14",null,"Development\\OWS7",null,null,null,"When changing the end date of a rotation unit for an employee with an open realization, the raised exception did not include the relevant employee information","When changing the end date of a rotation unit for an employee with a shift that has an open realization further in the future, an exception is raised while attempting to delete the shift from the schedule. The exception did not include the relevant employee information.\n\nThis has been fixed.\n\nThe exception now contains the correct employee information.\n\n\n\nTest hint(s):.When changing the end date of a rotation unit for an employee with a shift that has an open realization further in the future, verify the raised exception includes the relevant employee information. To attempt the deletion of the shift from the schedule, ensure that the DoNotDeleteUnnecessaryShifts is set to False and that the shift demand has already been met within the scheduling period.\n\n This scenario can be tested using either a standard employee import or by making the change directly through the Client.",null,32115,"https://ortec.link/Request?HID=16473990"]
[null,null,1620658,"2024-10-14",null,"Development\\OWS7\\Technical improvements",null,null,null,"Small performance improvement on consistency check for user property values","Small performance improvement on consistency check for user property values.\n\n\n\nTest hint(s)\n\nverify changing employee/duty/illness property value from default to non-default goes ok",null,34277]
[null,null,1620658,"2024-10-14",null,"Development\\OWS7",null,null,null,"When ETimeOutLockMutexTimeOut was raised during handling updates, the updates were not retried, which could cause a worker halt.","When an ETimeOutLockMutexTimeOut was raised during handling updates, the updates were not retried\n\nThis could cause a server to halt too soon or even unnecessarily.\n\nThis has been improved.\n\n\n\nThis was introduced in issue 34606 \"Improved logging for time out exception to provide more detailed information\" \n\nIn release  OWS7 - 8.5.0(2024-05-30)_Build1602133\n\n\n\nTest hint(s):\n\n1. Verify that queue updates are handled correctly (if configured)\n\n2. Verify that BI runs succeed correctly",null,49903,"https://ortec.link/Request?HID=16766135"]
[null,null,1622079,"2024-10-24",null,"Development\\OWS7",null,null,null,"It was possible to overwrite existing employment condition without warning","When adding a new employment condition, and making a typing error (eg. 2013 instead of 2023), it was possible to overwrite all existing employment conditions without warning or notification afterwards.\nThis has been improved. \nWhen adding a new employment condition overlapping with an already existing employment condition's from date a warning is shown. When the user replies 'Yes', the behaviour will be as before, when choosing 'No', the added line will be removed again.\n\nTest hint(s):\n1. Verify that when updating employment conditions and entering a from date that is before or equal to the an already existing employment condition's from date a warning is shown.","For this solution to become available, the ORTEC WS Win32 client must be installed.",13933,"https://ortec.link/Request?HID=15821518"]
[null,null,1622079,"2024-10-24",null,"Development\\OWS7",null,null,null,"Using the 'Carry over balance' remuneration rule per week could result in a incorrect cycle warning","Using the 'Carry over balance' remuneration rule per week in combination with transferbooking remuneration rules could result in a incorrect cycle warning when using detect cycles.\r\nThis has been fixed.\r\n\r\nThis was fixed behind feature toggle ImproveCarryOverBalancePerWeekRemuneration which is enabled by default.\r\n\r\nTest hint(s):\r\n1. In remuneration configuration that combines 'Carry over balance' rule per week with a transfer booking rule, verify that the configuration does not produce a cycle warning message by using \"Detect cycles\".",null,32695,"https://ortec.link/Request?HID=16542056"]
[null,null,1622079,"2024-10-24",null,"Development\\OWS7",null,null,null,"Remove feature toggle LogDescriptionInfoOnDescriptionLockException","Feature toggle LogDescriptionInfoOnDescriptionLockExceptionhas been removed.\nThis feature toggle was introduced in update 1597363 (2024-04-25).",null,33988]
[null,null,1622079,"2024-10-24",null,"Development\\OWSforTeamSchedulers",null,null,null,"When the access control group parameter for department was not filled in, logging in failed without a clear indication why","When the access control group parameter for department was not filled in, logging in failed without a clear indication why.\n\nThis has been improved.\n\nYou are now shown a page that says 'Signing in with this account is not allowed.'. The WebApiLog file can help further with why this is happening (no change was made here).",null,46129,"https://ortec.link/Request?HID=16650140"]
[null,null,1622079,"2024-10-24",null,"Development\\OWS7",null,null,null,"CMHS networks using a filewriter with a prefix value starting with %metadata...% would never unpause, therefore blocking the network","A CMHS network using a filewriter with a prefix value starting with %metadata...% would never unpause, therefore blocking the network.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that a CMHS network with a filewriter not using %metadata:variable% somewhere in the prefix is unpaused automatically.\n2. Verify that a CMHS network with a filewriter using %metadata:variable% somewhere in the prefix is unpaused automatically.\n3. Verify that a CMHS network with a filewriter using %metadata:variable% at the start of the prefix is unpaused automatically.",null,49493,"https://ortec.link/Request?HID=16755552"]
[null,null,1622079,"2024-10-24",null,"Development\\OWS7\\Technical improvements",null,null,null,"Checking and handling updates while processing self scheduling commands on a worker could cause timeouts ","Checking and handling updates while processing self scheduling commands on a worker could cause timeouts.\nThe checking and handling updates was done while processing commands, after locks were taken, this could cause timeouts and waits on other threads handling dependent data. \nThis has been improved. \nBy checking and handling updates just before processing the commands, some of the timeouts are avoided, improving performance.\nNOTE: when self scheduling commands are handled on a worker that also handles queues this 'before processing' is not done!\n\nThis is available behind feature toggle HandleUpdatesBeforeProcessingSelfSchedulingCommands and is disabled by default.\n\nTest hint(s):\n1. Verify that OWS for Workforce scheduling front ends handle self scheduling actions correctly.",null,49821]
[null,null,1622079,"2024-10-24",null,"Development\\OWSforTeamSchedulers",null,null,null,"Violation text in Team Schedulers did not show the name of the labor rule that was violated","Violation text in Team Schedulers did not show the name of the labor rule that was violated.\n\nThis has been improved.",null,50030]
[null,null,1622079,"2024-10-24",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to improve performance of retrieving shifts","Technical change to improve performance of retrieving shifts.",null,50101]
[null,null,1623707,"2024-11-06",null,"Development\\OWS7",null,null,null,"Translations 01-03-2024 OWS Backend","Several translations have been added for German.\n\n\n\nTest hint(s): None",null,32656,"https://ortec.link/Request?HID=16513182"]
[null,null,1623707,"2024-11-06",null,"Development\\OWS7",null,null,null,"Transferring calculated entries using nested bookings could lead to incorrect calculation and duplicate bookings","Using a 'Transferbooking based upon an expression' (=Transfer) rule could sometimes lead to incorrect calculated entries when the rule was set to \"per entry\", \"per entry day\" or per \"equal properties\" or per \"department period\".\nThis could happen in very specific situations:\nIf the result of the Transfer rule was carried over with a \"Carry over balance\" or \"Transferbooking\" type of rule that booked to a secondary account and the secondary account was then transferred back to the first account (close to a cycle, but separated by time).\nAnd, if the first account was requested for a period longer than the period defined in the \"Carry over balance\" rule. \nFor department periods, it could happen that the expression looked for a department period before the first department period. Leading to a 'too many nested calculations' error.\n  \nThis has been improved.\nThe transfer rule checks if a certain bookings interval has already been calculated completely before, and if so, does not create an additional booking.\nWhen the expression looks for a department period that does not exist, the calculation is stopped as it cannot look back any further.\nThis change needs Feature Toggle IMPROVEBOOKINGSWITHNESTEDCALCULATIONS to be enabled. As mentioned in \"9958 - Bookings with nested calculations were sometimes calculated wrong\", the feature toggle IMPROVEBOOKINGSWITHNESTEDCALCULATIONS has risks for existing configurations and is therefore by default off.\n\nTest hint(s):\n1. Verify that a booking setup as described will return the expected bookings.",null,37261]
[null,null,1623707,"2024-11-06",null,"Development\\OWS7",null,null,null,"ConsistencyCheckActivityDurationCheckRaisesException was enabled by default when no activities with a duration >= 24 hours were present, which inadvertently included activities with a duration of exactly 24 hours","The setting ConsistencyCheckActivityDurationCheckRaisesException was previously enabled by default when no activities with a duration longer than or equal to 24 hours were present in the database, which inadvertently included activities with a duration of exactly 24 hours. \nThis has been fixed.\nThe setting ConsistencyCheckActivityDurationCheckRaisesException is now enabled by default only when no activities with a duration longer than 24 hours are present in the database.\n\nTest hint(s):\nNone",null,49673,"https://ortec.link/Request?HID=16762649"]
[null,null,1623707,"2024-11-06",null,"Development\\OWS7",null,null,null,"Translations 10-10-2024 OWS Backend","Several translations have been added for German.\n\n\n\nTest hint(s):\n\nNone",null,49867,"https://ortec.link/Request?HID=16765787"]
[null,null,1623707,"2024-11-06",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for deleting a sick leave","Technical preparation for deleting a sick leave in ORTEC WS for Team Schedulers.",null,50040]
[null,null,1623707,"2024-11-06",null,"Development\\OWS7",null,null,null,"The State of a shift in a transactionfragment did not always include the subcontractids","The State of a shift in a transactionfragment did not always include the subcontractids.\nThis has been improved.\nFeatureToggleAddSubContractIdsToAllDescriptionStatesOfAShift has been added to resolve this. Default value is enabled.\nWhen enabled, all versions of a shift-change in a transactionfragment will contain the subcontractids attribute.\nThis change is required for part of the preparations for a new feature \"ShiftChange notifications\".\n\nTest hint(s):\nNone",null,50247]
[null,null,1623707,"2024-11-06",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to support additional grouping options","Technical change to support additional grouping options in ORTEC WS for Team Schedulers.",null,50357]
[null,null,1623707,"2024-11-06",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - BDA .NET Core updates are not handled fully unattended","When an update of the  .NET Core prerequisite is needed during an update of the BackendDomainsAPI, the UnattendedUpdates script would ask for user interaction.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that UnattendedUpdates will not ask for interaction when a .NETCore update is needed",null,50358]
[null,null,1623707,"2024-11-06",null,"Development\\OWSforTeamSchedulers",null,null,null,"Parent cost centers without a valid child cost center were shown in the cost center list in the shift edit screen","Parent cost centers without a valid child cost center were shown in the cost center list in the shift edit screen in ORTEC WS for Team Schedulers.\nThis has been fixed.\n\nTest hint(s):\nNone",null,50464]
[null,null,1625278,"2024-11-21",null,"Development\\OWS7","Monthly automatic exports did not take the configured time into account",null,null,"Monthly automatic exports did not take the configured time into account","Monthly automatic exports did not take the configured time into account.\n\nThis has been fixed.\n\nPlease note that, if customers are using <AutomaticExportTimeBetween unit='month'> in any definitions, the export will no longer occur at midnight, but at the time given in <AutomaticExportStart>.\n\n\n\nTest hint(s):\n\n1. Verify that after an automatic export, the setting \"INTERFACES\\AUTOMATICEXPORTSTART [interfacename]\" is updated to the correct datetime when using month units in AutomaticExportTimeBetween of an export definition.",null,32644]
[null,null,1625278,"2024-11-21",null,"Development\\OWS7","Copying a 'Carry over balance'-remuneration rule with period type 'Period and date as below' and an OnDate before the first date of next year, would result in an incorrect copied OnDate",null,null,"Copying a 'Carry over balance'-remuneration rule with period type 'Period and date as below' and an OnDate before the first date of next year, would result in an incorrect copied OnDate","Copying a 'Carry over balance'-remuneration rule with period type 'Period and date as below' and an OnDate before the first date of next year, would result in an incorrect copied OnDate.\n\nThis has been fixed.\n\nAdded feature toggle CheckRemainderBalanceRemParamsConsistency which is enabled by default.\n\n\n\nTest hint(s):\n\n1. Verify that when copying a carry of balance rule with period type 'Period and date as below' and an OnDate before the first date of next year, a new rule is created with the same dates.\n\n2. Verify that when importing a carry of balance rule with period type 'Period and date as below' and an OnDate before the first date of next year, a new rule is created with the same dates.",null,33047]
[null,null,1625278,"2024-11-21",null,"Development\\OWS7","OWS Win32 Client: When subcontracting a shift with a given position, changing the department unintentionally emptied the position field",null,null,"OWS Win32 Client: When subcontracting a shift with a given position, changing the department unintentionally emptied the position field","When subcontracting a shift with a given position, changing the department unintentionally emptied the position field. \nThis has been fixed. \nChanging the department does not change the position.\n\nTest hint(s):\n1. Subcontract a shift with a given position, and verify that changing the department does not change the position.","For this solution to become available, the ORTEC WS Win32 client must be installed.",33296]
[null,null,1625278,"2024-11-21",null,"Development\\OWS7","In workstation optimizer profile only employees could be selected that are currently part of the schedule",null,null,"In workstation optimizer profile only employees could be selected that are currently part of the schedule","In workstation optimizer profile only employees could be selected that are currently part of the schedule.\nThis has been improved.\nIt is now possible to include employees that are going to be a part of the schedule but currently are not.\nThis functionality is behind the new server setting PLANNER\\WORKSTATIONPLANNER\\SHOWFUTUREEMPLOYEESINWORKSTATIONPROFILE which is disabled by default.\n\nTest hint(s):\n1. Verify that both employees that are in the current schedule, and future employees, are shown in workstation optimizer profile when PLANNER\\WORKSTATIONPLANNER\\SHOWFUTUREEMPLOYEESINWORKSTATIONPROFILE is enabled.","For this solution to become available, the ORTEC WS Win32 client must be installed.",33548]
[null,null,1625278,"2024-11-21",null,"Development\\OWS7","The external planner could not deal with daylight savings change, causing the run to fail",null,null,"The external planner could not deal with daylight savings change, causing the run to fail","The external planner could not deal with daylight savings change, causing the run to fail.\nThis has been fixed.\n\nTest hint(s): None",null,33651]
[null,null,1625278,"2024-11-21",null,"Development\\OWSforTeamSchedulers","Technical change to update prerequisite Microsoft .NET Core Runtime 2.1 to the latest version",null,null,"Technical change to update prerequisite Microsoft .NET Core Runtime 2.1 to the latest version","Technical change to update the prerequisite Microsoft .NET Core Runtime 2.1 to the latest version (2.1.30).",null,48232]
[null,null,1625278,"2024-11-21",null,"Development\\OWS7","Unattended Updates - custom scripts do not use progress tracking",null,null,"Unattended Updates - custom scripts do not use progress tracking","Running custom scripts in Unattended Updates did not use progress tracking, and were therefore not retried/finished when necessary.\nThis has been improved.\nNote that a custom script is rerun in its entirety when necessary. It is up to the custom script to catch any errors that need mending or a rollback before it can be rerun.\n\nTest hint(s):\n1. Verify that a failed / not-started script is retried when running Unattended Updates after a failed run.",null,48554]
[null,null,1625278,"2024-11-21",null,"Development\\OWS7","Shift notification was not sent when changing subcontract status from final",null,null,"Shift notification was not sent when changing subcontract status from final","In Release OWS 7 - 8.5.0(2024-09-05)_Build1614627 we introduced a new notification type called \"Shift change\".\n\nIn that release, sending notifications based on an actual (central) subcontract status (e.g. final planning) to employees in ESS7 did not work yet. \n\nThis has been improved.\n\nFor this, FeatureToggle AddSubContractIdsToAllDescriptionStatesOfAShift (default enabled) added in 50247 needs to be enabled.\n\n\n\nTest hint(s):\n\n1. Verify that ShiftChangeNotifications are sent for subcontracted shifts when the status is set to or from final.",null,49198]
[null,null,1625278,"2024-11-21",null,"Development\\OWSforTeamSchedulers","Technical preparation to add a new permission for viewing employee details",null,null,"Technical preparation to add a new permission for viewing employee details","Technical preparation to add a new permission for viewing employee details in ORTEC WS for Team Schedulers.\nA new permission has been added: ORTEC WS for Team Schedulers > Allowed to view employee details.\nThis permission will be automatically assigned to anyone with permission to Edit Schedules.",null,50259]
[null,null,1625278,"2024-11-21",null,"Development\\OWS7","OWS Win32 Client: using the tab to activate the costcenter in an activity in the duty form could crash the client",null,null,"OWS Win32 Client: using the tab to activate the costcenter in an activity in the duty form could crash the client","When using tab to go to the cost center cell in an activity with an assigned cost center in the Win-32 Client and SHOWCOSTCENTERSINTREE was set to True, an endless loop could occur crashing the Client.\nThis has been fixed.\n\nTest hint(s): None","For this solution to become available, the ORTEC WS Win32 client must be installed.",51017]
[null,null,1625278,"2024-11-21",null,"Development\\OWS7","OWS Win32 Client: Unexpected focus and selected items in several grids showing controls containing time or integer values",null,null,"OWS Win32 Client: Unexpected focus and selected items in several grids showing controls containing time or integer values","OWS Win32 Client: Unexpected focus and selected items in several grids showing controls containing time or integer values.\nI.e. when selecting begin and end time elements in the activities in a duty realization.\nThis has been improved.\nThe changes causing this issue were reverted.\n\nThis was introduced in issue 33520 \"Retrieving the Workstation or ActivityType data for the Dutyform activities tab was called twice on each click\".\nThis issue was delivered in OWS 7 - 8.5.0 (2024-05-16) Build1600173.\n\nTest hint(s):\n1. Verify that when selecting begin and end time elements in the activities in a duty realization are fully selected when selecting the element using TAB or mouse click\n2. Verify that when selection an amount in the registration tab in a duty realization the amount fully selected when selecting the element using TAB or mouse click","For this solution to become available, the ORTEC WS Win32 client must be installed.",49494]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"BackendAPI - Reporting integrated security settings were ignored for (recently added) reporting endpoints.","Reporting integrated security settings were ignored for (recently added) reporting endpoints.\nThis has been fixed.\n\nTest hint(s):\n1. Verify reporting endpoints for Backend API work by retrieving reports in an ESS front end",null,35734]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"Feature toggle ImproveHandlingUpdatesUsingClientSideCursor has been removed","Feature toggle ImproveHandlingUpdatesUsingClientSideCursor has been removed.\n\nThis feature toggle was introduced in OWS 7 update 1564089  (2023-09-14).\n\n\n\nTest hint(s):\n\nNone.",null,37319]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"messageHubLog records within the same CMHS call did not have the same transactionGuid.","Records in the table messageHubLog that belong to the same CMHS call did not have the same transactionGuid.\n\nThis has been improved.\n\nAll messageHubLog records within the same CMHS call now get the same transactionGuid.\n\n\n\nTest hint(s):\n\nNone",null,49242,"https://ortec.link/Request?HID=16747058"]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"Importing a new account category would result in the category not being added to the running account on the import interfaceworker","Importing a new account category would result in the category not being added to the running account on the importing interfaceWorker.\nThis could lead to BI or salary export failures when importing rules that uses new account categories.\nThis has been fixed.\n\nTest hint(s):\n1. Verify that there are no BI or salary export fails when importing rules that use a newly imported account category (by the same interfaceworker).",null,49244,"https://ortec.link/Request?HID=16747062"]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"When running DBUpdate with parameters 'FullDropAndCreate = False' and 'ContinueWhenChangeTrackingIsEnabled', change tracking was disabled for the entire database","When running DBUpdate with parameters 'FullDropAndCreate = False' (or with switch '/OptimizedDropAndCreate') and 'ContinueWhenChangeTrackingIsEnabled', change tracking is disabled for the entire database.\n\nThis has been improved. \n\nChange tracking is now only disabled and re-enabled for the affected tables.\n\n\n\nTest hint(s):\n\nNone",null,50246]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"Technical preparation for a new ESS7 feature called \"accept shifts\". ","New functionality will be added in ESS7 in which employees can accept or decline scheduled shifts. Planners can mark shifts as \"'Open for confirmation\" via a Yes/No duty property. \nShifts that are marked as \"open for confirmation\" will be shown to the employee in a new ESS7 section and the employee is given the option to accept or decline them. \nThis will be communicated via two other duty properties, which the planner is able to see. \nIf the employee accepts a shift it will show up in this schedule, regardless of the schedule status (it will also be shown in status plan).   \n \nThe following settings are added to support this functionality:   \n- Comtec.Workforce.BackendAPI\\ESS7\\AcceptShifts\\DutyPropertyOpenForConfirmation     \n   Name of the boolean duty property used for 'open for confirmation' status. \n- Comtec.Workforce.BackendAPI\\ESS7\\AcceptShifts\\DutyPropertyForAcceptedStatus\n   Name of the boolean duty property used for 'accepted' status. \n- Comtec.Workforce.BackendAPI\\ESS7\\AcceptShifts\\DutyPropertyForDeclinedStatus\n   Name of the boolean duty property used for 'declined' status. \n- Comtec.Workforce.BackendAPI\\ESS7\\PersonalRoster\\DutyPropertyForOverridingPublishedStatus\n   Name of the boolean duty property used for overriding published status. \n \nTo get the accepted shifts to show up in the schedule regardless of their status you have to set DutyPropertyForOverridingPublishedStatus=DutyPropertyForAcceptedStatus.\n \nThe setting DutyPropertyForOverridingPublishedStatus can also be used independently for other cases, where a planned shift should be shown in the schedule of an employee. \nThink about the use case of already communicating the Christmas planning of next year to employees.\n \nTwo new routes are added to the backend API:\n- api/v2/acceptShifts/GetShiftsOpenStatus\n   This route returns the shifts for the given employee for which DutyPropertyOpenForConfirmation is set to True.\n- api/v2/acceptShifts/SetDutyPropertyShiftConfirmation\n   This route updates these duty properties accordingly based on whether the employee accepted or declined the shift.    \n \nFurthermore, there is one new Access Control permission that regulates for which employee this new functionality is available in ESS7: gui.workspace.ess.acceptshifts\n \nTest hint(s): None",null,50514]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"OWS Win32 Client: Customize menu bar window showed untranslated items","Customize menu bar window showed untranslated items.\n\nThis has been fixed.\n\nThis was introduced in issue 33774 \"Added the possibility to replace the legacy OWSClient helpfile with a webbased alternative.\"\n\nThis issue was delivered in OWS 7 8.5.0(2024-09-13)_Build1616090.\n\nA restart of OWS Win32 Client is still advised when changing language before accessing the customize menu bar window.\n\n\n\nTest hint(s):\n\n1. Verify that opening the customize menu (by right-clicking the menu bar) results in a translated menu.","For this solution to become\n\navailable, the ORTEC WS Win32 client must be installed.",50670,"https://ortec.link/Request?HID=16778995"]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"Improved performance of BackendApi query Comtec.Workforce.BackendAPI/Portal/v2/ScheduleDataByResourceIds","The query Comtec.Workforce.BackendAPI/Portal/v2/ScheduleDataByResourceIds could be made faster.\n\nThis has been improved.\n\n\n\nTest hint(s):\n\nNone",null,50674,"https://ortec.link/Request?HID=16778999"]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"When error is raised creating an overlapping illness for a resource some information on context of the overlapping illnesses was missing","When an error is raised creating an overlapping illness for a resource some information on the context of the overlapping illnesses was missing.\n\nThis has been improved.\n\nWhen such an error is raised, additional information on the periods and resources is added for analysis purposes.\n\n\n\nTest hint(s):\n\nNone",null,51210]
[null,null,1628312,"2024-12-17",null,"Development\\OWSforTeamSchedulers",null,null,null,"Fixed retrieving the parameters for reports when the user has permissions for a lot of departments","For users with permissions for a lot of departments (typically administrators), reports could throw an error when opened. This has been fixed.",null,51272]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"Technical preparation for hardening of authorizations in Backend-API routes","Preparation for hardening authorizations in Backend-API routes\n\nTest hint(s): None",null,51493]
[null,null,1628312,"2024-12-17",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation to make shift name editable","Technical preparation for showing the employee realizations tile in ORTEC WS for Team Schedulers.",null,51570]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"Shift notifications from the Backend Domains API were not propagated ","Shift notifications from the Backend Domains API were correctly propagated in to ORTEC Relevance via the OrtecRelevancePushNotificationSender plugin\n\n\n\nAn error was shown in the log with the following text 'Error processing notification with notification token: gotShiftNotification'\n\nThis has been improved.\n\nThe aforementioned notifications will be handled and propagated to ORTEC Relevance via the OrtecRelevancePushNotificationSender plugin\n\n\n\nThis was introduced in \"46613: Added new notification type for shift changes\" delivered in OWS7 - 8.5.0(2024-09-05) build1614627\n\n\n\nTest hints:\n\n1. Verify that expected shift offer notifications are handled by Backend Domains API and are propagated to ORTEC Relevance",null,51655,"https://ortec.link/Request?HID=16804152"]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"Skill levels were not imported correctly.","Skill levels were not imported correctly with deprecated xml node SKILL_LVL.\n\nThis has been fixed.\n\nPlease note that, while importing a skill level can now use both labels, using the xml-node SKL_LVL is preferred.\n\nThe skill level checks that the ExtraXMLCreator EmployeeBeforeImportChecks performs will also be done on both fields.\n\nThis change along with the features of 31502 (The begin-/enddates of an existing \n\nskill/grouplabel were not updated if the new begindate lies after the \n\ncurrent begindate or the new enddate lies before the current enddate) are available behind feature toggle IMPROVERESOURCEGROUPLABELANDSKILLIMPORT, which is turned on by default.\n\n\n\nTest hint(s):\n\n1. Verify that importing a skilllevel with node SKILL_LVL will result in a skill with the imported level\n\n2. Verify that importing a skilllevel with node SKL_LVL will result in a skill with the imported level\n\n3. Verify that importing a skilllevel without a level node will result in a skill with the level 0",null,51825,"https://ortec.link/Request?HID=16805633"]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"When performing an update in the OWS database no check was done for valid skill levels for the skill detail tables","When performing an update in the OWS database no check was done for valid skill levels for the skill detail tables\n\nThis has been improved.\n\nA warning will be displayed for the skill detail tables that have a level that is not in bounds of the defined lowest and highest level defined in the associated skill. \n\nNote: if the DBUpdate does return a warning on this check, the faulty data should be located and corrected (including import data)\n\n\n\nTest hint(s):\n\n1. Verify that updating the database when installing a patch does not show warnings",null,51995]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"High amount of deletion requests for cleaning ROS_NOTIFICATION_SENDER_LOGGING could decrease performance","High amount of deletion requests for cleaning ROS_NOTIFICATION_SENDER_LOGGING could decrease performance.\n\nThis has been improved.\n\nA index on table ROS_NOTIFICATION_SENDER_LOGGING has been added on Created_At column to improve performance of the deletes.\n\nA new CSCS setting OrtecRelevancePushNotificationSender\\General\\CleanupLoggingIntervalInMinutes has been added to regulate cleanup interval (default 60 minutes).\n\nSetting the value to zero reverts to old behavior.\n\n\n\nTest hint(s):\n\nNone.",null,52061,"https://ortec.link/Request?HID=16589016"]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"Shift offer notification could be sent with a wrong formatted date causing 'Invalid Date' error","Shift offer notification could be sent with a wrong formatted date causing 'Invalid Date' error\n\nDate of shift offer notification could be formatted with a format not equal to ISO 8601 date format that is supported, causing duplicates not to be handled correctly.\n\nThis has been improved.\n\n\n\nThis was introduced in issue 46613 \"Added new notification type for shift changes\"\n\nDelivered in OWS 7 Build 1614627, 2024-09-05\n\n\n\nTest hint(s):\n\n1. Verify shift offer notifications are sent as expected",null,52081,"https://ortec.link/Request?HID=16816961"]
[null,null,1628312,"2024-12-17",null,"Development\\OWS7",null,null,null,"Import employee skillLevel with workstation or location fails","Importing an employee skill level with a workstation or physical location would throw a database error.\nThis has been fixed.\nThis change is behind feature toggle IMPROVERESOURCEGROUPLABELANDSKILLIMPORT introduced with 51825\nNote this was introduced in version 8.5.0(2024-10-14)_Build1620658\n\nTest hint(s):\n1. Verify that a employee skill level can be imported with a workstation and physical location.",null,52302,"https://ortec.link/Request?HID=16820845"]
[null,null,1628904,"2025-01-06",null,"Development\\OWS7",null,null,null,"CMHS Network did not stop properly when XSLProcessor and CMHSAdvFilter is used and an error was encountered","CMHS Network did not stop properly when XSLProcessor and CMHSAdvFilter is used and an error was encountered.\nThis has been fixed.\n\nNote this change is also relevant for similar issues with other processor types.\n\nTest hint(s):\n1. Verify that when XSLProcessor and CMHSAdvFilter is used and an error is encountered the CMHS network now stops properly.",null,33630,"https://ortec.link/Request?HID=16586321"]
[null,null,1628904,"2025-01-06",null,"Development\\OWS7",null,null,null,"UnattendedUpdates variables could be used by customScripts","While running customScripts, variables between unattendedUpdates and the custom script were shared in the same scope.\nWhen both scripts used the same variable name, they could be mixed up. causing undesired side effects.\nThis has been improved\n- The concerning variable $logFile has been renamed to something more likely to be unique.\nTo further prevent occurrences on other variables, a new option can be added to the customScript configuration \nThis will start a customScript in new Powershell.exe instance.\nTo configure:\nAdd the following in a/each <customScript> node: <runInNewPowershell>Y</runInNewPowershell> in the UnattendedUpdate_Config.xml\nSee: Template_UnattendedUpdate_Config.xml for an example\n\n\nNotes\n- Using <runInNewPowershell>Y should be the preferred method. Exceptions are caught by UnattendedUpdates but are not returned in much detail. \n- Not adding the <runInNewPowershell> node is allowed then a value of N is assumed and the previous behavior is executed.\n\nTest hint(s):\n1. Verify that logging is as expected in unattendedUpdate logfile\n2. Verify that when a customScript raises an exception, UnattendeUpdate will also stop.",null,51166,"https://ortec.link/Request?HID=16792542"]
[null,null,1628904,"2025-01-06",null,"Development\\OWS7",null,null,null,"When using copy/paste on an overlapping shift a warning message was shown - Revert of 14040 ","When using copy/paste on an overlapping shift a warning message was shown.\nThis was introduced in issue 14040 \"When using copy/paste on an overlapping shift, it got unplanned without a warning message\"\nDelivered in OWS7 - 8.5.0(2024-09-05)_Build1614627\nThe changes done in 14040 have been reverted as this change did not have the expected acceptance when rolled out.\nIt will be investigated if a different resolution will be created to solve the issue raised in synergy ticket 15824793 that was the origin of 14040\n\nTest hint(s):\n1. Verify that copy and pasting a shift overlapping a shift, plans out the shift without a warning",null,52303,"https://ortec.link/Request?HID=16820849"]
[null,null,1628904,"2025-01-06",null,"Development\\OWS7",null,null,null,"Security of Back-end-API endpoints have been hardened","The security of the endpoints in the Back-end-API has been hardened.\nThis means that extra checks are being performed when calling an endpoint:\n- whether the logged in user has the correct permission(s) for the endpoint.\n- whether the logged in user matches the employee for which the call to the endpoint was made.\n\nThese checks are put behind setting FeatureToggles\\HardenAuthorizationForBackendAPIRoutes, which is disabled by default\n\nNote in some of the adjusted endpoints extra database queries are performed to be able to execute these extra checks.",null,52450]
[null,null,1631660,"2025-01-23",null,"Development\\OWS7",null,null,null,"Unattended Updates - Escape HTML tags in logfile and clean DBUpdate warnings text","The Unattended Updates logfile contained HTML tags.\r\nThis logfile is attached to the email Unattended Updates sends out\r\nSome SMTP servers may block emails with HTML in attached files.\r\nFurthermore, the output from DBUpdate warnings contained to much data when SQL Change Tracking is enabled.\r\nSome of this data could be interpreted as SQL injection.\r\nThis has been fixed\r\n- HTML tags are now removed from the Unattended Updates logfile\r\n- DBUpdate warnings only show clean and relevant information\r\n\r\nTest hint(s):\r\n1. Verify emails from unattended updates are sent and received\r\n2. Verify no html tags are present in the logfile\r\n3. Verify that information from DBUpdate warnings is sufficient","",12075,""]
[null,null,1631660,"2025-01-23",null,"Development\\OWSforTeamSchedulers",null,null,null,"Adding a lot of shifts in a short amount of time in ORTEC WS for Team Schedulers could result in errors","Adding a lot of shifts in a short amount of time in ORTEC WS for Team Schedulers could result in errors.\r\nThis has been improved.","",37223,""]
[null,null,1631660,"2025-01-23",null,"Development\\OWSforAdHocPlanners",null,null,null,"Technical preparation to Cancel responses of employees in ORTEC WS for Ad Hoc Planners","Technical preparation to Cancel responses of employees in ORTEC WS for Ad Hoc Planners","",52447,""]
[null,null,1631660,"2025-01-23",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation to manage sick leave properties in ORTEC WS for Team Schedulers","Technical preparation to manage sick leave properties in ORTEC WS for Team Schedulers","",52477,""]
[null,null,1631660,"2025-01-23",null,"Development\\OWS7",null,null,null,"Support (mouse) scroll wheel in duty palet and own sorting window","The \"duty palet\" and the \"own sorting\" windows in the ORTEC WS Win32 client did not support the use of the mouse scroll wheel.\nThis has been improved.\n\nTest hint(s):\nOpen duty palet in the planboard and verify the shifts and special duties can be scrolled through using the scroll wheel of the mouse, when there is a scroll bar on the side of the window. The window can be made shorter to get the scroll bar.","For this solution to become available, the ORTEC WS Win32 client must be installed.",53102,""]
[null,null,1631660,"2025-01-23",null,"Development\\OWSforTeamSchedulers",null,null,null,"Cyclical schedule shifts were not applied when there was no demand in ORTEC WS for Team Schedulers","Duties without a demand were not rolled out when rolling out a cyclical schedule in ORTEC WS for Team Schedulers. \nThis has been fixed.","",53182,""]
[null,null,1631660,"2025-01-23",null,"Development\\OWS7",null,null,null,"The security of the endpoints in the Back-end-API related to preferences has been hardened further.","The security of the POST and DELETE preferences route in the Back-end-API has been hardened further.\n\nThis means that extra checks are being performed when calling an endpoint:\n- whether the logged in user matches the employee for which the call to the\npreference was made.\n- Different permissions are checked based on which parameters are given.\nThis was already the case of other endpoints.\n\nThese checks are put behind existing setting\nFeatureToggles\\HardenAuthorizationForBackendAPIRoutes, which is disabled by\ndefault\n\nPlease note that extra database queries are performed to be able to execute these extra checks.","",53296,""]
[null,null,1631660,"2025-01-23",null,"Development\\OWS7",null,null,null,"The security of the endpoints in the Back-end-API related to templateWishes has been hardened further.","The security of the GET templateWishes route in the Back-end-API has been hardened further.\n\nThis means that extra checks are being performed when calling an endpoint:\n- Permissions are checked when retrieving template wishes over the API.\nThis was already the case of other endpoints.\n\nThese checks are put behind existing setting\nFeatureToggles\\HardenAuthorizationForBackendAPIRoutes, which is disabled by\ndefault","",53323,""]
[null,null,1631660,"2025-01-23",null,"Development\\OWSforTeamSchedulers",null,null,null,"Recurring duty requests were in some cases not shown in ORTEC WS for Team Schedulers","Recurring duty requests were in some cases not shown in ORTEC WS for Team Schedulers. This could happen if the request was for a certain day in the last week of the month.\r\nThis has been fixed.","",53401,"https://ortec.link/Request?HID=16846065"]
[null,null,1631660,"2025-01-23",null,"Development\\OWSforAdHocPlanners",null,null,null,"Shift remark for absent and offered shifts was always in English","When registering an employee absent and then offering the shift in ORTEC WS for Ad Hoc Planners, the generated shift remark notifying the user that the shift is not available anymore was always in English. \nThis has been fixed.\nNow, the shift remark is generated in the default language of the CWSS server.","",53480,"https://ortec.link/Request?HID=16847839"]
[null,null,1633448,"2025-02-06",null,"Development\\OWS7",null,null,null,"Handling updates no longer waits for cleaning of handled updates","It could occur that that CHandleUpdateInTransaction ran into a timeout when removing handled updates took a long time.\nThis has been improved, \n\nHandling updates can now queue a job to clean handled updates so it does no longer have to wait for cleaning.\n\nAdded feature toggle setting: FeatureToggles\\UseJobForTransactionCleaning which is disabled by default.\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s): None","","36746",""]
[null,null,1633448,"2025-02-06",null,"Development\\OWS7",null,null,null,"Added BI settings to influence chunk size for retrieving calculated data","Added two settings to BI to influence the batch size of employees and departments for which calculated data is retrieved from the HTTPSServer and InterfaceWorker(s).\nFor employees, this is used while retrieving account category lines, employee requests and violations.\nFor departments, this is used while retrieving department account category lines, duty demands and cyclical shifts\n\nThese integer settings have been added to CSCS -> Settings Manager -> CBIS -> Dataloads\n- NofEmployeesPerDataRetrievalLoop  \n- NofDepartmentsPerDataRetrievalLoop \n The default value for both settings is 50. \nA lower value can relieve strain on CWSSServer (like memory peaks and locking) while a higher value can speed up the BI run.  Note that changing these settings should only be done when there probable cause that the default values cause problems.\n\nTest hint(s):\n1. Verify a BI run runs within the usual time and finishes successfully.","Please update the values of the settings for customers where the chunk size has already been adjusted in the '@Length' variable in STAGE_Department_List_Insert.sql and/or STAGE_Employee_List_Insert.sql.","48301","https://ortec.link/Request?HID=16718417"]
[null,null,1633448,"2025-02-06",null,"Development\\OWS7",null,null,null,"TDutyPropertyXMLCreator returned a scientific notation for userproperties type decimal","TDutyPropertyXMLCreator returned a scientific notation for userproperties type decimal.\nThis has been changed. The value 12.25 is no longer exported as 1.22500 ?? 10^1, but as 12.25.\n\nThis change is behind Featuretoggle UseDecimalNotationForExportOfDecimalProperty which is enabled by default.\n\nTest hint(s):\n1. Verify that exporting a decimal dutyproperty using TDutyPropertyXMLCreator no longer exports the decimal value as scientific notation.","","51151","https://ortec.link/Request?HID=16792316"]
[null,null,1633448,"2025-02-06",null,"Development\\OWS7",null,null,null,"Added new compensation rule: Variable entry for consecutive activity types","Added new compensation rule: ConsecutiveActivityTypesRem (Variable entry for consecutive activity types).\n\nThis rule books a value based on the total duration of consecutive activity types that are marked as relevant. Which activity types are relevant can be selected in the rule.\nTwo activities are consecutive if they are directly adjacent to each other (no time in between). This is independent of the shift they are in. \nConsecutive activities in multiple shifts will be considered as one series of activities and will be booked as one value. Please note that a single activity that is not consecutive will also be considered a series (of one activity).\nThe resulting account category line is booked on the start date of the first activity in the series.\nI.e. If a night shift starts on day 1 and the first relevant activity in that shift starts on day 2, the value is booked on day 2.\n\nTest hint(s):\n1. Verify this new rule can be used after enabling it in the OWS Settings Manager","","51793",""]
[null,null,1633448,"2025-02-06",null,"Development\\OWS7",null,null,null,"Added the ability to select department periods in the requirement NofFreeWeekendsReq (Number of free weekends)","Added the ability to select department periods in the requirement NofFreeWeekendsReq (Number of free weekends).\r\n\r\nThis given the option to select any pre-defined period types for the interval to check the required number of free weekends in.\r\n\r\nThe option \"department period\" is a fixed period, so the rule will only be checked for intervals where a department period exists.\r\n\r\nTest hint(s):\r\n1. Open a Number of free weekends labour time requirement and verify that the option department period is selectable and a period type can be chosen.\r\n2. After creating a Number of free weekends requirement with a department period, open a schedule overlapping with a department period and verify that a violation is given, when the employee has too few free weekends in their schedule.","","53013",""]
[null,null,1633448,"2025-02-06",null,"Development\\OWS7",null,null,null,"Report \"Master schedule ESS\" gave an error in ESS7 when a department was selected that an employee is lent to.","Report \"Master schedule ESS\" gave an error in ESS7 when a department was selected that an employee is lent to.\r\nThis had been fixed.\r\nIt is now possible to open the report for a department the employee is borrowed in.\r\n\r\nTest hint(s):\r\n1. Verify that an ESS7 user can open the report \"Master schedule ESS\" for a department that the employee is lended to.","","53315","https://ortec.link/Request?HID=16844639"]
[null,null,1633448,"2025-02-06",null,"Development\\OWSforAdHocPlanners",null,null,null,"Vacant shift could get stuck when a fixed shift was offered from ORTEC WS for Ad Hoc Planners","Vacant shift could get stuck when a fixed shift was offered from ORTEC WS for Ad Hoc Planners.\r\nThis has been fixed.","","53597","https://ortec.link/Request?HID=16848872"]
[null,null,1633448,"2025-02-06",null,"Development\\OWS7",null,null,null,"Added functions GETDEMANDEDDUTIESFORDEPS_BI and GETDEMACTIVITIESFORDEPS_BI","Added _BI variants of database functions GETDEMANDEDDUTIESFORDEPS and GETDEMACTIVITIESFORDEPS.\r\nThese functions also return error messages returned by the HTTPServer or InterfaceWorker when raised.\r\nThis can be used to verify the successful retrieval of data.\r\n\r\nTest hint(s): None","","53666",""]
[null,null,1633448,"2025-02-06",null,"Development\\OWS7",null,null,null,"The security of the endpoints in the Back-end-API related to route api/V2/defaultShiftsWithGeneralAbsenceName has been hardened further.","The security of the GET api/V2/defaultShiftsWithGeneralAbsenceName route in the Back-end-API has been hardened further.\nThis means that extra checks are being performed when calling an endpoint: \n- Permissions are checked when retrieving template the default (master schedule) shifts of the specified employees in the specified period over the API. \nThis was already the case of other endpoints. \nThese checks are put behind existing setting FeatureToggles\\HardenAuthorizationForBackendAPIRoutes, which is disabled by default\n\nTest hint(s): None","","53744",""]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"DBUpdate raised a false positive on integer columns during datamodel comparison","During  the step 'comparing datamodel' the DBUpdate process raised a false positive that columns in some cpms and crbs tables were of type integer while they should be int.\r\nAs SQLServer treats integer as an alias of int, the column types in the database were already created as int, thus raising a false positive during every datamodel comparison and resulting in an unnecessary lift of dependencies at every DBUpdate.\r\nThis has been fixed\r\nThe OWS datamodel has been adjusted to always use (and compare to) the column type int.\r\nNote that the BI HDM_Stage and HDM datamodels have also been adjusted.\r\n\r\nTest hint(s): None","","37236","https://ortec.link/Request?HID=16626896"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"Recurring work wish gave a violation even if there is an overlapping leave wish","Recurring work wish gave a violation even if there is an overlapping leave wish.\r\nThis has been fixed\r\nA leave wish will override any overlapping recurring work or shift wish.\r\nThis change is behind Featuretoggle AllowLeaveWishToOverrideRecurringWorkOrShiftWish which is enabled by default.\r\nThis change also removes existing Featuretoggle AllowWorkInIntervalWishAndWishWithShiftToCreateMultipleViolationsIfNeeded.\r\nThis feature toggle was introduced in update 1533112 (2023-02-16)\r\n\r\nTest hint(s):\r\n1. Verify that having a leave wish and a recurring duty wish will not produce a violation for an empty schedule or a leave shift\r\n2. Verify that having a leave wish and a recurring work wish will not produce a violation for an empty schedule or a leave shift",null,"46562",""]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"Subsystem CRBS would still log to the eventviewer and the logfile of CWSS","The subsystem CRBS would still log to the eventviewer and the logfile of CWSS.\r\nThis has been changed.\r\n\r\nTest hint(s):\r\nNone","","46728","https://ortec.link/Request?HID=16665406"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"The report \"Master schedule ESS\" would sometimes be less readable when the background was dark","The report \"Master schedule ESS\" would sometimes be less readable when the background was dark.\r\nThis has been improved.\r\n\r\nTest hint(s):\r\n1. Verify the report Master Schedule ESS now shows white letters when  shifts have a less dark background color.","","46803","https://ortec.link/Request?HID=16667169"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"A failing import was missing details to allow the customer to know which employee had which shift/date not imported.","A failing import was missing details to allow the customer to know which employee had which shift/date not imported.\r\nThis has been improved.\r\nAdditional information has been added to the interface message.\r\n\r\n\r\nThis change is behind FeatureToggle ExtendInterfaceMessagesWithAdditionalInfo which is enabled by default.\r\n\r\nTest hint(s):\r\nNone","","46877","https://ortec.link/Request?HID=16668798"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"BI runs with manual trigger method could remain blocked due to remaining 'active' logfile","When using BI with the manual trigger option provided at some hosted customers, the 'BI_With_Manual_Trigger.ps1' script will check whether a BI run is currently active by looking at the BI logfiles.\r\nWhen a logfile was present ending on _RUNNING, a new BI run could not be started.\r\nDuring Windows maintenance (reboot), it could occur that a Powershell session running BI was forcefully closed, leaving the BI logfile as '_RUNNING'.\r\nIn such cases BI could no longer start by trigger or schedule until the logfile was removed.\r\nThis has been improved.\r\n\r\n\r\nThe 'BI_With_Manual_Trigger.ps1' script now assumes BI logfiles that are '_RUNNING' but are older than 23 hours belong to a crashed BI run.\r\nSuch logfiles will be renamed from _RUNNING to _FAILED to allow BI to start again according to schedule or trigger.\r\n\r\n\r\nTo enable this functionality, a new setting must be added to the customers BI_CONFIG_IL.ps1 \r\nPlace the following at the bottom:\r\n[boolean]$FailLogfileOnSuspectedCrash = $True\r\nWhen the setting is not present, it will be regarded as $False \r\n\r\n\r\nSee the BI_CONFIG_Template.ps1 for an example\r\n\r\nTest hint(s):\r\n1. Verify BI tasks run normally when manual trigger option is used.","","48513","https://ortec.link/Request?HID=16728171"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"Credentials on CCDSProcessor were not used when network started with a CCDSProducer","When a CMHS network starts with a CCDSProducer, the provided credentials for a CCDSProcessor were not used.\r\nThis has been improved.\r\nDepending on the value of a new CCDSProducer setting ComtecCredentialsOverwriteInheritedCredentials, a CCDSPlugin will first use supplied credentials, if they are not provided or the setting is set to false, it will look at an existing login session or create a new session.\r\n\r\nTest hint(s):\r\n1. Verify the credentials provided for a nested CCDSProcessor are used when provided and ComtecCredentialsOverwriteInheritedCredentials is set to True.\r\n1. Verify the credentials of the original process are used  for a nested CCDSProcessor when ComtecCredentialsOverwriteInheritedCredentials is set to False.","","48543","https://ortec.link/Request?HID=16728881"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"A translation has been corrected for the German language. ","The German translation for a button in the Duty palet window has been corrected.\r\n\r\nTest hint(s): None","For this solution to become available, the ORTEC WS Win32 client must be installed.","48769","https://ortec.link/Request?HID=16737398"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"A FieldCollector would not filter on the collected class when exporting a queue","A queue export with a FieldCollector defined for classtype TUserPropertyValue would always collect the class related to the userproperty, regardless whether this was the class defined in the collectedclass attribute. In addition, it would wrongly name the classnode in the resulting XML file.\r\nThis has been improved.\r\nA Fieldcollector for classtype TUserPropertyValue will now only collect the class defined in the collectedclass attribute and only when that is the class the exported userproperty is linked to.\r\nThis change is behind Featuretoggle FilterOnCollectedClassInFieldCollector which is enabled by default.\r\n\r\nTest hint(s):\r\n1 Verify that when defining a queue with a fieldcollector on Class TUserPropertyValue with collected class=TEmployee, an update on a department property no longer adds the Department class to the exported file.","","49038","https://ortec.link/Request?HID=16744358"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"Entering a leave request could be blocked by an incorrect leave balance check","When entering a leave request in ESS the check on leave balance could experience rounding issues, causing a message that there was not enough balance when the balance was exactly sufficient.\r\nThis has been improved.\r\nThis change is behind feature toggle UseRoundingOnCheckLeaveBalanceESS which is enabled by default.\r\n\r\nTest hint(s):\r\n1. Verify a leave request an be entered with a leave balance check that is exaclty sufficient.","","49191","https://ortec.link/Request?HID=16746935"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"Adding variable CANBEPAUSED with value false to a cmhs-network had no effect","Adding variable CANBEPAUSED with value false to a cmhs-network had no effect.\r\nThis has been improved.\r\nWith this change the CANBEPAUSED variables in the cmhs-network settings are reintroduced.\r\nThe CANBEPAUSED functionality can be disabled for the entire configuration by adding variable CANBEPAUSED with value false to the configuration variables.\r\nIt can be disabled for specific networks by adding variable CANBEPAUSED with value false to network variables.\r\nA network specific variable will override a configuration variable, so specific networks can have the functionality active, while the rest of the configuration has it disabled.\r\n\r\nTest hint(s):\r\n1. Verify that adding variable CANBEPAUSED with value false to the configuration variables will disable the pausing functionality for all networks in that configuration.\r\n2. Verify that adding variable CANBEPAUSED with value false to a network's variables will disable the pausing functionality for that specific network.","","50252","https://ortec.link/Request?HID=16772023"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"Changed the default option for CMHS processes \"action to take on critical error\" to \"stop all networks\"","When adding a CMHS process to CSCS process configuration, the default value for \"action to take on critical error\" was None.\r\nThis has been changed.\r\nThe default value for \"action to take on critical error\" is now the preferred \"stop all networks\" option. \r\nNote, all existing CMHS processes that have never applied this configuration explicitly will now also use this default.\r\n\r\nTest hint(s):\r\n1. Verify that adding a CMHS process in CSCS process configuration shows \"Stop all networks\" as default option for \"action required on critical error\".","","50876","https://ortec.link/Request?HID=16786459"]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"New interface queue collectors for pending updates","Two new queue collectors for pending updates have been added to be used in an XML export definition.\r\nThe ShiftPendingUpdatesByShiftCollector can enrich an xml export file with all shift pending updates linked to a updated shift object.\r\nThe ShiftPendingUpdatesByDutyCollector can enrich an xml export file with the shift pending updates linked to a updated duty object.\r\n\r\nTest hint(s):\r\n1. Given a XML definition with a queue export based on shifts and the new ShiftPendingUpdatesByShiftCollector, verify that an update to a shift with a pending update, will result in an export file with the shift pending update included.\r\n1. Given a XML definition with a queue export based on shifts and the \r\nnew ShiftPendingUpdatesByDutyCollector, verify that an update to a \r\nduty of a pending update in ESS, will result in an export file with the \r\nshift pending update included","","53025",""]
[null,null,1635163,"2025-02-25",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for supporting shift replacement type 'by contract hours'","Technical preparation for supporting a new replacement type 'by contract hours' when replacing shifts with illness shifts","","53742",""]
[null,null,1635163,"2025-02-25",null,"Development\\OWS7",null,null,null,"Several translations added for Danish, Finnish and German","Several translations have been added for Danish, Finnish and German for recent functional changes.\r\n\r\nTest hint(s):\r\nNone","","53799",""]
[null,null,1635163,"2025-02-25",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for supporting \"plan contract hours\" when adding special shifts","Technical preparation for supporting \"plan contract hours\" when adding special shifts","","54160",""]
[null,null,1635163,"2025-02-25",null,"Development\\OWSforTeamSchedulers",null,null,null,"Fixed warning about handle gone out of scope without disposing","When unassigning a shift in ORTEC WS for Team Schedulers, a message was written to the EventViewer: \"A CDSessionHandle instance (handler: /hmy/serverX/teamscheduling/CUnassignShifts) has gone out of scope without having been disposed.\"\r\nThis has been fixed. Now, the handle is disposed so no warning is logged.","","54519","https://ortec.link/Request?HID=16873992"]
[null,null,1636582,"2025-03-11",null,"Development\\OWS7",null,null,null,"Running the weekend optimizer in a month starting with a partial weekend could result in a 'No such element' error.","Running the weekend optimizer in a month starting with a partial weekend could result in a 'No such element' error.\nThis could happen when an employee was available to this department on Saturday but not anymore on Sunday, the error appeared as the employee did not exist anymore.\nThis has been fixed. \nAdded feature toggle Server setting: FeatureToggles\\WeekendPlannerFilterUnavailableEmployees which is disabled by default.\nWhile working on this fix, a second bug appeared. Running the weekend optimizer could result in an 'Overlapping shifts' error for fixed shifts.\nWhen an employee has a fixed shift, we do not allow any other employee to be assigned this shift by the weekend optimizer.\nThis has been fixed. \nAdded feature toggle Server setting: FeatureToggles\\WeekendPlannerFixedShiftsCheck which is disabled by default.\n\nTest hint(s):\n1. Verify that the weekend optimizer will run successfully in a period starting with a partial weekend.",null,"46090","https://ortec.link/Request?HID=16639329"]
[null,null,1636582,"2025-03-11",null,"Development\\OWS7",null,null,null,"A new queue filter 'WishEmployeePropertyQueueFilter' has been added.","A new queue filter 'WishEmployeePropertyQueueFilter' has been added.\nThis filter works on creation, changes and deletes of wishes for employees having a Yes value for a configured employee property valid on the date of the wish.\nTo configure add the following filter to a wish queue export definition:\n<WishEmployeePropertyQueueFilter employeePropertyNames=\"booleanEmplProp1,booleanEmplProp2\"/>\nThe configured properties must be an employee property and of the type Yes/No.\nMultiple employee properties can be defined (separated by a comma).\nThe export triggers on wish changes in the following condition:\nThe employee must have the value Yes for one of the configured employee properties valid on the (old or new) date of the wish, or the valid interval for recurring wishes.\n\nTest hint(s):\n1. Verify the queue export filters on mentioned conditions","","54517",""]
[null,null,1636582,"2025-03-11",null,"Development\\ORTEC Workforce\\Suite",null,null,null,"BackendEventPublisher did not include 'application/json' header when publishing events","BackendEventPublisher did not include 'application/json' header when publishing events\r\nThis has been improved. The header is included when publishing events.\r\n\r\nTest hint(s):\r\n1. verify that opening a shift for bidding in OWS Win32 client is correctly published to and visible in shift offering front-end","","54586",""]
[null,null,1638158,"2025-03-26",null,"Development\\OWS7",null,null,null,"UnattendeUpdates will run DBUpdate with the OptimizedDropAndCreate option","In card 8154, an option OptimizedDropAndCreate has been added to DBUpdate(Wizard).exe and DBUpdateConsole.exe\r\nBut for DBUpdateConsole.exe this was not default behaviour \r\nUnattendedUpdates will now use the OptimizedDropAndCreate option as default.\r\n\r\nTest hint(s):\r\n1.Verify that DBUpdate runs as expected","This functionality can be turned on or off in C:\\ProgramData\\Ortec\\ORTEC Workforce Scheduling\\UnattendedUpdates\\UnattendedUpdate_Config.xml If the <featureToggles>node does not exist, the following node can be inserted between </scriptOptions> and <eMail>:\n<featureToggles>\n     ...    \n    <useOptimizedDropAndCreateInDbUpdate>Y</useOptimizedDropAndCreateInDbUpdate>\n</featureToggles>  \nSee Template_UnattendedUpdate_Config.xml in the UnattendedUpdates scripts folder for an example  Note that it is active by default, also when the entry does not exist.",22356,""]
[null,null,1638158,"2025-03-26",null,"Development\\OWS7",null,null,null,"Unattended Updates mail would sometimes not contain the expected logfile as attachment","Unattended Updates mail would sometimes not contain the expected logfile as attachment due to a different logfile timestamp after the script has restarted itself after updating itself.\nThis has been improved.\n\nTest hint(s):  \n1.Verify that the mail send from Unattended Updates contains the expected attachment.","",28548,"https://synergy.ortec.com/synergy/docs/WflRequest.aspx?BCAction=1&ID=%7b67e94e97-2884-4971-bb99-bb16a9704a02%7d"]
[null,null,1638158,"2025-03-26",null,"Development\\OWS7",null,null,null,"Added option to UnattendedUpdates to copy standard stylesheets to additional locations","UnattendedUpdates would only roll out a styleSheets (libraries) update to the installation path but not to any location defined in the BaseStyleSheetPath\r\nThis has been improved.\r\nIt is now possible to add locations to the UnattendedUpdate_Config.xml to which to copy the contents of the updated libraries located in:\r\n<installPath>\\ORTEC\\Workforce Scheduling\\Server\\Interfaces\\Stylesheets\\Libraries\r\nThis path can be a local path, a network share or an UNC path.\r\nLocations can be configured by adding an extra XML structure below the <backendDomainsAPI> node in the UnattendedUpdate_Config.xml.\r\nSee Template_UnattendedUpdate_Config.xml for an example.\r\n<interfaces>\r\n  <environments>\r\n    <environment>\r\n      <name>EnvironmentName</name>\r\n      <stylesheets>\r\n        <librariesPath>D:\\non-default-folder\\ORTECDATA\\Interfaces\\Stylesheets</librariesPath>\r\n        <librariesPath>\\\\non-default-server\\d$\\UNCPath\\ORTECDATA\\Interfaces\\Stylesheets</librariesPath>\r\n        <librariesPath>\\\\non-default-server\\NetworkShare\\Stylesheets</librariesPath>\r\n      </stylesheets>\r\n    </environment>\r\n  </environments>\r\n</interfaces>\r\nNotes:\r\n- Multiple paths can be defined per environment.\r\n- When this configuration has been added, UnattendedUpdates will expect all environments to be configured and checks:\r\n  - All active environments in CSCS to be configured in UnattendedUpdate_Config.xml\r\n  - All environments configured in UnattendedUpdate_Config.xml to be available in the active environments in CSCS\r\n\r\nTest hint(s):\r\n1 Verify that when the UU configuration is extended with additional paths, the updated stylesheets are also copied to those paths during the UU process.","",29196,"https://ortec.link/Request?HID=16164662"]
[null,null,1638158,"2025-03-26",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - Treat CSCS as a manual update","Letting UnattendedUpdates process CSCS updates via the PatchUtilConsole could sometimes cause conflicts durng update.\r\nThis has been improved.\r\n CSCS updates will now be rolled out without the PatchUtilConsole to avoid conflicts.\r\n\r\nTest hint(s): \r\n1.Verify CSCS updates are rolled out","",30025,""]
[null,null,1638158,"2025-03-26",null,"Development\\OWS7",null,null,null,"Error handling improvements on BackendAPI installation","When an error occurred during the backup steps of the BackendAPI installation this would immediately stop the process.\r\nSubsequently, when restarting UnattenddUpdates in the same powershell session, the script could not clean the temporary files needed to install the BackendAPI and the script would stop.\r\nThis has been improved.\r\nA retry mechanism has been added to the BackendAPI backup steps in order to catch cases that might need some more time (for instance, folder/files being scanned).\r\nUnattendedUpdates will now correctly clean the temporary BackendAPI files to allow the script to finish the necessary update steps.\r\n\r\nTest hint(s): \r\n1.Verify that the BackendAPI can be installed/updated standalone or by means of UnattendedUpdates","",37382,"https://ortec.link/Request?HID=16633389"]
[null,null,1638158,"2025-03-26",null,"Development\\OWS7",null,null,null,"Unattended Updates would sometimes archive Update_xxxx_CVIS.zip under a temporary name","Unattended Updates would sometimes archive Update_xxxx_CVIS.zip under a temporary name.\r\nThis has been improved.\r\n\r\nTest hint(s):\r\n1 Verify that the Unattended Updated archive folder contains the expected files","",50249,"https://ortec.link/Request?HID=16771983"]
[null,null,1638158,"2025-03-26",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for showing the duty description and position in the shift details in OWSforTeamSchedulers","Technical preparation for showing the duty description and position in the shift details","",51045,""]
[null,null,1638158,"2025-03-26",null,"Development\\OWS7",null,null,null,"Unattended updates was not able to run custom scripts with boolean parameters in combination with the setting runInNewPowershell.","Unattended updates was not able to run custom scripts with boolean parameters in combination with the setting runInNewPowershell.\r\nThis has been fixed.\r\nA <customScript> node of an unattended updates config file can now be filled with the node <scriptArgs> instead of <scriptParams>.\r\nThe scriptArgs node can be filled with a string value all script argument like given to CJSS or a powershell console, which also includes switch parameters and boolean parameters with value $true or $false.\r\nThis work for runInNewPowershell on Y or on N.\r\nSee Template_UnattendedUpdate_Config.xml for an example.\r\nNote: It is not possible to provide both a  <scriptArgs> and a <scriptParams> node.\r\n\r\nTest hint(s):\r\n1. Verify that running a custom script during unattended updates with boolean parameters and setting runInNewPowershell on Y, when using the scriptArgs node\r\n2. Verify that running a custom script during unattended updates with switch parameters, when using the scriptArgs node","",53312,"https://ortec.link/Request?HID=16844605"]
[null,null,1638158,"2025-03-26",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for borrowing employees from proposal departments in OWSforTeamSchedulers","Technical preparation for the extension of the employee proposal functionality. Now, employees from proposal departments can be borrowed and assigned to a shift via the employee proposal.","",54812,""]
[null,null,1638158,"2025-03-26",null,"Development\\OWS7",null,null,null,"The planned hours shown in the workstation optimizer would sometimes include the already planned in hours of workstations without demand.","The planned hours shown in the workstation optimizer would sometimes include the already planned in hours of workstations without demand.\r\nThis has been improved.\r\nThe planned hours will now will now correctly show fullfilled demand after the run of the optimizer.\r\nThis issue was introduced in 8.5.0(2024-09-05)_Build1614627 : issue 37388 : \"(Required) workstation rules where not taken into account at shifts with already assigned workstation.\"\r\nThe changes related to that have issue now been put behind feature toggle WorkStationProfilePlannerApplyWorkstationRules which is enabled by default.\r\n\r\nTest hint(s):\r\n1. Verify that when running the workstation optimizer when workstations have already been pre-assigned to the shifts within the optimizer period, that the optimizer progress window only shows the actual hours planned during the current run of the optimizer.","",55645,"https://ortec.link/Request?HID=16899812"]
[null,null,1638158,"2025-03-26",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - Users on terminal servers could start Client again during update","While the Client on terminal servers are updated the time between Client shutdown and actual update take to long giving users the opportunity to start a Client again.\nThe Client being in use could cause the update to fail.\nThis has been improved.\nThe Client on terminal servers is now shutdown right before the update step, granting users less time to restart the Client.\n\nTest hint(s): \nNone","",55646,"https://ortec.link/Request?HID=16899851"]
[null,null,1639439,"2025-04-09",null,"Development\\OWS7",null,null,null,"Two new queue filters 'AccountCategoryLineEmployeePropertyQueueFilter' and 'AccountCategoryLineTypeQueueFilter' have been added.","Two new queue filters 'AccountCategoryLineEmployeePropertyQueueFilter' and 'AccountCategoryLineTypeQueueFilter' have been added. \nThese filters works on creation, changes and deletes of account category lines. \n\nThe EmployeePropertyQueueFilter allows exports of bookings for employees \nhaving a Yes value for a configured employee property valid on the date of the booking. \nThe TypeQueuefilters allows exports for the given AccountCategoryLine types.\n\nTo configure, add the following filters to a account category line queue export definition:\n<AccountCategoryLineEmployeePropertyQueueFilter employeePropertyNames=\"booleanEmplProp1,booleanEmplProp2\"/>\nThe configured properties must be an employee property and of the type Yes/No.\nMultiple employee properties can be defined (separated by a comma).\n<AccountCategoryLineTypeQueueFilter relevantTypes=\"acltBudget,acltCorrection\"/>\nThe configured types can be \"acltBudget\", \"acltCorrection\" and \"AcltInterface\".\nMultiple types can be defined (separated by a comma).\n\nTest hint(s):\n1. Verify the queue export filters on mentioned conditions","","54405",""]
[null,null,1639439,"2025-04-09",null,"Development\\OWS7",null,null,null,"FieldCollector did not add TUserProperty to export file when collecting on 'UPY_ID' with feature toggle FilterOnCollectedClassInFieldCollector","An XML export definition using a FieldCollector collecting on 'UPY_ID' did not add TUserProperty to export file with feature toggle FilterOnCollectedClassInFieldCollector on Y.\r\nThis has been fixed.\r\nWe recommend setting the feature toggle back to Y if you were previously advised to turn it off.\r\nThis was introduced in issue \r\n49038: \"A FieldCollector would not filter on the collected class when exporting a queue.\", which was delivered in OWS 7 update 1635163 (2025-02-25).\r\n\r\nTest hint(s):\r\n1. Verify that a TUserProperty is included in an export when using the appropriate field collector and updating a user property value.","","55711","https://ortec.link/Request?HID=16902293"]
[null,null,1639439,"2025-04-09",null,"Development\\OWS7",null,null,null,"Self scheduling in own department was not possible when person was lent out to another department","Self scheduling in own department was not possible when person was lent out to another department.\r\nThis has been improved.\r\nA new setting SELFROSTERING\\EXCLUDELENDINGPERIODSFROMSELFSCHEDULING has been introduced which is default disabled.\r\nWith the setting disabled an employee is able to pick shifts from his own department for the period he is lent out to another department.\r\nEnable the setting to revert to current behavior.","","55926",""]
[null,null,1639439,"2025-04-09",null,"Development\\OWS7",null,null,null,"BackendEventPublisher retried sending pending events even when receiving party responded with 'Unprocessable Enity' (422) code","BackendEventPublisher retried sending  pending events even when receiving party responded with 'Unprocessable Enity' (422) code\nThis could block handling the pending events until the 'unprocessable' event was removed from the database.\nThis has been improved.\nWhen a 'Unprocessable Enity' (422) is returned to the BackendEventPublisher for a pending event the event is dropped and removed from the pending events.\n\nTest hint(s):\n1. Verify that ShiftOfferening configured using the BackendEventPublisher processes opening shifts for bidding from OWS Win32 Client","","56181",""]
[null,null,1640539,"2025-04-23",null,"Development\\OWSforTeamSchedulers",null,null,null,"Improved permission checks for showing the details of a shift in ORTEC WS for Team Schedulers","In ORTEC WS for Team Schedulers, authenticated users that were authorized for at least one department, were able to use a workaround to see shift details from departments that they were not authorized for.\nThis has been disabled.","",51246,""]
[null,null,1640539,"2025-04-23",null,"Development\\OWSforTeamSchedulers",null,null,null,"Improved performance of loading the vacant shifts in ORTEC WS for Team Schedulers","Improved performance of loading the vacant shifts in ORTEC WS for Team Schedulers.","",56049,"https://ortec.link/Request?HID=16909612"]
[null,null,1640539,"2025-04-23",null,"Development\\OWS7",null,null,null,"Added a new Access Control permission 'ESS Assistant'","Added a new Access Control permission 'ESS Assistant' (workspace.ess.assistant) in preparation for an upcoming ESS7 change. \nThis has been made available in category: ORTEC WS for Employees/Assistant\n\nTest hint(s):\n1. Verify that a new permission with caption 'ESS Assistant' is available in the 'ORTEC WS for Employees/Assistant' subfolder of Access Control","",56357,""]
[null,null,1640539,"2025-04-23",null,"Development\\OWSforTeamSchedulers",null,null,null,"The employee proposal column for skills in ORTEC WS for Team Schedulers did not always show the correct information when using proposal departments","The employee proposal column for skills in ORTEC WS for Team Schedulers did not always show the correct information when using proposal departments.\r\nThis has been fixed.","",56582,"https://ortec.link/Request?HID=16924643"]
[null,null,1640539,"2025-04-23",null,"Development\\OWS7",null,null,null,"Adding additional information to the interface message could lead to an access violation during import of a LeaveWish when combined with extraXmlCreator TRemoveLeaveWish.","Adding additional information to the interface message could lead to an access violation during import of a LeaveWish when combined with extraXmlCreator TRemoveLeaveWish.\nThis has been resolved.\n\nThis bug was introduced in release 8.5.0(2025-02-25)_Build1635163 with featuretoggle ExtendInterfaceMessagesWithAdditionalInfo Enabled.","",57579,"https://ortec.link/Request?HID=16929311"]
[null,null,1641582,"2025-05-06",null,"Development\\OWS7",null,null,null,"Added logging table for shift bidding events","Added logging about shift bidding/offering actions. \nThe actions are logged to the table ROS_SHIFTBIDDING_LOG. \n\nThe following information is stored when the openForBidding value of a shift is changed: \nThe shifts id, the shifts name, department and employee at time of the action. \nThe application the action originated from and the actions date. \nThe following event types are distinguished: \n- OpenedForBidding \n- WithdrawnFromBidding \n- AssignedToEmployeeWithRequest (employee has entered a request for the offered shift) \n- AssignedToEmployeeWithoutRequest (no duty request or generic (recurring) duty request)\n\nThis functionality is dependent of the server setting Bidding/ShiftBidding/LogShiftBiddingEvents, which is disabled by default. \n\nLog records older than a configured number of days are cleaned daily. \nThis can be configured with the server setting Bidding/ShiftBidding/NofDaysToRetainShiftBiddingLog (default 90, min: 1, max: 1000)\n\nTest hint(s): \n1. Verify that actions that change the openForBidding value of a shift are logged to the ROS_SHIFTBIDDING_LOG table. \n2. Verify that log records are cleaned when they are older than a configured number of days.","",57486,""]
[null,null,1641582,"2025-05-06",null,"Development\\OWSforTeamSchedulers",null,null,null,"Approving employee realizations was not possible when forbidden violations were configured in ORTEC WS for Team Schedulers","Approving employee realizations was not possible when forbidden violations were configured in ORTEC WS for Team Schedulers. \r\nThis has been fixed.","",57487,""]
[null,null,1641582,"2025-05-06",null,"Development\\OWSforTeamSchedulers",null,null,null,"When replacing a night shift with a sick leave shift, this would sometimes be impossible in ORTEC WS for Team Schedulers","When replacing a night shift with a sick leave shift, this would sometimes be impossible in ORTEC WS for Team Schedulers. \r\nThis has been fixed.","",57846,""]
[null,null,1641582,"2025-05-06",null,"Development\\OWS7",null,null,null,"A warning was raised on CWSS Startup when feature toggle HANDLEUPDATESFOROWSUITEININTEGRATIONSERVERUPDATEHANDLER is enabled and WorkForceSuiteServiceUrl is empty","A warning was raised on CWSS Startup when feature toggle HANDLEUPDATESFOROWSUITEININTEGRATIONSERVERUPDATEHANDLER is enabled and WorkForceSuiteServiceUrl is empty\nThis has been improved. \nFeature toggle HANDLEUPDATESFOROWSUITEININTEGRATIONSERVERUPDATEHANDLER is now default disabled.","",59620,""]
[null,null,1643385,"2025-05-21",null,"Development\\OWS7",null,null,null,"NoTreatmentInPeriodReq could sometimes cause incorrect violations","NoTreatmentInPeriodReq (\"No kind in period\") could sometimes cause incorrect violations when an allowed series of shifts with the forbidden treatment was ended with a shift without the forbidden treatments.\r\nThis has been fixed.\r\nThis change is activated behind feature toggle OnlyCheckShiftsWithForbiddenTreatmentInNoTreatmentInPeriodReq which is enabled by default\r\n\r\nTest hint(s):\r\n1. Verify that correct violations are created for this rule for shift series consisting of a mix of shifts with and without the forbidden treatment.","",51145,"https://ortec.link/Request?HID=16792219"]
[null,null,1643385,"2025-05-21",null,"Development\\OWS7",null,null,null,"A single activity shift rearrangement in the workstation planboard would not lead to schedule change in ESS Workflow.","A single activity shift rearrangement in the workstation planboard would not lead to schedule change in ESS Workflow.\r\nThis has been fixed.\r\nThe change is available behind feature toggle CreateExchangeOnChangingShiftResourceInWorkstationPlanboard which is enabled by default.\r\n\r\nTest hint(s):\r\n1. Verify that the ESS workflow shows a schedule change, after a single activity shift has been moved to/from the employee using the workstation planboard.","",53514,"https://ortec.link/Request?HID=16847981"]
[null,null,1643385,"2025-05-21",null,"Development\\OWSforTeamSchedulers",null,null,null,"The sick leave percentage value did not support setting UseIllnessAvailabilitiesExtended in ORTEC WS for Team Schedulers","The sick leave percentage value did not support setting UseIllnessAvailabilitiesExtended in ORTEC WS for Team Schedulers.\r\nThis has been improved.","",54964,""]
[null,null,1643385,"2025-05-21",null,"Development\\OWS7",null,null,null,"When assigning an already assigned user to an employee the French translation showed an incomplete warning message.","When assigning an already assigned user to an employee the French translation showed an incomplete warning message.\r\nThis has been improved.\r\n\r\nTest hint(s):\r\nNone","",55788,"https://ortec.link/Request?HID=16903126"]
[null,null,1643385,"2025-05-21",null,"Development\\OWS7",null,null,null,"Opening an account could be slow when using the Finnish language.","Opening an account could be slow when using the Finnish language.\r\nThis has been improved\r\nWith this change comes a feature toggle SetDepartmentAfterSettingIntervalForEmployeeFiltering_OldBehaviour set to N by default. Setting this feature toggle to Y disables the new functionality.\r\n\r\nTest hint(s):\r\n1. Verify that it is possible (and faster) to open an account while having the Finnish language selected.","For this solution to become available, the ORTEC WS Win32 client must be installed.",55971,"https://ortec.link/Request?HID=16908697"]
[null,null,1643385,"2025-05-21",null,"Development\\OWS7",null,null,null,"Calculating travel distance for bookings could raise the memory usage","Calculating travel distance for bookings could raise the memory usage\nThis could happen when calculating bookings on running accounts that involved travel distance based on distances calculated using the cloud map service.\nWhen doing such calculations in i.e. a BI export a significant rise of memory usage was found.\nThis has been improved.\nThe probable cause of this rise in memory usage was eliminated.\n\nTest hint(s): \nNone","",71404,"https://ortec.link/Request?HID=16937695"]
[null,null,1643385,"2025-05-21",null,"Development\\OWSforTeamSchedulers",null,null,null,"Improved performance of getting shift data in ORTEC for Team Schedulers","Improved performance of getting shift data in ORTEC for Team Schedulers.","",72040,""]
[null,null,1643385,"2025-05-21",null,"Development\\OWS7",null,null,null,"Exporting a cyclic schedule with realisation duties showed (temporary) internal ID's in the output","Exporting cyclic schedule with realisation duties showed (temporary) internal ID's in the output.     This has been improved. The exported duty-Id's will now always be the actual duty-Id's, also in case of a realisation. This change is behind feature toggle PreserveOriginalDutyIdsOnExportCyclicShifts which is enabled by default. This change is also dependent on feature toggle CopyDutiesAsInternalObjectForInternalShifts being enabled.\n\nTest hint(s):\nNone","",72099,""]
[null,null,1643385,"2025-05-21",null,"Development\\OWSforTeamSchedulers",null,null,null,"The balance column in the employee proposal in ORTEC for Team Schedulers always showed '0'","The balance column in the employee proposal in ORTEC for Team Schedulers showed always '0'.\r\nThis has been fixed.","",72470,""]
[null,null,1644701,"2025-06-02",null,null,null,null,null,"Updated OWS 7 binaries","OWS 7 binaries are built using Delphi 11.1.5\n\nTest hints: \n1. Verify CMHS Networks function as expected (if applicable) \n2. Verify configured reports can be opened in OWS win32 client (if applicable)","For this update to become available, it is highly recommended to install the OWS Win32 client. \n\n\nDue to the Delphi upgrade all binary files have been updated.\nIt is highly recommended to use the OWS Client installer to:\n- Update the Client distribution packages (e.g. for Citrix)\n- Update the Client on a Terminal Server\n- Update the Client on FAT Clients\nIt is recommended to use UnattendedUpdates for the upgrade. Else use the separate PatchConfiguration application instead of the full CSCS.","46585",""]
[null,null,1644701,"2025-06-02",null,null,null,null,null,"System reports Attendance List Per Department and Overview shifts did not show the correct default activity types.","System reports Attendance List Per Department and Overview shifts did not show the correct default activity types.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\n1 Verify that activitytypes 'Amplitude', 'Availability (no labor)', 'Education', 'On Call', 'On Call (no labor)', 'Operational','Overtime',  'Overtime (for free time)', 'Overtime (for money)', 'Picket', 'Presence', 'Spare', 'Training', 'Unpaid work', 'Work', 'Work (stand by)' and 'Break' are checked by default in system reports Attendance List Per Department & Overview shifts","","50669","https://ortec.link/Request?HID=16778976"]
[null,null,1644701,"2025-06-02",null,null,null,null,null,"Numeric duty properties with a negative decimal value where not calculated correctly in a vertical counter.","Numeric duty properties with a negative value where not calculated correctly in a vertical counter.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\n1. Verify that a vertical counter on numeric duty property with negative decimal values now shows the correct value.","","51266","https://ortec.link/Request?HID=16795205"]
[null,null,1644701,"2025-06-02",null,null,null,null,null,"Improved stability of queries in the OrtecRelevancePushNotificationSender","Improved the stability of queries related to reading the employee ID in the route used by shift change notifications.\r\n\r\nTest hint(s):\r\n1. Verify that shift change notifications are sent","","51806",""]
[null,null,1644701,"2025-06-02",null,null,null,null,null,"Several translations changed for German.","Several translations changed for German.\r\n\r\nTest hint(s):\r\nNone","","51985","https://ortec.link/Request?HID=16815444"]
[null,null,1644701,"2025-06-02",null,null,null,null,null,"The cost center picker in the replace duty windows would not show new cost centers after updating the validity period of the duty.","The cost center picker in the replace duty windows would not show new cost centers after updating the validity period of the duty.\nThis has been fixed.\nWith this change comes a feature toggle UpdateActivityTabsOnUpdateReplaceFromDate_OldBehaviour set to N by default. Setting this feature toggle to Y disables the new functionality.\n\nTest hint(s):\n1. Verify that the cost center picker shows the correct cost centers after updating the from date in the replace duty window.","For this solution to become available, the ORTEC WS Win32 client must be installed.","53147","https://ortec.link/Request?HID=16839704"]
[null,null,1644701,"2025-06-02",null,null,null,null,null,"Interfaceworker waited on BackendEventPublisher to handle an open event","When sending calls to the BackendEventPublisher, the source was waiting for a response by the BackendEventPublisher send after it had processed all open events.\r\nThis has been improved.\r\nThe BackendEventPublisher now sends a response immediately after the call has been stored in the database table. The events are processed on a dedicated thread.\r\nAdditionally, the BackendEventPublisher will now automatically check if it has any events to process every 5 minutes.\r\nThis change is avaiable behind a new feature toggle PROCESSEVENTSONSINGLETHREAD which in enabled by  default.\r\n\r\nTest hints(s).\r\n1. Verify that event send from the BackendEventPublisher are received by their destined application.","","55536",""]
[null,null,1644701,"2025-06-02",null,null,null,null,null,"The optimizer could crash with an InvalidPointer error","The optimizer could crash with an InvalidPointer error\r\n\r\nThis issue was found during internal testing\r\nThis has been improved. \r\n\r\n\r\nThe changes have been put behind feature toggle PROTECTPLANNERPROGRESSSTRINGS which is enabled by default.\r\n\r\nTest hint(s): \r\n1. Verify that the optimizer (internal and external) finishes correctly.","","56252",""]
[null,null,1645673,"2025-06-17",null,"Development\\OWS7",null,null,null,"Importing a user property for a class (other than employee) returned an error when employee property with same name existed.","Importing a user property for a class (other than employee) returned an error when employee property with same name existed.\r\nThis has been improved.\r\nThis change is behind feature toggle ImportUserPropertyValueBasedOnDescriptionClass which is enabled by default.\r\n\r\nTest hint(s):\r\n1.  Verify that the import does not fail when trying to import a class (other than employee) with a userproperty that has the same name as an existing employee property.","",50045,"https://ortec.link/Request?HID=16769082"]
[null,null,1645673,"2025-06-17",null,"Development\\OWS7",null,null,null,"A realisation on an ex-instructor shift was not properly synced to the assigned student shift when re-enabling the instructor shift.","A realisation on an ex-instructor shift was not properly synced to the assigned student shift when re-enabling the instructor shift.\nThis has been improved.\nThis change is behind feature toggle ImproveSyncInstructorShiftRealisationWithStudentShift, which is enabled by default.\n\nTest hint(s):\n1. Verify that a realisation on an ex-instructor shift with an assigned student shift is also reflected in the student shift after re-enabling the instructor shift.","",51267,"https://ortec.link/Request?HID=16795211"]
[null,null,1645673,"2025-06-17",null,"Development\\OWS7",null,null,null,"Rolling out illness shifts for an employee that changes department partway through an illness could result in an error.","Rolling out illness shifts for an employee that changes department partway through an illness could result in an error.\r\nThis happened because the shifts were rolled out to the department an employee was not available for anymore.\r\nThis has been fixed.\r\nThe shifts are now rolled out for the main department of the employee.\r\nThis change is behind feature toggle SplitIllnessProcessIntervalOverMainDepartments which is enabled by default.\r\n\r\nTest hint(s):\r\n1. Verify that illness shifts can be rolled out for employees who change department partway through the \"rollout illness shifts\"-period.","",51520,"https://ortec.link/Request?HID=16799272"]
[null,null,1645673,"2025-06-17",null,"Development\\OWS7",null,null,null,"Improved error handling of UnattendedUpdates when logfile is not set","On handling an exception, UnattendedUpdates could raise another error when the logfile was not set or not yet set.\r\nThis caused the original exception message to be overwritten.\r\nThis has been improved.\r\n\r\nTest hint(s):\r\n1. Verify UnattendedUpdates updates OWS as expected.","",53400,"https://ortec.link/Request?HID=16846045"]
[null,null,1645673,"2025-06-17",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical preparation for being able to drag & drop shifts horizontally / diagonally in OWSforTeamSchedulers","Technical preparation for being able to drag & drop shifts horizontally / diagonally in OWSforTeamSchedulers","",56223,""]
[null,null,1645673,"2025-06-17",null,"Development\\OWS7",null,null,null,"Performing a shift offer action from the AdHoc planner could lead to duplicate notifications in ESS","Performing a shift offer action from the AdHoc planner could lead to duplicate notifications in ESS\r\nThis has been fixed\r\nAdditionally, information is logged on which server-side notifications types are enabled.\r\nThe interface worker responsible for notification will now log  on startup which server-side notification types are disabled and why.\r\nPlease note that the settings only determine if notification are send from the OWS Server. Notifications from shift offering are always send while the OrtecRelevancePushNotificationSender is active.\r\n\r\nTest hint(s):\r\nNone","",72372,"https://ortec.link/Request?HID=16949474"]
[null,null,1646912,"2025-07-01",null,"Development\\OWS7",null,null,null,"Monitoring query CountDepartmentsNotApprovedRecently could give false positives but also leave out relevant records.","Monitoring query CountDepartmentsNotApprovedRecently could give false positives but also leave out relevant records.\nThis has been improved.\nThe query will now return a count of departments of which: \n- There are schedules \n- The first schedules end date is at least 50 days old\n- The departments approved date is at least 50 days old\n- The department is not fully approved (approved date is not equal to the last schedules end date)\n\nTest hint(s):\n1. Verify that the records returned by the monitoring query CountDepartmentsNotApprovedRecently match the above criteria.","",33650,"https://ortec.link/Request?HID=16586432","Closed"]
[null,null,1646912,"2025-07-01",null,"Development\\OWS7",null,null,null,"A series subcontract with multiple shifts could be deleted when one of its shift was deleted.","When the latter shift in a series subcontract gets removed by shortening the schedule, the subcontract was removed leaving the first shift in the series subcontracted but without a subcontract. This raised a shift container error.\nThis has been fixed.\nA series subcontract is no longer deleted when shortening a schedule and the subcontract is still used by other shifts.\n\nAdded feature toggle FeatureToggles\\RemoveShiftFromSeriesSubContractWithoutDeletingSubContract which is enabled by default.\n\nTest hint(s): \n1. Verify that shortening a schedule containing a series of subcontracted shifts across the new end date succeeds \n2. Verify that finalizing a trial scenario on a schedule containing a series of subcontracted shifts succeeds.\n3. Verify the shifts remaining in that subcontract series can be (un)planned.","",48785,"https://ortec.link/Request?HID=16737515"]
[null,null,1646912,"2025-07-01",null,"Development\\OWS7",null,null,null,"When an access violation in a planboard occurred it was not always closed.","When an access violation in a planboard occurred it was not always closed.\nThis has been improved. When an access violation occurs the planboard is marked as defective and closed.\n\nTest hints(s): None","",50944,""]
[null,null,1646912,"2025-07-01",null,"Development\\OWS7",null,null,null,"Approved account entries are not always automatically recalculated after adjusting a correction date.","After adjusting the date of a correction on a running account, approved account entries were not automatically recalculated.\nThis has been fixed.\n\nAdded feature toggle FeatureToggles\\RecalculateBookingsOnCorrectionDateChange_OldBehaviour set to N by default. Setting this feature toggle to Y disables the new functionality.\n\nTest hint(s):\n1. Verify that saved account entries are recalculated for a relevant period when the date of a correction has been changed.","For this solution to become available, the ORTEC WS Win32 client must be installed.",51153,"https://ortec.link/Request?HID=16792384"]
[null,null,1646912,"2025-07-01",null,"Development\\OWS7",null,null,null,"Not possible to unmark shifts of employee calculations when marking was saved on previous version.","In OWS7 update 1611779 (2024-08-14) a fix was applied to prevent the saving of marked shifts for employee calculations.\nThis had the side effect of not being possible to unmark shifts for employee calculations when they were saved on a previous version.\nThis has been fixed.\nAny stored marked shifts for employee calculations are removed by the DBUpdate.\n\nTest hint(s):\n1. Verify that shifts can be marked and unmarked for calculation\n2. Verify this cannot be stored and marking is reset on reopening or refreshing the planboard","",52501,"https://ortec.link/Request?HID=16825384"]
[null,null,1646912,"2025-07-01",null,"Development\\OWS7",null,null,null,"If the main CWSS Server process did not properly handle an abort during an update, it could result in a verify state failed error, necessitating a process restart.","If the main CWSS Server process did not properly handle an abort during an update, it could result in a verify state failed error, necessitating a process restart.\nThe verify failed state showed that expected version in memory was not in sync with other worker(s) which could only be resolved by a process restart.\nThis has been improved.\n\nAdded feature toggle FeatureToggles/ImproveTriggerConsistencyChecksAfterHandleUpdateInTransaction, which is enabled by default.\n\nTest hints(s): None","",72153,"https://ortec.link/Request?HID=16946089"]
[null,null,1646912,"2025-07-01",null,"Development\\OWS7",null,null,null,"When an error occurred during an overtime calculation when using 'Overtime: calculated from cyclical schedule' definition a memory leak could occur.","When an error occurred during an overtime calculation when using 'Overtime: calculated from cyclical schedule' definition a memory leak could occur.\nThis has been fixed.\n\nTest hint(s):\n1. Verify when using 'Overtime: calculated from cyclical schedule' definition bookings are as expected.","",80611,"https://ortec.link/Request?HID=16973535"]
[null,null,1650946,"2025-07-15",null,"Development\\OWS7",null,null,null,"It is now possible to disable horizontal calculations in a planboard for employees with an active self-scheduling round.","It is now possible to disable horizontal calculations in a planboard for employees with an active self-scheduling round.\nTo increase performance during self-scheduling, an option was added to disable the employee calculations for employees that have an active self-scheduling round. Upon opening or refreshing a planbord, such an employee will have a '?' in their horizontal calculations instead of the calculated value. It is still possible to manually request a calculated value with the right mouse button.\nAdded a setting SELFROSTERING\\SKIPHORIZONTALCALCULATIONSINROUNDS, which can contain a comma separated list of scheduling rounds to disable the calculations in those specifics rounds only. By default this list is empty, and the horizontal calculations will not be disabled in any round.\nPossible valid values for this new setting are Round1, Round2 or Round3 or any combination of those in a comma separated list, or leave empty (=default value) so the horizontal calculations will not be disabled in any round.\nThis functionality is added behind a feature toggle ENABLESKIPHORIZONTALCALCULATIONSINROUNDS which in enabled by default\n\nTest hint(s):\n1. Verify that horizontal calculcation are disabled when opening a planboard with employees that have an active self-scheduling round.","For this solution to become available, the ORTEC WS Win32 client must be installed.",79878,""]
[null,null,1650946,"2025-07-15",null,"Development\\OWSforTeamSchedulers",null,null,null,"When logging into OWS for Team Schedulers, the event viewer showed some warnings.","When logging into OWS for Team Schedulers, the event viewer showed some warnings.\r\nThis has been fixed.","","80465","https://ortec.link/Request?HID=16968766"]
[null,null,1650946,"2025-07-15",null,"Development\\OWS7",null,null,null,"Added option to use snapshot transaction isolation level for handling of updates.","Added the option to change the transaction isolation level to snapshot in the UpdateHandlers to reduce database locking. Note the QueueUpdateHandler already uses snapshot isolation level. \nAdded feature toggle Server setting: FeatureToggles\\UseSnapshotIsolationForHandlingUpdates which is disabled by default. \nAdded feature toggle Server setting: FeatureToggles\\UseSnapshotIsolationForHandlingAsyncUpdates which is disabled by default.\nAdded feature toggle Server setting: FeatureToggles\\UseSnapshotIsolationForHandlingSkillMatchingUpdates which is disabled by default.\n\nThis functionality also needs the server setting StartSnapshotTransaction_WaitForDtcCommits to be disabled, otherwise the feature toggles will be disabled. StartSnapshotTransaction_WaitForDtcCommits is automatically disabled for customers using at least SQL Server 2022. \n NOTE: only an ORTEC consultant is allowed to change these settings in agreement with the Maintenance department.\n\nTest hint(s): None","Contact Casper to pick customer(s) for controlled release","80810",""]
[null,null,1653626,"2025-07-30",null,"Development\\OWSforAdHocPlanners",null,null,null,"The employee proposal functionality in ORTEC WS Ad Hoc Planner was sometimes slow.","The employee proposal functionality in ORTEC WS Ad Hoc Planner was sometimes slow.\r\nThis has been improved.","","32970","16.898.593"]
[null,null,1653626,"2025-07-30",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to support managing employee skills and employee properties in ORTEC WS for Team Schedulers.","Technical change to support managing employee skills and employee properties in ORTEC WS for Team Schedulers.","","55871",""]
[null,null,1653626,"2025-07-30",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical changes to support manual override on sick leave replacement type in ORTEC WS for Team Schedulers.","Technical changes to support manual override on sick leave replacement type in ORTEC WS for Team Schedulers.","","80813",""]
[null,null,1653626,"2025-07-30",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical changes for integration of Team Scheduling with Shift Offering.","Technical changes for integration of Team Scheduling with Shift Offering.","","80933",""]
[null,null,1653626,"2025-07-30",null,"Development\\OWS7",null,null,null,"BackendEventPublisher could throw an exception \" url must be non-empty string\" in case the url setting contained only whitespaces.","BackendEventPublisher could throw an exception \" url must be non-empty string\" in case the url setting contained only whitespaces.\nThis has been improved.\n\nTest hint(s):\nNone.","","83777",""]
[null,null,1653626,"2025-07-30",null,"Development\\OWS7",null,null,null,"The shiftbidding log table contained the userid of the requesting process instead of the actual user.","The shiftbidding log table contained the userid of the requesting process instead of the actual user.\r\nThis has been improved.\r\n\r\nTest hint(s):\r\n1. Verify that opening a shift for offering in teamscheduler now shows the userid of the actual user in the shiftbidding log table.","","84100",""]
[null,null,1653626,"2025-07-30",null,"Development\\OWSforTeamSchedulers",null,null,null,"The configuration check on period replacement type for sicknesses sometimes resulted in errors when it should not in ORTEC WS for Team Schedulers.","The configuration check on period replacement type for sicknesses sometimes resulted in errors when it should not in ORTEC WS for Team Schedulers.\r\nThis has been improved.\r\nIt now only checks the period replacement type for sicknesses when setting UseTwoReplaceTypesForIllnessType is true.","","84269",""]
[null,null,1658364,"2025-08-26",null,"Development\\OWS7",null,null,null,"Exporting data through an export can halt a worker when feature toggle ImproveLockingDescriptionsWhileExporting is enabled","In update OWS7 - 8.5.0(2024-06-27)_Build1605853 a change was made in the locking mechanism when exporting data through an export (issue 31040).\nInstead of locking all employees it now only locked the data in the export itself. This change was done behind feature toggle ImproveLockingDescriptionsWhileExporting, which was enabled by default. However, for some customers this caused issues (issue 49612 and 50933) in which export workers could halt. For these customers it was advised to turn of the ImproveLockingDescriptionsWhileExporting feature toggle. \nWe have now revisited the original change and improved it. The way entities are locked during exports has been changed. This achieves the same goal as we intended to in the original change, which is locking less irrelevant data.  Feature toggle ImproveLockingDescriptionsWhileExporting is now re-enabled by default. In addition, for the latest change a new (dependent) toggle FilterDescriptionsToLockInExport is introduced, which is also enabled by default.\n\nTest hint(s):\n1. Verify queue exports work as expected","",53389,""]
[null,null,1658364,"2025-08-26",null,"Development\\OWS7",null,null,null,"Added new ESS7 permission for requesting a partial day of leave","Added access control permission /CWGS/OWS/ESS/PartDayLeaveWishCreateAction in preparation for an ESS change.  This new permission in automatically granted if the usergroup already has the permission /CWGS/OWS/ESS/LeaveWishCreateAction\r\n\r\nTest hint(s): None","",83808,""]
[null,null,1658364,"2025-08-26",null,"Development\\OWSforTeamSchedulers",null,null,null,"The employee proposal column for account balance in ORTEC WS for Team Schedulers did not always show the correct information when using proposal departments","The employee proposal column for account balance in ORTEC WS for Team \r\nSchedulers did not always show the correct information when using \r\nproposal departments.\r\nThis has been fixed.","",84571,"https://ortec.link/Request?HID=17007894"]
[null,null,1662311,"2025-09-09",null,"Development\\OWS7",null,null,null,"Feature toggle ImproveLockingForWishMessages has been removed.","Feature toggle ImproveLockingForWishMessages has been removed.\nThis feature toggle was introduced in update 1561992 (2023-08-30).\n\nTest hint(s): \nNone","",14248,""]
[null,null,1662311,"2025-09-09",null,"Development\\OWS7",null,null,null,"Feature toggle IncludeCheckIntervalForViolationCalculationInResourceViolationsXmlCreator has been removed.","Feature toggle IncludeCheckIntervalForViolationCalculationInResourceViolationsXmlCreator has been removed.\nThis feature toggle was introduced in update 1567656 (2023-10-12).\n\nTest hint(s): \nNone","",18493,""]
[null,null,1662311,"2025-09-09",null,"Development\\OWS7",null,null,null,"Feature toggle CriticalSectionLockTryEnter has been removed.","Feature toggle CriticalSectionLockTryEnter has been removed.\r\nThis feature toggle was introduced in update 1550417 (2023-06-08).\r\n\r\nTest hint(s): \r\nNone","For this solution to become available, the ORTEC WS Win32 client must be installed. ",27338,""]
[null,null,1662311,"2025-09-09",null,"Development\\OWS7",null,null,null,"Feature toggle DetermineWhenToFillInterfaceOutput has been removed.","Feature toggle DetermineWhenToFillInterfaceOutput has been removed.\nThis feature toggle was introduced in update 1057488 (2018-02-15).\n\nTest hint(s): \nNone","",3052,""]
[null,null,1662311,"2025-09-09",null,"Development\\OWS7",null,null,null,"BackendDomains pagination requests could fail when proxy returns a different host from the original request","Paginated requests from the BackendDomainsApi could fail when i.e. a proxy returns a different host than the original request. In such cases an incorrect url is formed stopping the paginated action.\nThis has been improved.\nWhen facing such failing paginated request, it is possible to configure the correct url for the BackendDomainsApi\nIn CSCS Setting Workforce.BackendDomainApis\\URLs\\BackendDomainApisUrl \nNote to use the full url including https://\nWhen the setting is left empty, the default method of generating the paginated url's is used.\n\nTest hint(s): None","",72752,""]
[null,null,1662311,"2025-09-09",null,"Development\\OWS7",null,null,null,"Queue Export with ShiftPendingUpdatesByShift/DutyCollector could cause an error when used in combination with AddBeforeStates.","A queue export with ShiftPendingUpdatesByShift/DutyCollector could cause an error when used in combination with AddBeforeStates.\nThis has been fixed.\nIf the before state of an exported data object cannot be found, the export will continue without that before state, but will still produce a warning in the logging.\nThis was done behind feature toggle AllowExportWithOptionalBeforeStates which was enabled by default.\n\nTest hint(s):\n1. Run a queue export with a ShiftPendingUpdatesByShift or ShiftPendingUpdatesByDuty collector and the setting AddBeforeStates on Y. Verify that the export succeeds when changing the status of a shift with an approved pending update.","",80342,"https://ortec.link/Request?HID=16967128"]
[null,null,1662311,"2025-09-09",null,"Development\\OWS7",null,null,null,"Feature toggle ImproveLockingSelfSchedulingCommands has been removed.","Feature toggle ImproveLockingSelfSchedulingCommands has been removed.\r\nThis feature toggle was introduced in update 1607763 (2024-07-11).\r\n\r\nTest hint(s): None","",83666,""]
[null,null,1662311,"2025-09-09",null,"Development\\OWSforTeamSchedulers",null,null,null,"The number of schedules in the past or future was not always correct in ORTEC WS for Team Schedulers","The number of schedules shown in the past or future was not correct in ORTEC WS for Team Schedulers in case proposal departments were configured on parent departments.\r\nThis has been fixed.","",84580,"https://ortec.link/Request?HID=17008139"]
[null,null,1662311,"2025-09-09",null,"Development\\OWSforTeamSchedulers",null,null,null,"The add shifts functionality sometimes resulted in errors","The add shifts functionality sometimes resulted in errors. \r\nThis has been improved.","",85106,""]
[null,null,1662311,"2025-09-09",null,"Development\\OWSforTeamSchedulers",null,null,null,"The daily and weekly staffing could not always be retrieved in ORTEC WS for Team Schedulers","The daily and weekly staffing could not always be retrieved in ORTEC WS for Team Schedulers, specifically when a large amount of duties was involved.\r\nThis has been improved.","",85326,"https://ortec.link/Request?HID=17018884"]
[null,null,1662311,"2025-09-09",null,"Development\\OWSforTeamSchedulers",null,null,null,"Adding special shifts resulted in logging error","Adding special shifts resulted in an unnecessary BDA logging error. \nThis has been fixed.","",85349,""]
[null,null,1662311,"2025-09-09",null,"Development\\OWS7",null,null,null,"Missing calculated account entry values when feature toggle ImproveLockingDescriptionsWhileExporting was enabled","In version 1658364 (2025-08-26) we introduced a change that improves the locking mechanism while exporting. This change was behind feature toggle FilterDescriptionsToLockInExport, which was enabled by default. Unfortunately, this change caused issues with missing calculated account entry values when exporting.\nWe subsequently revoked this  version and advised to turn the feature toggle off if this version was used anyhow.\n\nWe have now fixed the issue. The feature toggle FilterDescriptionsToLockInExport is now disabled by default, but can be enabled on individual basis.","",87899,""]
[null,null,1662311,"2025-09-09",null,"Development\\OWS7",null,null,null,"ESS did not show shifts to accept in past.","The \"Accept shifts in ESS\" functionality did not show a user shifts to accept in the past.\r\nThis has been improved.\r\nNow all shifts in status published are shown to accept if the corresponding open status property is true.\r\n\r\nTest hint(s):\r\n1. Verify that when the ESS user opens a past schedule containing shifts with accept status Open, that these shifts are shown and can be accepted.","",88356,""]
[null,null,1665354,"2025-09-23",null,"Development\\OWS7",null,null,null,"View HMY_BISettings returned multiple rows after update","The view HMY_BISettings in the OWS database returned multiple rows after TeamScheduling settings were added to CSCS with the same name as a CBIS setting.\r\nThis led to an error in the BI run.\r\nThis has been fixed.\r\nThe view HMY_BISettings will only only look at settings from the 'CBIS' subsystem.\r\n\r\nTest hint(s):\r\n1. Verify BI runs without errors","",57654,"https://ortec.link/Request?HID=16929760"]
[null,null,1665354,"2025-09-23",null,"Development\\OWS7",null,null,null,"TransactionCleaner Job was scheduled on workers and main server process","TransactionCleaner Job was scheduled on workers and main server process\r\nThis has improved\r\nTransactionCleaner Job is only scheduled on the main server process (=process with lowest server number)\r\n\r\nTest hint(s): None","",71168,""]
[null,null,1665354,"2025-09-23",null,"Development\\OWS7",null,null,null,"\"Overtime: compare employment hours\" would lead to an error when an employee switched employment terms partway through a schedule.","Overtime definition \"Overtime: compare employment hours\" would lead to an error when an employee switched employment terms partway through a schedule.\r\nThis has been fixed.\r\nThe maximum hours an employee can work with this definition is now based on the availability of each employment terms in proportion to the number of days the employment terms is valid in the calculated interval.\r\nDuring testing, an additional bug was found that a shift with overwork smaller than the amount of break time would not produce an overtime booking. This was fixed as well.\r\nDo note that this change could lead to new overtime bookings that were missing before.\r\nThese changes were introduced behind feature toggle CalculateOvertimeWithMultipleEmploymentTermsInInterval which is enabled by default.\r\n\r\nTest hints:\r\n1. Using overtime definition \"Overtime: compare employment hours\" with any overtime booking rule, open the account for an interval in which the calculated employee has two employment terms","",72479,"https://ortec.link/Request?HID=16952674"]
[null,null,1665354,"2025-09-23",null,"Development\\OWS7",null,null,null,"Rules of type 'Labor time per period' would show incorrect duplicate violations","Rules of type 'Labor time per period' would show duplicate violations on shifts that could not cause the violation.\r\nI.e. a day off shift not consisting of labour or working time would show a duplicate violation when the violation was already raised.\r\nThis has been fixed\r\nShifts that do not cause a violation (e.g. no labour or working hours), will no longer show a duplicate violation.\r\n\r\nTest hint(s):\r\n1. Verify that the rule  'Labor time per period (Day)' only show s violations on shifts that cause or could solve the violation\r\n2. Verify that the rule  'Labor time per period (Night)' only show s violations on shifts that cause or could solve the violation","",80686,"https://ortec.link/Request?HID=16974965"]
[null,null,1665354,"2025-09-23",null,"Development\\OWSforTeamSchedulers",null,null,null,"Creating or updating illnesses was not possible when illness properties that require authorizations were configured in ORTEC WS for Team Schedulers.","Creating or updating illnesses was not possible when illness properties that require authorizations were configured in ORTEC WS for Team Schedulers. \r\nThis has been fixed.","",85444,""]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Updating a pending update would not update the pending update record","In case an existing pending duty is updated, none of the pending update fields would be updated.\nThis would cause the change to not be registered in the transaction fragment and queue field collectors not to collect shift pending update fields.\nThis has been fixed.\nAny change to a pending update will register as at least a change in the LAST_ADJUSTED_USER and LAST_ADJUSTED_DATE fields.\n\nThis change has been put behind server setting FeatureToggles/UpdateLastAdjustedPropertiesInPendingUpdateOnChangedDutyProperties with default value Y\n\nTest hint(s):\n1. Verify that queue field collectors can return collected pending update fields","",116204,"https://ortec.link/Request?HID=17035592"]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Updated German translation","Updated German translation for report 'Auditing - Overview status changes'\n\nTest hint(s): \nNone","",129109,""]
[null,null,1669618,"2025-10-08",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical changes to show older sick leaves in ORTEC WS for Team Schedulers","Technical changes to show older sick leaves in ORTEC WS for Team Schedulers","",129748,""]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Feature toggle ReduceShiftLoadingWhenChangingScheduleStatus been removed.","Feature toggle ReduceShiftLoadingWhenChangingScheduleStatushas been removed.\nThis feature toggle was introduced in update 1556752 (2023-07-14)","",13146,""]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Feature toggle OnlyLookForExistingDutiesInPlanboardUpdatehas been removed.","Feature toggle OnlyLookForExistingDutiesInPlanboardUpdate has been removed. \r\nThis feature toggle was introduced in update 8.4.0-1044280 (2018-01-04)","",3057,"https://synergy.ortec.com/Synergy/docs/WflRequest.aspx?BCAction=1&ID=%7B20e8444c-7909-4446-a264-3950200fc0fe%7D"]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Insert of loginSession data could cause an sql error","Inserting an entry in acLoginSessionLogOWSApplication could cause an sql error when the corresponding acLoginSessionLog entry is not (yet) available.\nAs the entry is inserted eventually, the error could be ignored.\nThis has been improved\n\nInserting a acLoginSessionLogOWSApplication entry is only done when it can.\n\nTest hint(s): \nNone","",49660,"https://ortec.link/Request?HID=16762627"]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Added option to override HMY_BISettings view with a custom view","Added the option to override the HMY_BISETTINGS view with a custom view to accommodate for special scenarios for BI IL periods\n When a view with name HMY_BISETTINGS_CUSTOM exists in the OWS database, the BI run will fill HDM_Stage.BI_CURRENT_SETTINGS from that view. Otherwise, the values from HMY_BISETTINGS (generated from CBIS settings in CSCS) will be used by default.\n\nPlease note that creating and maintaining a HMY_BISETTINGS_CUSTOM is not done by OWS product releases.\n\nTest hint(s): \nNone","",50533,"https://ortec.link/Request?HID=16777568"]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Workstation demand import could cause access violations when running at the same time as employee import.","Workstation demand import could cause access violations when running at the same time as employee import.\r\nThis has been improved.\r\nAdded feature toggle  'FEATURETOGGLES\\ImproveGetAllActivities' which is enabled by default.\r\n\r\nTest hint(s): \r\n1 Verify that workstation demand import can (still) run at the same time as employee import.","",52382,"https://ortec.link/Request?HID=16822557"]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Violations for \"working hours per period\" rules not fully translated when stored","Violations for \"working hours per period\" rules were not fully translated when they were stored in the violations table\r\nFor non-English languages some parameters were still shown n English.\r\nThis has been fixed.\r\nStored violation texts for \"working hours per period\" type rules are now fully translated for non-English languages\r\nNote that previously stored incorrect violation texts are not corrected. This would require a recalculation of the employee(s)\r\n\r\nTest hint(s):\r\n1. Verify translations for violation texts for \"working hours per period\" type rules are correct for all languages","",55091,"https://ortec.link/Request?HID=16887190"]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Updated Finnish translation","Updated Finnish translation for 'Show borrowed employees'\r\n\r\nTest hint(s):\r\nNone","",55790,"https://ortec.link/Request?HID=16903174"]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Translation: The violation text for 'Break rules' rule was unclear","The violation text for 'Break rules' rule was unclear.\r\nThis has been improved.\r\n\r\nTest hint(s):\r\nNone","",57753,"https://ortec.link/Request?HID=16930812"]
[null,null,1669618,"2025-10-08",null,"Development\\OWS7",null,null,null,"Write SQL TransactionLocksInfo when query fails on deadlock exception","In order to improve analysis of SQL Deadlock exceptions when handling updates in a transaction.\r\nThe Transaction Locks information is written to a separate file on a deadlock exception\r\nThe logfile of the server process will mention the filename.\r\nThis change is introduced behind feature toggle LogTransactionLocksOnSQLDeadLockVictim which is enabled by default.","",85458,""]
[null,null,1672637,"2025-10-21",null,"Development\\OWSforTeamSchedulers",null,null,null,"Shifts shown for replacement in the sick leave details only showed shifts for the currently selected departments in ORTEC WS for Team Schedulers","Shifts shown for replacement in the sick leave details only showed shifts for the currently selected departments in ORTEC WS for Team Schedulers.\r\nThis has been changed.\r\nIt now shows all shifts in all departments. \r\nA settings has been added to revert to the old functionality TeamScheduling\\SickLeave\\ShowShiftsForAllDepartments.","","105405",""]
[null,null,1672637,"2025-10-21",null,"Development\\OWS7",null,null,null,"Queries to handle ESS Notification would sometimes time out.","Queries to handle ESS Notification would sometimes time out.\r\nThe performance of the notification-related queries has been improved.\r\n\r\nTest hint(s):\r\n1. Verify that performing a relevant shift offer or shift change action leads to a valid notification, when notifications are enabled.","","105408","https://ortec.link/Request?HID=17033837"]
[null,null,1672637,"2025-10-21",null,"Development\\OWS7",null,null,null,"Opening dutyform on ORTEC WS Win32 client could be slow when the number of active costcenters was high.","Opening dutyform on  ORTEC WS Win32 client could be slow when the number of active costcenters was high.\r\nThis has been improved.\r\nThis change is behind client setting featuretoggles/ImproveLoadingCostCentersInDutyForm_OldBehaviour which is disabled by default.\r\n\r\nTest hint(s):\r\n1 Verify that opening dutyform in  ORTEC WS Win32 client opens correctly and shows the expected costcenters on all tabs.","For this solution to become available, the ORTEC WS Win32 client must be installed.","130148","https://ortec.link/Request?HID=17051832"]
[null,null,1672637,"2025-10-21",null,"Development\\OWS7",null,null,null,"The ORTEC WS Win32 client could become unresponsive while exporting bookings to Excel.","The ORTEC WS Win32 client could become unresponsive while exporting bookings to Excel.\r\nThis has been improved.\r\nAdded feature toggle  'FEATURETOGGLES\\KeepClientResponsiveOnExportBookingsToExcel_OldBehaviour' which is disabled by default.\r\n\r\nTest hint(s):\r\n1. Verify that while exporting bookings to Excel, the ORTEC WS Win32 client remains responsive.","For this solution to become available, the ORTEC WS Win32 client must be installed.","72162","https://ortec.link/Request?HID=16946132"]
[null,null,1672637,"2025-10-21",null,"Development\\OWS7",null,null,null,"The BI table FACT_ASSIGNED_ACTIVITY did not contain the activities of realised student shifts.","The BI table FACT_ASSIGNED_ACTIVITY did not contain the activities of realised student shifts.    This has been fixed The activities of a realised student shifts will now show after a new BI load.\r\n\r\nTest hint(s):   1. Verify that the activities of realised student shifts will now show the FACT_ASSIGNED_ACTIVITY table and associated views after a BI load.","","72404","https://ortec.link/Request?HID=16950549"]
[null,null,1672637,"2025-10-21",null,"Development\\OWS7",null,null,null,"Feature toggle DoNotTranslateUserGroupNamesInUserImport has been removed.","Feature toggle DoNotTranslateUserGroupNamesInUserImport has been removed.\nThis feature toggle was introduced in update 1569177 (2023-10-26).","","83652",""]
[null,null,1672637,"2025-10-21",null,"Development\\OWS7",null,null,null,"Added additional logging to the transaction mechanism","Added additional logging to aid the analysis of access violations related to destroying transactions.","","84995","https://ortec.link/Request?HID=17013949"]
[null,null,1672637,"2025-10-21",null,"Development\\OWS7",null,null,null,"Changing (via import) begin date of skill to later date not possible when location is linked","The begin-/enddates of an existing skill with assigned PhysicalLocation and/or Workstation were not updated if the new begindate lies after the current begindate or the new enddate lies before the current enddate, regardless of the settings REMOVEINTERVALAFTERIMPORTEDENDDATE and REMOVEINTERVALBEFOREIMPORTEDBEGINDATE. This has been fixed. With the settings REMOVEINTERVALAFTERIMPORTEDENDDATE or REMOVEINTERVALBEFOREIMPORTEDBEGINDATE = Y, the existing begin-/enddate of an overlapping skill will be replaced by the new begin-/enddate.\r\n\r\nTest hint(s): 1. With setting REMOVEINTERVALAFTERIMPORTEDENDDATE = Y, verify that the enddate is updated when importing an update to the existing skill with assigned PhysicalLocation and/or Workstation with an earlier enddate than the existing enddate. 2. With setting REMOVEINTERVALBEFOREIMPORTEDBEGINDATE = Y, verify that the beginddate is updated when importing an update to the existing skill with assigned PhysicalLocation and/or Workstation with a later begindate than the existing begindate.","","85255","https://ortec.link/Request?HID=17018244"]
[null,null,1672637,"2025-10-21",null,"Development\\OWSforTeamSchedulers",null,null,null,"Reports with special characters could not be used in ORTEC WS for Team Schedulers","Reports with special German characters in the filename could not be used in ORTEC WS for Team Schedulers.\r\nThis has been fixed.","","86048","https://ortec.link/Request?HID=17027263"]
[null,null,1672637,"2025-10-21",null,"Development\\OWS7",null,null,null,"Feature toggle ImproveIllnessProcessorForZeroHourContracts has been removed.","Feature toggle ImproveIllnessProcessorForZeroHourContracts has been removed.\nThis feature toggle was introduced in update 1585598 (2024-02-15).",null,31524]
[null,null,1676040,"2025-11-04",null,"Development\\OWSforAdHocPlanners",null,null,null,"If a shift was opened for bidding in ORTEC WS for Ad Hoc Planners, the Shift Bidding event log table showed a generic system user.","If a shift was opened for bidding in ORTEC WS for Ad Hoc Planners, the Shift Bidding event log table showed a generic system user instead of the correct user.\r\nThis has been fixed.\r\nThe Shift Bidding event log table now shows the correct user that opened the shift for bidding.","","105343",""]
[null,null,1676040,"2025-11-04",null,"Development\\OWS7",null,null,null,"The use of a semicolon character in the remark field of an account entry resulted in overlapping text on screen, making it unreadable.","The use of a semicolon character in the remark field of an account entry resulted in overlapping text on screen, making it unreadable.\r\nThis has been fixed by replacing the semicolon with a colon before displaying it in the account.\r\n\r\nTest hint(s):\r\n1. verify that when a booking remark contains (a) semicolon(s), the text shown on screen shows (a) colon(s) instead of (a) semicolon(s) and text remains readable.","For this solution to become available, the ORTEC WS Win32 client must be installed.","130750","https://ortec.link/Request?HID=17057973"]
[null,null,1676040,"2025-11-04",null,"Development\\OWS7",null,null,null,"(ORTEC) ESS Mobile App sometimes showed contract expired, while there was an active contract.","(ORTEC) ESS Mobile App sometimes showed contract expired, while there was an active contract.\nThis has been fixed.\nThis fix is behind feature toggle UseImprovedQueryForContractServiceGetContracts, which is enabled by default.\n\nTest hint(s):\n1. Verify that (ORTEC) ESS Mobile App shows the correct contract status, also for an employee that has >= 2 terms group lines of which one is non adjacent.","","72165","https://ortec.link/Request?HID=16946139"]
[null,null,1676040,"2025-11-04",null,"Development\\OWSforTeamSchedulers",null,null,null,"[BE] Error when creating sick leave shifts in a period for which there is no schedule (but there is a calendar)","Replacing shifts with sick leave shifts for a period where there is no schedule could result in errors in ORTEC WS for Team Schedulers.\r\nThis has been fixed.\r\n\r\nCreate a sick leave in the future, when there are no schedules.  Replace some shifts in a period where there are no schedules. No errors should occur.","","85094",""]
[null,null,1680681,"2025-11-18",null,"Development\\OWS7",null,null,null,"Setting feature toggle FeatureToggleSplitIllnessProcessIntervalOverMainDepartments enabled could lead to a panic exception on illness import.","Setting feature toggle FeatureToggleSplitIllnessProcessIntervalOverMainDepartments enabled could lead to a panic exception on illness import.\nThis has been fixed.\n\nTest hint(s):\n1 Verifiy that an illness for an employee that switches main department in the shift replacement period can be imported without exceptions and that all shifts in that period are replaced by sick leave shifts.",null,"130261"]
[null,null,1680681,"2025-11-18",null,"Development\\OWSforTeamSchedulers",null,null,null,"When opening an absence for an employee before they have any schedule data, an error could occur in ORTEC WS for Team Schedulers","When opening an absence for an employee before they have any schedule data, an error could occur in ORTEC WS for Team Schedulers.\nThis has been fixed.",null,"130650"]
[null,null,1680681,"2025-11-18",null,"Development\\OWSforTeamSchedulers",null,null,null,"Editing the properties of a shift could sometimes result in an error in ORTEC WS for Team Schedulers","Editing the properties of a shift could sometimes result in an error in ORTEC WS for Team Schedulers.\nThis has been improved.",null,"131201"]
[null,null,1680681,"2025-11-18",null,"Development\\OWS7",null,null,null,"Some special characters in Danish and German translations were not shown correctly","Danish and German translation became corrupted due to a faulty integration.\nThis caused some special characters as ä, ö, ü, ø and æ to be shown incorrectly.\nThis has been fixed\n\nNote this issue was introduced in update 1672637 (2025-10-08)\n\nTest hint(s):\n1. Verify special characters as ä, ö, ü, ø and æ are shown correctly in the Danish and German languages",null,"131241","https://ortec.link/Request?HID=17067373"]
[null,null,1683271,"2025-12-02",null,"Development\\OWS7",null,null,null,"A new backend API route to retrieve instances of recurring duty wishes has been created.","A new backend API route to retrieve instances of recurring duty wishes has been created.\r\nThis route requires permission gui_workspace_ess_requests and can only be executed for an employee linked to the authorized user.","","130902",""]
[null,null,1683271,"2025-12-02",null,"Development\\OWS7",null,null,null,"Windows 2025 is supported","Deploying ORTEC WS 7 on Windows 2025 is supported.\r\nPlease check upgrade notes.","1. When installing the BackendDomainsAPIs an installer must be used that has the same or higher build number as the OWS 7 release.\n2. The JsonSerializer binary has been replaced by Newtonsoft.Json\nAny custom CPMS plugin using JsonSerializer binary that is installed at customers might prevent a successful upgrade. \nA workaround could be rolling back the update or after upgrade manually re-adding the JsonSerializer.dll from an archive (older NLib upgrade zip)\nAdditional note: The Sciple custom plugin (cem) has been checked using static code review and does not show usage the mentioned JsonSerializer binary.","83792",""]
[null,null,1688654,"2025-12-16",null,"Development\\OWS7",null,null,null,"Access violation on shift realisation could occur in rare cases","On sending data between Client and Server (i.e. duty information on shift realisation), it could occur that extra characters were added to the data being sent.\r\nIn rare cases, the meaning of the data could be changed due to such a character which could lead to an access violation.\r\nThis has been improved.\r\nUnnecessary characters are removed from Client-Server communication\r\nThis change is behind Client setting FeatureToggles/ImproveMarshallingLongStringArrays_OldBehavior disabled by default (new behavior is active)\r\n\r\nTest hint(s):\r\n1. Verify planning actions can be performed on shifts i.e. realisations","","130616",""]
[null,null,1688654,"2025-12-16",null,"Development\\OWSforTeamSchedulers",null,null,null,"Vertical calculations could result in performance problems in departments with a lot of employees in ORTEC WS for Team Schedulers","Vertical calculations could result in performance problems in departments with a lot of employees in ORTEC WS for Team Schedulers.\r\nThis has been improved.\r\nVertical calculations are no longer calculated for departments with a lot of employees.\r\nThe amount can be configured with a new setting TeamScheduling\\VerticalCalculations\\MaxNrOfEmployeesInDepartment, with a default value of 500.","","131801",""]
[null,null,1688654,"2025-12-16",null,"Development\\OWSforTeamSchedulers",null,null,null,"[BDA] Improve query performance in GetShiftsToReplaceForSickness","Retrieving shifts to be replaced in case of a sickness was sometimes slow in ORTEC WS for Team Schedulers.\r\nThis has been improved.","","132132",""]
[null,null,1688654,"2025-12-16",null,"Development\\OWS7",null,null,null,"Expat library is updated to version 2.7.3","With this version memory allocation for CWSS server processes is improved.\n\nTest hint(s)\n1. Verify communication between CWSS Server processes work as expected\n2. Verify a user can logon in the OWS Win32 client","",132219,""]
[null,null,1688654,"2025-12-16",null,"Development\\OWS7",null,null,null,"UnattendedUpdates - Added support for libexpat updates","Added support to roll out manual libexpat updates in UnattendedUpdates\r\nThese files will be rolled out on the main application server and all configured role servers and terminal servers","","132289",""]
[null,null,1688654,"2025-12-16",null,"Development\\OWSforTeamSchedulers",null,null,null,"Sicknesses were sometimes not shown on the dashboard in ORTEC WS for Team Schedulers","Sicknesses were sometimes not shown on the dashboard in ORTEC WS for Team Schedulers. \r\nThis was the case when using self scheduling and using the configuration to 'store a copy of the schedule when the round begins'.\r\nThis has been fixed.","","132316",""]
[null,null,1688654,"2025-12-16",null,"Development\\OWSforTeamSchedulers",null,null,null,"The sick leaves in the dashboard sometimes showed sick leave periods of an employee when the employee is not part of the department anymore (but has been in the past or future)","The dashboard sometimes showed sick leave periods of an employee that was no longer part of the department (but was in the past or future).\r\nThis has been fixed. Now only sick leaves are shown that overlap with the department assignment.","","132689",""]
[null,null,1688654,"2025-12-16",null,"Development\\OWS7",null,null,null,"When editing the 'Transfer booking based upon expression' rule with an invalid expression a message could popup repeatedly","OWS Client:  when editing the 'Transfer booking based upon expression' rule with an invalid expression a message could popup repeatedly.\r\nThe behaviour of the control the description of the rule was shown could cause infinite popups.\r\nThis has been changed.\r\n The component for the description in the rule form has been replaced.\r\nThis replacement has caused the functionality of a clickable URL (when an URL was available in the rule description)  to not function anymore.\r\n\r\nThis change was added behind feature toggle UseDescriptionMemoInRequirementForm_OldBehaviour, disabled by default.\r\n\r\nTest hint(s):\r\n1. Edit the 'Transfer booking based upon expression' rule with an invalid expression, one error message is shown. after this the expression can be edited again.","For this change to become available, the OWS Win32 client needs to be updated","80989","https://ortec.link/Request?HID=16982360"]
[null,null,1689655,"2025-12-19",null,"Development\\OWSforTeamSchedulers",null,null,null,"Reverted change \"The number of schedules in the past or future was not always correct in ORTEC WS for Team Schedulers\"","The change \"The number of schedules in the past or future was not always correct in ORTEC WS for Team Schedulers\" released in ORTEC Workforce Scheduling 7 Update 1662311 has been reverted. \nThis change could lead to performance problems for customers that use a lot of proposal departments and have heavy Team Scheduler usage. Since the original bug is an edge case that also has a workaround, we reverted that change now and will look for another solution.",null,133177]
[null,null,1694250,"2026-01-13",null,"Development\\OWS7",null,null,null,"The planboard shortcut to replace with Illness shifts has been made configurable","The planboard shortcut to replace with Illness shifts could not be used on Clients on the ORTEC hosting platform.\r\nThis has been improved.\r\nA new setting OPTIONS\\PLANBOARD\\SHORTCUTS\\REPLACEWITHILLNESSSHIFTS has been added to allow overriding the default shortcut Ctrl+Alt+Z\r\nA new value will become effective after performing a Refresh Settings action\r\n\r\nTest hint(s):\r\n1. Verify that when defining a new shortcut value, the client can use this new shortcut after refreshing settings.","","129637","https://ortec.link/Request?HID=17047376"]
[null,null,1694250,"2026-01-13",null,"Development\\OWS7",null,null,null,"Importing an update to a shift, making  it longer than 24 hours, always gave an error when using ExtraXMLCreator FillFieldsOfCOMTECShift","Importing a shift update making the shift longer than 24 hours using ExtraXMLCreator FillFieldsOfCOMTECShift always resulted in an error.\nThis has been fixed.\nWhether and error or warning is given now depends on the global setting UseDutyTooLongWarning, with the setting checked gives a warning and failing the realisation, and unchecked lets the realisation go trough.\nThis feature is introduced behind a new feature toggle RAISEDUTYTOOLONGERRORDEPENDINGONUSEDUTYTOOLONGWARNING which is enabled by default\n\nTest hint(s):\n1. Using ExtraXMLCreator FillFieldsOfCOMTECShift, import a shift realisation that causes a shift to have a length longer than 24 hours. Verify that with the setting UseDutyTooLongWarning unchecked, the import succeeds but gives a warning.\n2. Using ExtraXMLCreator FillFieldsOfCOMTECShift, import a shift realisation that causes a shift to have a length longer than 24 hours. Verify that with the setting UseDutyTooLongWarning checked, the import fails and gives an error.","","131200","https://ortec.link/Request?HID=17066667"]
[null,null,1694250,"2026-01-13",null,"Development\\OWSforAdHocPlanners",null,null,null,"Retrieving shifts in ORTEC WS for Ad Hoc Planners could sometimes take a long time.","Retrieving shifts in ORTEC WS for Ad Hoc Planners could sometimes take a long time.\r\nThis has been improved.\r\nSimilar improvements have been applied to the Shift Offering functionality.","","131474",""]
[null,null,1694250,"2026-01-13",null,"Development\\OWSforTeamSchedulers",null,null,null,"Sick leave percentage was sometimes incorrect in ORTEC WS for Team Schedulers","Sick leave percentage was sometimes incorrect in ORTEC WS for Team Schedulers.\nThis has been fixed.\nIf the sick leave percentage would change during the sickness, we now show the percentage of today.\nThis issue was introduced when we released the 'Manage old sick leaves' feature.","","131840",""]
[null,null,1694250,"2026-01-13",null,"Development\\OWS7",null,null,null,"Adjustment of ESS7 settings available through Back-end API","The following settings have been adjusted\n- Comtec.Workforce.BackendAPI\\ESS7\\Assistant\\AccountIdForLeaveBalance was added\n- Comtec.Workforce.BackendAPI\\Portals\\UseServerDateTimeOffset - The default setting changed from False to True\n\nTest hint(s)\nverify a user can logon to ESS7 verify a user can logon to WS for Employees","As the default value of UseServerDateTimeOffset changes to True, also the running (configured) value will change to True.\r\nThis means the front end for ESS7 will \"Display all datetimes in the server timezone (instead of converting it to the user device timezone).\"  after this update.","132691",""]
[null,null,1694250,"2026-01-13",null,"Development\\OWSforTeamSchedulers",null,null,null,"Vertical calculations sometimes did not update when assigning a shift in ORTEC WS for Team Schedulers","Vertical calculations sometimes did not update when assigning a shift in ORTEC WS for Team Schedulers.\r\nThis has been fixed.\r\nA new setting StartSnapshotTransaction_WaitForDtcCommits_BDA was added to OWSSettingsManager, default value 'Y'.","","133610",""]
[null,null,1694250,"2026-01-13",null,"Development\\OWS7",null,null,null,"Improved performance and memory usage during account category calculations","The way the account category calculations are prepared for each resource has been changed.\nThis improved the memory usage and performance of the account category calculations.\n\nTest hint(s): None","","133679",""]
[null,null,1694250,"2026-01-13",null,"Development\\OWS7",null,null,null,"Time for time type options list was not showing available values after entering entry cause.","In the running account line form, the time for time type options list was not showing available values after entering an entry cause.\nThis has been improved.\nThe time for time type options list is always refreshed after a change in the entry cause field.\n\nTest hint(s):\n1. Verify that when changing the entry cause of a time for time related booking, the correct time for time value can be selected from the time for time options list.","For this solution to become available, the ORTEC WS Win32 client must be installed.","72375","https://ortec.link/Request?HID=16949487"]
[null,null,1694250,"2026-01-13",null,"Development\\OWS7",null,null,null,"A CWSS server could be stuck in starting loop when the DB server went down during startup.","A CWSS server could be stuck in a starting loop when during startup the DB server went down.\nThis has been improved.\nThe server will now properly shutdown, allowing monitoring to pick this up so a manual restart can be executed.\n\nTest hint(s): None","","72710","https://ortec.link/Request?HID=16955247"]
[null,null,1694250,"2026-01-13",null,"Development\\OWS7",null,null,null,"The feature toggle MakeEmployeeNumberStaticWhenSuiteIsActive was added for future functionality","The feature toggle MakeEmployeeNumberStaticWhenSuiteIsActive was added for future functionality.\n\nThe feature toggle MakeEmployeeNumberStaticWhenSuiteIsActive is enabled by default.\nThe functionality behind the feature toggle depends on the WorkforceSuiteServiceURL being configured (BackendEventPublisher).",null,130839]
[null,null,1698566,"2026-01-27",null,"Development\\OWS7",null,null,null,"The scrollbar of Employee tab Skills in OWS Win32 Client could jump to the right when selecting another employee.","The scrollbar of Employee tab Skills in OWS Win32 Client could jump to the right when selecting another employee.\r\nThis has been fixed.","For this solution to become available, the ORTEC WS Win32 client must be installed.",132238,""]
[null,null,1698566,"2026-01-27",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to add remark to employee requests in ORTEC WS for Team Schedulers","Technical change to add remark to employee requests in ORTEC WS for Team Schedulers","",132469,""]
[null,null,1698566,"2026-01-27",null,"Development\\OWS7",null,null,null,"Pressing the Apply next (right or down) button after a shift realisation did not open the next shift","Pressing the Apply next (right or down) button after a shift realisation did not open the next shift when feature toggle ImproveLoadingCostCentersInDutyForm_OldBehaviour was set to N.  \nThis has been fixed.\n\nPlease, reset the value of this feature toggle to its default (N) if it was previously set it to Y.\n\nTest hint(s):  \n1. Create a realisation of a shift with a neighbour to its right/down. Verify that pressing the \"apply ->\" button will update the form to show the next shift.","For this solution to become available, the ORTEC WS Win32 client must be installed.",132578,""]
[null,null,1698566,"2026-01-27",null,"Development\\OWSforTeamSchedulers",null,null,null,"The number of shifts for a sickness was sometimes wrong in ORTEC WS for Team Schedulers","The number of shifts for a sickness was sometimes wrong in ORTEC WS for Team Schedulers.\r\nThis has been fixed.\r\nThis was the case if you have an employee that works for multiple departments, and you select those in the dashboard.","",133097,""]
[null,null,1698566,"2026-01-27",null,"Development\\OWS7",null,null,null,"New configuration options are introduced to provide greater control over illness registration and editing in OWS Win32 Client.","New configuration options are introduced to provide greater control over illness registration and editing in OWS Win32 Client by introducing a new permission to restrict changes to the illness type of an existing illness and a setting to enforce entry of an illness end date.\nThese additions allow organizations to better align illness registration behavior with internal policies and compliance requirements.\nAdded permission ILLNESS_CHANGE_ILLNESSTYPE which is granted for all users by default. When not granted, altering an illness type on an existing illness registration is prohibited.\nAdded global setting OPTIONS\\ILLNESS\\ENDDATEISMANDATORY which is disabled by default. When enabled all illnesses added or updated will need a set end date. Existing data will not be affected by this setting unless it is edited.\n\nTest hint(s):  \n1. Create or edit an illness registration and verify that the **end date** is optional when `OPTIONS\\ILLNESS\\ENDDATEISMANDATORY` is disabled and mandatory when enabled.  \n2. Edit an existing illness registration and verify that the **illness type** field is editable when the `ILLNESS_CHANGE_ILLNESSTYPE` permission is granted and read-only when it is revoked when updating an illness registration.","For this solution to become available, the ORTEC WS Win32 client must be installed.",133993,""]
[null,null,1698566,"2026-01-27",null,"Development\\OWSforTeamSchedulers",null,null,null,"The special duties were not always shown in the planboard in ORTEC WS for Team Schedulers.","The special duties were not always shown in the planboard in ORTEC WS for Team Schedulers..\r\nThis has been fixed.\r\nThis specifically happened if a database script was used to alter the ids of default objects, like the root department.\r\nThis fix is added behind a toggle in a CSCS setting TeamScheduling/FeatureToggles/SpecialDutiesQueryNonHardcodedRootDepartment, default True.","",134174,""]
[null,null,1698566,"2026-01-27",null,"Development\\OWS7",null,null,null,"Picking a shift from ESS could pick a similar shift not available for employee","Picking a shift from ESS could pick a similar shift subcontracted to another department which was not available for employee raising an error in the process.\nThis has been improved.\nA picked shift is now checked for the current department being the same as the department the pick is requested for.\nThis change was introduced behind feature toggle CheckCurrentDepartmentWhilePickingShift which is enabled by default\n\nTest hint(s):\n1. Verify that a picked shift belongs to the department the employee picked it from.","",80712,"https://ortec.link/Request?HID=16975259"]
[null,null,1698566,"2026-01-27",null,"Development\\OWS7",null,null,null,"Improved loading of account category lines on startup","Improved loading of account category lines on startup of the CWSS server.\nThis will decrease the time that the cwss process requires to start.\nThis change was introduced behind feature toggle ImproveLoadingLinesForRunningAccountsQuery which is enabled by default.\n\nTest hint(s):\nNone","",80799,"https://ortec.link/Request?HID=16977910"]
[null,null,1698566,"2026-01-27",null,"Development\\OWS7",null,null,null,"The template for unattended updates config did not mention the correct subfolder in the example Styleheet-libraries paths.","The template for unattended updates config did not mention the correct subfolder in the example Styleheet-libraries paths.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\nNone","",80899,"https://ortec.link/Request?HID=16980218"]
[null,null,1702119,"2026-02-10",null,"Development\\OWS7",null,null,null,"Unattended Updates could fail when an empty roleServer name was configured","Unattended Updates could fail when an empty roleServer name was configured.\r\nThis has been fixed\r\nUnattendedUpdates will now discard configured roleServers with an empty name.\r\n\r\nTest hint(s): None","This solution makes it mandatory to install the ORTEC WS Win32 client.  If this should not be possible,  feature toggle MarshallingGenericComCalls_OldBehaviour needs to be set enabled.","133882",""]
[null,null,1702119,"2026-02-10",null,"Development\\OWS7",null,null,null,"Updated several translations","Updated several translations for Danish, French and German\r\n\r\nTest hint(s): None","","134412",""]
[null,null,1702119,"2026-02-10",null,"Development\\OWS7",null,null,null,"OWS Win32 Client to CWSSServer communication could fail if client and server had different regional settings.","OWS Win32 Client to CWSSServer communication could fail if client and server had different regional settings.\nThis has been fixed.\nThis change is behind feature toggle MarshallingGenericComCalls_OldBehaviour which is disabled by default.\n\nTest hint(s): None","","134575","https://ortec.link/Request?HID=17053582"]
[null,null,1702119,"2026-02-10",null,"Development\\OWS7",null,null,null,"Comtec.WorkBench.Project.Sciple productized","The custom plugin Comtec.WorkBench.Project.Sciple has been productized, meaning it will be delivered and updated together with ORTEC WS deliveries.\nThis was done to remove the hassle of, and uncertainty about, separate plugin updates.\n\nTest hint(s): None","",134682,""]
[null,null,1702119,"2026-02-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"The name of an activity type can now be translated with the MultiLang module in ORTEC WS for Team Schedulers","The name of an activity type can now be translated with the MultiLang module in ORTEC WS for Team Schedulers.","","71178",""]
[null,null,1702119,"2026-02-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"The name of an absence in the planboard can now be translated with the MultiLang module in ORTEC WS for Team Schedulers","The name of an absence in the planboard can now be translated with the MultiLang module in ORTEC WS for Team Schedulers","","71180",""]
[null,null,1702119,"2026-02-10",null,"Development\\OWS7",null,null,null,"Using the leave processor to apply partial leave requests would sometimes lead to an incorrect leave shift","When using the leave processor to apply a partial leave request to a shift with activity types that are not considered work or labour, it would produce an incorrect leave shift.  \nThis has been fixed  \nno-work activity types, and no-labour activity types within the period of the partial wish will be converted to the activity type with the Leave (No work) and Leave (No labour) treatment respectively.  \nShifts completely consisting of activity types considered as rest time will not be converted, functioning just like before the change.\n\n  \nThis change was introduced behind feature toggle IncludeNoWorkNoLabourInPartialLeaveProcess, which is enable by default\n\nTest hint(s):\n1. Verify that applying a partial leave wish overlapping with a shift with activity types not considered work will convert the overlapping activities to Leave (no work) Verify that applying a partial leave wish overlapping with a shift with \nactivity types not considered labour will convert the overlapping \nactivities to Leave (no labour)","","72668","https://ortec.link/Request?HID=16955181"]
[null,null,1702119,"2026-02-10",null,"Development\\OWS7",null,null,null,"Running the optimizer on other employeecontract could result in shifts disappearing.","Running the optimizer on other employeecontract could result in shifts disappearing.\nThis has been fixed.\nA new feature toggle AddDepartmentsFromOtherContractsInExternalPlanner has been added and is enabled by default.\n\nTest hint(s):\n1. Verify that when running the optimizer on a schedule that has employees with shifts assigned on another contract, these shifts are not planned out with feature toggle AddDepartmentsFromOtherContractsInExternalPlanner enabled.","","80114","https://ortec.link/Request?HID=16965135"]
[null,null,1702119,"2026-02-10",null,"Development\\OWS7",null,null,null,"An Update of CSCS was not installed on all servers when using Unattended Updates.","An Update of CSCS was not installed on all application servers when using Unattended Updates.\nThis has been improved. \nThe CSCS manual update will now be installed on all configured application servers when using Unattended Updates.\n\nTest hint(s): None",null,"80711","https://ortec.link/Request?HID=16975254"]
[null,null,1702119,"2026-02-10",null,"Development\\OWS7",null,null,null,"The optimizer did not plan in a shift if an employee had a wish to work overlapping with a recurring wish not to work.","The optimizer did not plan in a shift if an employee had a wish to work overlapping with a recurring wish not to work.\nThis has been fixed\nA one-time work in interval wish will override any overlapping recurring work or shift wish for the optimizer as well. This was already default behaviour in the OWS client.\nThis change is behind Featuretoggle OneTimeWishOverridesRecurringWishForOptimizer which is enabled by default.\n\nTest hint(s):\n1. Verify that running the optimizer will plan in a possible shift when an employee has a one time work in interval wish overlapping with a recurring wish not to work.",null,"80922","https://ortec.link/Request?HID=16980458"]
[null,null,1703292,"2026-02-24",null,"Development\\OWS7",null,null,null,"Retrieving a batch of shifts in a certain period in Team Scheduler and Ad Hoc Planner could be time consuming.","Retrieving a batch of shifts in a certain period in Team Scheduler and Ad Hoc Planner could be time consuming.\r\nThis has been improved.\r\nAn additional index SHT_LOAD_REM_CURRENT_DPT_ID_I has been added to the database.\r\n\r\nTest hint(s): None","","135620",""]
[null,null,1703292,"2026-02-24",null,"Development\\OWSforTeamSchedulers",null,null,null,"The leave type and shift names of a leave request can now be translated with the MultiLang module in ORTEC WS for Team Schedulers","The leave type and shift names of a leave request can now be translated with the MultiLang module in ORTEC WS for Team Schedulers","","71179",""]
[null,null,1703292,"2026-02-24",null,"Development\\OWSforTeamSchedulers",null,null,null,"Absences could not be retrieved for leave requests without an activity type in ORTEC WS for Team Schedulers","Absences could not be retrieved for leave requests without an activity type in ORTEC WS for Team Schedulers\nThis has been fixed.",null,135775]
[null,null,1704031,"2026-03-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to improve the performance of retrieving shifts","Technical change to improve the performance of retrieving shifts.\r\nA toggle has been added to revert to the previous version TeamScheduling\\FeatureToggles\\ShiftQueriesImprovedPerformance, default on.","",134723,""]
[null,null,1704031,"2026-03-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to improve the performance of retrieving sicknesses","Technical change to improve the performance of retrieving sicknesses.\r\nA toggle was added to revert to the old functionality TeamScheduling\\FeatureToggles\\SicknessTileQueryImprovedPerformance.","",136151,""]
[null,null,1704031,"2026-03-10",null,"Development\\OWSforTeamSchedulers",null,null,null,"Shift details now can be translated using TeamScheduling.TranslationService.","The following fields are now translated: \r\nShift name \r\n Description \r\n Activity type names \r\n Property names","",71177,""]
[null,null,1704521,"2026-03-25",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to support addresses and activity properties in employee realizations in ORTEC WS for Team Schedulers","Technical change to support addresses and activity properties in employee realizations in ORTEC WS for Team Schedulers","","129383",""]
[null,null,1704521,"2026-03-25",null,"Development\\OWS7",null,null,null,"A nightshift could be only partially replaced by Illness if the shift exceeded the Illness end time.","A nightshift could be only partially replaced by Illness if the shift exceeded the Illness end time.\r\nThis has been improved.\r\nA new global setting UseReplaceEntireNightShiftWhenIllnessEndsAtMidnight is added, when enabled, the entire shift will be replaced by Illness, even when it only partially overlaps with the Illness and the Illness ends at midnight exactly.\r\n\r\nTest hint(s):\r\n1 Verify that when UseReplaceEntireNightShiftWhenIllnessEndsAtMidnight is enabled a nightshift is entirely replaced by an Illness shift even if the nightshift only partially overlaps with the Illness and the Ilness ends at midnight exactly.","","134251",""]
[null,null,1704521,"2026-03-25",null,"Development\\OWS7",null,null,null,"When a distributed transaction was aborted, the CWSS Server (process) could become unresponsive and eventually crash due to an invalid exchange validation error being raised during the rollback of changes","When a distributed transaction was aborted, the CWSS Server (process) could become unresponsive and eventually crash due to an invalid exchange validation error being raised during the rollback of changes.\r\nThis has been fixed.\r\nAdded feature toggle: FeatureToggles\\SkipEqualResourceAndShiftChecksOnRollingbackOrApplyingOrLoading which is enabled by default.\r\n\r\nTest hint(s):\r\nNone.","","135324",""]
[null,null,1704521,"2026-03-25",null,"Development\\OWS7",null,null,null,"Added option to archive duty exchanges","An option to archive duty exchanges has been added to reduce memory usage. \nArchived duty exchanges and their corresponding realization duties and activities will no longer be read into memory at startup of a CWSS server process\nIn the win32 Client such duty exchanges will no longer be visible in the overview mutations form\n\nThis functionality is behind server setting FeatureToggles\\EnableArchivingDutyExchanges, which is enabled by default\nTriggering the archiving task is done by a new CJSS task 'ArchiveDutyExchanges'\nThis task is disabled by default\n\nThe archiving period is set as follows:\n- The minimum number of days in the past the task will archive from is set by server setting OPTIONS\\COMMANDHANDLERS\\TARCHIVEDUTYEXCHANGES\\MINNOFDAYSOLD. This set to 30 days by default\n- The maximum number of days in the past the task will archive to is set to the bufferedHistory of the CWSS Process running the task. This is done to prevent data from before the bufferedHistory is loaded to archive the exchanges (with corresponding memory risks). This means that duty exchanges before the bufferedHistory will not be explicitly archived (ARCHIVED_IND = Y).\n  Server setting OPTIONS\\COMMANDHANDLERS\\TARCHIVEDUTYEXCHANGES\\MAXNOFDAYSOLD can be added if this needs to be overwritten\n\nArchiving period timeline example\n  BufferedHistory/MAXNOFDAYSOLD------MINNOFDAYSOLD------Today\n  366-----------------------------------------30------------------------Today\n  |--------------archiving period--------------|\n\nNotes:\n- When determining a CJSS schedule timing for this task, please keep in mind any other tasks that touch shifts and duties in the same period. I.e. CleanUpRemovedShifts task, imports or exports\n- Task will be executed on a CWSS Server with role Import/Export. If needed, this can be specified by adding OPTIONS\\COMMANDHANDLERS\\<ServerOptions>\\RegisterArchiveDutyExchanges and set value Y to desired <ServerOptions> and N for others\n- An archived duty exchange has the new ARCHIVED_IND column in ROS_EXCHANGES set to 'Y'\n- The column ARCHIVED_IND has not been added to the view HMY_EXCHANGES. Any existing reports or queries will still display archived duty exchanges\n- In general the memory footprint of duty exchanges that are read in memory has slightly been reduced.\n\nTest hint(s):\nVerify that after setting up and running the archiving task:\n1. Less exchanges are loaded in memory during startup\n2. Duty exchanges are archived and no longer visible in the win32 Client for the configured period.","","135418",""]
[null,null,1704521,"2026-03-25",null,"Development\\OWS7",null,null,null,"Adding a shift in ESS for a roster with a state >= Justified would check the wrong permission codes","Adding a shift in ESS for a roster with a state >= Justified would check the wrong permission codes.\r\nNote this action required FeatureToggle HardenAuthorizationForBackendAPIRoutes to be enabled.\r\nThis has been fixed.\r\n\r\nTest hint(s):\r\n1 Verify that adding a shift in ESS for a roster with state >= justified is possible when the correct permission is granted :\r\nJustified needs permission guiactions.ows.ess.AddShiftInPastForClosedSchedule Final needs permission guiactions.ows.ess.AddShiftInPastForApprovedSchedule Processed needs permission guiactions.ows.ess.AddShiftInPastForProcessedSchedule  Note  For status >= Justifed we only allow dayOffDuties (OnlyContainsTreatments([trmDayOff, trmSaturdayOff, trmSundayOff, trmCompensationDayOff])) Otherwise error \"This functionality is not supported\" is returned","","135972",""]
[null,null,1704521,"2026-03-25",null,"Development\\OWS7",null,null,null,"FeatureToggle HardenAuthorizationForBackendApiRoutes has been enabled by default","FeatureToggle HardenAuthorizationForBackendApiRoutes was added with a default value of False in issue 52450 and released in OWS 7 update 1628904 (2025-01-06). This was done to improve the security of Back-end-API endpoints for WS for Employees and ESS7 \r\nThis FeatureToggle is now set to True by default\r\n\r\nTest hint(s):\r\n1. Verify that actions done in WS for Employees and ESS7 do not raise unexpected permission errors","","135973",""]
[null,null,1704521,"2026-03-25",null,"Development\\OWSforTeamSchedulers",null,null,null,"Editing a special shift would sometimes result into errors in ORTEC WS for Team Schedulers.","Editing a special shift would sometimes result into errors in ORTEC WS for Team Schedulers.\r\nThis has been improved.","","136364",""]
[null,null,1705035,"2026-04-08",null,"Development\\OWS7",null,null,null,"Feature toggle KeepClientResponsiveOnExportBookingsToExcel_OldBehaviour has been removed.","Feature toggle KeepClientResponsiveOnExportBookingsToExcel_OldBehaviour has been removed.\r\nThis feature toggle was introduced in update 1672637 (2025-10-08).","",129495,""]
[null,null,1705035,"2026-04-08",null,"Development\\OWS7",null,null,null,"Shift options in ORTEC WS for Employees could fail for scheduling periods containing days without duty demand","Shift options in ORTEC WS for Employees could fail for scheduling periods containing days without duty demand\r\n\r\nThis has been fixed.\r\nThis functionality is behind feature toggle FeatureToggles\\HandleNoDemandInSelfRosterGetShiftOptions, which is enabled by default\r\n\r\nTest hint(s):\r\n1. Verify that shift options can be retrieved in ORTEC WS for Employees for a period containing days with and without duty demand\r\n 2. Verify that shift options are still retrieved correctly for periods containing only days with duty demand","",131503,""]
[null,"C",1705035,"2026-04-08",null,"Development\\OWS7",null,null,null,"Clicking in dropdown menu of overview wishes in ORTEC WS Win32 client before it had finished loading could cause an exception and freeze the ORTEC WS Win32","Clicking in dropdown menu of overview wishes in ORTEC WS Win32 client before it had finished loading could cause an exception and freeze the ORTEC WS Win32\nThis has been fixed.\n\nTest hint(s):\n1. Verify that when clicking in dropdown menu of overview wishes the expected data is shown in the dropdown list.","For this solution to become available, the ORTEC WS Win32 client must be installed.",131612,"https://ortec.link/Request?HID=17071993"]
[null,null,1705035,"2026-04-08",null,"Development\\OWS7",null,null,null,"Upgrade Microsoft Identity Libraries","This update upgrades the Microsoft Identity and JWT token handling libraries across the OWS 7 back-end applications.\nThis also includes support for Microsoft Entra login for OWS win32 Client, for use with Azure Virtual Desktop.\n\nTest hint(s):\n1. Verify logging in different OWS 7 cloud based front-ends Verify notifications on shift opened for bidding\n2. When Comtec.Workbench.Project.Common.Email is used, verify mails are sent as expected.","For this solution to become available, the ORTEC WS Win32 client must be installed.",132647,""]
[null,null,1705035,"2026-04-08",null,"Development\\OWSforTeamSchedulers",null,null,null,"Fixed the issue where employees with multiple active sort categories were shown","Fixed the issue where employees with multiple active sort categories were shown a random category instead of the most recent one. Team Scheduler now always uses the sort category with the latest begin date.","",134600,""]
[null,null,1705035,"2026-04-08",null,"Development\\OWSforTeamSchedulers",null,null,null,"Technical change to support refreshing horizontal and vertical calculations more often in ORTEC WS for Team Schedulers","Technical change to support refreshing horizontal and vertical calculations more often in ORTEC WS for Team Schedulers.\r\nTwo settings have been added to configure when calculations should be refreshed.\r\nTeamScheduling\\VerticalCalculations\\RecalculateAfterXMinutes TeamScheduling\\HorizontalCalculations\\RecalculateAfterXMinutes  \r\nOne setting has been added to configure an optional dedicated server for the horizontal calculations.\r\nTeamScheduling\\HorizontalCalculations\\ServerNumber","",134700,""]
[null,null,1705035,"2026-04-08",null,"Development\\OWSforTeamSchedulers",null,null,null,"Employee counts for departments with recurring or historical assignments sometimes skipped vertical calculations in ORTEC WS for Team Schedulers","Employee counts for departments with recurring or historical assignments sometimes skipped vertical calculations in ORTEC WS for Team Schedulers.\nThis has been improved.\n\nDepartments that were incorrectly skipping vertical calculations due to inflated counts will now be calculated as expected.\nThis relates to an earlier introduced setting TeamScheduling\\VerticalCalculations\\MaxNrOfEmployeesInDepartment","",134898,""]
[null,null,1705035,"2026-04-08",null,"Development\\OWS7",null,null,null,"An ORTEC WS for Employees request to get all recurring requests did not include declined recurring requests","An ORTEC WS for Employees request to get all recurring requests did not in,clude declined recurring requests\nThis has been changed.\nDeclined recurring requests are now also returned to ESS7\n\nTest hint(s):\n1. Verify that declined recurring requests are also returned when requesting recurring requests from ORTEC WS for Employees.","",136681,""]
[null,null,1705035,"2026-04-08",null,"Development\\OWSforTeamSchedulers",null,null,null,"The employee calculation names can now be translated with the MultiLang module in ORTEC WS for Team Schedulers","The employee calculation names can now be translated with the MultiLang module in ORTEC WS for Team Schedulers","",56069,""]
[null,null,1705491,"2026-04-24",null,"Development\\OWS and Enablers\\OWS7",null,null,null,"Removed feature toggle UpdateLastAdjustedPropertiesInPendingUpdateOnChangedDutyProperties","Removed feature toggle UpdateLastAdjustedPropertiesInPendingUpdateOnChangedDutyProperties\nThis was released in '116204 Updating a pending update would not update the pending update record' in OWS7 8.5.0(2025-10-08)_Build1669618\n\nTest hint(s)\n1. Verify that queue field collectors can return collected pending update fields","",129631,""]
[null,null,1705491,"2026-04-24",null,"Development\\OWS and Enablers\\OWS7",null,null,null,"Writing information to the database about the OWS application used by a logged on user in any of the OWS cloud applications could cause contention issues","Writing information to the database about the OWS application used by a logged on user in any of the OWS cloud applications could cause contention issues\nThis has been improved.\nA different transaction isolation level is used for writing this information which reduces contention when users login on OWS cloud applications\n\nTest hint(s)\n1. Verify OWS cloud applications can be logged onto.","",131874,""]
[null,null,1705491,"2026-04-24",null,"Development\\OWS and Enablers\\OWS7",null,null,null,"Sick leave shifts did not always get the correct translation when using the MultiLang module","In Team Scheduler, when creating a sick leave shift for a shift that has translations, only the name of the shift would be replaced by the name of the sick leave shift, but the translations would remain the same as the translations for the original shift. This has been fixed. Now the translations for the sick leave shift are also copied.\r\nThis change is behind feature toggle FeatureToggles\\CopyTranslationsForIllnessShift, which is enabled by default.","",135606,""]
[null,null,1705491,"2026-04-24",null,"Development\\OWS and Enablers\\OWS7",null,null,null,"Isolation level used during reading updates in CHandeUpdateInTransaction could cause unnecessary blocking of other database transactions","Isolation level used during reading updates in CHandeUpdateInTransaction could cause unnecessary blocking of other database transactions\nThis has been improved.\nImproved update handling by using a dedicated isolation level while reading incoming updates and restoring the original transaction isolation level afterwards\n\nAdded feature toggle: UseIsolationLevelForReadingUpdatesWhenApplyingUpdates which is disabled by default\nNOTE: only an ORTEC consultant is allowed to change this setting in agreement with the Maintenance department.\n\nTest hint(s):\n1. Verify updates are applied successfully under concurrent load with the default configuration\n2. Verify transaction behavior remains stable when the toggle is turned on","",136662,""]
[null,null,1706196,"2026-05-05",null,"Development\\OWS and Enablers\\OWS7",null,null,null,"CCleanupRemovedshifts could cause memory inconsistency that resulted in server crash","CCleanupRemovedshifts could cause memory inconsistency that resulted in server crash\r\nThis has been improved.\r\nTo allow deeper investigation of this issue instrumentation code has been added.\r\nThis change is behind feature toggle AddWriteLocksForDutyPropertyValue which is enabled by default.\r\n\r\nTest hint(s): None","","136375"]
[null,null,1706196,"2026-05-05",null,"Development\\OWS and Enablers\\OWSforTeamSchedulers",null,null,null,"Technical change to support configuring rollout method per department in ORTEC WS for Team Schedulers","Technical change to support configuring rollout method per department in ORTEC WS for Team Schedulers","","138841"]
[null,null,1706507,"2026-05-19","Y","Development\\OWS and Enablers\\OWS7",null,null,null,"Workstation proposal showed workstations that have the checkbox 'Entering a workstation is not allowed' even though selecting these was not possible","Workstation proposal showed workstations that have the checkbox 'Entering a workstation is not allowed' even though selecting these was not possible\r\nThis has been improved\r\nA workstation that has checkbox 'Entering a workstation is not allowed' checked is no longer shown in the workstation proposal\r\n\r\nTest hint(s):\r\n1. Verify that workstations that have the checkbox 'Entering a workstation is not allowed' are no longer shown in the workstation proposal.","","131997","https://ortec.link/Request?HID=17078813"]
[null,null,1706507,"2026-05-19","N","Development\\OWS and Enablers\\OWS7",null,null,null,"CAIS dependency Log4net binary has been updated","CAIS dependency Log4net library has been updated to mitigate a vulnerability.\n\nTest hint(s):\n1. Verify that configured CAIS endpoints work as expected","","138444",""]
[null,null,1706507,"2026-05-19","Y","Development\\OWS and Enablers\\OWSforAdHocPlanners",null,null,null,"Shifts with status 'plan' were always shown in ORTEC WS for Ad Hoc Planners","Shifts with status 'plan' were always shown in ORTEC WS for Ad Hoc Planners\r\nThis has been changed.\r\nA new setting has been added: AdhocPlanning\\Shifts\\ShowPlannedShifts, default True.\r\nIf this setting is turned off, planned shifts are no longer shown in the application.","","138491",""]
[null,null,1706507,"2026-05-19","Y","Development\\ORTEC Workforce\\Suite",null,null,null,"Teamscheduler: When applying a shiftpattern sometimes new shifts were created instead of reusing pre-existing unassigned shifts","When applying a shiftpattern sometimes new shifts were created instead of reusing pre-existing unassigned shifts\n\nThis has been fixed\n\nTest hint(s):\nUsing teamscheduler and shift pattern rollout\n1. Verify that when an unassigned shift with the same duty and start time exists it is assigned to the employee during roll out\n2. Verify that blocked, fixed or realised unassigned shifts are handled correctly and that other scheduling behavior remains unchanged","","139233",""]
[null,null,1706919,"2026-06-02","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Support was added to let the ESS assistant interpret yearly hour balances correctly when a customer uses an inverted balance meaning","Support was added to let the ESS assistant interpret yearly hour balances correctly when a customer uses an inverted balance meaning\n\nAdded CSCS Setting Manager setting: Comtec.Workforce.BackendAPI\\ESS7\\Assistant\\InvertedValueForHourBalance with default value N\n\nTest hint(s): \nNone","","139009",""]
[null,null,1706919,"2026-06-02","N","Development\\OWS and Enablers\\OWSforTeamSchedulers",null,null,null,"Forbidden violations can now be checked when performing certain plan actions in ORTEC WS for Team Schedulers","Forbidden violations can now be checked when performing certain plan actions in ORTEC WS for Team Schedulers.\nA new CSCS setting was added called TeamScheduling\\PlanActions\\CheckForbiddenViolation, which is False by default.\nWhen the setting is enabled, the system checks whether the performing user has permissions to create any violation that occur from the action (if permissions are enabled on the violation type). If not, the action is blocked. \n\nNote that this change only includes the backend check. When a user does not have permissions, the backend will throw an error and the user will see a generic error in the Team Scheduler UI. In a future change, we will show a more explanatory message to end users.\n\nThe following plan actions are affected:\nEditing a shift Adding a shift Moving a shift Approving an employee realization Assigning a shift through the employee proposal  \nWe will monitor the need for checks in additional places.","Important notes:\nWhen the setting is enabled, the user needs additional ORTEC WS permissions for certain 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, the users will not be able to do these actions in Team Scheduler.","139484",""]
[null,null,1707207,"2026-06-17","N","Development\\OWS and \nEnablers\\OWSforTeamSchedulers",null,null,null,"Technical change to support showing effective work time in ORTEC WS for Team Schedulers","Technical change to support showing effective work time in ORTEC WS for Team Schedulers","","134375",""]
[null,null,1707207,"2026-06-17","N","Development\\OWS and \nEnablers\\OWSforTeamSchedulers",null,null,null,"Technical change to add Access Control permissions for dashboard tiles in ORTEC WS for Team Schedulers","Technical change to add Access Control permissions for dashboard tiles in ORTEC WS for Team Schedulers","","134567",""]
[null,null,1707207,"2026-06-17","Y","Development\\OWS and Enablers\\OWS7",null,null,null,"The  labor rule working-hours-per-period (general) could return incorrect results for shifts that contained Leave activity class entries.","The working-hours-per-period (general) labor rule could return incorrect results for shifts that contained Leave activity class entries. \nThis has been fixed.\n\nThis change is behind added feature toggle FeatureToggles\\UseCorrectGrossWorkingTimeBufferInDuty which is enabled by default\n\nTest hint(s):\n1. Verify that a shift mix including Leave (no labor) is now correctly included/excluded according to the labor rule definition in Working hours per period (general) \n2. Verify that existing labor rule results remain unchanged for scenarios without Leave (no labor) and for standard Plan board planning flows","","135936",""]
[null,null,1707207,"2026-06-17","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Added department to BackendApi request model","Technical preparation for a future ESS7 change for filtering on department for shiftPicking duty requests\n\nTest hint(s): None","","137788",""]
[null,null,1707207,"2026-06-17","N","Development\\OWS and Enablers\\OWS7",null,null,null,"CLSS license check removed","The CLSS license check has been removed, which means ORTEC WS no longer performs a CLSS license check at server startup. This is done to remove the dependency on the (old) CLSS server.\n\n\nTwo new Settings Manager settings have been introduced:\nSETTINGS\\MAXEMPLOYEES with default value 99999. This setting is used to check the number of scheduled employees at Client startup. If the number of scheduled employees exceeds the configured number, the Client will return the usual license check error. EXTRACLIENTCUSTOMERNAME with default value ''. This setting is used as a replacement for the customer name in the license, which is shown in several places in the ORTEC WS Client (e.g. the application title bar)\n  \nThere is no longer a check on used modules.\n\nTest hint(s):\n1. Verify the client shows the configured customer name in the title bar and About screen - Verify the client still starts and applies the default employee limit when both settings use their default values","As the customer name displayed in the title bar of the win32-Client will no longer read form the license, the customer name should be filled in the Settings Manager server setting EXTRACLIENTCUSTOMERNAME","138732",""]
[null,null,1707207,"2026-06-17","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Added technical preparation for leave request status update notifications, so OWS can send notifications after ORTEC WS for Employees development is completed","Added technical preparation for leave request status update notifications, so OWS can send notifications after ORTEC WS for Employees development is completed\r\nAdded Server setting: OrtecRelevancePushNotificationSender\\LeaveWishStatusUpdateNotification\\SendLeaveWishStatusUpdateNotification with default value False\r\nKeep this setting disabled until ORTEC WS for Employees development is completed\r\n\r\nTest hint(s): None","","138926",""]
[null,null,1707207,"2026-06-17","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Improved error message on rolling out or requesting cyclical schedule","On rolling out or requesting cyclical schedule a check is done whether the shifts that have been created based on the cyclical schedule have equal duties and dates.\r\nIn some use cases valid duties are not available on the specific date and OWS will find similar duties (by name). This however, could cause overlap in the rollout result if not checked.\r\nThe error message raised by this check did not show any info for which resource or date, the error occurred, making it hard to analyze the case.\r\nThis has been improved.\r\nThe error message now mentions the resource, date and name and id of the equal duties\r\n\r\nTest hint(s): None","","139388",""]
[null,null,1707207,"2026-06-17","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Queue export files did not contain the username that triggered the export","Queue export files did not contain the username that triggered the export.\nThis has been added to assist in certain Parent-Child scenario's.\nThe field ExportParameters/UserId has been added to the export file containing the definition identifier (for example XMLImp:<DefinitionName>)\n\nTest hint(s):\n1. Verify that a queue export now contains the field ExportParameters/UserId filled with the import trigger value as user","","139983",""]
[null,null,1707207,"2026-06-17","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Notification processing could become less reliable over longer CWSS Server (process) runtimes due to internal resource handling and possibly causing out of memory","Notification processing could become less reliable over longer CWSS Server (process) runtimes due to internal resource handling and possibly causing out of memory\nThis has been fixed\n\nTest hint(s): \n1. Verify notification update behavior remains the same for shift change, and shift offer scenarios","","140394",""]
[null,null,1707590,"2026-06-30","Y","Development\\OWS and Enablers\\OWS7",null,null,null,"Labor rules of type 'Duration of a day/night shift' type filter out irrelevant contracts","The labor rules 'Duration of a day shift' and 'Duration of a night shift' would also throw a violation on an employee contract that is not assigned to the shift.\r\n\r\nThis is not always desirable, as for the other employee contract it is likely not possible to solve the violation as these rules look at at single shift. \r\nThis has been improved \r\n\r\n\r\nThese rules will now only throw the violation on the employee contract that is assigned to the shift. \r\nThis has been put behind setting FeatureToggles/DiscardOtherContractsInShiftTimeRequirement, which is enabled by default\r\n\r\nTest hint(s): \r\n1. Verify violations on labor rules are only raised on the employee contract that planned the shift","",130045,""]
[null,null,1707590,"2026-06-30","Y","Development\\OWS and Enablers\\OWSforTeamSchedulers",null,null,null,"Student shift is counted as regular shift in staffing counters","Student shifts have been excluded from the KPIs when counting understaffed and overstaffed days","","140911",""]
[null,null,1707590,"2026-06-30","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Whether a department id would be added to a shift bidding request was dependent on the logging of shift bidding being enabled","Whether a department id would be added to the shift bidding request data was dependent on the logging of shift bidding being enabled. \r\nThis has been improved. \r\n\r\n\r\nWhen a user creates a shift bidding request, the department id is now always added to the request data.\r\n\r\nTest hint(s): \r\n1. Verify a shift bidding request can be created with server setting Bidding/ShiftBidding/LogShiftBiddingEvents enabled and disabled","","140915",""]
[null,null,1707590,"2026-06-30","N","Development\\OWS and Enablers\\OWSforTeamSchedulers",null,null,null,"Updating duty requests sometimes failed when using the Shift Offering module","Updating duty requests sometimes failed when using the Shift Offering module.  \r\nThis was the case when one of the requests was already removed. \r\nThis has been fixed.","","140917",""]
[null,null,1707590,"2026-06-30","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Re-enable StartSnapshotTransaction_WaitForDtcCommits on OWS environments running SQL Server 2022","In card 32050, we disabled StartSnapshotTransaction_WaitForDtcCommits for OWS environments with a database running on SQL Server 2022 instances for performance reasons. \r\nHowever, it has come to our attention that StartSnapshotTransaction_WaitForDtcCommits is still required on all supported SQL Server versions for increased stability. \r\n\r\n\r\nStartSnapshotTransaction_WaitForDtcCommits will be enabled again when running DBUpdate.\r\n\r\nTest hint(s): \r\n1.Verify transaction between CWSS main process and Interface workers are handled and finish correctly","","141706",""]
[null,null,1707590,"2026-06-30","N","Development\\OWS and Enablers\\OWS7",null,null,null,"FeatureToggles around UseSnapshotIsolationForHandlingUpdates have been enabled by default","FeatureToggles    \n  - FeatureToggles/UseSnapshotIsolationForHandlingUpdates \n  - FeatureToggles/UseSnapshotIsolationForHandlingAsyncUpdates \n  - FeatureToggles/UseSnapshotIsolationForHandlingSkillMatchingUpdates  \nwere added with a default value of False in issue 80810 and released in OWS 7 update 1650946 (2025-07-15) \nThis was done to improve database locking during the handling of updates\n\nThese FeatureToggles are now set to True by default \n\n\nFurthermore, these featureToggles were dependent on the setting StartSnapshotTransaction_WaitForDtcCommits being disabled. \nThis dependency has been removed for greater freedom in setting combinations where needed\n\nTest hint(s): None","",83998,""]
[null,null,1707976,"2026-07-13","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Reduce memory footprint of labor rules NofFreeWeekendsReq and NofDaysReq","In order to comply with labor rule legislation, the following rules often require a setup that look back 52 weeks:\n- 'Number of free weekends' (NofFreeWeekendsReq) \n- 'Number of free days on a weekday' (NofDaysReq)\nThis causes the CWSS Server to need more historical data (higher bufferedHistory) than most of the other rules require.\nThis added memory consumption could lead to memory problems at larger customers.\n\nThis has been improved.\nFor these two rules, it is now possible to fetch the required data with a reduced memory footprint, by reading it from the database instead of from memory. A new table has been added that stores specific metadata of shifts. It contains only the fields necessary for these two rules and will be used to calculate for periods that are outside the bufferedHistory. This can mean that the BufferedHistory setting can be lowered if the rest of the requirement and remuneration configuration allows it.\n\nThis improvement has been placed behind settings\n- FeatureToggles\\UseLoadingHistoricalRequirementShiftDataNofFreeWeekendsReq\n- FeatureToggles\\UseLoadingHistoricalRequirementShiftDataNofDaysReq\nBoth settings are disabled by default. It is advised to enable these feature toggles only if the customer situation requires it (from a memory perspective) and only in consultation with Product Support. Additional (performance) improvements will follow in a later release.\n\nNote:\nAfter enabling the feature toggle(s), activating this functionality also requires an additional run of the DBUpdate.\nThis will run a query to initially fill the ROS_REQUIREMENT_SHIFTS table based on the ROS_SHIFTS data of the last 4 years.\n\nDuring runtime CWSS Server will update the requirement shift records when shifts are added, updated or deleted\nEach DBUpdate will refill the ROS_REQUIREMENT_SHIFTS table to ensure consistency.\n\nTest hint(s):\n1. Verify that violation calculations are correct for the labor rules 'Number of free weekends' and 'Number of free days on a weekday'.","\nAfter enabling the feature toggle(s), activating this functionality also requires an additional run of the DBUpdate.\n\nIn order to get the most from this improvement consider the following settings: \n- OPTIONS\\PLANBOARD\\LOADING\\LOADDAYSBEFORE \n- OPTIONS\\PLANBOARD\\LOADING\\LOADDAYSAFTER\nThey should be set to the lowest possible value, and if possible to 0. Although this depends on the history the other labor rules require.\n\nConsider setting the values to similar values as\n- OPTIONS\\RUNNINGACCOUNTS\\LOADING\\LOADDAYSAFTER\n- OPTIONS\\RUNNINGACCOUNTS\\LOADING\\LOADDAYSBEFORE\n\nNow consider a new value for the BufferedHistory setting. This depends on the history other requirement and remuneration rule require.\n\nOther remarks\n  - Known issue: Using the internal optimizer with either one of the mentioned feature toggles turned on will load shift data in memory. This will be handled in a follow up issue. Advice is to use external optimizer.\n  - Known issue: The commandHandler selfroster/CGetShiftOptions with either one of the mentioned feature toggles turned on will load shift data in memory. This will be handled in a follow up issue. \n  - Known issue: The MS report 'Violations' with either one of the mentioned feature toggles turned on will load shift data in memory. This will be handled in a follow up issue. \n  - Changing UseBreakOnCall setting needs running DBUpdate to refill the ros_rquirements_shifts table \n  - Changing UseBreakWithinActivities setting needs running DBUpdate to refill the ros_rquirements_shifts table\n  - When turning on feature toggles, make sure the requirement shift data is populated by running DBUpdate.","139477",""]
[null,null,1707976,"2026-07-13","N","Development\\OWS and Enablers\\OWSforTeamSchedulers",null,null,null,"In TeamScheduler, rolling out demanded duties had created exchanges as Requested (red) instead of Required (blue) in published periods.","In TeamScheduler, rolling out demanded duties had created exchanges as Requested (red) instead of Required (blue) in published periods.\nThis has been fixed.  \nThe rollout was updated so newly created demand shifts use Required exchange kind consistently.","","140346",""]
[null,null,1707976,"2026-07-13","Y","Development\\OWS and Enablers\\OWSforTeamSchedulers",null,null,null,"The sick leaves and leave requests tiles in the Team Scheduler could load slowly or time out for large departments","The sick leaves and leave requests tiles in the Team Scheduler could load slowly or time out for departments with a lot of data. This has been improved.\nThe queries behind both tiles were rebuilt so they return faster.\nAdded feature toggle Server setting: TeamScheduling\\FeatureToggles\\LeaveRequestsTileQueryImprovedPerformance which is enabled by default.\n\nTest hint(s):\n1. Verify the sick leaves tile opens and shows the correct sick leaves for a department.\n2. Verify the leave requests tile opens and shows the correct leave requests for a department.","","141008",""]
[null,null,1707976,"2026-07-13","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Deleting a linked employee could lead to an exception in the server","Trying and failing to delete a linked employee could lead to an exception in the server.\nThis happened in rare cases when additional checks based on stored data prevented the deletion of the employee\nThis has been fixed.\nNow only a warning is shown why the action is not allowed.\n\nThis change is behind feature toggle ProvideContextWhenLoadingLinkedShiftContainer which is enabled by default.\n\nTest hint(s):\n1. Verify a user can link employees with planned shifts using their employee number.\n2. Verify a linked employee cannot be deleted if it has old related data stored in the database.\n3. Verify a linked employee can be deleted when it has no related data.","","82845","https://ortec.link/Request?HID=16988898"]
[null,null,1707976,"2026-07-13","Y","Development\\OWS and Enablers\\OWS7",null,null,null,"Unchecking schedule status in 'Days without kind in period' labor rule still showed violation in planboard","When unchecking a schedule status in the labor rule 'Days without kind in period' a violation would still show in the planboard.\r\nThis has been fixed.\r\nWhen opting to not show violations in certain schedule statuses, violations will not longer be shown in those statuses.\r\nThis change is behind a new setting FeatureToggles\\CheckScheduleStatusInNoTreatmentInDaysReq which is enabled by default.\r\n\r\nTest hint(s):\r\n1. Verify that configuring the labor rule 'Days without kind in period' to not show a violation in certain schedule statuses, the planboard will not show the violation in configured statuses.","","85258","https://ortec.link/Request?HID=17018248"]
[null,null,1708625,"2026-08-11","Y","Development\\OWS and Enablers\\OWS7",null,null,null,"Selecting employee calculations in the Master Schedule report using the OWS client could be very slow","Selecting employee calculations in the Master Schedule report using the OWS client could be very slow, potentially leading to an unresponsive client. \nThis has been improved.\n\nTest hint(s): \n1. Open the master schedule report in the client and verify that employee calculations can be selected.\n2. Verify the report shows these calculations on a refresh of the report.","","116516","https://ortec.link/Request?HID=17035605"]
[null,null,1708625,"2026-08-11","N","Development\\ORTEC Workforce\\Suite",null,null,null,"UnattendedUpdates - Add support for Workforce Suite","In order to support new Suite features in the BackendDomainsApi, a FeatureToggle 'useWorkforceSuite' has been added for the UnattendedUpdates\\UnattendedUpdate_Config.xml\r\nThis will postpone starting the BackendDomainsApi until after the starter service has started, in order to send a sync request to the BackendEventPublisher after an update.\r\n\r\nTest hint(s): None","This can be turned on or off in C:\\ProgramData\\Ortec\\ORTEC Workforce Scheduling\\UnattendedUpdates\\UnattendedUpdate_Config.xml \n This should be turned on for customers that use the ow suite.       \nIf the <featureToggles>node does not exist, it can be inserted between </scriptOptions> and <eMail>:   <featureToggles>     ...         <useWorkforceSuite>Y</useWorkforceSuite> \n  </featureToggles>  \nSee Template_UnattendedUpdate_Config.xml in the UnattendedUpdates scripts folder for an example  Note that it is inactive by default, also when the entry does not exist.","141827",""]
[null,null,1708625,"2026-08-11","N","Development\\OWS and Enablers\\OWSforTeamSchedulers",null,null,null,"Login sessions from Team Schedulers were no longer recorded with the originating system","Login sessions from Team Schedulers were no longer recorded with the originating system. \r\nThis has been fixed.","","142193",""]
[null,null,1708625,"2026-08-11","N","Development\\OWS and Enablers\\OWS7",null,null,null,"UnattendedUpdates could run into locked files while updating itself","When the UnattendedUpdates script updates itself it could run into files in use by another process, likely due to a virusscanner.\r\nThis has been improved.\r\nA retry mechanism has been added to give the other process some time to release it.\r\n\r\nTest hint(s): None","","142907",""]
[null,null,1708625,"2026-08-11","Y","Development\\OWS and Enablers\\OWS7",null,null,null,"Reduce memory footprint of labor rules NofFreeWeekendsReq and NofDaysReq","In order to comply with labor rule legislation, the following rules often require a setup that looks back 52 weeks:\n'Number of free weekends' (NofFreeWeekendsReq)\n'Number of free days on a weekday' (NofDaysReq)\nBuild 1707976 introduced the possibility to reduce the memory footprint of these rules by reading historical shift data from the database instead of from memory. While this reduced memory consumption, it also introduced additional database queries during labor rule calculations.\n \nThis has been further improved.\nThe database queries used to retrieve historical shift data for these two rules have been consolidated, significantly reducing the number of queries required during calculation. This improves CWSS Server performance for customers who have enabled the functionality introduced in build Build 1707976, while maintaining the same reduced memory footprint.\n\nIn addition, several edge cases in the underlying rule calculations have been hardened. Requirement violations for these rules are now updated correctly and immediately after shifts are assigned or unassigned, correctly follow resources linked to a contract, and remain accurate when multiple schedules are displayed simultaneously on the plan board.\nSupporting database indexes and the stored procedure associated with the ROS_REQUIREMENT_SHIFTS table have also been updated to further improve performance.\n \nThis improvement continues to be controlled by the existing settings:\n- FeatureToggles\\UseLoadingHistoricalRequirementShiftDataNofFreeWeekendsReq\n- FeatureToggles\\UseLoadingHistoricalRequirementShiftDataNofDaysReq\nBoth settings remain disabled by default. It is advised to enable these feature toggles only if the customer situation requires it (from a memory perspective) and only in consultation with Product Support.\nNo additional settings have been introduced.\n\nTest hint(s):\n\n1. Verify \"number of free weekends\" and \"number of days\" requirement violations are calculated correctly across various scheduling periods and period kinds, for both standalone resources and resources linked to a contract\n2. Verify that unassigning a shift which resolves one of these requirement violations clears the violation immediately on the plan board\n3. Verify requirement violations remain correct when multiple schedules are visible together on the plan board\n 4. Verify CWSS Server performance (query count / calculation time) for these two rules has further improved compared to phase 1, with no change in behavior when the feature toggles are disabled","","143126",""]
[null,null,1708625,"2026-08-11","Y","Development\\OWS and Enablers\\OWSforTeamSchedulers",null,null,null,"Rule violation messages when saving a shift are shown in the application language","When a shift change was blocked by a hard rule, the message that explained why was always shown in English, even when the application used another language.\r\nThis has been fixed.\r\nThe message now follows the language of the application.","","143599",""]
[null,null,1708625,"2026-08-11","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Allowed expression in the settings value for three \"maximum number of days in the past...\" settings","It is now possible to provide expressions and numerical values to the following settings in the OWS settings manager:\n\\CLOCKING\\MAXNOFDAYSINPASTTOOPENCLOCKINGOVERVIEW\n\n\\OPTIONS\\PLANBOARD\\MAXNOFDAYSINPASTTOOPENROSTERS\n\n\\OPTIONS\\RUNNINGACCOUNTS\\MAXNOFDAYSINPASTTOOPENRUNNINGACCOUNT \nThis allows for a flexible minimum from date when opening the associated windows (Clocking overview, planboard/Master schedule and running account respectively).\nThese settings are only checked if the user does not have permission in access control to view clockings/rosters/running accounts in the past\n\nTest hint(s):\n1. Fill in an expression into the settings mentioned above. Open one of the associated windows and select a from date before that lies before the \"maximum number of days\" window. Verify that the client shows a warning","For this solution to become available, the ORTEC WS Win32 client must be installed.","143838",""]
[null,null,1708625,"2026-08-11","N","Development\\OWS and Enablers\\OWS7",null,null,null,"BI - Duty demands include demands on holidays of closed/replaced duties","Stored procedure GETDEMANDEDDUTIESFORDEPS could return demanded duties on holidays for duty that are no longer valid.\r\nThis has been fixed.\r\nThis changes is introduced behind feature toggle FILTEROUTINVALIDHOLIDAYDUTIES, enabled by default.\r\n\r\nTest hint(s):\r\n1. Run a BI load for a period that contains a holiday. Verify that no demands of invalid duties have made it in the BI database.","This procedure is used by BI to fill FACT_SHIFT_DEMAND with demanded duties","83837","https://ortec.link/Request?HID=16993395"]
[null,null,1709026,"2026-08-25","Y","Development\\OWS and Enablers\\OWS7",null,null,null,"Opening the search-by-employee-number window could take a long time and make ORTEC WS Client temporarily unresponsive when a department had many employees","Opening the search-by-employee-number window could take a long time and make ORTEC WS Client temporarily unresponsive when a department had many employees\nThis has been improved\n\n The search-by-employee-number window now also takes into account the \"only consider resources without a contract end date\" option, matching the rest of the Employee window\n\nTest hint(s):\n1. Verify that opening the search-by-employee-number window for a department with many employees opens correctly and does not show 'not responding' in the application caption bar\n2. Verify that enabling \"only consider resources without a contract end date\" on the Employee window also filters the employee-number search list, and that disabling it shows all employees again","For this solution to become available, the ORTEC WS Win32 client must be installed.","102235","https://ortec.link/Request?HID=17031968"]
[null,null,1709026,"2026-08-25","Y","Development\\OWS and Enablers\\OWS7",null,null,null,"Using plan in activity type across multiple schedules could lead to an incorrect weekend or holiday shift","Planning an activity type across multiple schedules could incorrectly create a weekend or holiday shift on the final selected day when that day was the first day of the next roster period.\r\nThis has been fixed.\r\n\r\nTest hint(s):  \r\n1. Open two schedule, with the second schedule starting on a weekend- or holiday. Plan in activity type for a few days ending in the first day of the second schedule in a single action. Verify that this does not create a shift on the weekend-/holiday.\r\n2. Plan in an activity type on only a weekend- or holiday for the individual day, verify this does create a shift on that day","","129580","https://ortec.link/Request?HID=17044474"]
[null,null,1709026,"2026-08-25","Y","Development\\OWS and Enablers\\OWSforTeamSchedulers",null,null,null,"Certain schedules were not visible on the dashboard when proposal departments were set at higher organizational levels","Certain schedules were not visible on the dashboard when proposal departments were set at higher organizational levels, and loading times were slow for environments with many proposal departments. \r\nThis has been fixed and improved.\r\n\r\nA new CSCS setting has been added that can be used to revert to the old behavior: TeamScheduling\\FeatureToggles\\RosterPeriodsQueryImprovedPerformance (default True).","","142940",""]
[null,null,1709026,"2026-08-25","N","Development\\OWS and Enablers\\OWS7",null,null,null,"Processing incoming updates could in some cases cause unnecessary blocking of other database operations.","Processing incoming updates could in some cases cause unnecessary blocking of other database operations.This has been improved by optimizing the update process, helping to reduce unnecessary database blocking while maintaining correct update handling. \n\n Feature toggle involved: UseIsolationLevelForReadingUpdatesWhenApplyingUpdates (disabled by default). Note: Only an ORTEC consultant may change this setting in consultation with the Maintenance department.\n\nTest hint(s): \n1. Verify updates are applied successfully under concurrent load with the default configuration\n2. Verify transaction behavior remains stable when the toggle is turned on","","144328",""]
[null,null,1709026,"2026-08-25","Y","Development\\OWS and Enablers\\OWS7",null,null,null,"Refreshed ORTEC branding in OWS Win32 Client","The OWS win32 Client displays refreshed 2026 branding in its splash screen, About window, caption styling, and application icons\n\nNOTE: The application icon has changed significantly, This might cause a user to search or miss the application.\nKnown issues:\nWindows explorer: icons are cached for i.e. desktop/taskbar possible fix: use command 'ie4uinit.exe -show'  Windows explorer: when shortcuts have been created referencing older binaries the old icon will be shown in shortcut and as application icon workaround: refresh the binaries used in the shortcuts for the icon, and update the icon using 'Change Icon...' in 'Properties' context menu of shortcut\n\nTest hint(s):\n1. Start the OWS Client and verify the new splash screen, logo, colors, and progress display are shown\n2. Open the About window and verify the updated branding while confirming normal Client startup and scheduling workflows remain available","For this solution to become available, the ORTEC WS Win32 client must be installed.","144470",""]

{"sheet":"Blad1","index":1,"n_rows":0,"n_cols":0,"rows_kept":0,"cut":false,"hidden":false,"merged":[]}