Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »


Requirements

  • Requires minimum MOB version 5.41

What is going to happen?

Pack & Ship will no longer be its own separate extension.

We have continuously improved the features based on your feedback and it has today grown into a solid product ready for the next step.

We are now ready to merge the existing Per-Tenant extension Pack & Ship into our main product Mobile WMS that you are already using today.

  • The migration will include data and functionality
  • After the migration, all existing functionality will be available

Why is this an advantage?

  • It is no longer required to manually install and update a separate Per-Tenant extension to use Pack & Ship, you will only need Mobile MWS.
  • In order to create new functionality around the License Plate data structure, we need the License Plate data structure in Mobile WMS  

When is this going to happen?

  • We expect to deliver the first version of Mobile WMS with Pack & Ship functionality in Q2 of 2023
  • All information related to this migration will be announced on the Tasklet Yammer forum.

Will we be forced to migrate?

  • No, It´s up to you when you are ready and want to migrate, but new features related to Pack & Ship functionality will only be released as part of Mobile WMS.

What does this mean for existing customers?

You will need to migrate from the existing separate Pack & Ship extension to the new version of Mobile WMS.

To ensure the correct migration process, please follow this guide: How-to: Migration of Pack & Ship

After the migration process, all existing functionality and data from Pack & Ship will be available.

Should we stop making customizations?

No. you can still continue to build customization for Pack & Ship.

We will share a simple guide on how to handle any customizations in the section "How should we handle existing customizations" below.

How should we handle the migration process?

To ensure the correct migration process, please follow the guide below

How-to: Migration of Pack & Ship

How should we handle existing customizations?

In case of any customizations, you need to follow this simple guide to prepare your code to work after the migration.

All existing objects from Pack & Ship have been renamed from MOS ObjectName to MOB ObjectName when moved into Mobile WMS.


  1. Replace dependency from Pack & Ship to Mobile WMS in the app.json file in your custom project
  2. Update dependency on Mobile WMS to version 5.41.0.0
  3. Search and replace 'MOS' with 'MOB' in your customized code to reference the renamed object and events now located in Mobile WMS
    1. make sure to use these settings when using the replace function in VS Code
      1. 'Match Case'
      2. 'Match whole word'
  4. Verify the result,
  5. Update your version number and re-compile your customization

    Example of Search & Replace: 

How should we handle the 'ShipIT365 Connector' and 'Loctrade Connector'?

A new version of the connectors will be available.

Do you need more help?

  • Please raise an issue in the Service Desk and request assistance on Pack & Ship migration.

 

  • No labels