KCT-14055

Issue:

By default, File Share Category was showing all categories along with the list of Document types linked to those categories.

Solution:

Now, the File Share Category will only show Document type with linked File share category and File Share Categories list that are created without linking any document type.

KCT-14672

Issue:

On Shipment dynamic screen, upon double-clicking a grid line record, the system was displaying shipment header view.

Solution:

The issue is fixed. Now, when user double-clicks any grid line record, the respective form for shipments will be opened in a pop-up window.

KCT-15674

Issue:

T&T Item and Container linked navigation were showing inconsistent behavior with respect to display of the fields list.

Solution:

The issue is addressed, and the container details are now consistent through all the views.

KCT-15719

Issue:

T&T Container screen was not showing expected details.

Bug Cause:

Due to incorrect retrieval query, expected data did not show up in T&T Container screen.

Solution:

Retrieval query is corrected, and the T&T screen is now working as expected.

KCT-15726

Issue:

EnablePartyAccessAuthorization system parameter was causing access denial on all menu navigations when set to Y.

Solution:

Authorized party access users can view the shipments

and conduct the business operations when the parameter is set to Y.

KCT-15768

Issue:

Additional Service field value was not being carried over from Template to the shipment screen.

Solution:

The Additional Service field value set at Template is now being carried over to shipment screen while creating the shipment using Template.

KCT-15794

Issue:

Users were not able to search for companies or relations with “&” character in the name.

Solution:

Users can now search for companies (by name) or relations (by company) with “&” character in the company name.

KCT-15806

Issue:

On Alert profile screen, system was clearing the selected Main group value upon selecting another field.

Solution:

The issue is addressed, and users can now add Alert Profile as per expected configuration.

KCT-15808

Issue:

Container Number was being defaulted while adding a milestone.

Bug Cause:

It is because, if a drop-down field has only one value, that value will be defaulted based on the current system behavior.

Solution:

For Milestone component, the value defaulting behavior for Container Number field has been removed. Now, the Container Number is not being defaulted while adding a milestone even in case of one Container per T.O.

KCT-15810

Issue:

Mandatory validation of Item dimension subframe was failing.

Solution:

When Item dimension subframe is configured as mandatory and a user attempts to save an Item without filling the Item dimension record, the system will display a mandatory subframe missing validation message to the user.

KCT-15814

Issue:

'dorderdate' field was set as Mandatory in PO Uploads, whereas it was set as optional in Import XSD. This difference was causing some discrepancy while creating Shipments.

Solution:

Like XSD definition, the ‘dorderdate’ field is set as optional in PO Uploads.

KCT-15817

Issue:

Dimensions were not being properly calculated and updated on the dimensions window due to a script issue.

Solution:

Logic of the calculation of dimensions is fixed. The dimensions are now correctly calculated and updated irrespective of UOM changes.

KCT-15824

Issue:

Functionality of PO_Delivered_Milestone system parameter is not working.

Solution:

Whenever PO_Delivered_Milestone is configured and fully confirmed P.O. based T.O. is created, the milestone will be added to the P.O. when the status of P.O. is changed from Confirmed to Delivered.

KCT-15841

Issue:

VBE next profile field was being defaulted to existing single process.

Bug Cause:

It is because, if a drop-down field has only one value, that value will be defaulted based on the current system behavior.

Solution:

For VBE Next profile item field, the value defaulting behaviour has been removed.

KCT-15845

Issue:

Non-Standard parties were not getting copied from Template while creating shipment using Template.

Solution:

The issue is addressed and now all set parties are correctly flowing into the new shipment created using Template.

KCT-15848

Issue:

P.O. Dispatch was blocking T.O creation for P.O.s with two-line items (confirmed) when client did not have a configured Business unit.

Solution:

User can now create a T.O. via P.O. Dispatch for P.O.s with more than one-line item (confirmed) even when client does not have a configured Business Unit.

KCT-15877

Issue:

T.O. Container - Sequence No field was not being updated properly when multiple containers were added.

Solution:

When user attempts to add multiple containers for a T.O., the records will be sequentially numbered in the Sequence No field.

KCT-15942

Issue:

Shipments were failing to get accepted by TMS due to the empty tag generation of ‘Instructions’.

Solution:

The integration issue has been addressed and shipments are successfully getting accepted by TMS.

KCT-15946

Issue:

Secondary process shipment is not showing under correct process.

Solution:

When user configures a secondary process for P.O. and/or T.O. and conducts the secondary process operation, shipment will be shown under the respective process heading in Task List and Pivot tables as well.

KCT-15964

Issue:

User was receiving T.O. XML for every Status export.

Solution:

The Status EDI is fixed. Now, for any milestone that is set to export, T.O. XML auto generation is controlled, and user will only receive the Status export.

KCT-15869

Issue:

Reports and Track & Trace were showing different results for same criteria.

Bug Cause:

This was due to Reports having one additional flag which was not considered in T&T

Solution:

The additional check at Reports is cleared, and Reports and Track and Trace show same results for same set of criteria.

KCT-15981

Issue:

On Carrier screen (System Maintenance > Static Look-up > Carrier), when a search was performed based on Mode of Transport, the system was showing ‘No matching records found’ message even when matching records were there.

Solution:

Mode of Transport based search on the Carrier screen has been fixed and the system is accurately displaying the results.

KCT-16015

Issue:

User was experiencing page display issues while navigating between Custom report results pages (Query retrieval).

Solution:

The system is now appropriately displaying the results while navigating between the Custom report results pages.

KCT-16020

Issue:        

When FileShare search was performed, the results were either empty or displayed with error even when relevant files were there.

Solution:

The issue is addressed and when FileShare search is now performed, the results are accurately displayed.

KCT-16029

Major security fixes have been applied in Control Tower.

KCT-16039

Issue:

In all standard reports, the download process for CSV format was showing 0 KB.

Solution:

The issue is addressed, and user can now download and email the report results in CSV format.

KCT-16040

Issue:

User was experiencing a never-ending loading screen when PO specific global search action was performed.

Solution:

The page loading issue is handled and when user performs global search based on the criteria, the system fetches and displays the results.

KCT-16046

Issue:

The system was throwing an error message when user tried to upload and save the company logo.

Solution:

The issue of saving and retrieval of the Company logo is resolved, and the company logo uploaded by the end user is getting reflected immediately upon save.

KCT-16060

Issue:

In shipment Parties subframe (P.O. and T.O.), when only one value was available in Party Type ID list, Party Type ID was getting cleared while selecting and saving the party.

Solution:

User is now able to save Parties even when the Party ID list has one value.

KCT-16061

Issue:

P.O. header level status was not updated correctly when shipment had more than one item record.

Bug Cause:

P.O. header status was updated based on the confirmation status of first item, hence the mismatch of expected vs actual shipment status.

Solution:

P.O. header status is now being updated considering all the P.O. item confirmation records of the shipment.

KCT-16065

Issue:

On Company Relation screen, when 'Default PO Qty as TO package Qty' was set to N, it was not allowing the available packages of P.O. Conf to flow to T.O.

Solution:

When user sets 'Default PO Qty as TO package Qty’ to N and when packages are available at P.O. Conf, those will now flow to dispatch screen and to T.O. as well.

KCT-16073

Issue:

Under P.O. Dispatch grouped by P.O., search based on Goods Ready date was not fetching any results.

Solution:

The issue is handled and now system is displaying search results based on Goods Ready date set value.

KCT-16084

Issue:

When KEF_Variable_Filed_Lengths system parameter was set to Y, Item Weight and Net weight fields were being auto calculated based on the Dimension.

Bug Cause:

For T.O. Import, KEF_Variable_Filed_Lengths system parameter was not validated.

Solution:

The system parameter is validated. Now for any T.O. import if the KEF_Variable_Filed_Lengths system parameter is set to Y, Item Weight and Net weight fields are not being auto calculated based on Dimension.

KCT-16086

Issue:

When a country does not have date-format and decimal-format set at country master level, System default values are considered. Due to retrieval data type conflict, Party Import for the above case was failing.

Solution:

The retrieval data type conflict has been fixed. Now, when a country does not have date-format and decimal-format set at country master level, System default values are considered during the Party Import and Party will get created.

KCT-16088

Issue:

Unable to create company.

Bug Cause:

Due to duplicate GID, system was not allowing to add company with existing GID.

Solution:

The issue is handled, and users are now able to add companies in the application.

KCT-16093

Issue:

Even when Party Type ID was set to empty/no selection,

previously selected Party Type ID based companies list was persisted in the Company ID field.

Solution:

The persistence of loaded Companies list in Company ID is handled. Now, whenever the Party Type ID is changed from any selected value to empty, the linked Company ID field will reset to 'No matching records' display upon search.

KCT-16108

Issue:

Due to a Home page session glitch, an unnecessary 'Back to Dispatch List' button was showing up.

Solution:

The issue is addressed, and user does not see the unwanted button any more during operational flows while navigating between the dispatch, home, and any shipment screens.

KCT-16119

Issue:

A prefix 'EPOMS T.O./P.O.:' was automatically getting added to the subject of the FileShare Documents email.

Solution:

The prefix has now been changed to 'Ref:’ which automatically gets added to the subject of FileShare Documents email.

KCT-16120

Issue:

While adding an item to T.O. based on P.O. item, Quantity Type on T.O. Item screen was being defaulted to Package Type instead of P.O Item’s Quantity Type.

Users were able to select the Quantity Type along with Quantity while creating a T.O. Item on Add matching conf’s screen.

Solution:

Quantity Type associated issues are now addressed.

Quantity Type on T.O. Item screen is being defaulted to P.O Item’s Quantity Type.

Quantity Type field is disabled while creating T.O, and users will not be able to select it on Add matching conf’s screen.

KCT-16130

Issue:

PO & TO Remarks email subjects were not displayed as per the set System Parameter values.

Solution:

The issue has been addressed, and the PO and TO remarks email subjects are now displayed based on the respective System Parameter values.

KCT-16208

Issue:

While dispatching P.Os to create a T.O., the available references were not flowing from P.O. to T.O.

Solution:

The issue is addressed, and the available references are now flowing from P.Os to T.O. while creating a T.O.

KCT-16232

Issue:

Keyboard key (TAB) was appending one space against navigated field values in back-end.

Solution:

The space appending issue is fixed.

KCT-16239

Issue:

Fields alerts were sent more than once for every user action over the Dynamic screen.

Solution:

A Condition has been applied, so that, for any set field alerts configuration, Email would be triggered only under the following two conditions:

1.Field value when changed to other value

2.Field value when changed to blank (based on field type). 

KCT-16242

Issue:

TO Item description with special character ' (Single quote) was causing shipment saving issue.

Solution:

This is handled and both Import and Exports are working fine with the single quote including the max field length text.

KCT-16264

Issue:

TO PTT Container URL had an issue while decoding.

Solution:

The issue is fixed and all TO PTT screens are now properly being displayed.

KCT-16279

Issue:

During the addition of Schedule Reports, blank page was displayed while saving.

Solution:

Phrase code corrections are done on Schedule Report screen and the blank screen is not displayed anymore.

KCT-16282

Issue:

Job Type field value was getting copied while user was creating TO using 'Based On' feature.

Solution:

Job Type field is now categorized as field which will not copy the value upon duplicate actions like, 'Based On', 'Template' and 'TO Duplication'.

KCT-16286

Issue:

Users with Party Names containing single quote character had issue with Pivot display.

Solution:

The issue has been handled and all users with Party Names containing single quote character can properly see the Pivot display.

KCT-16298

Issue:

User was not able to revert the workflow.

Bug Cause:

PO status was not updated as Completed when a shipment was dispatched using System Function, which was configured on a VBE exit type button and did not have "Next profile item" configured.  

Solution:

Code changes have been done to properly update the PO status when such exit type button is configured.

KCT-16303

Issue:

When MOT_dependent_locations system parameter was set to Y, user was forced to select only MOT dependent values in PLR and PLD fields to save the shipment.

Solution:

PLR and PLD fields are now accepting any master location values and user can save the shipment without any PLR and PLD location validations when MOT_dependent_locations system parameter is set to Y.

KCT-16307

Issue:

TO Import update for new line items case was not properly handled and the shipment was moving to quarantine.

Solution:

The issue is addressed. Now, TO Import updates for addition of new line items or updates to existing line items are properly done against a shipment and properly displayed in the application.

KCT-16325

Issue:

Alerts were not triggered when Booking confirmation milestone was actualized after receiving eDoc in CT.

Solution:

The issue is addressed, and alerts are now being triggered in the following cases:

•when a milestone is actualized after receiving eDoc

•when an eDoc is received after milestone actual details are filled