TMS Issue Tracking - QA and Production

NOTR & PBPS may be feeding into 4Kites in staging, but we need to make sure they are turned on in Prod, as we are going live with the integration between TMS and Samsara, and PBPS and NOTR are already live in Samsara

The LH team has requested to rename the existing "AdHoc" to "AdHoc60" to be consistent with the other two new values of AdHoc48 & AdHoc24.

We are planning to have a 24hr, 48hr and general adhoc value for the Extra field. This is an improvement to issue TMS-I-141 Also we wish to filter out and exclude systemic SCAC's: GECO, SYSH, and UNKN on the Ref: Extra DRS's

Geno believes by promoting the Oct release form QA to Prod, it will (allegedly) overwrite all custom DRS' in Prod. We need to verify this behavior and plan for recovery/recreating the DRS post promotion

Tested in PRD, updated existing DRS for RNO2 (OID78442277237) , Created now DRS for ONT1 (OID78501010090)

Oct release + ACE 1132 + ACE 1134

Ann requested if we could automate, Ref: LoadProcess Criteria, if Shipment Type on the EL includes Interfacility, ReturnOB, or DeliveryOB, then Ref: LoadProcess = ToClientStaged needs to be applied to the shipment (SN) Geno, you should probably be...

How does a carrier input the actual pallet count?

We had discussed that this audit pend can be removed in the case when the totals match. Example: VSCA 1705044, 1705042, 1033527, etc

Unable to save Ref: NGSFacilityNum 0345. Getting Admin processing error