FieldStack Mobile Version 11.5

Modified on Mon, 18 Nov at 3:23 PM

IMPROVEMENTS


SEND MODE

Open Send Reasons Function like Create Transfer

In locations without bins, Open Purchase Order Reasons (like Missing/Found inventory) now function like Send: Create Transfer and will stack items in a carded fashion.



AUTOSELECT QTY WHEN TAPPED


Many areas of the application have been updated to autoselect the quantity when that field is tapped into for edits. This includes:


  • Receive
  • Send: Create Transfer & Open Reasons
  • Pick by Zone, PO, and Clustered
  • Item Lookup
  • Put Away


PICK WITHIN STORES

Ladder/Lift items no longer filtered.

In locations without bin locations, Ladder/Lift items were previously pre-filtered. To see the totals and start, Pick All would need to be tapped. Although the message disappeared in an earlier version, Pick All still needed to be tapped. This behavior has been updated. Pick All will be assumed; the pick total will show as soon as the user begins the Pick.


ITEM LOOKUP CHANGES

  • Item list page now named Item Lookup – Search Results
  • Item Cards have been reduced in scale to display more items.
  • Pagination in footer has been altered.



BUG FIXES

Pick Mode – On the summary screen, destination store would not always show when using Pick by PO. This has been fixed.

Receive: Stage All – Item list caching - In a store, using Stage All could sometimes show items that were previously received, each with a quantity of zero. The function was calling cached information. Stage All will no longer show items already received on a previous order.

UPC entry – Adding a UPC that was already in use on an item did not warn the user or block them from adding that duplicate UPC. This had no affect on the item itself but the user interface has been updated.

UPC Primary – When setting a UPC as primary, the selected primary UPC would not show on the item list detail screen after the change had been saved. This did not affect the UPC list or the UPC that was set to primary but was a data refresh issue. This has been resolved.

User Tokens - At times, if two users accessed the same item within the same span of a few seconds, even from differing stores, the cached information could collide and assign the user’s action to the wrong store. This has been fixed.

 



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article