Issue
Issue No
Issue Name
Issue Description
Response
Submitted by ReAssign To
Date Submitted Priority
Expected Date New Status
Version In Version
Orig Assigned To Billable
Now Assigned To Customer
Priority Customer Status
Status Customer Product
Billable Next Action Date  
Customer Contact Information (When Applicable)
Customer Added
Name
Phone Number
Email Address

Issue Documents
Document Upload/Delete Documents List Attached To This Issue

 


(Select File To Delete From List)
'22855-Script-Alter-DomesticShipQuoteBoardWT-PrintRoutingLabel.txt
'22855-Script-CF-1767.txt
'22855-Script-CF-27-UserSecurity.txt
'22855-Script-Create-tbl_CustomerRoutingLabelCode.txt
'22855-Script-VW_RoutingDetail.txt
'22855_vw_DefaultNew.txt
'22855_vw_DefaultNewCHB.txt
22855-TestCases-162Update.docx
22855_consignee_not_matching.png
22855_Label_NEW_FORMAT_Example.docx
47868_RoutingLabelAR.pdf
7623_RoutingLabelAR.pdf
CF-1864 and CF-1867 set to 'N'.png
CVPortal-CF-1864-CF-1867-Set-N.png
Dom-Consol-1071-Carrier-Fix.png
Dom-Ship-Carrier-Issue-3.png
DomRoutingLabel-CarrierFix-43340-47247.png
HAWB-282935863-RoutingLabel-Pilot-Production.png
HAWB-7119-Forair.png
IMG_2981.jpg
Label-Print-Test-162-Order-52868.png
Pilot-Test-CustomerLabelRoutingCodespng.png
Pilot-UAT-Consol-737-Agent-Partner.png
pilot_pieces_space.png
pilot_routing_label.PNG
Pilot_Routing_Label_Remaining_Issues_20210426.docx
Pilot_Routing_Label_Remaining_Issues_20210503.docx
RoutingLabel Label.pdf
RoutingLabel Label_20210528.pdf
RoutingLabel Label_20210823 NEW LAYOUT.png
Screenshot 2023-08-28 125126.jpg
TestCase -162-Print-Label-Domestic-Ship-OrderNo-52868.docx
TestCase 162-Consol-12322.png
TestCase-OrderNo-47247-SchDateAndDelAgentFix.png
TestCase162-SepLayoutForDomShipments.docx
There are 2 issues with the routing label.docx


Response History
ByDateCustomer
Can View
 Note Status?ResponseAssigned ToPriorityStatus 
Nick Schubert 9/7/2023 11:53:58 AM NO Installed on UAT on 09/07/2023. Waiting for Release High Waiting For ReleaseP
Nathan Palmer 9/6/2023 4:09:43 PM NO Brian Cronin High Ready For Install
Nick Schubert 8/30/2023 9:48:29 AM NO Nathan Palmer High Branch - 02/22
Preeti Nevrekar 8/30/2023 1:32:54 AM NO Test case 162
International shipment ,HAWB 12564 on 162. LEA-ORD carrier.

With this fix, the Destination Airport on the top and bottom of the International label are pulled from the aircost record.

Please test the update/Fix dated 8/28/2023 10:39:12 AM
Nick Schubert High Ready For Testing
Nathan Palmer 8/29/2023 6:56:12 PM NO Preeti Nevrekar High Ready For Testing
Preeti Nevrekar 8/29/2023 5:29:31 AM NO Worldtrak
Changeset 69387
rptRoutingLabel.Designer.vb
DataAccess.vb






Note : Fix for the update dated 8/28/2023 10:39:12 AM
Nathan Palmer High Merge to 79/162
Nick Schubert 8/28/2023 12:52:35 PM NO HAWB 12564 on 162. LEA-ORD carrier. Airports on the label are pulling from page 1. They want them to pull from LEA-ORD.

Screenshot 2023-08-28 125126.jpg
Preeti Nevrekar High Questions
Preeti Nevrekar 8/28/2023 12:47:24 PM NO Thanks Nick. Can you please give a similar test case from 162 for the international Routing Label if possible? to understand What 'Dest Airport' the International Label is currently showing and what it should be after this change. Nick Schubert High Questions
Nick Schubert 8/28/2023 11:49:04 AM NO See HAWB 100022934 on UAT.

The International Label works a little differently than the Domestic Label.

The Domestic Label still pulls in the Dest Airport from page 1 + the MAWB Dest Airport from the Aircost record. You will see that the AirCost Dest Airport (LAX) is correctly pulling into the MAWB Dest Airport on the bottom left of the label.

The International always pulls from page 1. We need to make sure the Aircost Dest Airport shows for the Dest Airport at the top of the label, and the AirPort that shows on bottom middle of the label.
Preeti Nevrekar High Questions
Preeti Nevrekar 8/28/2023 11:33:46 AM NO Nick, can you give me a test case from Pilot UAT for Domestic Routing Label where it is working perfectly? Nick Schubert High Questions
Nick Schubert 8/28/2023 10:39:12 AM NO Preeti - Pilot wants to make one minor tweak to the International Routing Label. Everything with the Domestic Routing Label is working perfectly.

HAWB 100017960 on UAT. If you generate the routing label from Carrier 0472, the Destination Airport on the top and bottom of the label are pulling from page 1 of the shipment and not the aircost record.

Please change the international label to pull airports from the aircost record just like we do with the domestic label. Make sure to do this at the Consolidation level as well.

Also, please make any necessary changes to 24315 for the changes in this ticket.
Preeti Nevrekar High Re-Work
Nick Schubert 4/13/2023 10:19:44 AM NO Waiting for Release Highest Waiting For ReleaseP
Preeti Nevrekar 4/13/2023 5:22:56 AM NO Fixed the below reported issue dated 4/12/2023 4:11:48 PM in Ticket # 25429 Nick Schubert Highest Questions
Nick Schubert 4/13/2023 12:25:15 AM NO #1 - Correct.

#2 - Correct.
Preeti Nevrekar Highest Questions
Preeti Nevrekar 4/13/2023 12:23:16 AM NO Thanks Nick, I Have below clarifications

#1 This change would come on both the reports when 'Generate Reports with 3 barcodes' is checked/Unchecked right?

#2 For this test case HAWB 13531 on 162.
The'HAWB DEST' on the top left section would show 'YMX/C' and the 'HAWB DEST' on the bottom right would show 'WMR-IN' right?
Nick Schubert Highest Questions
Nick Schubert 4/13/2023 12:13:26 AM NO HAWB 13531 on 162. Preeti Nevrekar Highest Questions
Preeti Nevrekar 4/13/2023 12:05:36 AM NO Nick, Can you please give me a test case on 162 for this. Nick Schubert Highest Questions
Nick Schubert 4/12/2023 4:21:15 PM NO If it's easier to handle this in 25429, please feel free to do so. Preeti Nevrekar Highest Re-Work
Nick Schubert 4/12/2023 4:11:48 PM NO Preeti - One minor change request from Pilot.

See HAWB 100001214 on UAT. When generating the routing label, the logic found a hit on a record in tbl_CustomerRoutingLabelCode. GOOD.

If you view the label, you will see that the code 'WMR-IN' from the table populates on the bottom right HAWB-DST section and the top left HAWB DEST section.

They only want it to show in the bottom right HAWB-DST section going forward.

The HAWB DEST on the top left section can just pull directly from the shipment like we normally do when we don't find a hit in tbl_CustomerRoutingLabelCode.
Preeti Nevrekar Highest Re-Work
Nick Schubert 4/11/2023 12:10:54 PM NO Installed on 04/06/23. Waiting for Release Highest Waiting For ReleaseP
Nathan Palmer 4/6/2023 6:39:24 PM NO Merged to 2/22. Brian Cronin Highest Ready For Install
Nathan Palmer 4/6/2023 6:32:12 PM NO Preeti Nevrekar Highest Ready For Testing
Nick Schubert 4/6/2023 1:35:05 PM NO Nathan Palmer Highest Merge to 79/162
Nick Schubert 4/6/2023 1:13:26 PM NO Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 4/6/2023 5:46:49 AM NO Nick as discussed, fixed the issue dated 4/6/2023 3:36:20 AM in the below changeset when we generate the 'Routing label' and 'Email the Routing Label' for Consolidation from Documents Board for both 'Linehaul' and 'AIR' carriers.

Only 'Linehaul' had an issue. Looks like 'Air carriers' is working even before this fix as for 'AIR' carriers we do not append the vendor prefix as the 'Vendor Prefix' will always be the part of MAWB#.(as per Brian's comments dated 9/29/2022 9:24:24 AM at the end).

Also added the missing part from Ticket # 23721 in Email-Routing Label feature, where it appends !D for Domestic and !I for International for the 'Tracking barcode' on the Routing label.

This part was only missing in the 'Email Routing Label' feature but already added when we generate the 'Routing Label' from Shipment Board/Documents tab in
Ticket # 23721.

Changeset 67324
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb
------------------------------------------
Also, as per my analysis I don't think we need any changes to Ticket # 24315 in VisibleFunctions.asmx-->GenerateShipmentDocument as the above issue comes when we generate the label for Consolidation with multiple shipments.

As I understand, the GenerateShipmentDocument only generates the label for single shipments and not for consolidation. We might want to check with Shilpa on this.


Notes:
Test case 162 for Linehaul and AIRcarriers
Consol (ALHL) # 16041/1071
Consol (AIR) # 15539
Test case Pilot UAT consol # 5686
Test case Pilot Prod Consol # 901
Nick Schubert Highest Questions
Preeti Nevrekar 4/6/2023 3:36:20 AM NO Nick, Fixed the issue of Multiple Prefix getting appended to the MAWB in the below changeset when we generate the 'Routing label' and 'Email the Routing Label' for Consolidation from Documents Board.

Also added the missing part from Ticket # 23721 in Email-Routing Label feature, where it appends !D for Domestic and !I for International for the 'Tracking barcode' on the Routing label.

This part was only missing in the 'Email Routing Label' feature but already added when we generate the 'Routing Label' from Shipment Board/Documents tab in
Ticket # 23721.

Changeset 67324
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb
------------------------------------------
Also, as per my analysis I don't think we need any changes to Ticket # 24315 in VisibleFunctions.asmx-->GenerateShipmentDocument as the above issue comes when we generate the label for Consolidation with multiple shipments.

As I understand, the GenerateShipmentDocument only generates the label for single shipments and not for consolidation. We might want to check with Shilpa on this.



Notes:
Test case 162 : Consol # 16041/1071
Test case Pilot UAT consol # 5686
Test case Pilot Prod Consol # 901
Nick Schubert Highest Questions
Nick Schubert 4/5/2023 3:48:41 PM NO Preeti - Please see consol # 5686 on UAT.

If you view the routing label from the consolidation documents page, there is an issue.

Since there are three shipments with 3 pieces total, three labels show as per this ticket.

The MAWB # on the first label looks good.

The MAWB # on the second label is duplicating the '472' prefix once. 47247283683607

The MAWB # on the third label is duplicating the '472' prefix twice. 47247247283683607

Please fix so that the carrier prefix is not duplicated.

Also, after you complete the fix please let me know if any changes needed to 24315.
Preeti Nevrekar Highest Priority
Nick Schubert 3/23/2023 3:13:19 PM NO Installed on 03/23/23. Waiting for Release High Waiting For ReleaseP
Nathan Palmer 3/22/2023 6:12:29 PM NO Brian Cronin High Ready For Install
Nick Schubert 3/22/2023 11:33:02 AM NO Nathan Palmer High Branch - 02/22
Preeti Nevrekar 3/21/2023 10:13:01 PM NO Nick Please test #4 dated 3/21/2023 12:11:10 AM
Test case 162 Shipment with Multiple carriers
Ship # 47247 hawb : 7119
Ship # 54105 hawb : 12801
Nick Schubert High Ready For Testing
Nathan Palmer 3/21/2023 6:27:37 PM NO Preeti Nevrekar High Ready For Testing
Preeti Nevrekar 3/21/2023 8:11:56 AM NO Worldtrak
Changeset 67062
EmailDoc.aspx.vb



Note :

Fixed #4 below dated 3/21/2023 12:11:10 AM
4. This is confirmed an issue. Please fix. On 162 it always sends the first label via email regardless of which one you choose. Also on 162, I cannot duplicate the error when trying to send documents you found on UAT.
Nathan Palmer High Merge to 79/162
Nick Schubert 3/21/2023 12:40:10 AM NO Preeti - On my comments for #3: I will let this go for now. We may need to change this in the future to generate all labels if multiple carriers regardless of the IsDefault column in tbl_Aircost.

For now, please just fix #4.
Preeti Nevrekar High Questions
Preeti Nevrekar 3/21/2023 12:31:54 AM NO Nick, Please find my inline comments below.
3. Shipment # 47247 on 162. When trying to generate the labels from the default new board, it does not show all available labels. The labels it does show are missing data.
-----PN----03/21----
Nick, Is this the new issue you found? or you talking about #3 issue I reported dated 3/20/2023 1:37:06 AM where I was getting object Reference error?

When we generate a label or shipment with multiple carriers, from the default board, it prints the data for the default carrier only. This is as per the original requirement. tbl_Aircost( Isdefault='Y'). In this test case , Shipment # 47247 there is no default carrier and hence MAWB data is missing.

Here is another test case with Multiple carriers and having a default carrier( Isdefault='Y' in tbl_AirCost) .

Test case 162 : Shipment # 54105 default carrier : 'FORAIR' mawb : 00000364. It print all the details on the label.

Please let me know if we need to discuss.
-------End----------

4. This is confirmed an issue. Please fix. On 162 it always sends the first label via email regardless of which one you choose. Also on 162, I cannot duplicate the error when trying to send documents you found on UAT.
-----PN----03/21----
ok I will fix this.
----End-------------
Nick Schubert High Questions
Preeti Nevrekar 3/21/2023 12:21:36 AM NO Nick, Please find my inline comments below.
3. Shipment # 47247 on 162. When trying to generate the labels from the default new board, it does not show all available labels. The labels it does show are missing data.
-----PN----03/21----
Nick, Is this the new issue you found? or you talking about #3 issue I reported dated 3/20/2023 1:37:06 AM where I was getting object Reference error?

When we generate a label or shipment with multiple carriers, from the default board, it prints the data for the default carrier only. This is as per the original requirement. tbl_Aircost( Isdefault='Y'). In this test case , Shipment # 47247 there is no default carrier and hence MAWB data is missing.

We can try this with a different shipment with Multiple carriers and having a default carrier( Isdefault='Y' in tbl_AirCost) .

Please let me know if we need to discuss.
-------End----------

4. This is confirmed an issue. Please fix. On 162 it always sends the first label via email regardless of which one you choose. Also on 162, I cannot duplicate the error when trying to send documents you found on UAT.
-----PN----03/21----
ok I will fix this.
----End-------------
Nick Schubert High Questions
Nick Schubert 3/21/2023 12:11:10 AM NO Preet - flipping back to you for #3 & #4.

3. Shipment # 47247 on 162. When trying to generate the labels from the default new board, it does not show all available labels. The labels it does show are missing data.


4. This is confirmed an issue. Please fix. On 162 it always sends the first label via email regardless of which one you choose. Also on 162, I cannot duplicate the error when trying to send documents you found on UAT.
Preeti Nevrekar High Re-Work
Nathan Palmer 3/20/2023 6:44:48 PM NO Brian Cronin High Ready For Install
Nick Schubert 3/20/2023 4:04:55 PM NO Nate - Please merge what Preeti has so far.


Preeti - I will flip back to you for #3 & #4.
Nathan Palmer High Branch - 02/22
Brian Cronin 3/20/2023 9:38:31 AM NO Nick Schubert High Ready For Testing
Preeti Nevrekar 3/20/2023 1:37:06 AM NO Nick , please test below #1 , #2 and #3 also I have a clarification for the #4 issue I found today while testing this on 162.

Test Case 162 for the issues dated 3/14/2023 1:29:42 PM

#1 Domestic Consol : 14735
Org/Dest Airport on Consol screen 1 DTW/ORD
Org/Dest Aiport on MAWB screen ABE/AAR

As per the #1 fix dated 3/14/2023 1:29:42 PM changed the pecking order to look at tbl_Aircost first, then tbl_Airwaybill.

#2) Ship # 54567/54561 no carriers (similar test case as that of pilot UAT HAWB : 100062850

Ship # 47247 multiple carries (just to confirm the shipment with Carriers works fine)

With this fix, When we 'Email' the RoutingLabel we do not get any object reference error any more for shipment with no carries.

#3) Similar issue as #2 when generating the 'Routing Label' from Shipment Board. I found this issue while testing the above 2 fix on 162 dated 3/17/2023 1:30:27 AM

Test case : Ship # 54567/5456 no carriers (similar test case as that of pilot UAT HAWB : 100062850

--------------------------------------------------------
#4 Shipment : 47247 HAWB : 7119 Shipment with multiple carriers.

When we 'Email' the shipment it always pics the MAWB Org/Dest from the top 1 entry. In this case it always picks MAWB Org/Dest as SLC/PHL.

I tried to confirm the issue on Pilot UAT Ship # : 69662 HAWB : 100055160 with multiple carries. When I Email the Routing Label from documents board by selecting the carrier, I get the below error. So I could not confirm the issue on Pilot UAT.

"An error occurred while sending document(s). Try again later."

Please test above #1,#2,#3 and For #4 , once you confirm this is an error, please flip the ticket to me I will fix this.
Nick Schubert High Ready For Testing
Nathan Palmer 3/17/2023 5:54:20 PM NO Preeti Nevrekar High Ready For Testing
Preeti Nevrekar 3/17/2023 2:07:11 AM NO Worldtrak
Changeset 67028
RoutingLabelAR.aspx.vb




Note : Fixed the below issue while testing generate Routing Label from Shipment board.
Nathan Palmer High Merge to 79/162
Preeti Nevrekar 3/17/2023 1:30:27 AM NO While testing the Email issue for the consol #2 issue dated 3/14/2023 1:25:39 PM , found the similar issue from the shipment board.

Dom Ship # 54567 / 54561 with no carriers, when we generate the label from shipment Board. It gives the below error similar to the Email #2 issue dated 3/14/2023 1:25:39 PM.

[NullReferenceException: Object reference not set to an instance of an object.]
AirTrak.RoutingLabelAR.Page_Load(Object sender, EventArgs e) +28485
System.Web.UI.Control.OnLoad(EventArgs e) +107
System.Web.UI.Control.LoadRecursive() +89
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1532
Preeti Nevrekar High In progress
Preeti Nevrekar 3/17/2023 1:24:24 AM NO Test Case 162 for the issues dated 3/14/2023 1:29:42 PM

#1 Domestic Consol : 14735
Org/Dest Airport on Consol screen 1 DTW/ORD
Org/Dest Aiport on MAWB screen ABE/AAR

As per the #1 fix dated 3/14/2023 1:29:42 PM changed the pecking order to look at tbl_Aircost first, then tbl_Airwaybill.

#2) Ship # 54567/54561 no carriers (similar test case as that of pilot UAT HAWB : 100062850

Ship # 47247 multiple carries (just to confirm the shipment with Carriers works fine)
Preeti Nevrekar High In progress
Nathan Palmer 3/16/2023 5:45:21 PM NO Preeti Nevrekar High Ready For Testing
Preeti Nevrekar 3/16/2023 12:21:04 AM YES Changeset 66953
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb
VisibleFunctions.asmx.vb

Changeset 66967
EmailDoc.aspx.vb




Note : Fixed the #1 and #2 issues dated 3/14/2023 1:29:42 PM

Test case 162 : Ship # 54567 HAWB : 13283 no carriers (similar test case as that of pilot UAT HAWB : 100062850
Ship # 47247 multiple carries
Nathan Palmer High Merge to 79/162
Nick Schubert 3/14/2023 11:44:21 PM NO Preeti - Please try with HAWB 100062850 on UAT.

This issue only appears to happen when there is no Domestic Air Carrier or Linehaul Carrier on the shipment. If you add either one, you can successfully email the routing label.
Preeti Nevrekar High Questions
Preeti Nevrekar 3/14/2023 10:32:13 PM NO Hi Nick, I am not able to duplicate the below #2 issue on Production.

"https://worldtrak.pilotdelivers.com/Main/International/Docs_New.aspx?OrderNo=100000380&BoardView=DL"

Clicked the 'Email Documents' option and I received the Document through Email. Attached is the same.'RoutingLabel Label.pdf'

Do I need to test in some other way? Please advice.
Nick Schubert High Questions
Brian Cronin 3/14/2023 1:29:42 PM NO Updating with another issue (2)

1. Okay that may have been a mistake by me in December. We need to change the pecking order to look at tbl_Aircost first, then tbl_Airwaybill.

Looks like tbl_Airwaybill will not get automatically updated unless a user hits reset.


2. Another issue: If you try to email a routing label before there is a LH or Air Carrier on the shipment, it errors out.

HAWB 382936197 - production

Note: It works from defaultnew. Just need to make sure it works for email.

Here is the error:

Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an object.]
AirTrak.EmailDoc.GenerateRoutingLabel(String CarrierId, String MAWB, String SeqNoS, String DelAgent, String FromEmailDocs) +26709
AirTrak.EmailDoc.btnSubmit_Click(Object sender, EventArgs e) +94448
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +9794554
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +211
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +12
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +15
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +9856108
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1696

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4110.0
Preeti Nevrekar High Re-Work
Brian Cronin 3/14/2023 1:25:39 PM NO Updating with another issue (2)

1. Okay that may have been a mistake by me in December. We need to change the pecking order to look at tbl_Aircost first, then tbl_Airwaybill.

Looks like tbl_Airwaybill will not get automatically updated unless a user hits reset.


2. Another issue: If you try to email a routing label before there is a LH or Air Carrier on the shipment, it errors out.

HAWB 382936197 - production

Here is the error:

Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an object.]
AirTrak.EmailDoc.GenerateRoutingLabel(String CarrierId, String MAWB, String SeqNoS, String DelAgent, String FromEmailDocs) +26709
AirTrak.EmailDoc.btnSubmit_Click(Object sender, EventArgs e) +94448
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +9794554
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +211
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +12
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +15
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +9856108
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1696

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4110.0
Preeti Nevrekar High Re-Work
Brian Cronin 3/14/2023 1:25:06 PM NO Updating with another issue (2)

1. Okay that may have been a mistake by me in December. We need to change the pecking order to look at tbl_Aircost first, then tbl_Airwaybill.

Looks like tbl_Airwaybill will not get automatically updated unless a user hits reset.


2. Another issue: If you try to email a routing label before there is a LH or Air Carrier on the shipment, it errors out.

HAWB 382936197 - production

Here is the error:

Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an object.]
AirTrak.EmailDoc.GenerateRoutingLabel(String CarrierId, String MAWB, String SeqNoS, String DelAgent, String FromEmailDocs) +26709
AirTrak.EmailDoc.btnSubmit_Click(Object sender, EventArgs e) +94448
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +9794554
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +211
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +12
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +15
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +9856108
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1696

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4110.0
Preeti Nevrekar High Re-Work
Nick Schubert 3/13/2023 1:04:45 PM NO Okay that may have been a mistake by me in December. We need to change the pecking order to look at tbl_Aircost first, then tbl_Airwaybill.

Looks like tbl_Airwaybill will not get automatically updated unless a user hits reset.
Preeti Nevrekar High Questions
Preeti Nevrekar 3/13/2023 12:45:45 PM NO Nick, Please Ignore my prev comments and please find my inline comments below.

Consol # 5322 on UAT.

I created the consol with 'DTW' as the Destination on the consolidation, I then changed the Destination to 'ORD', but the routing label still shows 'DTW' as the MAWB-DST.

I feel like we fixed this at one point on shipments as it's working fine, but it's an issue on consolidations.
----------PN-03/13--------
On consolidation level, we read the MAWB Org/Dest values from the Consol screen 1 (tbl_AirCost) but if the MAWB screen has the Org/Dest airport specified, then we read the values from (OrgAirport/DestAirport) from tbl_AirWayBill.

We added this tbl_AirWayBill logic for the requirement you asked dated '12/21/2022 3:44:39 PM'

Based on the current issue looks like when we change the airports on the Consol screen 1 , airports on the MAWB screen are not updated.

The pecking order to grab the MAWBOrg/ MAWBDest is first
to look at the MAWB table (tbl_AirwayBill) and then look at the screen 1 (tbl_AirCost)
----------End-------------
Nick Schubert High Questions
Preeti Nevrekar 3/13/2023 3:32:01 AM NO Nick, I have below clarification.
Consol # 5322 on UAT.

I created the consol with 'DTW' as the Destination on the consolidation, I then changed the Destination to 'ORD', but the routing label still shows 'DTW' as the MAWB-DST.

I feel like we fixed this at one point on shipments as it's working fine, but it's an issue on consolidations.

-----PN---13/03------
I analyzed the code, in the current logic, we get the MAWBOrg/MAWBDest from FK_RateOrgAirport,FK_RateDestAirport fields in tbl_AirCost table which is good and this fields have the updated values for Destination as 'ORD'.

In the recent fix for the issue dated 12/21/2022 3:44:39 PM. I added some additional logic to override this data with the OrgAirport/DestAirport as MAWBOrg/MAWBDest from tbl_AirWayBill if data is not null.

When we change the Origin/Destination on consolidation the tbl_AirCost data is updated but the tbl_AirWayBill fields are not updated and it still has 'DTW' as the destination and hence the issue.

I don't remember why I added this extra logic to override the Origin/Dest values from tbl_AirCost with tbl_AirWayBill if OrgAirport/OrgDest from tbl_AirwayBill are not null. As you know we have made many updates/Fix to this logic in recent times.

The fix for this particular issue would be to comment this part of code where it overrides the data from tbl_AirWayBill but I am only concerned as am not able to recollect the scenario for which this part of code was added.

Please advice. Once you confirm we Comment/Remove the logic.
-----End-------------
Nick Schubert High Questions
Nick Schubert 3/10/2023 10:04:10 AM NO Yes 100055160 is a good test case with multiple carriers on a shipment. This just seems to be a problem on the consolidation level where any change to the MAWB Origin/Destination is not populating.

Another example of this consol # 5323
Preeti Nevrekar High Questions
Preeti Nevrekar 3/10/2023 7:22:57 AM NO Nick, Please find my inline comments below.
Consol # 5322 on UAT.

I created the consol with 'DTW' as the Destination on the consolidation, I then changed the Destination to 'ORD', but the routing label still shows 'DTW' as the MAWB-DST.

I feel like we fixed this at one point on shipments as it's working fine, but it's an issue on consolidations.

-------PN--03-10---------------
I understand what the issue is on the above consol, In order to confirm my fix for consol, can you please share a test case from Pilot UAT where checked that the shipments are working fine.

I guess to confirm the shipments are working fine you have taken a shipment with multiple carriers and changed the Destination on one of the Carriers and the routing label is printing the correct Destination right?

Can you please share this test case? Is it HAWB : 100055160 on pilot UAT? This shipment has multiple carriers on it.
--------End--------------------
Nick Schubert High Questions
Nick Schubert 3/9/2023 3:08:32 PM NO Preeti - Consol # 5322 on UAT.

I created the consol with 'DTW' as the Destination on the consolidation, I then changed the Destination to 'ORD', but the routing label still shows 'DTW' as the MAWB-DST.

I feel like we fixed this at one point on shipments as it's working fine, but it's an issue on consolidations.
Preeti Nevrekar High Re-Work
Nathan Palmer 3/7/2023 1:22:29 PM NO Brian Cronin High Ready For Install
Nick Schubert 3/7/2023 10:39:41 AM NO Nathan Palmer High Branch - 02/22
Preeti Nevrekar 3/7/2023 10:14:18 AM NO Nick based on our discussion today, part of this Changeset 64696 dated 10/20/2022 1:19:29 PM was missing on Pilot Release (02/22) and hence the below reported issue on Pilot production

"The labels are printing correctly through the logic in 24315 but the 258 highlighted in the screenshot
'HAWB-282935863-RoutingLabel-Pilot-Production.png' is not printing on the label. Do you see anything wrong in GenerateShipmentDocument that would be causing this issue? That prefix is setup against https://worldtrak.pilotdelivers.com/Main/Maintenance/Vendors/LinehaulCarrier.aspx?"

Added the missing code from VisibleFunctions.asmx.vb on Pilot Release and checked in the code in the below chnageset and shared the Airtrak dll with you from Pilot release. Please review.

Worldtrak Pilot Release (02/22)
Chnageset 66840
VisibleFunctions.asmx.vb
Nick Schubert High Questions
Brian Cronin 1/9/2023 9:35:47 AM NO just adding jira ticket# for filtering to the original write-up Waiting for Release High Waiting For ReleaseP
Nick Schubert 1/4/2023 7:00:21 PM NO Installed on 01/04/23. Waiting for Release High Waiting For ReleaseP
Nathan Palmer 1/4/2023 3:32:24 PM NO Brian Cronin High Ready For Install
Nick Schubert 1/4/2023 1:27:20 PM NO Nathan Palmer High Branch - 02/22
Nick Schubert 1/3/2023 4:52:45 PM NO Nick Schubert High Waiting on Feedback
Nick Schubert 1/3/2023 4:10:03 PM NO Nathan Palmer High Branch - 02/22
Nathan Palmer 1/3/2023 1:15:25 PM NO Preeti Nevrekar High Ready For Testing
Preeti Nevrekar 12/22/2022 3:41:57 PM NO Worldtrak
Changeset 65764
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb edit
VisibleFunctions.asmx.vb
DataAccess.vb
Nathan Palmer High Merge to 79/162
Preeti Nevrekar 12/22/2022 12:32:56 PM NO Preeti Nevrekar High In progress
Brian Cronin 12/22/2022 6:47:07 AM NO Preeti - HAWB 100055160 on UAT. It may not be the exact example that Nick gave below, but it is the example that Pilot tested with. Preeti Nevrekar High Re-Work
Preeti Nevrekar 12/21/2022 10:29:37 PM NO Nick, Can you please give me the Shipment you tried having carriers 6258 and 0526 ? Nick Schubert High Questions
Nick Schubert 12/21/2022 3:44:39 PM NO Preeti - Need to make one more change. On the routing label we are populating the Origin Airport from page 1 of the shipment.

Please default in the Origin Airport from the MAWB instead.

Example on Pilot UAT.

Origin Airport on the Shipment is SLC and that is what currently populates on the routing label.

Carrier 6258 has an Origin Airport of SLC. The label should show SLC as the Origin Airport.

Carrier 0526 has an Origin Airport of ORD. The label should show ORD as the Origin Airport.
Preeti Nevrekar High Re-Work
Nick Schubert 12/15/2022 10:32:51 AM NO Installed on 12/15/2022. Waiting for Release High Waiting For ReleaseP
Nathan Palmer 12/14/2022 7:25:07 PM NO Brian Cronin High Ready For Install
Nick Schubert 12/12/2022 12:02:34 PM NO Nathan Palmer High Branch - 02/22
Preeti Nevrekar 12/11/2022 9:13:39 PM NO Test case 162 : Ship # 47247 HAWB : 7119
Fixed the issue dated 12/8/2022 2:20:23 PM

In this case, MAWB : 63636636 has DEST='PHL' rest all MAWB's have DEST='LAX'
Nick Schubert High Ready For Testing
Nathan Palmer 12/9/2022 5:16:49 PM NO Preeti Nevrekar High Ready For Testing
Preeti Nevrekar 12/9/2022 12:48:17 PM NO Wordldtrak
Changeset 65541
RoutingLabelAR.aspx.vb
Nathan Palmer High Merge to 79/162
Preeti Nevrekar 12/9/2022 12:49:29 AM NO Preeti Nevrekar High In progress
Nick Schubert 12/8/2022 2:20:23 PM NO Preeti - See HAWB 100053123 on Pilot UAT.

On the routing label for Carrier 6258, the MAWB/DST is showing ORD, but it should be showing PHL based on the MAWB setup. Looks like it is always looking at the first MAWB DST which in this case is Carrier # 0472.

I don't think we ever added logic to handle this at the shipment level for non-consolidated vendor lines. Please review and fix.


Also, I need Shilpa to make changes to 24314 & 24315 as Pilot is still having issues printing the labels. The two of you will most likely need to coordinate on all your changes.
Preeti Nevrekar High Re-Work
Nick Schubert 10/31/2022 11:16:40 AM NO Installed on 10/27/22. Nathan Palmer High Waiting For ReleaseP
Nathan Palmer 10/27/2022 8:46:54 PM NO Brian Cronin High Ready For Install
Nick Schubert 10/21/2022 1:59:03 PM NO Nathan Palmer High Branch - 02/22
Dave Fisher 10/21/2022 12:40:25 PM NO Brian Cronin High Needs to be Merged
Preeti Nevrekar 10/20/2022 11:55:51 PM NO Dave we cannot test this on 162. Tested loccally through code before checkin.

Test case 162
Ship # 50269 / 47247
Consol # 14420/14550
Dave Fisher High Ready For Testing
Nathan Palmer 10/20/2022 6:24:23 PM NO Preeti Nevrekar High Ready For Testing
Preeti Nevrekar 10/20/2022 1:19:29 PM NO Worldtrak
Changeset 64696
VisibleFunctions.asmx.vb

Changeset 64697
VisibleFunctions.asmx.vb
Nathan Palmer High Merge to 79/162
Preeti Nevrekar 10/20/2022 2:56:45 AM NO Worldtrak
Changeset 64696
VisibleFunctions.asmx.vb
Nathan Palmer High Merge to 79/162
Preeti Nevrekar 10/20/2022 12:06:24 AM NO Preeti Nevrekar High In progress
Dave Fisher 10/19/2022 2:15:04 PM NO Make sure that all changes done to RoutingLabelAR.aspx.vb are also done to the VisibleFunctions.asmx.vb routine, GenerateRoutingLabel. Preeti Nevrekar High Priority
Nick Schubert 10/6/2022 12:10:51 PM NO Installed on 10/6/22. Nathan Palmer High Waiting For ReleaseP
Nick Schubert 10/6/2022 12:10:50 PM NO Installed on 10/6/22. Nathan Palmer High Waiting For ReleaseP
Nathan Palmer 10/5/2022 6:40:03 PM NO Brian Cronin High Ready For Install
Nick Schubert 10/5/2022 4:30:58 PM NO Nathan Palmer High Branch - 02/22
Brian Cronin 10/4/2022 7:36:39 AM NO Nick - Please test on 162 and let me know your results. I don't want this merged into 02/22 just yet even if it works because there is one more thing that needs to be fixed with the label. I'm waiting for Dave to update this ticket (or it might be a '113' ticket he needs to update). Nick Schubert High Ready For Testing
Preeti Nevrekar 10/3/2022 11:26:00 PM NO Brian,

Fixed the issues dated 9/27/2022 9:27:40 AM along with the below fix.

Tested with HAWB : 7119 on 162. None of the shipments in this are attached to a consol. We can test this on Pilot.

"LH Vendor - We are good. No change required.

Air Carrier - The waybill prefix will ALWAYS be a part of the MAWB#. It automatically defaults on the page when the air carrier is selected. No need to append it from tbl_AirCarrierVendors.AirCarrierPrefix

Make sure you fix this from a shipment and from a consolidation."
Brian Cronin High Ready For Testing
Nathan Palmer 10/3/2022 6:39:01 PM NO Preeti Nevrekar High Ready For Testing
Preeti Nevrekar 10/3/2022 2:25:57 AM NO Worldtrak
Changeset 64332
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb
Nathan Palmer High Merge to 79/162
Preeti Nevrekar 9/30/2022 8:09:57 AM NO ------PN----09/30---------
Once we know if the shipment is attached to consol, we need to get the consolno the shipment is attached to, to print the 'MAWBDest' like it does for consolidation.

In the above test case, Shipment # 47689 is attached to 3 consols with same SeqNo=1. What will be the differentiating factor in this case, will it be the MAWB?

------BC----09/30---------
I would assume so. The documents page certainly knows that there are 3 possible vendor lines to generate the label for, so I was just thinking that once the user selects it, you would just check to see if that entry in tbl_ShipmentAPAR has a consolno > 0. If so, you would use that consol# to generate the label. But whatever makes more sense is fine with me.

----PN---09/30---------
got it Brian, Thanks
Preeti Nevrekar High In progress
Brian Cronin 9/30/2022 6:38:54 AM NO ------PN----09/30---------
Once we know if the shipment is attached to consol, we need to get the consolno the shipment is attached to, to print the 'MAWBDest' like it does for consolidation.

In the above test case, Shipment # 47689 is attached to 3 consols with same SeqNo=1. What will be the differentiating factor in this case, will it be the MAWB?

------BC----09/30---------
I would assume so. The documents page certainly knows that there are 3 possible vendor lines to generate the label for, so I was just thinking that once the user selects it, you would just check to see if that entry in tbl_ShipmentAPAR has a consolno > 0. If so, you would use that consol# to generate the label. But whatever makes more sense is fine with me.
Preeti Nevrekar High Questions
Preeti Nevrekar 9/30/2022 2:50:03 AM NO Brian, I have some additional clarifications unser your comment-BC---09/28---

Pilot - UAT
HAWB: 100033166

It has 3 consolidated lines on it. 2 for LH and 1 for Air Carrier.

Consol# 1896: CMH to ATL - VendorID: 0472
Consol# 1897: ATL to SLC - VendorID: 6258
Consol# 1898: SLC to PHL - VendorID: 0526

------PN---09/28--------
In all 3 cases above the 'MAWBDest' is printing 'ATL' instead of 'PHL' when 'Routing Label' is printed from the shipment.

At Shipment level, How should we get the correct 'MAWBDest' in this scenario?

-------BC---09/28--------
When the user tries to print the routing label from the shipment (or shipment board), You have to see if the line item they are printing the routing label for is on a consolidation. If so, use the same logic as you do when printing it from the consolidation.

------PN----09/28---------
Got it. I will fix this.
--------------------------
------PN----09/30---------
Once we know if the shipment is attached to consol, we need to get the consolno the shipment is attached to, to print the 'MAWBDest' like it does for consolidation.

In the above test case, Shipment # 47689 is attached to 3 consols with same SeqNo=1. What will be the differentiating factor in this case, will it be the MAWB?
Brian Cronin High Questions
Brian Cronin 9/29/2022 9:24:24 AM NO Preeti, please find my inline comments below for 09/29 (just 1 update at the very bottom).

Pilot - UAT
HAWB: 100033166

It has 3 consolidated lines on it. 2 for LH and 1 for Air Carrier.

Consol# 1896: CMH to ATL - VendorID: 0472
Consol# 1897: ATL to SLC - VendorID: 6258
Consol# 1898: SLC to PHL - VendorID: 0526

------PN---09/28--------
In all 3 cases above the 'MAWBDest' is printing 'ATL' instead of 'PHL' when 'Routing Label' is printed from the shipment.

At Shipment level, How should we get the correct 'MAWBDest' in this scenario?

-------BC---09/28--------
When the user tries to print the routing label from the shipment (or shipment board), You have to see if the line item they are printing the routing label for is on a consolidation. If so, use the same logic as you do when printing it from the consolidation.

------PN----09/28---------
Got it. I will fix this.
--------------------------

It is also printing the 'prefix' for 526 twice. I assume that is a setup issue, but please let me know. If you print it from the consolidation, the label prints fine - except for 526 showing twice.
-------------------------------------------------------

-------PN-28-09------
In this case the MAWB on the documents page itself is '526222222222' and we add we add prefix of '526' and hence the issue. This is a data issue.
-------BC---09/28--------
Preeti - I know there has been a lot of discussions about the prefix from both the air carrier and linehaul for this label. As the logic stands right now, please tell me exactly what we are doing with the prefix for both types of vendors and if there are multiple places on the label where we are showing the prefix - I will need to know the logic on that as well.

--------PN---09/28--------
For Air Carrier/ Linehaul vendors ,here is the logic for prefix.

For ExpansionCode='AALHL' we get the 'VendorPrefix' field from tbl_LinehaulCarrierVendors based on the vendorId as below

"select B.VendorPrefix from tbl_vendors (nolock) as A INNER JOIN dbo.tbl_LinehaulCarrierVendors (nolock) as B on A.PK_VendorNo = B.FK_VendorNo where A.VendorId = '" & VendorId & "'

For ExpansionCode='AIR' we get the 'AirCarrierPrefix' field from tbl_AirCarrierVendors based on the vendorId as below

"select B.AirCarrierPrefix from tbl_vendors (nolock) as A INNER JOIN dbo.tbl_AirCarrierVendors (nolock) as B on A.PK_VendorNo = B.FK_VendorNo where A.VendorId = '" & VendorId & "'"


The VendorPrefix is displayed at the below two places.

1.For both Dom/Intl Label.Appended at the beggining of the MAWB as displayed as MAWBBARCODE .

MAWBBARCODE = Vendorprefix + MAWB
we show this at the top of both Dom/Intl Routing label below barcode section.

2.Only for Intl Label.Appended at the end of the value Label below Barcode.
-------BC---09/29--------
LH Vendor - We are good. No change required.

Air Carrier - The waybill prefix will ALWAYS be a part of the MAWB#. It automatically defaults on the page when the air carrier is selected. No need to append it from tbl_AirCarrierVendors.AirCarrierPrefix

Make sure you fix this from a shipment and from a consolidation.

Bill your time to this mod.
Preeti Nevrekar High Re-Work
Preeti Nevrekar 9/28/2022 9:09:26 AM NO Brian, please find my inline comments below.

Pilot - UAT
HAWB: 100033166

It has 3 consolidated lines on it. 2 for LH and 1 for Air Carrier.

Consol# 1896: CMH to ATL - VendorID: 0472
Consol# 1897: ATL to SLC - VendorID: 6258
Consol# 1898: SLC to PHL - VendorID: 0526

------PN---09/28--------
In all 3 cases above the 'MAWBDest' is printing 'ATL' instead of 'PHL' when 'Routing Label' is printed from the shipment.

At Shipment level, How should we get the correct 'MAWBDest' in this scenario?

-------BC---09/28--------
When the user tries to print the routing label from the shipment (or shipment board), You have to see if the line item they are printing the routing label for is on a consolidation. If so, use the same logic as you do when printing it from the consolidation.

------PN----09/28---------
Got it. I will fix this.
--------------------------

It is also printing the 'prefix' for 526 twice. I assume that is a setup issue, but please let me know. If you print it from the consolidation, the label prints fine - except for 526 showing twice.
-------------------------------------------------------

-------PN-28-09------
In this case the MAWB on the documents page itself is '526222222222' and we add we add prefix of '526' and hence the issue. This is a data issue.
-------BC---09/28--------
Preeti - I know there has been a lot of discussions about the prefix from both the air carrier and linehaul for this label. As the logic stands right now, please tell me exactly what we are doing with the prefix for both types of vendors and if there are multiple places on the label where we are showing the prefix - I will need to know the logic on that as well.

--------PN---09/28--------
For Air Carrier/ Linehaul vendors ,here is the logic for prefix.

For ExpansionCode='AALHL' we get the 'VendorPrefix' field from tbl_LinehaulCarrierVendors based on the vendorId as below

"select B.VendorPrefix from tbl_vendors (nolock) as A INNER JOIN dbo.tbl_LinehaulCarrierVendors (nolock) as B on A.PK_VendorNo = B.FK_VendorNo where A.VendorId = '" & VendorId & "'

For ExpansionCode='AIR' we get the 'AirCarrierPrefix' field from tbl_AirCarrierVendors based on the vendorId as below

"select B.AirCarrierPrefix from tbl_vendors (nolock) as A INNER JOIN dbo.tbl_AirCarrierVendors (nolock) as B on A.PK_VendorNo = B.FK_VendorNo where A.VendorId = '" & VendorId & "'"


The VendorPrefix is displayed at the below two places.

1.For both Dom/Intl Label.Appended at the beggining of the MAWB as displayed as MAWBBARCODE .

MAWBBARCODE = Vendorprefix + MAWB
we show this at the top of both Dom/Intl Routing label below barcode section.

2.Only for Intl Label.Appended at the end of the value Label below Barcode.
Brian Cronin High Questions
Brian Cronin 9/28/2022 7:25:58 AM NO Preeti - Please find my inline comments below.

Pilot - UAT
HAWB: 100033166

It has 3 consolidated lines on it. 2 for LH and 1 for Air Carrier.

They are having issues with the routing labels. Please review:

-------------------------------------------------------
Consol# 1896: CMH to ATL - VendorID: 0472 - Routing label works fine if they print it from the shipment or from the consolidation.
-------------------------------------------------------

Consol# 1897: ATL to SLC - VendorID: 6258 -

Routing Label doesn't print the correct info if printed from the shipment.

It is printing ATL for the MAWB-DST at the bottom (should be SLC). If you print it from the consolidation, the label prints fine.
-------------------------------------------------------

Consol# 1898: SLC to PHL - VendorID: 0526 - Routing Label

Routing Label doesn't print the correct info if printed from the shipment.

It is printing ATL for the MAWB-DST at the bottom (should be PHL). If you print it from the consolidation, the label prints fine.

-------PN---09/28--------
In all 3 cases above the 'MAWBDest' is printing 'ATL' instead of 'PHL' when 'Routing Label' is printed from the shipment.

In the current logic, we get the 'FK_RateDestAirport' field from tbl_AirCost table.

Shipment Level -MAWBDest =FK_RateDestAirport from tbl_Aircost based on OrderNO

Consolidation Level -MAWBDest=FK_RateDestAirport from tbl_AirCost based on ConsolNo.

In the test case used while testing on 162 HAWB : 7119.
All the entries in tbl_AirCost has same MAWBDest (FK_RateDestAirport) i.e 'LAX'

In the Pilot's test case above, all the 3 consolidated lines have different DestAiport (tbl_AirCost) and from the current logic it pics the top entry='ATL'

At Shipment level, How should we get the correct 'MAWBDest' in this scenario?

or

I should take the 'DestAirport' filed from tbl_ShipmentHeader='PHL' ?

-------BC---09/28--------
When the user tries to print the routing label from the shipment (or shipment board), You have to see if the line item they are printing the routing label for is on a consolidation. If so, use the same logic as you do when printing it from the consolidation.

-----------------------------------------------------

It is also printing the 'prefix' for 526 twice. I assume that is a setup issue, but please let me know. If you print it from the consolidation, the label prints fine - except for 526 showing twice.
-------------------------------------------------------

-------PN-28-09------
In this case the MAWB on the documents page itself is '526222222222' and we add we add prefix of '526' and hence the issue. This is a data issue.
-------BC---09/28--------
Preeti - I know there has been a lot of discussions about the prefix from both the air carrier and linehaul for this label. As the logic stands right now, please tell me exactly what we are doing with the prefix for both types of vendors and if there are multiple places on the label where we are showing the prefix - I will need to know the logic on that as well.

-----------------------------
Preeti Nevrekar High Questions
Preeti Nevrekar 9/28/2022 6:16:53 AM NO Brian, Please find my inline comments below. Also let me know when you have some time to discuss.

Pilot - UAT
HAWB: 100033166

It has 3 consolidated lines on it. 2 for LH and 1 for Air Carrier.

They are having issues with the routing labels. Please review:

-------------------------------------------------------
Consol# 1896: CMH to ATL - VendorID: 0472 - Routing label works fine if they print it from the shipment or from the consolidation.
-------------------------------------------------------

Consol# 1897: ATL to SLC - VendorID: 6258 -

Routing Label doesn't print the correct info if printed from the shipment.

It is printing ATL for the MAWB-DST at the bottom (should be SLC). If you print it from the consolidation, the label prints fine.
-------------------------------------------------------

Consol# 1898: SLC to PHL - VendorID: 0526 - Routing Label

Routing Label doesn't print the correct info if printed from the shipment.

It is printing ATL for the MAWB-DST at the bottom (should be PHL). If you print it from the consolidation, the label prints fine.

-------PN---09/28--------
In all 3 cases above the 'MAWBDest' is printing 'ATL' instead of 'PHL' when 'Routing Label' is printed from the shipment.

In the current logic, we get the 'FK_RateDestAirport' field from tbl_AirCost table.

Shipment Level -MAWBDest =FK_RateDestAirport from tbl_Aircost based on OrderNO

Consolidation Level -MAWBDest=FK_RateDestAirport from tbl_AirCost based on ConsolNo.

In the test case used while testing on 162 HAWB : 7119.
All the entries in tbl_AirCost has same MAWBDest (FK_RateDestAirport) i.e 'LAX'

In the Pilot's test case above, all the 3 consolidated lines have different DestAiport (tbl_AirCost) and from the current logic it pics the top entry='ATL'

At Shipment level, How should we get the correct 'MAWBDest' in this scenario?

or

I should take the 'DestAirport' filed from tbl_ShipmentHeader='PHL' ?

-----------------------------------------------------

It is also printing the 'prefix' for 526 twice. I assume that is a setup issue, but please let me know. If you print it from the consolidation, the label prints fine - except for 526 showing twice.
-------------------------------------------------------

-------PN-28-09------
In this case the MAWB on the documents page itself is '526222222222' and we add we add prefix of '526' and hence the issue. This is a data issue.

-----------------------------
Brian Cronin High Questions
Brian Cronin 9/27/2022 9:27:40 AM NO Pilot - UAT
HAWB: 100033166

It has 3 consolidated lines on it. 2 for LH and 1 for Air Carrier.

They are having issues with the routing labels. Please review:

-------------------------------------------------------
Consol# 1896: CMH to ATL - VendorID: 0472 - Routing label works fine if they print it from the shipment or from the consolidation.
-------------------------------------------------------

Consol# 1897: ATL to SLC - VendorID: 6258 -

Routing Label doesn't print the correct info if printed from the shipment.

It is printing ATL for the MAWB-DST at the bottom (should be SLC). If you print it from the consolidation, the label prints fine.
-------------------------------------------------------

Consol# 1898: SLC to PHL - VendorID: 0526 - Routing Label

Routing Label doesn't print the correct info if printed from the shipment.

It is printing ATL for the MAWB-DST at the bottom (should be PHL). If you print it from the consolidation, the label prints fine.

It is also printing the 'prefix' for 526 twice. I assume that is a setup issue, but please let me know. If you print it from the consolidation, the label prints fine - except for 526 showing twice.
-------------------------------------------------------
Bill your time to this ticket.






CMH to ATL correct
Preeti Nevrekar High Re-Work
Nick Schubert 9/15/2022 11:16:43 PM NO Installed on Pilot UAT on 09/15/22. Nathan Palmer Highest Waiting For ReleaseP
Nathan Palmer 9/15/2022 6:01:43 PM NO Merged to 2/22. Brian Cronin Highest Ready For Install
Nathan Palmer 9/15/2022 5:38:08 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 9/15/2022 2:22:16 AM NO Nate, Please merge the below changesets

Worldtrak
Changeset 64001
RoutingLabelAR.aspx.vb

Changeset 64002
EmailDoc.aspx.vb



Note : Fixed the issue dated 9/12/2022 12:07:56 PM
Nathan Palmer Highest Merge to 79/162
Nick Schubert 9/14/2022 8:59:03 AM NO Preeti - This should not be an issue based of the logic created in 24731. When Control Flag 2058 is 'Y' a shipment can't be attached to more than one Consolidation. Preeti Nevrekar Highest Questions
Preeti Nevrekar 9/14/2022 4:41:53 AM NO Nick,

I had the below additional clarification.

What if the shipment that we are trying to generate the routing label from the International shipmentBoard board, is attached to more than one consol?

For eg on 162 OrderNo : 49210 is attached to the below consols : 14473/12325/14475/14420/14492

how should we handle this case? what AgentPartnerNo to pick in this case?
Nick Schubert Highest Questions
Nick Schubert 9/13/2022 11:02:48 AM NO Preeti - Per our conversation, flipping this one back to you.

Need to make sure the Agent Partner shows on the routing label when initially going to a shipment's documents page from the International Shipment Board.
Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 9/13/2022 12:42:42 AM NO Nick,

As per my understanding, is this change only for the international shipments that are attached to a consol and we try to generate the 'Routing Label' from the shipment board, using the documents tab, then we need to do this change right?

Please let me know when you have some time to discuss this before I make any change.
Nick Schubert Highest Questions
Nick Schubert 9/12/2022 12:07:56 PM NO Preeti - Per my change request on 7/5, on Consol # 737 Pilot UAT, if we view the routing label from the documents page, the Agent Partner shows as the 'Agent' on the label.

We only applied this logic on the consolidation. Please apply this logic when viewing the routing label from a shipment.
Preeti Nevrekar Highest Re-Work
Nick Schubert 8/24/2022 7:01:06 AM NO Installed on Pilot DEV on 08/24/22. Nathan Palmer Highest Waiting For ReleaseP
Nathan Palmer 8/23/2022 7:19:04 PM NO Merged to 2/22. Brian Cronin Highest Ready For Install
Nathan Palmer 8/23/2022 6:02:59 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 8/23/2022 3:47:15 AM NO Worldtrak
Changeset 63721
RoutingLabelAR.aspx.vb
Nathan Palmer Highest Merge to 79/162
Nick Schubert 8/22/2022 2:39:12 PM NO Preeti - See Consol # 1660 on Pilot UAT. When printing/viewing the routing label, there is an issue with the MAWB Barcode #.

The MAWB Barcode # is resetting with each HAWB attached to the consolidation.

Pieces 1 & 2 are linked to 100000258.

Piece 1 - PIT0210018000001
Piece 2 - PIT0210018000002

100000259 - Piece 3

Piece 3 - PIT0210018000001

100017439 - Piece 4-6

Piece 4 - PIT0210018000001
Piece 5 - PIT0210018000002
Piece 6 - PIT0210018000003

As you can see by the example above, the Barcode # is being reset with each HAWB. It should not be reset and should show as seen below.

100000258 - Piece 1 & 2

Piece 1 - PIT0210018000001
Piece 2 - PIT0210018000002

100000259 - Piece 3

Piece 3 - PIT0210018000003

100017439 - Piece 4-6

Piece 4 - PIT0210018000004
Piece 5 - PIT0210018000005
Piece 6 - PIT0210018000006


Please fix and bill your time to this ticket.
Preeti Nevrekar Highest Re-Work
Brian Cronin 8/1/2022 11:35:48 AM NO Nathan Palmer Highest Waiting For ReleaseP
Brian Cronin 8/1/2022 10:40:06 AM NO Nathan Palmer Highest Waiting For ReleaseP
Nick Schubert 8/1/2022 10:20:49 AM NO Installed on Pilot DEV last week. Nathan Palmer Highest Waiting For ReleaseP
Preeti Nevrekar 7/27/2022 9:01:30 AM NO Brian, Test case Pilot Dev
for the fix dated 7/20/2022 4:02:49 PM


#1 I cannot test this, will need to test via API

#2 Domestic Consol : 1431
Agent : 'Reading Trans'
Brian Cronin Highest Ready For Install
Nathan Palmer 7/22/2022 7:02:27 PM NO Brian Cronin Highest Ready For Install
Brian Cronin 7/22/2022 7:19:19 AM NO Ok, thanks! Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 7/22/2022 7:04:16 AM NO Hi Brian,

Discussed with Shilpa yesterday as she had worked on Ticket #23815 and tested it locally by using SOAP UI and saved the generated pdfString in my local folder the one I shared with you.

We do not Checkin this code to save the label in local folder . This is for testing purpose.

On 162 it just returns a pdf string as attached.'Label-Print-Test-162-Order-52868.png'
Brian Cronin Highest Ready For Testing
Brian Cronin 7/22/2022 6:39:54 AM NO Preeti - It looks good...just curious though...how did you do the printed label? Preeti Nevrekar Highest Questions
Preeti Nevrekar 7/22/2022 12:47:23 AM NO Brian,

Fixed the issue dated 7/20/2022 4:02:49 PM
Please find the attached test case for #1.

TestCase -162-Print-Label-Domestic-Ship-OrderNo-52868.docx'
Brian Cronin Highest Ready For Testing
Nathan Palmer 7/21/2022 2:02:31 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 7/21/2022 11:27:05 AM NO Nate,

Please merge the below changesets
Changeset 63174
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb

Worldtrak
Changeset 63175
VisibleFunctions.asmx.vb


Note : Fixed the issue dated 7/20/2022 4:02:49 PM
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 7/21/2022 11:26:02 AM NO Worldtrak
Changeset 63175
VisibleFunctions.asmx.vb




Note : Fixed the #1 dated 7/20/2022 4:02:49 PM
Also attached is the test case on 162.
'TestCase -162-Print-Label-Domestic-Ship-OrderNo-52868.docx'
Preeti Nevrekar Highest In progress
Brian Cronin 7/21/2022 10:05:33 AM NO sorry about that. Preeti Nevrekar Highest Priority
Preeti Nevrekar 7/21/2022 9:24:38 AM NO Thanks Brian, Looks like you missed to upload the 'IMG_2981.jpg' Brian Cronin Highest Questions
Brian Cronin 7/21/2022 9:00:47 AM NO 1. I uploaded an image of the routing label that is being printed. It is NOT the same one as my example HAWB# that I gave you, but you should get the idea.

IMG_2981.jpg
Preeti Nevrekar Highest Re-Work
Brian Cronin 7/21/2022 6:24:01 AM NO 1. ok...I will take a picture of it today when I get to their office and attach to this ticket.

2. ok, good.
Brian Cronin Highest Questions
Preeti Nevrekar 7/21/2022 3:56:07 AM NO Below are my inline clarifications.

Installed on Pilot DEV/TEST/UAT. Please review:

1. Found another issue...Very similar to what we found with the shipper/consignee label (22777) last week or so.

The PDF is perfect, but what prints to the label printer is missing some info at the bottom...Please make sure that what we send to the label printer has the same info as the PDF.

Example - UAT - HAWB: 100015131

Please fix. Bill to this ticket.

--PN--07/21--
This feature where it generates the label from printer was addded in Ticket # 23815 and is missing few changes done to the PDF.

If possible, can you please share the doc generated from the label printer? So that I will get to know exactly what is missing and will add that logic.

I am not aware of how to generate the Routing label from Label Printer.
---End----

2. I tested Consol# 737 on UAT for the agent partner tweak and generating the routing label from the consol docs page works fine...BUT - look at consol 1034 Why isn't it printing the agent info? It isn't a international consol, so there won't be an agent partner, but I fear the last fix you made wiped out the logic that is supposed to happen if it isn't an international consol.

--PN--07/21--
As you mensioned it was wiping out the logic that is supposed to happen if it isn't an international consol.

Fixed the issue in the below changeset.
Changeset 63174
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb
Brian Cronin Highest Questions
Preeti Nevrekar 7/20/2022 11:19:35 PM NO Preeti Nevrekar Highest In progress
Brian Cronin 7/20/2022 4:02:49 PM NO Installed on Pilot DEV/TEST/UAT. Please review:

1. Found another issue...Very similar to what we found with the shipper/consignee label (22777) last week or so.

The PDF is perfect, but what prints to the label printer is missing some info at the bottom...Please make sure that what we send to the label printer has the same info as the PDF.

Example - UAT - HAWB: 100015131

Please fix. Bill to this ticket.

2. I tested Consol# 737 on UAT for the agent partner tweak and generating the routing label from the consol docs page works fine...BUT - look at consol 1034 Why isn't it printing the agent info? It isn't a international consol, so there won't be an agent partner, but I fear the last fix you made wiped out the logic that is supposed to happen if it isn't an international consol.
Preeti Nevrekar Highest Priority
Brian Cronin 7/20/2022 3:12:48 PM NO Installed on Pilot DEV/TEST/UAT. It works, BUT, found another issue...Very similar to what we found with the shipper/consignee label (22777) last week or so.

The PDF is perfect, but what prints to the label printer is missing some info at the bottom...Please make sure that what we send to the label printer has the same info as the PDF.

Example - UAT - HAWB: 100015131

Please fix. Bill to this ticket.
Preeti Nevrekar Highest Priority
Nathan Palmer 7/19/2022 7:17:21 PM NO Brian Cronin Highest Ready For Install
Brian Cronin 7/19/2022 9:37:14 AM NO ok...someone probably transferred the consolidation from an air consol to a misc consol. Just bad test data. Will let this go. Thanks! Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 7/19/2022 9:25:16 AM NO Brian,

I am fetching the 'AgentPartner' field from tbl_AirCost table for a Consol or if shipment is attached to a consol as below

"select AgentPartnerNo from tbl_AirCost (nolock) where FK_SeqNo=9999 and consolNo=12322"

I agree we cannot see the Agent : 523 assigned on the consol/Shipment on UI.

But in this case for consol : 12322, the above query returns '523'

Please advice.
Brian Cronin Highest Questions
Brian Cronin 7/19/2022 9:09:32 AM NO Preeti - Please review:

Consol : 12322 (Intl) - this is a misc agent consolidation. You cannot select an agent partner from here, nor can you print the routing label from the consolidation - which is ok...I went to the docs page for the 1 shipment that was on that consolidation and generated the label. There is no agent partner on the shipment either. It is printing 'BEST BUY CANADA523' and I cannot figure out where it is coming from. I know that is customer# 523, but I don't see it associated with the shipment in any way.

Maybe everything is ok, but I need you to tell me where it is coming from.

Consol : 14420 (Intl) - this worked fine.
Preeti Nevrekar Highest Questions
Preeti Nevrekar 7/19/2022 12:45:52 AM NO Brian, as Nick is on vacation fliping this ticket to you for testing.

Test case 162
Consol : 12322 (Intl)
Consol : 14420 (Intl)

Attached is the snapshot 'TestCase 162-Consol-12322.png'

Added the below updates dated 7/5/2022 3:24:43 PM and 7/15/2022 4:00:37 PM

#1 Preeti - See HAWB # 100003422 on Pilot UAT. For International Shipments ONLY pull the Agent Partner on the Consolidation into the 'Agent' section of the routing label. If there is no Agent Partner filled out on the consolidation, or if the shipment is not attached to a consolidation, do what we do today and leave the 'Agent' section on the label blank.

#2 Preeti - You can go ahead and add this logic on the documents tab of the consolidation.

Also, instead of showing the customer # on the labels when printing from a shipment or consolidation, please change it to customer name.

So instead of showing '1334343', show 'DAVIES TURNER AIR CARGO'.
Brian Cronin Highest Ready For Testing
Nathan Palmer 7/18/2022 2:15:15 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 7/18/2022 4:22:50 AM NO Worldtrak
Changeset 63088
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb
Nathan Palmer Highest Merge to 79/162
Nick Schubert 7/15/2022 4:00:37 PM NO Preeti - YOu can go ahead and add this logic on the documents tab of the consolidation.

Also, instead of showing the customer # on the labels when printing from a shipment or consolidation, please change it to customer name.

So instead of showing '1334343', show 'DAVIES TURNER AIR CARGO'.
Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 7/15/2022 4:16:41 AM NO Nick,

On Pilot UAT, It is working for me. Attached is the snapshot 'Pilot-UAT-Consol-737-Agent-Partner.png'

As discussed in our last meeting, Here are the steps I followed.

For ConsolNo=737

Step 1 : Click on the Eye icon for the Primary Shipment hawb : 100003422 .Redirects to the page1.

Step 2 : Click On the documents tab, Selected the first carrier : 100003422 with MAWB : 0061234567

step 3 : Click 'Cancel' on the Print popup page.
attached is the report 'Pilot-UAT-Consol-737-Agent-Partner.png' containing the Agent Partner : 1334343

I guess you are trying to print the Routing label by Going directly to the documents tab.

I have not done any changes related to 'Agent Partner', if User clicks the documents tab from consolidation, as per our last discussion we were awaiting Pilots response on this.

Please let me know if you want to discuss.
Nick Schubert Highest Questions
Nick Schubert 7/15/2022 3:20:58 AM NO Preeti - I installed this on all Pilot environments. I'm waiting on Pilot's feedback with the '!D' issue.

On the issue I pointed out on 7/5/2022, I cannot see the Agent Partner on the Routing Label when printing from the consolidation. Please review the example below.


https://worldtrak-uat.pilotdelivers.com/Main/Reports/StationPrinterSelectPage.aspx?PrinterDocType=RoutingLabel&OrderNo=&ConsolNo=737&MAWB=&VendorId=&SeqNo=&FromDocs=Y&BackToConsol=
Preeti Nevrekar Highest Questions
Nathan Palmer 7/14/2022 6:50:56 PM NO Brian Cronin Highest Ready For Install
Nick Schubert 7/14/2022 4:08:58 PM NO Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 7/14/2022 1:59:20 AM NO Test case 162
International Consol : 12322
Agent Partner : 523

Note : Fixed the update dated 7/5/2022 3:24:43 PM reported By Nick.


Also fixed the below issue reported by Pilot
When Ops is printing labels, the label is missing the '!D' for Barcode. Works fine in pdf.
Nick Schubert Highest Ready For Testing
Nathan Palmer 7/13/2022 6:21:16 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 7/13/2022 12:17:13 PM NO Nate, Please merge the below changesets
Worldtrak
Changeset 62955
Changeset 62968
Changeset 63003
Changeset 62989
Changeset 63023
Chnageset 63024
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 7/13/2022 8:53:49 AM NO Worldtrak
Changeset 63023
VisibleFunctions.asmx.vb

Chnageset 63024
VisibleFunctions.asmx.vb




Note : Fixed the below issue reported by Pilot
When Ops is printing labels, the label is missing the '!D' for Barcode. Works fine in pdf.
Preeti Nevrekar Highest In progress
Preeti Nevrekar 7/12/2022 11:59:22 AM NO Worldtrak
Changeset 62989
Docs_New.aspx
Docs_New.aspx.vb
RoutingLabelAR.aspx.vb

Changeset 63003
Docs_New.aspx
Docs_New.aspx.vb
EmailDoc.aspx.vb
StationPrinterSelect.ascx
Preeti Nevrekar Highest In progress
Preeti Nevrekar 7/12/2022 5:59:42 AM NO While working on the Update dated 7/5/2022 3:24:43 PM found an issue caused in Ticket # 24314 when CF # 2008 SET to 'Y' (Enable New Print Server Architecture? Y/N)

All the Required querystring parameters for the Routing Label are not passed and hence the Routing label when CF#2008 set to 'Y' differs when CF#2008 SET to 'N'

Working on the same to fix.
Preeti Nevrekar Highest In progress
Preeti Nevrekar 7/8/2022 7:25:52 AM NO Worldtrak
Changeset 62968
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb
Preeti Nevrekar Highest In progress
Preeti Nevrekar 7/7/2022 9:50:24 AM NO Worldtrak
Changeset 62955
Docs_New.aspx
Docs_New.aspx.vb
RoutingLabelAR.aspx.vb
Preeti Nevrekar Highest In progress
Nick Schubert 7/6/2022 2:02:42 PM NO Preeti - Flipping back to you per our conversation. Preeti Nevrekar Highest Questions
Preeti Nevrekar 7/6/2022 7:56:12 AM NO Nick,

Please let me know when you have some time for clarification for the below update.
Nick Schubert Highest Questions
Nick Schubert 7/5/2022 3:24:43 PM NO Preeti - See HAWB # 100003422 on Pilot UAT. For International Shipments ONLY pull the Agent Partner on the Consolidation into the 'Agent' section of the routing label. If there is no Agent Partner filled out on the consolidation, or if the shipment is not attached to a consolidation, do what we do today and leave the 'Agent' section on the label blank.

Please bill your time to this ticket.


UAT Link:

https://worldtrak-uat.pilotdelivers.com/default.aspx
Preeti Nevrekar Highest Re-Work
Nick Schubert 5/17/2022 12:44:15 PM NO Installed on Pilot DEV on 05/17/22. Nathan Palmer Highest Waiting For ReleaseP
Nathan Palmer 5/16/2022 8:43:44 PM NO Brian Cronin Highest Ready For Install
Nick Schubert 5/16/2022 2:10:36 PM NO Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 5/15/2022 1:30:49 PM NO Test case 162
Dom shipments

Order No : 43340
Bill To customer : 1126

Order No : 47247
Bill To customer :43340


Note : Consider the 'Customer Routing Label Codes' for Domestic shipments too. Also, use the special instructions from it as well.
Nick Schubert Highest Ready For Testing
Nathan Palmer 5/13/2022 5:43:30 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 5/13/2022 2:57:14 PM NO Worldtrak
Changeset 62087
DataAccess.vb
Nathan Palmer Highest Merge to 79/162
Dave Fisher 5/12/2022 10:33:50 AM NO Preeti, yes, please consider the Customer Routing Label Codes for both Domestic and International.
Also, please use the special instructions from it as well.
Preeti Nevrekar Highest Open
Nick Schubert 5/9/2022 1:10:17 PM NO Hey Dave - Can you answer Preeti's question on this one? Dave Fisher High Questions
Preeti Nevrekar 5/6/2022 2:01:29 PM NO Nick/Dave

We have two different 'Routing Label' report layouts for Domestic and international shipments.

We consider the 'Customer Routing Label Codes' table entry for 'International Shipments' only #15/#16 in attached layout 'pilot_routing_label.PNG'

For Domestic shipments, we follow the attached new layout 'RoutingLabel Label_20210823 NEW LAYOUT.png' from Pilot.

In this case, HAWB : 100011984 , we are showing 'Dest Airport/Area' for 'MAWB-DST' i.e 'DFW/C'.

For Domestic Layout too, Do you want me to consider the 'Customer Routing Label Codes' entry and show the 'Customer Code' as 'MAWB-DST' in this case 'HAA-TX'?

Also, for Special Instructions, for both layouts (Dom/Intl) we show the special instructions attached to the shipment.(NOtes from tbl_Instructions). We do not consider the 'Special instructions from 'Customer Routing Label Codes' entry.

In this case too, Do we need to show the 'Special Instructions' from 'Customer Routing Label Codes' entry if we get a hit?
Nick Schubert High Questions
Nick Schubert 5/6/2022 10:50:58 AM NO Preeti - Please review the email I forwarded you. On Pilot DEV, there is an entry in the Customer Routing Label Codes table that should have applied to the routing label on HAWB 100011984.

Per the entry in this table, HAA-TX and the special instruction 'Return Routing Label' should be showing on the routing label but are not. Please review.
Preeti Nevrekar High Re-Work
Nick Schubert 4/19/2022 8:51:23 AM NO Installed on Pilot DEV on 04/18/22. Nathan Palmer High Waiting For ReleaseP
Nathan Palmer 4/15/2022 3:31:11 PM NO Brian Cronin High Ready For Install
Nick Schubert 4/12/2022 9:08:48 AM NO Nathan Palmer High Branch - 02/22
Brian Cronin 4/12/2022 6:54:15 AM NO Nick Schubert High Ready For Testing
Preeti Nevrekar 4/12/2022 6:20:27 AM NO Test Case 162 Air Carrier Vendors
Intl Shipment : 52035
HAWB : 10482
Carrier:'AA-DOM'
MAWB : 00101511274

Dom Shipment : 47247
HAWB : 7119
Carrier : AA-DOM
MAWB : 00101511263
Brian Cronin High Ready For Testing
Nathan Palmer 4/11/2022 7:21:57 PM NO Preeti Nevrekar High Ready For Testing
Preeti Nevrekar 4/11/2022 8:31:18 AM NO Worldtrak
Changeset 61389
RoutingLabelAR.aspx.vb




Note : Fixed the issues dated 4/8/2022 8:33:23 AM
Nathan Palmer High Merge to 79/162
Brian Cronin 4/11/2022 7:05:26 AM NO Yes, please do that as well. Preeti Nevrekar High Re-Work
Preeti Nevrekar 4/11/2022 5:55:48 AM NO Brian,

Analysis Pilot Dev
Consol : 971
HAWB : 100007004
Expansion Code : AIR
Vendor Id : 0006
Vendor Service : IA

In the current logic we have code to get the vendorPrdefix for linehaul Carriers i.e when Expansion Code='AALHL' from the tbl_LinehaulCarrierVendors.

Currently we do not have the logic to get the vendor prefix for the Air Carrier Vendors i.e when Expansion Code='AIR' (tbl_AirCarrierVendors)

Do you want me to account for 'Air Carriers' too?
Brian Cronin High Questions
Brian Cronin 4/8/2022 8:33:23 AM NO Preeti - Please review and let me know if this is a bug or a setup issue. Bill to the original ticket.

The Carrier prefix not showing: When viewing the Intl Routing level from Consol #971, the carrier prefix (006) is not showing at the bottom of the label.

The prefix is also not showing from both of the HAWBs that are in the consol.

Same issue is occurring when the label is pulling from the Customer Routing Label Codes table.
Preeti Nevrekar High Re-Work
Nick Schubert 4/7/2022 9:56:03 AM NO Dave - Can you take a quick look at this today and let us know why this is happening?

Carrier prefix not showing: When viewing the Intl Routing level from Consol #971, the carrier prefix (006) is not showing at the bottom of the label.

The prefix is also not showing from both of the HAWBs that are in the consol.

Same issue is occurring when the label is pulling from the Customer Routing Label Cods table.
Dave Fisher Highest Questions
Nick Schubert 1/10/2022 11:28:48 AM NO Nathan Palmer Highest Waiting For ReleaseP
Nathan Palmer 1/5/2022 1:49:18 PM NO Brian Cronin Highest Ready For Install
Brian Cronin 1/4/2022 7:45:26 AM NO Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 1/4/2022 3:34:48 AM NO Test Case 162
Order No : 39948

Note : Update Email same as Print report.
Brian Cronin Highest Ready For Testing
Nathan Palmer 1/3/2022 3:51:06 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 12/29/2021 4:34:04 AM NO Worldtrak
Changeset 59715
EmailDoc.aspx.vb



Note : The latest changes updated for the Email too.
Test case Pilot : HAWB : 100000085 OrderNo : 24862
Nathan Palmer Highest Merge to 79/162
Brian Cronin 12/27/2021 12:00:04 PM NO Preeti - this works fine when you print it, but when you email it, it doesn't have the latest changes. Please fix and bill to this mod.

HAWB 100000085
Preeti Nevrekar Highest Re-Work
Nathan Palmer 12/16/2021 7:05:49 PM NO Looks like the last few changesets since 8/3/2021 weren't merged to 2/22 yet. This ticket is all in 2/22 now. Brian Cronin Highest Ready For Install
Dave Fisher 12/15/2021 1:56:09 PM NO Nate... please recheck merge. I know at least Changeset 57835 did not make it. Nathan Palmer Highest Branch - 02/22
Brian Cronin 10/1/2021 4:28:57 PM NO fixed in other ticket. Nathan Palmer Highest Waiting For ReleaseP
Brian Cronin 9/27/2021 4:21:06 PM NO Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 9/27/2021 10:20:04 AM NO This should be fixed in Ticket #23721 and Dave. W is working on it. Dave Fisher Highest Questions
Dave Fisher 9/26/2021 10:36:18 PM NO Please change the barcode type from Code 39 to Code 128. Preeti Nevrekar Highest Re-Work
Brian Cronin 9/23/2021 11:31:36 AM NO Nathan Palmer Highest Branch - 02/22
Dave Fisher 9/23/2021 9:59:01 AM NO Brian Cronin Highest Needs to be Merged
Preeti Nevrekar 9/17/2021 8:56:32 AM NO Test case 162 : Consol 1071 Carrier : 'BBB'
attached is the test case 'Dom-Consol-1071-Carrier-Fix.png'
Dave Fisher Highest Ready For Testing
Dave Fisher 9/17/2021 8:38:53 AM NO could you please test a consol too Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 9/14/2021 10:42:34 PM NO Dave, Please find the attached test case
OrderNo : 43340 , 47247
'DomRoutingLabel-CarrierFix-43340-47247.png'





Note : Fixed the below
#3 the carrier is not the prefix, it is the vendor id.
Dave Fisher Highest Ready For Testing
Nathan Palmer 9/14/2021 5:39:53 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 9/14/2021 12:46:02 PM NO Worldtrak
Changeset 57974
DataAccess.vb






Note : Fidex #3 below
#3 the carrier is not the prefix, it is the vendor id.
Nathan Palmer Highest Merge to 79/162
Dave Fisher 9/14/2021 11:27:07 AM NO correct, only #2 will be the vendorid Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 9/14/2021 9:47:12 AM NO Dave, for the below fix #3 in the attached doc
'Dom-Ship-Carrier-Issue-3.png' #1 will be prefix and #2 will be VendorId right?
Dave Fisher Highest Questions
Preeti Nevrekar 9/14/2021 9:46:03 AM NO Dave Fisher Highest Questions
Preeti Nevrekar 9/14/2021 9:24:58 AM NO Dave, for the below fix #3 in the attached doc
'Dom-Ship-Carrier-Issue-3.png' #1 will be prefix and #2 will be VendorId right?
Preeti Nevrekar Highest Re-Work
Dave Fisher 9/13/2021 10:17:24 AM NO one thing I missed, #3, the carrier is not the prefix, it is the vendor id. Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 9/10/2021 4:35:17 PM NO Dave,

Please find the attached test case 'TestCase-OrderNo-47247-SchDateAndDelAgentFix.png' . Fixed the issues dated 9/7/2021 10:36:03 AM
Dave Fisher Highest Ready For Testing
Nathan Palmer 9/8/2021 6:16:34 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 9/8/2021 3:58:20 PM NO Worldtrak
Changeset 57907
DataAccess.vb edit
Nathan Palmer Highest Merge to 79/162
Nathan Palmer 9/8/2021 1:47:50 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 9/7/2021 11:46:35 PM NO Worldtrak
Changeset 57896
rptRoutingLabel.Designer.vb
rptRoutingLabelDom.Designer.vb
RoutingLabelAR.aspx.vb
DataAccess.vb
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 9/7/2021 11:30:48 AM NO Preeti Nevrekar Highest In progress
Dave Fisher 9/7/2021 10:36:03 AM NO Preeti... please check on the 2 new issues from testing by Pilot:

There are 2 issues with the routing label.docx
Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 8/31/2021 9:43:11 AM NO Test case 162 : for the Update dated 8/23/2021 12:01:25 PM

Dom Shipments:
Order No : 48475/47247/43340

Dom Consol Shipments :
Consol : 11074/10308

Dave , Please find the attached documents with the test cases.
'TestCase162-SepLayoutForDomShipments.docx'
Dave Fisher Highest Ready For Testing
Nathan Palmer 8/30/2021 5:30:56 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 8/30/2021 4:03:23 PM NO Worldtrak
Chnageset 57835
AirTrak.vbproj

rptRoutingLabelDom.Designer.vb add
rptRoutingLabelDom.resx add
rptRoutingLabelDom.vb add

RoutingLabelAR.aspx.vb
DataAccess.vb
Nathan Palmer Highest Merge to 79/162
Dave Fisher 8/27/2021 1:03:53 PM NO Look at the new attachment for guidance:
22855_Label_NEW_FORMAT_Example.docx
Preeti Nevrekar Highest Open
Preeti Nevrekar 8/24/2021 11:10:21 AM NO Dave,

In the attached 'RoutingLabel Label_20210823 NEW LAYOUT.png'
I have below clarifications.

1) MAWB-DST-(ORD)- Is this the DEST Airport?
2) HAWB-DEST-(DSM/B)-where should I get this value from?
3) CARRIER-This is the VendorPrefix that we show with the DEST Airport at the bottom of the label for international shipments right? eg (ORD-0472)
4) Can you please give me the OrderNo from Pilot Test for the attached label?
Dave Fisher Highest Questions
Preeti Nevrekar 8/23/2021 12:25:42 PM NO Preeti Nevrekar Highest In progress
Dave Fisher 8/23/2021 12:01:25 PM NO We have a new layout I need you to account for.
This will only apply for domestic shipments, so you will need to keep the original layout for international.

Attached:
RoutingLabel Label_20210823 NEW LAYOUT.png
Preeti Nevrekar Highest Re-Work
Brian Cronin 8/5/2021 2:51:29 PM NO Installed on Pilot AWS DEV TEST on 08/05. Nathan Palmer Highest Waiting For ReleaseP
Nathan Palmer 8/3/2021 6:32:32 PM NO Brian Cronin Highest Ready For Install
Dave Fisher 7/28/2021 9:19:56 AM NO Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 7/19/2021 10:08:20 PM NO Note : Fixed the below
small issue with the pieces on the routing label... it looks to be a space issue. I have attached an image of what is happening (pilot_pieces_space.png). Please allow space for at least "9999 of 9999".
Dave Fisher Highest Ready For Testing
Nathan Palmer 7/19/2021 5:48:30 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 7/19/2021 3:36:03 PM NO Worldtrak
Changeset 57057
rptRoutingLabel.Designer.vb

CVPortal
Changeset 57058
rptRoutingLabel.Designer.vb
Nathan Palmer Highest Merge to 79/162
Dave Fisher 7/19/2021 3:00:08 PM NO small issue with the pieces on the routing label... it looks to be a space issue. I have attached an image of what is happening (pilot_pieces_space.png). Please allow space for at least "9999 of 9999". Preeti Nevrekar Highest Re-Work
Nathan Palmer 6/17/2021 5:48:32 PM NO Put new script in 2/22 PRS folder. Brian Cronin Highest Ready For Install
Brian Cronin 6/16/2021 2:51:32 PM NO Nathan Palmer Highest Branch - 02/22
Dave Fisher 6/16/2021 2:41:36 PM NO Brian Cronin Highest Needs to be Merged
Preeti Nevrekar 6/15/2021 1:43:46 PM NO I updated the view '22855-Script-VW_RoutingDetail.txt' and the 'CustomerLabelRoutingCodes' grid loads the correct consignee name.

Attached is the screenshot 'Pilot-Test-CustomerLabelRoutingCodespng.png'
Dave Fisher Highest Ready For Testing
Dave Fisher 6/15/2021 1:18:01 PM NO yes, please go ahead and update the view on Pilot TEST... and confirm fixed. Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 6/15/2021 11:39:15 AM NO Dave, Fixed the below issue and attached is the updated View '22855-Script-VW_RoutingDetail.txt' Dave Fisher Highest Ready For Testing
Preeti Nevrekar 6/15/2021 10:47:54 AM NO Dave, Fixed the below issue and attached is the updated View '22855-Script-VW_RoutingDetail.txt'

Please let me know if you want me to update the view on Pilot Test.
Dave Fisher Highest Questions
Dave Fisher 6/15/2021 8:42:08 AM NO Looks like there may be an issue with the new "Customer Routing Label Codes" grid.

From Sam at Pilot:
F"or the Customer Routing Label Codes, the name of the consignee is not matching up with the consignee number. For example, in the last row, the consignee number that has been entered is 133, which is the number for ABT ELECTRONICS. But the name in the line shows Invoice Testing, which is number 28."

I have attached a screenshot "22855_consignee_not_matching.png".
Preeti Nevrekar Highest Re-Work
Brian Cronin 6/15/2021 6:57:45 AM NO Dave - A few things: I saw Sam sent you an email about fixing something on this ticket. Please update it. Also - Please look at the latest notes from Preeti on her testing and confirm. Dave Fisher Highest Re-Work
Preeti Nevrekar 6/7/2021 9:36:26 AM NO Brian,

Test case : Pilot Test
Consol : 272
Consol : 250
HAWB : 1592/ 1606

Tested the issues reported in the below attached docs from Pilot
1)Pilot_Routing_Label_Remaining_Issues_20210426.docx
2)RoutingLabel Label_20210528.pdf

Also Brian, I am yet to merge this fixes in CVPortal. Please let me know if all goes well will fix in CVPortal as well.
Brian Cronin Highest Ready For Testing
Preeti Nevrekar 6/7/2021 9:33:57 AM NO Brian,

Test case : Pilot Test
Consol : 272
Consol : 250
HAWB : 1592/ 1606

Tested the issues reported in the below attached docs from Pilot
1)Pilot_Routing_Label_Remaining_Issues_20210426.docx
2)RoutingLabel Label_20210528.pdf
Brian Cronin Highest Ready For Testing
Brian Cronin 6/5/2021 1:40:45 PM NO Installed on Pilot TEST on 06/05. Preeti - Please test and give me the HAWB#/Consol# you test with. Preeti Nevrekar Highest Priority
Nathan Palmer 6/2/2021 6:05:46 PM NO Brian Cronin Highest Ready For Install
Brian Cronin 6/2/2021 1:06:43 PM NO Nathan Palmer Highest Branch - 02/22
Dave Fisher 6/2/2021 12:21:22 PM NO Brian Cronin Highest Needs to be Merged
Preeti Nevrekar 5/28/2021 12:20:06 PM NO Yes Dave,

I have already fixed the issues also confirmed the same in the test cases(162) dated 5/14/2021 3:47:38 PM.
Dave Fisher Highest Ready For Testing
Dave Fisher 5/28/2021 12:03:28 PM NO Preeti,

This is from Sam at Pilot. Please either fix or confirm this was already fixed (since we don't have your latest changes installed yet). I attached the PDF, called "RoutingLabel Label_20210528.pdf".

"I attached a copy of the routing label that was emailed at the consol level (consol #272).
When emailing the label, the pieces and weight are not being shown, but when we view the label we can see them.

Also, when emailing the label, the MAWB # is pulling from the Consolidation Ref # field. But when viewing the label it shows the line haul carriers prefix in front of the Auto-assigned Pro #, which is what it's supposed to be.
Same thing goes for the MAWB # that is shown at the bottom of the top barcode."
Preeti Nevrekar Highest Priority
Dave Fisher 5/28/2021 10:34:04 AM NO Dave Fisher Highest Ready For Testing
Brian Cronin 5/14/2021 3:56:10 PM NO Dave - please test. I don't want to install at Pilot until you think we are good. Dave Fisher Highest Ready For Testing
Preeti Nevrekar 5/14/2021 3:47:38 PM NO Worldtrak-Test Cases 162

TestCases:-Consolidation Level-Consol:11367/130102
Tested from : Docs Page/Email/Individual HAWB (part of consolidation) from Shipment Board.

TestCases: Shipment Level-HAWB: 47247/ 3072 /43340
Tested from : Docs Page/Email/Shipment Board

Fixed the below issues reported for Consolidation-HAWB-118 on Pilot Test also in the Email feature.

1)The top of the label is supposed to show the combined pieces and weight of all the shipments within the consol, but it only shows the individual shipment level details.

2) Was showing multiple vendor Prefixes for the top label.

3) The bottom tracking number (ORD-45648914) is pulling from the Consolidation Ref # field but it should just be pulling the Dest airport code followed by the linehaul carrier prefix.

4) The top MAWB # is also pulling from the Consolidation Ref # field but it's supposed to contain the line haul carriers prefix in front of the Auto-assigned Pro # field.

5) The "Agent" field in the label is showing the Agent # but we need it to show the Agent Name.

6) When printing the Routing Label from the Domestic Shipment Board, the MAWB information does not show up.
Brian Cronin Highest Ready For Testing
Nathan Palmer 5/14/2021 2:45:47 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 5/14/2021 12:35:39 PM NO Worldtrak
Changeset 56040
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb



Note : Minor fix after testing
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 5/14/2021 10:09:04 AM NO Preeti Nevrekar Highest In progress
Nathan Palmer 5/13/2021 5:19:45 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 5/13/2021 1:06:13 PM NO Nate,

Please merge the below Changesets
Worldtrak
Changeset 56017
Changeset 56022
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 5/13/2021 1:05:01 PM NO Worldtrak
Changeset 56022
EmailDoc.aspx.vb
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb
DataAccess.vb
Preeti Nevrekar Highest In progress
Preeti Nevrekar 5/12/2021 9:33:01 PM NO Worldtrak
Changeset 56017
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb
DataAccess.vb
Preeti Nevrekar Highest In progress
Preeti Nevrekar 5/11/2021 11:17:02 AM NO Preeti Nevrekar Highest In progress
Brian Cronin 5/11/2021 11:04:27 AM NO Just note on the ticket which ones failed and get them fixed and checked into 162. Once they test out here, I will have Nate merge them into the 02/22 release. Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 5/11/2021 10:40:05 AM NO Brian,
While testing on Pilot found a few issues. How should I proceed on this? Make a Test cases document with the Pass/Fail ? or Directly Fix them?
Brian Cronin Highest Questions
Preeti Nevrekar 5/10/2021 3:50:18 PM NO Preeti Nevrekar Highest In progress
Brian Cronin 5/8/2021 8:47:50 AM NO Preeti - I installed this on Pilot TEST on 05/08. Please test over there and let me know how everything goes. Please give me the test shipment/consol you worked with as well. Preeti Nevrekar Highest Priority
Nathan Palmer 5/7/2021 5:05:04 PM NO Brian Cronin Highest Ready For Install
Brian Cronin 5/7/2021 12:58:59 PM NO Nathan Palmer Highest Branch - 02/22
Dave Fisher 5/7/2021 11:49:53 AM NO Brian Cronin Highest Needs to be Merged
Preeti Nevrekar 5/3/2021 12:40:04 PM NO Dave,

Please find the attached document 'Pilot_Routing_Label_Remaining_Issues_20210503.docx' with the Test Cases from 162 at the end.

Let me know if all ok. I will make the changes to CVPortal as well.
Dave Fisher Highest Ready For Testing
Nathan Palmer 4/30/2021 5:57:46 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 4/30/2021 3:37:02 PM NO Worldtrak
Changeset 55803
Docs.aspx.vb

Changeset 55804
Docs.aspx.vb





Note : Fixed an issue on 162 on click of documents page from consolidation . Ticket #23513
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 4/30/2021 12:40:20 PM NO Preeti Nevrekar Highest In progress
Nathan Palmer 4/29/2021 5:47:12 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 4/29/2021 4:18:29 PM NO Worldtrak
Changeset 55788
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb
DataAccess.vb
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 4/29/2021 9:20:18 AM NO Preeti Nevrekar Highest In progress
Dave Fisher 4/26/2021 9:20:26 AM NO Please review the attached document Pilot_Routing_Label_Remaining_Issues_20210426.docx, and fix what needs to be fixed. Let me know if you have any questions. Preeti Nevrekar Highest Open
Nathan Palmer 4/19/2021 12:53:38 PM NO Brian Cronin Highest Ready For Install
Brian Cronin 4/13/2021 6:29:21 AM NO ok...I will let it go for now. Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 4/12/2021 8:51:39 PM NO Brian,

Please find the attached test case HAWB : 7119 'HAWB-7119-Forair.png
Now it shows prefix with the HAWB at the end of the label i.e 4720019955667756 where 472 is the Prefix.

I am showing the entire MAWB with prefix and not only the prefix as per Dave's comments.

Note : Fixed below
#7 -04/07 - per our conversation: Pull the waybill prefix either from the additional info page for LH or the additional info page for the air carrier based on the type of the vendor used on the shipment/consolidation.
Brian Cronin Highest Ready For Testing
Nathan Palmer 4/12/2021 5:54:10 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 4/12/2021 11:53:15 AM NO Worldtrak
Changeset 55442
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb
DataAccess.vb


Note : Fixed below
04/07 - per our conversation: Pull the waybill prefix either from the additional info page for LH or the additional info page for the air carrier based on the type of the vendor used on the shipment/consolidation.
Nathan Palmer Highest Merge to 79/162
Brian Cronin 4/7/2021 11:16:06 AM NO Installed on Pilot TEST on 04/05.

HAWB 1026

1. ok.

2. ok.

3. ok.

4. ok.

5. ok.

6. ok

7. Looks like you are printing the MAWB#. I am guessing they will not like this, but I will see what they say.

04/07 - per our conversation: Pull the waybill prefix either from the additional info page for LH or the additional info page for the air carrier based on the type of the vendor used on the shipment/consolidation.

8. ok.

9. Better, but not great. I think they will have to resize it. Doesn't look correct on other forms either. Leave alone for now.

04/07 - Nothing further needed as of now.

10. Consol# 200 -

a. ok

b. The carrier code isn't showing next to the shipment level barcode.
------------------------
04/05 - still doesn't look right to me.
04/07 - Actually per the spec. Will talk to Pilot.

c. And when using the CHB, the tracking # field is showing correctly, but the barcode still shows the HAWB number.
-----------------------
04/07 Looks good now.

d. 04/05 NEW - At the very bottom of the form, it is showing 'Test Code-FL-32434'. I know it is supposed to show the destination airport of the consolidation followed by the waybill prefix.

04/07 - You explained why. Thanks.
Preeti Nevrekar Highest In progress
Preeti Nevrekar 4/5/2021 12:40:11 PM NO Preeti Nevrekar Highest In progress
Brian Cronin 4/5/2021 10:54:14 AM NO Installed on Pilot TEST on 04/05.

HAWB 1026

1. ok.

2. ok.

3. ok.

4. ok.

5. ok.

6. ok

7. Looks like you are printing the MAWB#. I am guessing they will not like this, but I will see what they say.

8. ok.

9. Better, but not great. I think they will have to resize it. Doesn't look correct on other forms either. Leave alone for now.

10. Consol# 200 -

a. ok

b. The carrier code isn't showing next to the shipment level barcode.
------------------------
04/05 - still doesn't look right to me.

c. And when using the CHB, the tracking # field is showing correctly, but the barcode still shows the HAWB number.

d. 04/05 NEW - At the very bottom of the form, it is showing 'Test Code-FL-32434'. I know it is supposed to show the destination airport of the consolidation followed by the waybill prefix.

Bill your time to the original mod.
Preeti Nevrekar Highest Priority
Nathan Palmer 3/29/2021 5:29:23 PM NO Brian Cronin Highest Ready For Install
Brian Cronin 3/22/2021 12:26:22 PM NO 4. ok

7. 03/15 - ok for now.

9. 03/22 - ok for now. Won't know for sure until we install at Pilot, but as of 03/22, it looks better on 162.

10. Consol# 11367 - on 162

a. ok
b. I still don't see it. Am I missing it?
-------
03/15 - HOLD FOR NOW

c. 03/15 - when using the CHB, the tracking # field is showing correctly, but the barcode still shows the HAWB number.
-------
03/22 - ok for now.
Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 3/22/2021 10:50:13 AM NO Brian Cronin Highest Ready For Testing
Nathan Palmer 3/19/2021 5:09:09 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 3/19/2021 11:04:25 AM NO Worldrak
Changeset 54946
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb

CVportal
Changeset 55066
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb
DataAccess.vb
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 3/15/2021 4:08:26 PM NO Worldrak
Changeset 54946
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb
Preeti Nevrekar Highest In progress
Brian Cronin 3/15/2021 1:35:18 PM NO Preeti - ok, please check in your code. Preeti Nevrekar Highest Questions
Preeti Nevrekar 3/15/2021 12:31:10 PM NO Brian, I am yet to checkin the code with updates and hence you cant see the changes, I gave you the working snapshots form my local in the attached document with the clarifications. Did you get a chance to review the clarifications at the end of the attached document '22855-TestCases-162Update.docx' ? starting with 1.ok?


If you have already, then I will go ahead and checkin the changes.
Brian Cronin Highest Questions
Brian Cronin 3/15/2021 11:53:24 AM NO 1. ok.

2. ok.

3. ok.

4. HAWB 7119 - I added a delivery agent to the shipment. The delivery agent isn't showing on the label. Why?
--------------
03/15 - Still isn't working. I just tested on 162. Same HAWB: 7119

5. ok.

6. ok

7. 03/15 - ok for now.

8. ok.

9. 03/15 - ok for now. Won't know for sure until we install at Pilot.

10. Consol# 11367 - on 162

a. ok
b. I still don't see it. Am I missing it?
-------
03/15 - HOLD FOR NOW

c. 03/15 - when using the CHB, the tracking # field is showing correctly, but the barcode still shows the HAWB number.
Preeti Nevrekar Highest Re-Work
Brian Cronin 3/15/2021 11:45:35 AM NO 1. ok.

2. ok.

3. ok.

4. HAWB 7119 - I added a delivery agent to the shipment. The delivery agent isn't showing on the label. Why?
--------------
03/15 - Still isn't working. I just tested on 162. Same HAWB: 7119

5. ok.

6. ok

7. 03/15 - ok for now.

8. ok.

9. 03/15 - ok for now. Won't know for sure until we install at Pilot.

10. Consol# 11367 - on 162

a. ok
b. I still don't see it. Am I missing it?
-------
03/15 - HOLD FOR NOW

c. I will test this later
-------
03/15 - HOLD FOR NOW
Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 3/15/2021 10:50:56 AM NO Brian,

Please find the attached '22855-TestCases-162Update.docx' with your Testcases and clarifications at the end of the document starting with 1.Ok 2 .OK.
Brian Cronin Highest Questions
Brian Cronin 3/12/2021 2:09:14 PM NO 1. ok.

2. ok.

3. ok.

4. HAWB 7119 - I added a delivery agent to the shipment. The delivery agent isn't showing on the label. Why?

5. ok.

6. ok

7. HAWB 7199 - I picked the FORAIR carrier and generated the label. The prefix is shows 001, which I know isn't correct. FORAIR is set to '472'. I believe it is picking it from AA-DOM.

Also - What are you doing when there is more than 1 carrier on the shipment and you produce the label from the shipment board? Just picking the first carrier you see?

8. ok.

9. Sorry...I meant to type the LOGO. Like this:

The logo is NOT sized correctly. It should be just like every other form. Please fix.

10. Consol# 11367 - on 162

a. ok
b. I still don't see it. Am I missing it?
c. I will test this later
Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 3/12/2021 8:52:38 AM NO Brian,

I have fixed the below mentioned issues in Worldtrak for now. If all works good will just replicate this in CVPortal.


Please find the attached '22855-TestCases-162.docx' document containing the issues and the test case screenshots.
Brian Cronin Highest Ready For Testing
Nathan Palmer 3/11/2021 6:26:02 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 3/11/2021 4:00:38 PM NO Worldtrak

Changeset 54881
EmailDoc.aspx.vb
RoutingLabelAR.aspx.vb


Changeset 54886
EmailDoc.aspx
EmailDoc.aspx.designer.vb
EmailDoc.aspx.vb
Nathan Palmer Highest Merge to 79/162
Nathan Palmer 3/10/2021 6:27:01 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 3/10/2021 1:22:12 PM NO Worldtrak
Changeset 54874
Docs.aspx
Docs.aspx.vb
EmailDoc.aspx.vb
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb
DataAccess.vb
Nathan Palmer Highest Merge to 79/162
Nathan Palmer 3/9/2021 5:25:11 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 3/9/2021 2:10:31 PM NO Nate ,

Please merge the below chnagesets
Worldtrak
Changeset 54173
Changeset 54840
Changeset 54856
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 3/9/2021 2:08:22 PM NO Changeset 54856
Docs.aspx
Docs.aspx.vb
EmailDoc.aspx.vb
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb
DataAccess.vb
Preeti Nevrekar Highest In progress
Shilpa Sahu 3/8/2021 2:07:27 PM NO Changeset 54173
ShipmentBoard.aspx.vb

Note: Fixed modeID columnindex based on this ticket's change.
Preeti Nevrekar Highest In progress
Preeti Nevrekar 3/8/2021 10:50:32 AM NO Checking with Dave for a couple of Clarifications. Preeti Nevrekar Highest In progress
Preeti Nevrekar 3/5/2021 7:10:44 PM NO Worldtrak
Changeset 54840
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb
DataAccess.vb
Preeti Nevrekar Highest In progress
Preeti Nevrekar 3/4/2021 8:57:30 AM NO Preeti Nevrekar Highest In progress
Brian Cronin 3/4/2021 8:54:36 AM NO Found several issues on Pilot TEST. Please review and fix. Let Dave know if you have any questions.

HAWB 1026

1. Product Code Description is wrapping. Reduce the font for this and the 'SSA' area.

2. Show the product code and the description. Example:
XXX - TEST PRODUCT CODE DESC

3. SSA is showing the salesperson. It should be showing the delivery agent vendor ID from the shipment/consol

4. Change the description of 'SSA' to 'AGENT'

5. The Barcode at the top of the label and the number underneath it need to be hidden if no MAWB# filled out for the shipment/consol. tbl_aircost - MAWB

6. You are showing delivery instructions instead of special instructions. Please fix.

7. If you aren't already doing this, you need to show the waybill prefix (vendor master - additional info for LH or Air Carrier) after the destination airport at the bottom of the label.

8. Remove 'Party Type' from the form.

9. The label is NOT sized correctly. It should be just like every other form. Please fix.

10. Consol# 200 -

a. The MAWB # isn't appearing on the label or under the Master bill barcode.
b. Thee carrier code isn't showing next to the shipment level barcode.
c. And when using the CHB, the tracking # field is showing correctly, but the barcode still shows the HAWB number.

Bill your time to the original mod.
Preeti Nevrekar Highest Priority
Brian Cronin 3/4/2021 6:27:43 AM NO Found several issues on Pilot TEST. Please review and fix. Let Dave know if you have any questions.

HAWB 1026

1. Product Code Description is wrapping. Reduce the font for this and the 'SSA' area.

2. Show the product code and the description. Example:
XXX - TEST PRODUCT CODE DESC

3. SSA is showing the salesperson. It should be showing the delivery agent vendor ID from the shipment/consol

4. Change the description of 'SSA' to 'AGENT'

5. The Barcode at the top of the label and the number underneath it need to be hidden if no MAWB# filled out for the shipment/consol. tbl_aircost - MAWB

6. You are showing delivery instructions instead of special instructions. Please fix.

7. If you aren't already doing this, you need to show the waybill prefix (vendor master - additional info for LH or Air Carrier) after the destination airport at the bottom of the label.

8. Remove 'Party Type' from the form.

9. The label is NOT sized correctly. It should be just like every other form. Please fix.

Bill your time to the original mod.
Preeti Nevrekar Highest Priority
Brian Cronin 3/1/2021 11:27:56 AM NO Nathan Palmer Highest Waiting For ReleaseP
Preeti Nevrekar 3/1/2021 11:26:22 AM NO Brian,

Updated the Ticket 22777 and this is working on Pilot test.
Brian Cronin Highest Ready For Testing
Brian Cronin 3/1/2021 8:07:14 AM NO Installed on Pilot TEST on 03/01. I have both label flags on, but I don't see either in CVPortal. Preeti Nevrekar Highest Priority
Nathan Palmer 2/24/2021 5:19:16 PM NO Brian Cronin Highest Ready For Install
Brian Cronin 2/23/2021 7:40:10 PM NO Nate - Do NOT put any of these scripts in the PRS folder. Nathan Palmer Highest Branch - 02/22
Preeti Nevrekar 2/23/2021 6:43:31 PM NO Brian,

Please find the attached 'CF-1864 and CF-1867 set to 'N'.png' test case for the below issue in Worldtrak #2

2. This label shows as an option on the regular default board even though 1767 = 'N'. This happens on 162 as well.

Also , tested the CVPortal for the below reported issue by Nate. Test Case 'VPortal-CF-1864-CF-1867-Set-N.png'

Found another issue in CVPortal. Ticket# 22855 is involved as well. When the flag is off for this mod it hides the column on the shipment board like it should, but it is putting the columns after out of order.
Brian Cronin Highest Ready For Testing
Nathan Palmer 2/23/2021 5:43:34 PM NO Merged the latest CVPortal changes for a small fix to 2/4(4.7.2) since the rest is already in there. Preeti Nevrekar Highest Ready For Testing
Nathan Palmer 2/23/2021 5:24:09 PM NO Preeti Nevrekar Highest Ready For Testing
Nathan Palmer 2/23/2021 2:57:42 PM NO CVPortal
Changeset 54674

Worldtrak
Changeset 54664
Nathan Palmer Highest Merge to 79/162
Nathan Palmer 2/23/2021 2:19:37 PM NO The below is for CVPortal by the way. Preeti Nevrekar Highest Re-Work
Nathan Palmer 2/23/2021 2:16:14 PM NO See ticket# 22777 as well. When the flag is off for this mod it hides the column on the shipment board like it should, but it is putting the columns after out of order.

I believe it has something to do with the way you're hiding the column. Instead of using Visible true or false, set the data-type to "hidden" to hide and "checkbox" to show it.

Call me if you have any questions.
Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 2/23/2021 8:26:50 AM NO Changeset 54664
ShipmentBoard.aspx.vb


Note : Fixed the below #2 in this and another similar issue in Ticket #22777 in same above changeset. When we merge this ticket to release Please merge Ticket #22777 too.

2. This label shows as an option on the regular default board even though 1767 = 'N'. This happens on 162 as well.
Nathan Palmer Highest Merge to 79/162
Brian Cronin 2/22/2021 10:27:15 AM NO 1. It doesn't hang anymore, but there are still some issues with it. I will ask someone else to review that part as it has nothing to do with this ticket.

Note: I re-uploaded with the latest copies from 162:

'22855-Script-Alter-DomesticShipQuoteBoardWT-PrintRoutingLabel.txt
'22855_vw_DefaultNew.txt
'22855_vw_DefaultNewCHB.txt

2. back to you.
Preeti Nevrekar Highest Re-Work
Preeti Nevrekar 2/22/2021 9:49:04 AM NO Brian,

#1 We need to run the attached script '22855-Script-Alter-DomesticShipQuoteBoardWT-PrintRoutingLabel.txt' which contains the below columns on Pilot.

'PrintShipperConsigneeLabel' and 'PrintRoutingLabel'.


#@ In Progress
Brian Cronin Highest Questions
Brian Cronin 2/22/2021 7:50:57 AM NO I installed the 02/04/2021 release on Pilot TEST:

https://worldtrak-test.pilotdelivers.com/

I haven't tested this completely yet, but 2 issues stick out that need to be fixed ASAP:

1. DefaultNEW Hangs when you try to get to it. Here is the error:

DB Message:
Invalid column name 'PrintShipperConsigneeLabel'.
Invalid column name 'PrintRoutingLabel'.

Note: This one does NOT happen on 162. I tried running the latest script for the vw_DefaultNew and vw_DefaultNewCHB views. At first they didn't run because it was missing 'gatewaystation', so I removed that...I was then able to run the script, but I still get the same error.

2. This label shows as an option on the regular default board even though 1767 = 'N'. This happens on 162 as well.
Preeti Nevrekar Highest Priority
Brian Cronin 2/22/2021 7:29:59 AM NO I installed the 02/04/2021 release on Pilot TEST:

https://worldtrak-test.pilotdelivers.com/

I haven't tested this completely yet, but 2 issues stick out that need to be fixed ASAP:

1. DefaultNEW Hangs when you try to get to it. Here is the error:

DB Message:
Invalid column name 'PrintShipperConsigneeLabel'.
Invalid column name 'PrintRoutingLabel'.

Note: This one does NOT happen on 162. Just try attaching the latest script for the defaultnew view. As soon as you have it attached, text me so I can run it over there and see if it works.

2. This label shows as an option on the regular default board even though 1767 = 'N'. This happens on 162 as well.
Preeti Nevrekar Highest Priority
Brian Cronin 2/1/2021 3:08:02 PM NO Nathan Palmer Highest Branch - 04/12
Dave Fisher 2/1/2021 10:03:18 AM NO Brian Cronin Highest Needs to be Merged
Brian Cronin 1/26/2021 3:55:41 PM NO Dave - Please review Jeanne's comments. Based on her results, do you think this ok? I don't think she tested the maint program. I also don't see anything about the API for the scanner app. Is that going to be handled separately? Dave Fisher Highest Ready For Testing
Jeanne Graziano 1/25/2021 12:30:03 PM NO Breaking this up into two responses.
For this first part on label printing see below
Label Format response to follow

With CF set to N, you do not see the Routing labels options.
With CF set to Y, You see the options

Selected shipment 7610 and 7611 from main board and clicked on the routing label icon. It pulled up the correct number of shipment and correct number of labels for each.

Went into individual shipments to the document tab and selected routing label. It printed the correct labels for each shipment selected.

NOTE: The check marks do not clear once you select the print Icon. Not sure if you want this to happen.


Pulled up consol 130102 and clicked on documents tab. Selected Routing Label. Received pdf with correct number of shipments and correct number of labels for each shipment.

Emailed routing labels and received correct number of labels for each shipment on the consol.

Note: Not sure if a button should appear on the Consolidation board or consolidation entry screen to print these labels. The only available place I see is on the documents tab.
Brian Cronin Highest Ready For Testing
Brian Cronin 1/23/2021 3:40:10 PM NO Jeanne - Please test. Jeanne Graziano Highest Ready For Testing
Preeti Nevrekar 1/6/2021 9:55:40 PM NO Dave Fisher Highest Ready For Testing
Nathan Palmer 1/6/2021 6:41:35 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 1/6/2021 12:23:24 PM NO Worldtrak
Changeset 53803
CustomerLabelRoutingCodes_mp.aspx
DataAccess.vb


CVPortal
Changeset 53802
DataAccess.vb



Note : Fix After testing
Nathan Palmer Highest Merge to 79/162
Nathan Palmer 1/5/2021 4:29:09 PM NO Preeti Nevrekar Highest Ready For Testing
Preeti Nevrekar 1/5/2021 3:00:42 AM NO Nate Please merger the below Changeset
Worldtrak
Changeset 53726
Changeset 53728
Changeset 53735
Changeset 53767
Changeset 53784


CVportal
Changeset 53743
Changeset 53744
Changeset 53745
Changeset 53783
Nathan Palmer Highest Merge to 79/162
Preeti Nevrekar 1/5/2021 2:55:19 AM NO CVPortal
Changeset 53745
CVPortal.vbproj

Changeset 53783
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb

Worldtrak
Changeset 53767
UserEdit.aspx
UserEdit.aspx.designer.vb
UserEdit.aspx.vb

Changeset 53784
EmailDoc.aspx.vb
rptRoutingLabel.Designer.vb
RoutingLabelAR.aspx.vb
Preeti Nevrekar Highest In progress
Dave Fisher 1/4/2021 12:33:23 PM NO sent email Preeti Nevrekar Highest In progress
Preeti Nevrekar 12/30/2020 12:26:00 PM NO Dave,

For the below point where do we get the "Use For Documents" flag in which table?


CVPortal, DomShipBoard.aspx - add an additional checkbox to the grid to allow for multiple selection.
- When selecting multiple from the boards, check the expansion table (LH, AIR, etc.) for the carrier marked "Use For Documents" to get the correct MAWB.
Dave Fisher Highest Questions
Preeti Nevrekar 12/27/2020 12:34:05 PM NO CVPortal
Changeset 53743

rptRoutingLabel.Designer.vb add
rptRoutingLabel.resx add
rptRoutingLabel.vb add

RoutingLabelAR.aspx add
RoutingLabelAR.aspx.designer.vb add
RoutingLabelAR.aspx.vb add

DomShipBoard.aspx
DomShipBoard.aspx.designer.vb
DomShipBoard.aspx.vb

DataAccess.vb

Changeset 53744
CVPortal.vbproj
Preeti Nevrekar Highest In progress
Preeti Nevrekar 12/23/2020 3:55:05 PM NO Worldtrak
Changeset 53735
EmailDoc.aspx
EmailDoc.aspx.designer.vb
EmailDoc.aspx.vb

DefaultBoard_New.aspx
DefaultBoard_New.aspx.designer.vb
DefaultBoard_New.aspx.vb
Preeti Nevrekar Highest In progress
Preeti Nevrekar 12/23/2020 9:46:00 AM NO Worldtrak
Changeset 53728
AirTrak.vbproj
Preeti Nevrekar Highest In progress
Preeti Nevrekar 12/23/2020 1:09:40 AM NO Worldtrak
Changeset 53726
Docs.aspx
Docs.aspx.designer.vb
Docs.aspx.vb

CustomerLabelRoutingCodes_mp.aspx add
CustomerLabelRoutingCodes_mp.aspx.designer.vb add
CustomerLabelRoutingCodes_mp.aspx.resx add
CustomerLabelRoutingCodes_mp.aspx.vb add

ShipmentBoard.aspx
ShipmentBoard.aspx.designer.vb
ShipmentBoard.aspx.vb

rptRoutingLabel.Designer.vb add
rptRoutingLabel.resx add
rptRoutingLabel.vb add

RoutingLabelAR.aspx add
RoutingLabelAR.aspx.designer.vb add
RoutingLabelAR.aspx.vb add

WorldTrakSetup.Master
WorldTrakSetup.Master.designer.vb
WorldTrakSetup.Master.vb

DataAccess.vb
Preeti Nevrekar Highest In progress
Brian Cronin 12/18/2020 3:38:46 PM NO Preeti - Please finish this ticket. Preeti Nevrekar Highest In progress
Dave Fisher 11/10/2020 1:37:58 PM NO 1. correct.
2. just add 2 LH carriers to a shipment, then go to Documents.. you will see a little grid under Carrier Label. ex. HAWB 7119.
Preeti Nevrekar Highest In progress
Preeti Nevrekar 11/6/2020 11:16:56 AM NO Dave,


1) For "Customer Routing Label Codes" Maint screen
On ADD Record
Carrier(VendorId) lookup will Show the Vendors Lookup screen (VendorBoard_mp.aspx) with only linehaul carriers(Vendors)

i.e Only those records from tbl_Vendors where vendorID in (tbl_LinehaulCarrierVendors) right?

2) If a shipment has more than one carrier, you will need to present a selection grid similar to the Carrier Label in order to get the correct MAWB.

Can I get one test case for this?
Dave Fisher Highest Questions
Preeti Nevrekar 10/22/2020 12:24:55 PM NO Preeti Nevrekar Highest In progress