Workflow Types

This workflow is called when the Inspection Request workflow is call automatically where it issued a Inventory Status Change Request activity. When it is done this way the input context is InspectionTaskReleased. During this time this workflow can apply any desired activity the end-user has designed such as inventory status changes from Active to on Hold. It can also apply reason codes to this status change. The second time this workflow is called is from the Mobile Inspection Screen whenever the Pass or Fail buttons are clicked.

This example shows a deterministic workflow that first compares the order class of the inbound and if it is correct type, it then proceeds to check if this is the very first time the lot has been received. If these conditions are met then the CreateInspectionRequestActivity is called. Here this workflow does not consider the InputContext parameter but considers the order class. Manufacturing orders can be handle this way. With workflows there are infinite ways to develop them based upon one’s needs. The activities used in this workflow are:

• CreateInspectionRequestActivity
• FlowDecision
• GetOrdersActivity
• GetLotsActivity
• GetMaterialsActivity

This workflow is called by request in Blind receiving or blind receiving using barcodes. The objective of this workflow is to allow the user to automatically find a order and shipment to add this receiving task to. Also one can use this workflow to create a new order and shipment if it cannot find the appropriate order.

This Workflow is triggered whenever the license plate has moved. Therefore it can be used to find pick task associated to this license plate and attempt to system reallocate them to the new moved location drop. Or one could use this workflow to create accessorial charge tasks as a result of a move for say a special handling charge.

This Workflow is triggered whenever the order, shipment, or task status is changed. It is one of the most useful and important workflows in footprint . It can be used to addition tasks, accessorial charges, and so on during a close of a shipment or order. It can be also used to prevent a close of a shipment based on information or details that are missing, for instance a temperature reading on a License plate. It can be used to prevent or supplement moves of inventory or LPs as well. In fact in the Task change all number of combinations can be applied as most operations in footprint are task based. As one task is completed the workflow can be used to create new cascaded tasks. An example of this is as a putaway to a staging area is completed, a new chained putaway can be created and release to complete the move.

This workflow given an Input string considered to be a barcode scanned from source and the context which is the calling screen and area can be designed to break and parse the string into the output barcode properties. Essentially one is using string function to break it into material names, lot details, serial numbers or ant thing supported in the returning object

This workflow’s objective is to get a parsing definition given input such as the owner and project or account or even the scanned string itself. It is expected to return the definition which is defined under Settingsà ConfigurationsàBarcode Definitions.

This Workflow is at the heart of FootPrint that give flexiability to how and where a material is being allocated. Given the material, quantity and the package this workflow’s job is to return a list of responses of lots, and locations where the user should pick from. Anything is possible in this workflow when allocating. The workflow has an input of context to allow an ability to allocate differently under for instance outbound orders verse replenishment to forward pick faces. Easily the most complex of workflows

This workflow is triggered to perform a blind picking. Given a list of task and context, the goal of this work is to confirm the picking tasks that are grouped together basis on inputted requests properties. As an example consider we have a rack full of coats and scan the label and transfer to a shipping container. This workflow will find and complete the pick tasks for the order

When processing an outbound order and there is a need for the system to divide the materials and quantities into the best or least amount of boxes then this is your workflow. Given the materials and quantities then this workflow will return a list of boxes and types with the fill amount of each. FootPrint then creates the output shipment lines and shipping containers directed by this workflow in order to direct user to pick into specific shipping boxes.

This is a helper workflow to be used by the main cartonize workflow shown above. It is given raw data like sizes of boxes and materials and can be used to organize the logic and math use when calculating the fitting rules.

This workflow is used to execute a list of commands for an entity (Type/Id) and return a list of PostCommandActions

This workflow is used to return a list of commands for an entity (Type/Id)

This workflow is triggered whenever a license plate is requested but not found.

A very specific workflow, Loading Request returns a Boolean value based on licensePlateId and locationId, TRUE indicates it's a final Loading location and FALSE indicates it's a preLoading location.

This workflow is triggered whenever a Manufacturing Request needs to be created from Outbound Order.

This workflow is triggered whenever a message needs to be displayed on the mobile device based on a context

This Workflow will return Shipments for either all the Orders in a Master Order or for a single Order. The workflow is invoked by clicking “Consolidate Shipments” on the master order, or “Auto Assign Shipment” on the Shipment tab of an outbound sales order. From here the workflow can load data about the order and accounts and use this to create new shipments or use it to assign the order lines to an existing shipment.

This Workflow is used to assign shipments to order and/or adjust and create substitute order lines. This workflow in in conflict with Outbound Processing Strategy which does the same job. The invoking of the workflow is the difference. When set active this workflow will always run.

This Workflow returns optimized Outbound Package Quantities based on an input order. This workflow will run just prior to processing and cartoization of a outbound order. During the workflow one can alter the order line quantity and package types in the output variable. This could be used to read the material properties first for thing like ready to ship packages, or given each, convert this to case and so on

This workflow is trigger by end users in Footprint when processing outbound order. The use would choose the processing specifically. The intent of this workflow is to handle the processing of order line and possible creation of shipments. When this workflow it is possible to turn order line of kits into kit quantities as sub line. One can use this workflow to find substitute material and add them as order lines under the original parent. In another case this workflow can look at all the inventory and create shipment based on warehouse. There are many possibilities with this workflow

This Workflow will process the inventory records before the soft allocation check is done or the allocation engine tries to allocate inventory.

This Workflow will process a print request trigger from the Manifest and rate and ship screens. The input in a PrintRequest that contains a list of reports, labels, that Connectship, FootPrint, and other third party printing software FootPrint supports integration with. The workflow can be customized to remove items, automatic select items, set the printers, format, orientation, paper type and copies, based on data in the shipping container or manifest.

This workflow is triggered by the FootPrint Explorer API. It is exposed here to allow users of the API to design and create their own workflows and functions. These are they only public workflow that FootPrint exposes.

This workflow will process a receiving request.

This workflow is called by request of the end user by using the Recommend ([R]) button on the desktop or Mobile from the Putaway screens, or License Plate Move or Directed Move, and Inventory Move or Directed Move. When the button is clicked from the UI it will take the selected record’s values as the input context and data for the workflow. Then execute the workflow that has been designed. The workflow must assign a value to the OutputLocation the output of the workflow function. This Output is what is then displayed in the user interface in the Target Location field.

This workflow is called by request of the end user by using the Recommend ([R]) button on the desktop or Mobile from the Putaway screens, or License Plate Move or Directed Move, and Inventory Move or Directed Move. When the button is clicked from the UI it will take the selected record’s values as the input context and data for the workflow. Then execute the workflow that has been designed. The workflow must assign a value to the OutputLocation the output of the workflow function. This Output is what is then displayed in the user interface in the Target Location field.

This workflow is used to recommend an existing Lot/VendorLot or creation of a new one. It can be use to create lookupcode that match the input manufacturing date; or create Julian formatted lookup codes; or set the dates for a lot lookup code.

This workflow is used to recommend a receiving location

This workflow is called during a receiving by way a scale. Its intent is to create the receiving task based on the inputted request line. It is a way to inject actions during the process.

These workflows can be assigned to a scheduled event and thus are call on a routine time. They are useful in they can be designed to synchronize FootPrint data with third party system or can be used to clean up data within the system or trigger alerts based on how data is set.

This workflow determines if the measured weight of a shipping container is acceptable based on tolerances defined inside the workflow.

This workflow is triggered whenever a survey orchestration is required. Its goal is to get the correct survey (questionnaire) when operations on the mobile are performed. For example after a receiving a pallet the system will ask a series on question about the condition of the pallet.

This workflow is triggered whenever a wave is released. It allows user to perform operations like printing of packing slips and report on the release

This workflow is used to assign work tasks for a user.