Multi-Parcel Component

Use Cases

The Multi-Parcel field component provides the following features that enable users to submit additional and resourceful data during the packing operation:

• Create and submit more than one parcel per order fulfillment
• Define common parcel types, enabling you to do the following:
  • Define a preselected default parcel type value. This allows in-store associates to skip having to select a parcel type for each fulfilment, particularly useful if the Operation only has one primary parcel type
  • Optionally disable preselected parcel types on the ‘select parcel type’ dropdown. This ensures that in-store associates select a parcel type each time
  • Specify dimensional data for each parcel type
  • Option to specify minimum and maximum weights for each parcel type, to ensure users enter reasonable values to avoid under/overstating cost implications with Carriers
  • Option to define a default weight for each parcel type so that users don’t always need to manually capture the weight of each parcel resulting in a more efficient packing time per order
  • Capture custom parcel dimensions to cater for situations where none of the usual parcels are suitable for the fulfilment
  • Set different parcel types at different contexts or locations so that individual stores can have their own unique preset packaging options
  • Supports mobile views

Field behaviour

Adding and Removing parcels

• In-Store Associates are able to add another parcel to the top of the table via the ADD PARCEL button
• When there is more than one parcel, a REMOVE button appears on each row, allowing the users to remove that row.

`allowMultipleParcelsPerItem`

Choosing a Parcel type

• The parcel type can be chosen from a dropdown and should reflect the physical container the Packer has chosen to put the items into. These are sourced from either the 

  `fc.mystique.fields.basicpack`

   setting or the legacy attributes solution. See configuration behaviour for more details.
• If no parcel types are configured, then the only available option will be 

  `custom`

   and preselected for the user.

Parcel Dimensions and Weights

• After selecting a parcel type, the user must specify a weight. If the parcel type has a default weight, this field will be preselected with that value, allowing the user to accept a default if it is suitable for their operation.
• The "weight" field will accept positive values in kilograms (kg) to two decimal places between 

  `"minWeight"`

   and 

  `"maxWeight"`

   (if defined, see configuration).
• When a 

  `custom`

   parcel type is chosen the Packer will be prompted to enter the dimensions for the parcel, these must be positive values to a maximum of one decimal place.
• Otherwise, if a preconfigured parcel type has been chosen, these dimensions will be used downstream.

Submission

• Upon 

  `CONFIRM PACK`

   the end-user will be met with an error message if they have attempted to submit with any values blank. Otherwise, the user will then progress onto step 3 of the Wave Wizard - Dispatch.

Field Logic

• The Multi-Parcel field refreshes the Wave data until it is deemed ready for parcel creation. Specifically, until each of the items is

  `filled + rejected quantities = requested quantity`

  . If this statement does not return true then the field component will not load.

Configuration Options

The Multi-Parcel field is configurable via the 

`fc.mystique.fields.basicpack`

Header Properties

`true`

`false`

`quantity`

`items`

Query Property

The following is the default query that is used to populate them basicpack component. If the 

`query`

1query ($waveId: ID!) {
2  waveById(id: $waveId) {
3    id
4    ref
5    status
6    location {
7      id
8      ref
9      attributes {
10        name
11        type
12        value
13      }
14    }
15    fulfilments(first: 100) {
16      edges {
17        node {
18          id
19          ref
20          status
21          toAddress {
22            id
23            ref
24          }
25          items(first: 100) {
26            edges {
27              node {
28                ref
29                filledQuantity
30                rejectedQuantity
31                requestedQuantity
32              }
33            }
34          }
35          order {
36            id
37            ref
38            type
39            status
40            fulfilmentChoice {
41              deliveryType
42            }
43            customer {
44              firstName
45              lastName
46              primaryEmail
47              primaryPhone
48            }
49          }
50        }
51      }
52    }
53  }
54}

Attribute Property

When not explicitly specified, the following configuration is displayed by default:

`{{data.order.ref}}`

`["fc.sf.ui.wave.pickAndPack.list.pack.multiparcel.column.order.ref.heading", "Order reference"]`

`'xs'`

`'sm'`

`'md'`

`'lg'`

`'xl'`

1    {
2  "attributes": [
3    {
4      "value": "{{data.order.ref}}",
5      "label": ["fc.sf.ui.wave.pickAndPack.list.pack.multiparcel.column.order.ref.heading", "Order reference"],
6      "hideBelow": "sm"
7    },
8    {
9      "value": "{{data.order.customer.firstName}} {{data.order.customer.lastName}}",
10      "label": ["fc.sf.ui.wave.pickAndPack.list.pack.multiparcel.column.customer.name.heading", "Customer name"]
11    },
12    {
13      "value": "{{orderType}}",
14      "label": ["fc.sf.ui.wave.pickAndPack.list.pack.multiparcel.column.order.type.heading", "Order type"]
15    },
16    {
17      "value": "{{data.status}}",
18      "label": ["fc.sf.ui.wave.pickAndPack.list.pack.multiparcel.column.fulfilment.status.heading", "Fulfilment status"]
19    }
20  ]

Parcels Properties

Add the details about each individual parcel in the parcels object below

N/A