Please enable JavaScript to view this site.

Control Tower v22.0.0 - Operations Guide

Navigation: Previous Releases List

Version 21.0.1

Scroll

Note: The Item reference numbers in the document are from the BluJay Solutions Control Tower issue tracking system and are intended for use by BluJay Solutions Support.

 

Feature Enhancements

Item Ref.

Summary

KCT-16507

Transport Order Enhancements

 

What’s New:

The behaviour of routing information while creating a new T.O on the basis of an existing T.O. is enhanced.

Vehicle details that are mandatory in XML till now are made as non-mandatory.

 

Summary:

When a T.O. is created using CREATE BASED ON or T.O. DUPLICATE system function, the routing information that is available on the existing T.O. will not be copied over to the new T.O.

When Routing information is added for a T.O., the T.O. can now be successfully exported or imported even without entering vehicle details.

To reflect the enhancement, both Import & Export T.O XSD's have been modified by making the <Vehicle> segment and <VehicleID> tags non-mandatory.

 

T.O. Upload using excel sheet format

Now, user can provide both vessel and voyage details while uploading a T.O. using excel sheet.

The excel sheet format has been enhanced by adding another set of VehicleID and VehicleLabel fields.

The fields have been renamed to VehicleID1, VehicleLabel1 & VehicleID2 & VehicleLabel2.

When a TO is uploaded with these details, the data will be saved in the respective fields in the application.

 

T.O. XML Import or Export

Now, T.O XML can be successfully imported or exported even without <Vehicle> segments.

When an XML is imported or exported with <VehicleLabel> tag alone without <VehicleID> XML, the data will be inserted as Null against <VechicleID> in tbltoroutinginfo table.

 

WSO2 Mapping Changes:

With the current enhancement, when data is available in <VehicleID> tag, it will be sent to TMFF. If data is not available in <VehicleID> tag, then no data will be sent to TMFF.

If a T.O has data in <VehicleLabel> tag and data is not available in <VehicleID> tag, then no ­­data will be sent to TMFF.

 

 

 

Bug Fixes

Item Ref.

Summary

KCT-16852

Issue:

When an XML that was not well-formed was­­­­ received by Control Tower from an external system, the XML was being held in the same folder. This was causing issues in processing other files that were in queue.

 

Solution:

The issue is addressed by moving the malformed XML into a separate folder in wso2 so that the processing of files in queue will continue without hampering.

KCT-16942

Issue:

When Document Type was not added to FileShare Category, documents were not being attached to alert emails.

 

Solution:

The issue has been addressed. Now, documents will be attached to alert mails as per notification layout configuration, regardless of the addition of Document Type to the Fileshare Category.

 

KCT-16958

Issue:

In Custom Report, milestone date columns were displaying values based on user time zone without considering the case of ‘Daylight Saving Time’. Hence, the Date & Time values were incorrectly being shown.

 

Solution:

The issue is fixed, and the milestone date columns are now displaying correct dates.

KCT-16972

Issue:

Due to the generation of high volume of alerts in the given interval, alerts were not triggered as per the calculated due date time stamp.

 

Solution:

The issue has been addressed, and the alerts are consistently being triggered.

 

CONFIDENTIAL © 2018 - 2021 BluJay Solutions Ltd. All rights reserved.