CreateFuelOrderSimple transition

Introduction:

The CreateFuelOrderSimple transition allows creating an Order (with less fields Uplift/Defuel) with a Fuel Ticket (Uplift, Defuel, Transfer, Purchase) at the same time. This transition screen is added within an Order workflow.

Transition properties:

Name	CreateFuelOrderSimple
Workflow type	Order
Linked to	SKU, Order
Purpose	Adding an Order (with simplified fields for Uplift/Defuel) with a fuel stock mutation (fuel ticket) at the same time.
Impacts	Order, Fuel Stock
Email out	NO
Product settings	NO
Configuration string	YES
Email message settings	NO
Report settings	NO

Transition screens:

Fuel mutation: Uplift / Defuel

Fuel mutation: Transfer

Fuel mutation: Purchase

Configuration string settings:

The following ‘Configuration string' settings can be set on the transition in the workflow.

Note: All settings must be separated by a semi-colon ';'.

Configuration string

Type

Default

Description

Example

ProductToAdd

String

BLANK

Indicates the fuel product (by Product Code) that should be added for the workflow. If blank or product chosen is a non fuel product, then the workflow will show an error to define the fuel product.

Ensure the product has a ‘Stock keeping unit’ and ‘Stock mutation type’ to be defined as a fuel product.

ProductToAdd=JET A1 UPLIFT

IncludeFuelTicket

Boolean

TRUE

Indicates if the fuel ticket details are available to enter when creating the Fuel Order (Uplift). If FALSE, then the fuel ticket is hidden.

IncludeFuelTicket=TRUE

ProductToAddStartTransition

String

BLANK

Indicates which initial workflow state the fuel product should be added in if there are more than one initial states.

This setting allows setting the product to it’s end state with fuel ticket fields becoming mandatory, if not set the product will add in a Not Started state.

The ‘Name’ of the Workflow start transition should be entered in the config with surrounding quotes.

If there are multiple initial transitions for the product:

No config added on the order workflow, THEN fuel product is added as NOT STARTED and fuel fields are NOT MANDATORY
Config ProductToAddStartTransition added stating which initial state on the order workflow, THEN fuel product added to workflow state defined and fuel fields are MANDATORY=dependent on the initial state
Config ProductToAddStartTransition added stating which initial state on the order workflow but is NO MATCH on product workflow THEN fuel product is added as NOT STARTED and fuel fields are NOT MANDATORY

if there is a single initial transitions for the product:

No config added onthe order workflow THEN the only initial workflow state for the product is chosen, and fuel fields are MANDATORY=dependent on the initial state
Config ProductToAddStartTransition added stating which initial state on the order workflow, THEN fuel product added to workflow state defined, and fuel fields are MANDATORY=dependent on the initial state
Config ProductToAddStartTransition added stating which initial state on the order workflow but is NO MATCH on product workflow THEN the only initial workflow state for the product is chosen, and fuel fields are MANDATORY=dependent on the initial state

ProductToAddStartTransition="Enter complete ticket"

How to use:

Ensure the ‘ProductToAdd’ configuration string is added to the order workflow with the correct fuel product.

Click Create Order or keyboard shortcut Alt+N
Choose the Fuel Order workflow and enter the required details (in red)
Optional (dependent on ProductToAddStartTransition configuration string) - Add the fuel ticket details
Click OK. Order and fuel ticket is now added

Related to

Search

Welcome to our Support Portal

Introduction:

Contents:

Transition properties:

Transition screens:

Configuration string settings:

How to use:

Comments