Description

Steps are used to collect additional information in Unplanned Functions or on Order/Lines.

Contents

Where are steps defined

• Planned Functions (Header/Line steps)
  
  
  • Standard workflow steps:
    • Statically defined Line Steps in Mobile Configuration File as part of a Workflow
      
      
  • Customized steps:
    • Dynamically defined Header/Line steps.  See How-to: Add Line Step

• Unplanned Functions
  • Always dynamically sent on-the-fly from Backend
    • See OnGetRegistrationConfiguration_OnAddSteps

Steps in Planned functions 

Step on posting (header step)

Additional information that is collected when Posting registrations.

This happens only once.

Header Step Ordering

Step per line (line step)

Additional information that is collected during a line registration

This happens for each and every order line.

Ordering

Custom steps and existing standard steps are both ordered by "id".

Example

Standard steps are defined by the workflow named "standard".

Standard steps are numbered with ID's 10, 20, 31 etc.

So, adding new steps with ID 25 will be displayed between "To/From Bin" and "Expiration Date" 

Note: Order Lines must be configured with stepSorting=byId

Steps in Unplanned functions

Steps are used to collect information after a Header has been accepted

1. The user "accepts" the Header
   
   
2. Backend responds with a set of Steps to Collect 

See more Unplanned Functions.

Using steps in code