Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Description
Steps are used to collect additional information in Unplanned Functions or on Order/Lines.
ContentsOverview
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Where are steps defined
- Planned Functions (Header/Line steps)
- Standard workflow steps:
- Statically defined Line Steps in Mobile Configuration Files as part of a Workflow
- Statically defined Line Steps in Mobile Configuration Files as part of a Workflow
- Customized steps:
- Dynamically defined Header/Line steps. See How-to: Add Line Step
- Standard workflow steps:
- Unplanned Functions
- Always dynamically sent on-the-fly from Backend
Steps in Planned functions
Step on posting (header step)
Additional information that is collected when Posting registrations.
This happens only once.
Orders | Step on a Receipt Order |
Ordering
Custom steps and existing standard steps are both ordered by "id".
We use "Receive" in this example due to it being the only planned function to feature a Header Step as standard.
Example
A standard step "Delivery Note" may exist at warehouse receipts and purchase orders (Controlled by Mobile WMS Setup, field: "Skip collection of delivery note on receive" ).
- Standard Step "DeliveryNote" is id=10
- Adding new steps with id less than 10 will display before DeliveryNote
- Adding new steps with id greater than 10 will display after DeliveryNote
The standard step for entering "Delivery Note" when posting a Receipt
See also: Whitepaper Understanding Steps
Step per line (line step)
Additional information that is collected during a line registration
This happens for each and every order line.
Order Lines | Step on a Receipt 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
See more Unplanned Functions.