Page Comparison

What is going to happen?

Pack & Ship was first launched in October 2021 as a Per-tenant will no longer be it´s 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.

...

• It is no longer required to manually install and update a separate Per-Tennant extension to use Pack & Ship, you will only need to download and update Mobile MWS(PDJ: Foreslår at fremhæve, at SaaS kunder endda får det automatisk).
• In order to create new functionality around the License Plate data structure, we need the License Plate data structure in Mobile WMS  

...

• When we have a timeline ready, it will be communicated here and on the Tasklet Yammer forum(PDJ: Foreslår at nævne der bliver en overgangsperiode) (MIV: fremhæve at man selv bestemmer hvornår man migrerer, men at der ikke kommer nye versioner af Pack and Ship som separat extension efter frigivelsen af version 1.XX).
• It´s up to you when you want to migrate, but after Pack & Ship version 1.XX new features related to Pack & Ship functionality will only be released as part of Mobile WMS.

What does this mean for existing customers?

If you are using Pack & Ship today without any specific code customizations, you just need to enable Pack & Ship as a feature in Mobile WMS. (PDJ: Foreslår at indsætte "today" eller "the PTE version" før "without")

It will require the last version of Pack & Ship and the latest version of Mobile WMS to do this.

After you enable Pack & Ship in Mobile WMS, all existing functionality and data from Pack & Ship will be available (PDJ: Foreslår at tilføje: "(We will provide guidance if you have made table extensions to MOS tables)".

Should we stop making customizations?

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

We have created a simple guide on how to handle any customizations below.

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.  (MIV: evt flytte selve guiden til konvertering af tilretninger til separat dokument (forbedre læsbarhed af artiklen for dem der ikke har tilretninger, alternativt fremhæve sektionen med egen overskrift, eller omformulere til the simple guide below))

All existing objects from Pack & Ship has have been renamed from MOS ObjectName to MOB ObjectName when from moved into Mobile WMS (PDJ: Der er lidt med formuleringen til sidste).

1. Replace dependency from Pack & Ship to Mobile WMS in the app.json file (MIV: in your custom project)
2. Search and replace 'MOB' to 'MOS' in your customized code to reference the renamed object and events now located in Mobile WMS (PDJ: ...object and events...)
3. Compile and build your customized code

Should we stop making customizations to Pack & Ship?

...

If you have made any table extensions to MOS tables, we can provide additional guidance to handle this.

Do you need more help?

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

...