DRS 6.1.19 - 11th April, 2025

Type

Issue Key

Description

Change Notes

Issue

DRS-8428

The order of operatives within a saved Diary Bookmark does not display as saved if updated after creation.

A change has been made to update the ORDER BY value in the diary display request to better reflect the saved changes.

Issue

DRS-8499

Importing Sectors fails when using Complete Restoration without displaying a valid failure reason.

The import command was incorrectly applying feature rights and profile permissions which resulted in DRS denying the operation due to invalid user permissions.  This has been updated to ensure the correct user profile rights are applied during the Import and Export routine.

Issue

DRS-8517

Exporting large datasets causes a error from the Import Export routine

A timeout designed to protect product stability and performance was being exceeded during the export request.  A new parameter has been added 'com.kirona.drs.ignoreTimeoutForImportExportRequests'. 

For customers experiencing this issue, the value should be set to FALSE, which will disable the timeout set for exporting large datasets.

Issue

DRS-8609

Duration adjustment is not being taken into account for all jobs when using various appointing methods

A change has been made  where the manual assignment will now correctly show the assigned period of the popup and schedule the job with the adjusted duration. The duration will still show 60 minutes but the final duration on the worker request will be the value with efficiency.

Note: For a multi worker job the duration assigned period will be set to the worker with the highest duration after efficiency and both schedule items will have this duration. 

Issue

DRS-8413

"Use Contract during load" not respecting operatives that are set to that contract within Project Planner Web

A change has been made so that all operatives with a CONTRACT attribute set as a connected Service Order attribute will apply correctly during the Load function

Issue

DRS-8421

If SORs are not configured in DRS, PP will not process an OrderAmendment

The logic for OrderAmendments and OrderCreates has been changed to allow for these requests to be processed through the WebService and Inbound Connector to Ignore the missing SOR values and continue to process all items which are correctly configured within DRS.

Issue

DRS-8518

Unable to Zoom on initial planning board load

This issue of not being able to zoom happens when a diary template without a planning configuration is used. A change has been made to set the diary display hours from the standard configuration if no project planner configuration is present in the selected diary template.

Issue

DRS-8809

Number of retries does not match in Background Services error handling

Background Services was looking for the highest error count value to add 1 to, but instead of looking for the highest error count value for that job it looks at all jobs being processed in the current run. This means that if there is a job that is 1 away from the maximum in the current run, but the job being processed has an errors count much lower it will still think that it has reached the maximum and set the row to actioned for the current job.  This has been resolved and now all tasks will respect their error count.

Issue

DRS-7879 and

DRS-8089

Unavailabilities and Travel Time not showing after housekeeping has run

An issue was found with the way Housekeeping was recording unavailability and travel when moving objects to the Past.  This has been resolved going forward. 

A resynchronisation following a patch will restore un-displayed data.

Issue

DRS-8525

Quotas ignore worker duration adjustment

Duration adjustment was being incorrectly applied when calculating Quota availability.  This will now calculate availability correctly, taking into account duration adjustment

Issue

DRS-8579

Violations & system booking over quota limit

DRS was incorrectly reporting a violation of planning when Quota availability was being incorrectly calculated after schedule.  This has now been resolved.

Small Enhancement Request

DRS-8468

The USERID value being passed through in API responses is not as expected

A new setting has been created;

'tblConfigurations.UserIdBDFieldName';

with the name of a business data field to use for populating the USERID FIELD. It is set with a default value of USER_QUEUE.

This will then return the configured value in the USERID field within the API XML.

If the TBLCONFIGURATIONS value is empty or doesn’t match to a valid business data then continue returning the USER_QUEUE as default. 

SmalL Enhancement

DRS-8477

Implement Pendo in DRS 6

Pendo has been released in DRS 6.1.19 enabling a deep feature set of customer communication.

Small Enhancement Request

DRS-8819

Add new parameter to disable OrderAmends on Project Planner

New Parameters have been created within TBLCONFIGURATIONS to allow OrderAmendment requests to be ignored.  It is set to FALSE by Default.

Webservice Property: optitimeweb.IgnoreProjectPlannerOrderAmends with a default of false.

Inbound Connector property: IgnoreProjectPlannerOrderAmends with a default of false

If either property is set to true, when an order amendment is received for project planner it will not process any details and return success.

Function

Version

DRS Server (Kernel)

6.3.1.9

Background Service

6.1.19

Connector Services

6.1.19

Inbound Connector

6.1.19

Mobile Gateway

6.1.19

Project Planner

6.1.19

Utility Service

6.1.19

DRS Web Services Gateway

6.1.19

Archive/Housekeeping 

6.1.19

UK Geocoding Postcode Database

07/2022

Description

Version

Apache

2.4.63.0

Java

8.442.06.1

MariaDB

10.6.17.0

MariaDB Java Client (JDBC)

3.1.2

php

8.3.14

Tomcat

9.0.102.0

Tomcat Native

2.0.3.0

.Net

4.7

SoapUI

5.7.2