Unplanned Functions

Description

Processes performed on Ad-hoc-basis, as opposed to Planned Functions.

Examples of unplanned operations

It could be items gets damaged and the inventory needs to be adjusted.

How unplanned functions operate

Unplanned functions always use a Header
Optionally follwed by one or more Steps

The logic is to ask for one of more information in the header and use that to generate the steps.

Standard Unplanned functions

Attach Image
Add Count Line
Adjust Quantity
Bulk Move
Item Cross Reference
Item Dimensions
Post Shipment
Substitute Items
Tote Shipping
Unplanned Count
Unplanned Move

Key points

Often used for custom functions. See How-to: Create custom Unplanned function in Main Menu
A Header is always used
Based on the header input, steps can be used to collect additonal information (optional)
Can be combined with the result from Lookup Functions to create a powerful customized function. See Page Navigation

Mobile document flow

User fills in Header and Accepts (or Scans)
Backend responds with Steps to collect (if any)
Document Type GetRegistrationConfiguration
User posts the registration (header and steps)
Document Type PostAdhocRegistration

Empty header

Three steps was returned after header was been filled in and accepted

A success message is shown

Document Types

GetRegistrationConfiguration

This request is sent to back-end when header values are accepted.

The backend must return an XML that contains the additional steps to collect before the registration can be posted.

XML Example: Request

<request name="GetRegistrationConfiguration" created="2021-08-06T11:21:30+02:00" xmlns="http://schemas.microsoft.com/Dynamics/Mobile/2007/04/Documents/Request">
  <requestData name="GetRegistrationConfiguration">
    <Location>WHITE</Location>
    <Item>1000</Item>
    <RegistrationType>UnplannedCount</RegistrationType>
  </requestData>
</request>

XML Example: Response

<registrationCollectorConfiguration xmlns="http://schemas.taskletfactory.com/MDMF/Platform/Controls/RegistrationCollectorConfiguration.xsd">
    <steps>
        <add id="1"
             header="Enter LOT number"
             helpLabel=""
             inputType="Text"
             label="LOT No."
             length="20"
             name="LotNumber"/>
        <add id="2"
             header="Enter exp. date"
             helpLabel=""
             inputType="Date"
             label="Exp. date"
             name="ExpirationDate"
             minDate="2009-01-01"
             maxDate="2012-12-31"/>
        <add id="3"
             header="Enter quantity"
             helpLabel=""
             label ="Quantity"
             inputType="Integer"
             minValue="0"
             maxValue="150"
             name="QUantity" />
        <add id="4"
             header="Select Location"
             helpLabel=""
             label ="Location"
             inputType="List"
             listValues="Warehouse 1@Warehouse 2@Warehouse 3"
             listSeparator="@"
             name="Location" />
    </steps>
</registrationCollectorConfiguration>

PostAdhocRegistration

This request is sent to back-end when header is accepter or, if used, steps are completed.