|
DAT-MAIL 5.10.25.03 / Statements 5.10.25.04
Install Notes:
Includes IPS 7.0.31.0
Case Notes:
Requires MD Client Manager v5.10.25.01
Case #3455
Revisited – coding upgrades to ensure 'Copy Weights' in the Mail Piece Unit View are accurate.
Case #3553
Revisited – more changes added to Daemon processing options for conformance testing, Export PO! Update Release File Automatically, ensure that Build Floating Batch ManifIest & Print Delivery Point Barcodes instead of Piece ID's are mutually exclusive, Import CVF Files option appears depends on the Print Delivery Point Barcodes instead of Piece ID's option.
Case #3564
Revisited – the option to delete ‘ALL’ Mother Pallets on import is now not dependent on NDC/MxNDC/SCF designations.
Case #3581
We have modified our USPS Sorted Pallets Plan options. We are no longer using the USPS optional minimums and only retaining the USPS required minimums (i.e. trays that meet 500 pounds or 72 linear feet). You may now choose whether our palletization program will use minimum pounds or linear feet. If both options are selected, both minimums must be met.
Case #3592
We removed the ‘sticky’ setting on the Single File Import screen for PDR and IMR options. We now will always display the Default Program Settings for those PDR and IMR options but allow a one-time-use override.
Case #3598
Revisited - More work was needed to ensure that newly imported files are capturing the Historical JobID data. We also changed the button text from ‘Populate missing Historical Job Numbers’ to ‘Populate Missing Historical Job ID’s’.
Case #3604
Functions in the old barcode library have been replaced with IPS calls.
Old bc553x.dll library removed.
Case #3606
Our ‘Export Mail.dat File’ feature has been updated to allow clients the option of exporting the entire file or a limited set of files that only includes the HDR and CSM records. An additional ‘Export File Name’ field is also present and allows for an override of the file name that will be exported. More work is needed to ensure that the file export windows are consistent from the main file menu and the file menu that appears from inside an opened Mail.dat job. In Part 2 of this case, we added CSV Exports to the Main Reports menu. A new CSV Export option was also added named ‘Container Summary by Scheduler ID’. This will export CSM fields from the Mail.dat file in CSV format that can be sent to Transportation companies that do not have Mail.dat software capabilities.
Case #3609
We have added .CSV as an option for importing Transportation Updates to Mail.dat files. New CSM fields are also available for importing that includes:
CSM - 1112: Reservation Number
CSM - 1113: Actual Container Ship Date
CSM - 1117: Scheduled Induction Date
CSM - 1118: Scheduled Induction Time
CSM - 1164: Actual Container Ship Time
CSM - 1162: FAST Content ID
CSM - 1163: FAST Scheduler ID
Case #3634
We added a new tab named ‘by Historical Job ID’ to the ‘Select Mail.Dat Files for batch Reports’ window.
Case #3635
Fixed several bugs with the ‘Tag By Range feature’ at the Mother Pallet View.
Case #3636
There are new IMB Assignment options in Program Setup at the Pallet Tracking/Intelligent Mail tab. Clients now have the option of assigning unique Intelligent Mail serial numbers upon file import or wait until the time of tag printing. The default selection is shown on the Single File import window and has a one-time override setting then the default setting will re-appear. Clients that wish to use their own IMB codes by not activating the ‘override’ boxes will see this new setting and should leave the default setting as ‘assign on import’ in order for the supplied codes to be logged to our SQL database. No new IMB codes will be assigned at import or tag printing.
Case #3639
We modified the coding for TMS Status updates in multi-user environments. If two users are both looking at the same Carter file in our TMS View and one of the jobs is ready for statement generate, User 1 starts the generate process and the record is locked correctly which doesn’t allow User 2 to access this record. When the record is unlocked at the end of the statement generation and PostalOne! ready-to-pay export processes, User 2 will now see the status change immediately. Also, after the Get Data Button is pressed, the PostalOne! status is now refreshed immediately.
Case #3650
We added Mass updates of User Info Lines 1 & 2 to Mother Pallet records. This also required us to open User Info Line 2 on Mother Pallet records. Changes to this data will propagate to the child containers.
Case #3655
We fixed an issue with Tag Printing when all Containers were selected. Only 60 tags at a time were being processed.
Case #3675
Record not available (33) error on the mdbmlg.tps\MDImportlog file when creating PostalOne export
Case #3677
We fixed an Error 41 when deleting a Mail.dat file. Clients who have experienced this error should rename their MDTrlrStop.dat file and allow the new version of DatMail to create a new (albeit empty) file.
Case #3695
We replaced NPS with IPS text on the Maintenance tab in program setup.
Case #3697
We fixed a refresh issue when the Related PQT records were called from within the Container Summary View. The list was either returned empty or it displayed incorrect PQT records after an edit.
Case #3706
Inside the 'View Entry Points' button of a Transportation Scheme record, we changed the text on the 'Populate BMC's' button to 'Populate NDC's'.
Statements 5.10.25.04
Case Notes:
Case #3542
MailShop interface changes:
a. MailShop browse list now allows incremental location on Job (previously only 1st character would be used).
b. MailShop could provide a list of drops without having a Job causing drops for all Jobs to be displayed. We are now preventing drop list in this scenario.
c. MailShop setup option added for Job selection to prevent records for Closed Jobs
Case #3680
Report Column Heading update on the Accounting Permit Activity Report now conditionally shows either 'Mailing Date' or "Posted Date' depending on which is selected in the report options.
Case #3689
3602-RV Destination experienced a vertical alignment issue when a standard consolidated form had only 1 destination. This has been cosmetically corrected.
Case #3475
We have begun supporting the 8017 form ‘Expedited Plant-Load Shipment Clearance (7/2008)’ for Origin mailings. There is a new setup option in DAT-MAIL Statements for 8017. ‘Allow Creation of 8017’ activates the ability to see and use the new 8017 form. ‘Always Create 8017’ will generate a corresponding 8017 form when an Origin postage statement is created. The default ‘DMU Destination Office’ information will be printed in Box 24. An 8017 form can also be manually created at the ‘Drop Ship Certification 8125/8017’ menu and includes the ability to tag multiple Origin statements. More work is needed to incorporate the 8017 form during statement generation of a Mail.dat file.
Case #3591
CSR Mailing Report by Job reflected a different client which led to changes in our Job renaming process.
|