INDHOLDSFORTEGNELSE
- Updating user roles after a release
- Opdatering af brugerroller efter en release
- New feature overview
- New features
- Updates to existing features
- Bug fixes and other corrections
Expected release: 19/11
Updating user roles after a release
After each release, we update the PeakWMS standard roles so they give access to the new features.
Your own user roles are not updated automatically
We do not update user roles that you have created yourselves. You need to keep them up to date after each release. For each feature and update in the release notes, you can see whether you need to change your user roles to get access to it. If nothing is noted next to a feature, it doesn’t need any user role permissions to work.
Note: Always have at least one employee with a standard admin role
We recommend that at least one of your employees always has one of the PeakWMS standard admin roles. That way, at least one person always has access to the new features. If none of your employees has a PeakWMS standard role, you won’t be able to update your own user roles.
Opdatering af brugerroller efter en release
Efter hver release opdaterer vi PeakWMS’ standardroller, så de giver adgang til de nye funktioner.
Jeres egne brugerroller opdateres ikke automatisk
Brugerroller, som I selv har oprettet, bliver ikke opdateret af os. Dem skal I selv holde opdateret efter hver release. Ved hver funktion og opdatering i release noten kan I se, om I skal ændre jeres brugerroller for at få adgang til den. Er der ikke angivet noget ud for funktionen, er ingen brugerrollerettighed påkrævet, for at funktionen virker.
OBS: Hav altid mindst én medarbejder med en standard adminrolle
Vi anbefaler, at mindst én af jeres medarbejdere altid har en af PeakWMS’ standard adminroller. Så har I altid mindst én person med adgang til de nye funktioner. Hvis ingen af jeres medarbejdere har en PeakWMS standardrolle, kan I ikke selv opdatere jeres egne brugerroller.
New feature overview
Type | Title | Subtitle | Source | Value |
|---|---|---|---|---|
New feature | Shipping: Resend a shipped shipment and replace the old documents | New Resend action on shipped deliveries that can delete the old shipping documents when the new ones are created | No duplicate documents on the delivery that have to be cleaned up by hand | |
New feature | Admin: Combine "and" and "or" when searching tables | Search criteria in the table dialogs can be combined with both "and" and "or" | Not specified | Better search in tables, making it easier to find exactly the data you are looking for |
New features
Shipping: Resend a shipped shipment and replace the old documents
Shipped deliveries have a new action, Resend. When a delivery is sent again, the old shipping documents, such as the Commercial Invoice and End of Day list, can be deleted at the same time as the new ones are created. This means there are no longer duplicate documents on the delivery that have to be cleaned up by hand.
Admin: Combine "and" and "or" when searching tables
Search in the table dialogs now supports combining search criteria with both "and" and "or" in a more intuitive interface. This makes it easier to find exactly the data you are looking for.
Updates to existing features
Receiving: Find order lines by any part of the item number, description or barcode
The "Search for line" field in receiving now finds a line from any part of the item number, description or barcode, for example "10234" or "blk" for the item number MUR-10234-BLK. Previously you had to type the start of the item number or the full barcode. This saves time when receiving orders with many lines.
Shipping: Planned pickup date is sent to Homerunner
When a shipment is booked with Homerunner, the carrier's planned pickup date is now included, as with the other shipping integrations. Note that the shipping setup must have pickup days selected in the setup dialog under Settings > Integrations > Shipping.
Returns: Clearer highlighting of the selected line when putting items back in stock
In returns/refunds, the hover effect could hide the green highlight of the selected line, especially on touch screens. The highlight is now clear, so there is no doubt about which line is being put back in stock.
Labels: Label Designer only offers fields that can be printed
Label Designer offered some fields, such as Roles on login labels, that were always printed as "--". These fields have now been removed from the list, so you no longer find out only when printing. Existing templates that already use one of these fields must be updated manually.
Bug fixes and other corrections
Picking and packing
Pack: "Multi Quantity" works again when scanning
Since release 3.35.2, "Multi Quantity" was switched off when a product was scanned, so the packer had to scan the product once per unit. The setting now stays on, and several units can again be packed with a single scan.
Pack: No repeated error message when packing without a shipping label
When the packer had chosen to continue without a shipping label, the error "No label exists" was shown on every single scan. The error is no longer shown once that choice has been made.
Pack: Scanning the pickup label works with location-controlled pickup
With location-controlled pickup, scanning the pickup label was rejected with "Wrong Label". The label can now be scanned again, ensuring that the right label is on the parcel.
Pack: High-runner pack table no longer stalls after a split parcel
When the remainder of a split parcel was reset and released again, the pack table could not finish the order until a cleanup had run. The order can now be completed straight away.
Pack: Correct weight in the colli dimension dialog
The dialog suggested the weight of one unit per line without multiplying by the quantity, so colli were booked with too low a weight. The weight is now calculated correctly, reducing the risk of weight corrections from the carrier.
Pack: Parked orders are placed in the warehouse where packing takes place
An order that was parked during packing in a warehouse other than the shipping warehouse was parked in the shipping warehouse. It is now parked in the warehouse where the packing takes place.
Pick: Cycle count during picking in "Pick alone" works correctly
When a pick triggered a cycle count, the worker moved on to the next order before the count had been done. The count is now held correctly, can be resumed after a reload, and a count of zero also works when replenishment during pick is switched on.
Pick: The rest of a partly packed "send with" line is released correctly
The remaining quantity on a partly packed "send with" line was released with the full ordered quantity again, so more could be picked and shipped than was ordered. Now only what is missing is released.
Orders: New orders are released quickly even while many held orders are retried
When many orders on hold for missing stock were retried for release at once, new orders could wait for hours. New orders now also get a place in the automatic release, so the warehouse quickly gets pick orders.
Shipping and labels
Shipping: PostNord parcel shop booking no longer fails
Booking to a PostNord parcel shop could fail if PostNord's response was missing a customer service phone number. This is now handled, so the label is booked and the order can be shipped.
Warehouse move: Finish load unit with label for carriers using the PeakWMS shipping label
Finishing a warehouse move with "Finish & print label" failed when the shipping method used PeakWMS' own shipping label. It now works, so the warehouse move does not leave the warehouse without a label.
Order history: Failed label requests for multiple colli are logged
When fetching labels for multiple colli failed, for example during colli packing, B2B packing or pallet shipment, nothing was written to the order history. The failure is now logged, and the reason shows the correct names instead of placeholders.
Shipping: Unused labels from generic shipping setups are no longer left behind
When PeakWMS rejected the response from a generic shipping setup, the labels created were left active with the carrier, and every new attempt created more. This is now handled, so unused labels no longer pile up.
Delivery note: No extra blank page
A delivery note whose lines ended at the bottom of the page was printed with an extra blank page. The same applied to the End of Day list. Both are now printed without the blank page.
Shipping: Link to return product is cleared when a shipping product is deleted
When a shipping product is deleted, its link to the related return product is now also removed, so no invalid link is left behind.
Warehouse and production
Put-away: Correct location shown for fixed locations
When putting away to a product's fixed location, the flow could show the name and check digit of another location holding the same product. The location PeakWMS actually suggests is now shown, so the product ends up in the right place.
Replenishment: The "Start delivery" button has been removed where it did not work
In the replenishment flow, a "Start delivery" button could be shown that did nothing. The button has been removed, and products are still delivered through the flow as normal.
Production: Confirmation on the handheld no longer fails on label errors
If label printing failed, the user got an error even though production had been confirmed, and the label could not be printed again. The confirmation is now shown correctly, and the label can be printed again.
Returns
Returns: Replacement lines are no longer shown twice
Replacement lines created through Shopify's return flow were shown twice in the return worker, so a refund could be made on both. The lines are now shown only once.
Returns: Images can be opened in large format again
Images in returns/refunds could no longer be clicked to enlarge. This works again.
Purchasing
Purchasing: Purchase need calculation no longer stops after two minutes
Since release 3.42.0, the purchase need calculation could stop after two minutes without a result. The calculation now completes again.
Purchasing: Advanced search in purchase needs works with the packaging level vendor
The search button did not respond when the packaging level's vendor field was used in advanced search. The search now works.
Integrations
Shopify: Cancelled fulfillment no longer causes double picking
When a fulfillment was cancelled in Shopify, products that had already been delivered could be requested again and picked a second time. Now only what is actually still missing is requested.
Shopify: "Send with" lines get the correct Shopify location
Lines that an order adds to the order it is sent with had no Shopify location. They now keep the location, so the products are picked from the warehouse Shopify assigned.
Shopify: Location is saved on order lines when the integration has only one location
If the integration's only location was not the default warehouse, the location was not saved on the order lines, and the stock figure sent to Shopify was too high. This has been fixed, reducing the risk of overselling.
Shopify: The pick order follows when Shopify changes location
If Shopify moved an order to another location after release, picking still happened in the old warehouse. The pick order now follows, so for example click and collect orders end up in the right store.
Shopify POS: No false alarm on returns without a refund
Returns handled in PeakWMS without money back or as a gift card raised a false alarm about a missing store area. This no longer happens, and the products are not put back in stock twice.
Product import: Skipped products no longer stop the import
If a product was skipped through an integration script, the import could fail in Uniconta, Rackbeat, Business Central, HostedShop, WooCommerce, PrestaShop and Shopware, among others. The product is now skipped, and the import continues.
Integrations: Integration scripts are not stopped during brief busy periods
Integration scripts were stopped after 200 milliseconds, so a short delay on the server could reject an order, a product or a purchase order. Scripts now have more time, so receiving does not fail unnecessarily.
Integration API: The warehouse is kept when purchase orders are updated
Updating a purchase order through the integration API cleared the warehouse on the order. The warehouse is now kept, and the warehouse sent with the update is used.
HostedShop: The progress bar for product download shows the correct progress
The progress bar stayed at 100% even though products were still missing from the download. It now shows the actual progress.
Admin
Admin: Fixes to creating and editing in several dialogs
Five issues have been fixed: open store stocktaking orders can be edited again, a line on an inbound order cannot be set lower than what has been received, an invoice email is not saved if e-conomic rejects it, transport orders can be moved to or freed from a forklift, and pack tables can be created from the dialog.
Export: Column headers in background exports include the table name
In background exports, columns from related tables were missing the table name in the header. The headers are now the same as in a direct download.
Email templates: Formatting is kept when editing
Editing the text in an email template could change the layout to left-aligned. The formatting is now kept.
Var denne artikel nyttig?
Fantastisk!
Tak for din feedback
Beklager, at vi ikke var nyttige
Tak for din feedback
Feedback sendt
Vi sætter pris på din indsats og vil forsøge at rette artiklen