Contents
- Fixes and Resolutions
- Reference field is not populated on scheduleItem for PP Jobs
- TargetDate field in Audit Log has incorrect formatting on insert field causing errors
- Splitting a Package Giving Unknown Error message
- Passwords are displayed in clear text in some server audit logs
- Unable to pull down any Project Planner jobs to mobile via Mobile Gateway
- New Projects are not populating the Name field correctly
- Split Project Package by Time does not allocate SOR's to the split package
- MESSAGE business data value is not being populated as expected when presented with [CDATA] references.
- Manual Scheduling worker selection can display an error when using a MultiKernel environment
- Error setting up new tenant code rule when including spaces in the rule name
- Internal Component Versions
- External Component Versions
DRS 6.1.16 - November 8th, 2024
Updated
by Andrew Dotto
- Fixes and Resolutions
- Reference field is not populated on scheduleItem for PP Jobs
- TargetDate field in Audit Log has incorrect formatting on insert field causing errors
- Splitting a Package Giving Unknown Error message
- Passwords are displayed in clear text in some server audit logs
- Unable to pull down any Project Planner jobs to mobile via Mobile Gateway
- New Projects are not populating the Name field correctly
- Split Project Package by Time does not allocate SOR's to the split package
- MESSAGE business data value is not being populated as expected when presented with [CDATA] references.
- Manual Scheduling worker selection can display an error when using a MultiKernel environment
- Error setting up new tenant code rule when including spaces in the rule name
- Internal Component Versions
- External Component Versions
Development of DRS Version 6.1.16 is now complete and was released in November 2024. DRS 6.1.16 is a maintenance release containing a number of fixes for issues reported since the release of 6.1.15. It can be deployed as a patch version to 6.1.15
Fixes and Resolutions
Type | Issue ID | Summary | Change Notes |
Issue | DRS-8408 | Reference field is not populated on scheduleItem for PP Jobs | An issue was found with the Webservice integration concerning Project Planner jobs where a reference field was not being included on the stored SOR within the Project Planner ScheduleItem table. This is a mandatory field for specific integrations. This has now been resolved. |
Issue | DRS-8394 | TargetDate field in Audit Log has incorrect formatting on insert field causing errors | String Field Types have now been set on Patch upgrade and Full Installation for all date type fields in the Audit Log |
Issue | DRS-8375 | Splitting a Package Giving Unknown Error message | Splitting a package by SOR code required the user to have access to the 'EDIT SOR' permission to be enabled on the Users profile. This is not optimal for security reasons. The permissions have been separated so this function will now work as expected without enabling that permission. |
Issue | DRS-8374 | Passwords are displayed in clear text in some server audit logs | Passwords have now been obfuscated in all system logs. |
Issue | DRS-8373 | Unable to pull down any Project Planner jobs to mobile via Mobile Gateway | An error was found in the SQL required to pull jobs down using the Mobile Gateway where ambiguous SQL statements were used. The SQL associated with Mobile Gateway has been updated to remove ambiguity. |
Issue | DRS-8372 | New Projects are not populating the Name field correctly | The Project Name field was set to only accept configuration in full caps. Now configuration is accepted in Proper Case, Lower case and Uppercase. |
Issue | DRS-8313 | Split Project Package by Time does not allocate SOR's to the split package | When splitting packages by Time, SOR's will be duplicated to ensure that each appointment is provided an appropriate SOR within the appointment confirmation. |
Issue | DRS-8311 | MESSAGE business data value is not being populated as expected when presented with [CDATA] references. | An update has been made to the webService orderCreate request to allow additional possible values in the <message> tag to set the MESSAGE business data item to YES or NO. These values are, 'true', 'True', '1', which will set the value to 'YES', and, 'false','False','0', which will set the value to 'NO' |
Issue | DRS-8274 | Manual Scheduling worker selection can display an error when using a MultiKernel environment | An issue was resolved in the Worker Selection modal assigned to Manual Assignment. This issue presented for MultiKernel configured customers. This has now been resolved. |
Issue | DRS-8115 | Error setting up new tenant code rule when including spaces in the rule name | Spaces were being rejected as part of the Tenant Code Rule name. This was causing an issue for a customer with their Housing system configuration. This has now been resolved and spaces can now be used within the Tenant Code rule name |
Internal Component Versions
Function | Version |
DRS Server (Kernel) | 6.3.1.9 |
Background Service | 6.1.16 |
Connector Services | 6.1.16 |
Inbound Connector | 6.1.16 |
Mobile Gateway | 6.1.16 |
Project Planner | 6.1.16 |
Utility Service | 6.1.16 |
DRS Web Services Gateway | 6.1.16 |
Archive/Housekeeping | 6.1.16 |
UK Geocoding Postcode Database | 07/2022 |
External Component Versions
Description | Version |
Apache | 2.4.62.0 |
Java | 8.372.07.1 |
MariaDB | 10.6.17.0 |
MariaDB Java Client (JDBC) | 3.1.2 |
php | 8.3.11.0 |
Tomcat | 9.0.95.0 |
Tomcat Native | 2.0.3.0 |
.Net | 4.7 |
SoapUI | 5.7.2 |