Contents

DRS 6.1.18 - 13 February 2025

Andrew Dotto Updated by Andrew Dotto

Development of DRS Version 6.1.18 is now complete and was released in February, 2025. DRS 6.1.18 Contains a number of updates and fixes to ensure the product remains stable and secure. It can be deployed as a patch to version 6.1.17.


Notable Issue Resolutions

Changing a value on a Worker Template Attribute changes the value in all Worker Templates (DRS-8461)

What have we done?

A major change to the way we manage Worker Template Attributes in DRS 6. This will effect the recorded ATTRIBUTE ID for all new Attributes created on a Worker Template.

Why have we done this?

DRS allowed for Worker Template Attributes to use the same ID and NAME values for consistency, which resulted in the same values being shared across all Worker Template Attributes of the same ID. When attempting to use different lists of values using Attributes which shared the same ID value, all listed values would be updated across all Attribute lists on all Templates. This was resulting in unexpected selection options in varying Worker Templates.

How will you benefit?

DRS will now automatically apply an increment value to all Attribute ID's where the value already exists. This change will not resolve any existing issues where attribute ID's are shared across existing Templates.

Details of the change

When creating new Worker Template Attributes, DRS will now do a check to determine if that Template Attribute already exists. If it does, DRS will automatically apply an incremented value to the end of the Attribute ID.

Example: An attribute has been created with an ID of "SKILL". DRS will check if an Attribute with an ID of "SKILL" exists, if it does, DRS will change this value to "SKILL_1". The NAME field for this Attribute will remain unchanged.

This will resolve issues for all new Attributes created. If there are any existing Attributes with shared ID fields that you would like to maintain separate scheduling values for, you will need to create a new Worker Attribute and make the necessary Template and Worker changes to manage your future scheduling.


Component Update: Upgrade the version of 7Zip released with the application (DRS-8501)

What have we done?

We have released a new version of 7Zip deployed within the APPS folder in the DRS installation.

Why have we done this?

The deployed version was reported as compromised.

How will you benefit?

All bundled applications within the APPS folder will be deployed with stable reported versions.

Details of the change

The latest version of 7Zip will be deployed with all new deployments of DRS.



Component Update: Java Version Upgrade (DRS-8488)

What have we done?

This release is aligned with the latest versions of available supporting infrastructure

Why have we done this?

Aligning DRS with latest infrastructure releases ensures DRS maintains a secure and stable posture.

How will you benefit?

Latest infrastructure patches contain security and performance improvements.

Details of the change

The following versions of product will be released with DRS 6.1.18:

Java - 8.442.06.1

NOTE: A Manual Command is required to be run on upgrade to ensure this deploys.  Please read the README file within the release for more information.



 Other Fixes and Resolutions

Type

Issue ID

Description

Change Notes

Issue

DRS-8352

Unable to Replace Project Package Error displayed when creating a follow on

When attempting to create a follow on for a Package within Project Planner, an issue was found that would result in the system displaying the error message 'Unable to replace Project Package'. The issue happens because of some flawed logic which tries to find the highest value of the Sorcode item number when special characters are used within the ProjectID and or Project Name.


This has now been resolved and the SOR selection will no longer fail this request.

Issue

DRS-8460

Business Data Audit field resets after full product restart

When setting a piece of Business Data to 'Audit', a full product reset would clear this flag and set the default value as the 'Audit' field for the History tab.


This issue was caused by hard-coded default settings in some customer deployments.  This change will now mean the configuration on all new installs will be removed from the hard coded option to allow the UI to set this correctly. 


For upgrades and imports, the values that are already in the database already will be kept and used.

 

When upgrading a customer it will be necessary to amend the file \\DRS\CONF\custom.properties and \\DRS\TOMCAT\SERVICES\TOMCATxCSxXXXX\webapps\opt-ffa-connector-services_optitimeweb\conf\user.properties and remove references to (if configured): com.kirona.drs.audit.jobBDToStore=APPOINTMENT_REASON

Issue

DRS-8471

Has Follow On Flag does not filter correctly within views

When adding the 'Has Follow On' flag to views and attempting to use this to Filter, the selected Filter options are not respected and will always show all tasks which have a follow on.


Yes/No Flags were not being interpreted correctly within some View configurations.  A change has been made for all Yes/No flags to now be interpreted correctly.

Issue

DRS-7971

Appointment Assignment for Templates with Multiple Skills is not properly respected

If a Job Template has multiple values assigned to an Attribute, DRS is not respecting all values when attempting to find available operatives for scheduling, and instead, will select any operative with either value configured.


It was found that the getPossibleWorkers command was not using all configured options to determine who was available for scheduling.  This will not consider all possible values when multiple values are configured.

Issue

DRS-8371

View Name not showing correctly in dropdown list

When loading a screen with a selectable View, there are instances where these names will not be displayed correctly and will use the system value name for the configured View. The issue occurs because the data source was being applied to the combo box before an ItemCaptionGenerator has been set. 

A change has been made to all components where an ItemCaptionGenerator is used and made sure the data source is set after the caption generator.

Issue

DRS-8438

Operative Comments are not flowing through to Project Planner from Mobile

When jobs are completed in Mobile, Operative Comments are passing through to the DRS Job correctly, but are not being mapped to the Project Planner Diary Item as part of the object updates. A mapping issue was found with Project Planner updates. 

This has been changed so that comments will now be correctly passed through to the project package schedule item and project package when the associated job is updated.

Deployment

DRS-8491

A disabled Admin Account will terminate an upgrade attempt

If a customer disables the default ADMIN user account within their environment, any attempt to complete an upgrade will miss several key component updates.

Upgrades will now temporarily enable the default Admin account to allow necessary changes to complete

Issue

DRS-8441

Profile Restrict by Template is not respected fully

When using the 'Restrict Job Template' option within the user profile, it is not masking all configured Job Templates and I am able to select from a variety of Templates which should be hidden from me.  Within Views, details of Templates are provided which should be restricted to me.

A change has been made for Job views to now only show jobs with the allowed templates. A new warning will be displayed at the bottom of the selected view.

Issue

DRS-8454

Project Planner Diary items are assigned to a worker on their non-working day

Project Planner Diary Items are being scheduled to Operatives on Non-Working days for some configured Rotas. This issue was caused by the calculation to work out what day in the rota it needed to start from when calculating availability was incorrect. The calculation was always one day behind where it should be, so if the package period started on the 20/01, which relates to day 10 in the rosta calendar, and day 10 is a day off, the calculation would start it at day 9. If day 9 was a normal working day then it would schedule the package thinking there was space on that date, instead of moving on as it was actually unavailable.

This has now been updated to ensure the availability check only returns available time.

Issue

DRS-8469

The Delete un-started diary items option completes the diary items instead

Using the 'Delete Unstarted Diary Items' option on the Status Update function for the Project Package, some instances of Diary Items are not being deleted. The problem occurred when an Sor code with a high quantity (eg. quantity 10, SMV 120) was split over multiple diary items. The planned diary items were deleted but another update then changed the status of those items to completed which reinstated the items. 

This has now been resolved to correctly complete the Package and remove the unstarted Diary Items.



Known Issues



Internal Component Versions

Function

Version

DRS Server (Kernel)

6.3.1.9

Background Service

6.1.18

Connector Services

6.1.18

Inbound Connector

6.1.18

Mobile Gateway

6.1.18

Project Planner

6.1.18

Utility Service

6.1.18

DRS Web Services Gateway

6.1.18

Archive/Housekeeping 

6.1.18

UK Geocoding Postcode Database

07/2022

External Component Versions

Description

Version

Apache

2.4.62.0

Java

8.442.06.1 (From 8.372.07.1)

MariaDB

10.6.17.0

MariaDB Java Client (JDBC)

3.1.2

php

8.3.14

Tomcat

9.0.98.0

Tomcat Native

2.0.3.0

.Net

4.7

SoapUI

5.7.2

Was this article useful?

DRS 6.1.19 - 11th April, 2025

DRS 6.1.17 - 20th December 2024

Contact