Content Comparison

Description

Planned functions

• Receive

• Put-away

• Pick

• Ship

• Move

• Count

• Assembly

• Production

Key points

• Displays data is in two levels. Header and Lines
  Uses a Header defined in Reference Data with search filters

• Can

  have Unplanned Functions as actions

  Action Menus on both Orders and Order Lines

• Standard Steps are

  definned

  defined by Workflows in Mobile Configuration Files but can be changed using Customization

Hierarchy

Each order can have multiple Order LinesImage Removed

Image Added

Steps

Workflows defines the Steps.

Workflows are stored directly in the Mobile Configuration Files, but somewhat configurable from the backend using Order Lines GetOrderLines Response

• ValidateToBin

• ValidateFromBin

• RegisterLotNumber

• RegisterSerialNumber

• and many more..

Customization

You can customize the existing functionality or create your own Planned function.

Document Flow

The document type name is shown in (paranthesesparentheses)

1. Orders are displayed

1. (GetOrders)

   1. User selects an order

1. 1. 
      or

   2. User edits Header fields to search for a desired Order

1. 1. 
      

2. Lock the

1. order (LockOrder)
   

1. Order Lines

1. are displayed.(GetOrderLines)

   1. User selects a line

1. Line collector steps are displayed

1. Device can go Offline now

1. 1. User completes the steps
      

1. User is returned to the Order Lines

1. Still offline

1. 1. Repeat Step 3
      or

   2. Go Step 6
      

2. User

1. Posts

1. (PostOrder)

1. The order is released (UnLockOrder)

Image Removed

Image Added

Mobile Configuration

Page types

Planned functions always uses two pages, called "OrderList" and "OrderLines".