Author:
Fluent Commerce
Changed on:
8 July 2024
User action capability is used to revise an Order. It is possible to configure Order Revision functionality via both UI and Postman.
In case there is no Billing Account Flow in the Orchestration, it is necessary to add the workflow via PUT request using Postman.
PUT request:
`https://<ACCOUNT_ID>.<environment>.api.fluentretail.com/api/v4.1/workflow`
Variable | Description |
ACCOUNT_ID | The name of the Fluent account |
environment | The Fluent deployment Environment type for the particular Fluent Account (SANDBOX, PRODUCTION, TEST, STAGING). |
Body
Add the following JSON fragments to the ruleset.
Create Ruleset
EvaluateRevisedOrder Ruleset
OrderRevision Ruleset
Order Revision Ruleset HD JSON
NewBillingAccount
ProcessBillingAccount
Process Billing Account HD JSON
OrderCancel
Add the following JSON fragment to the statuses:
1"statuses": [
2 {
3 "name": "",
4 "entityType": "ORDER",
5 "category": "DONE"
6 },
7 {
8 "name": "CREATED",
9 "entityType": "BILLING_ACCOUNT",
10 "category": "BOOKING"
11 },
12 {
13 "name": "",
14 "entityType": "BILLING_ACCOUNT",
15 "category": "DONE"
16 },
17 {
18 "name": "",
19 "entityType": "RETURN_ORDER",
20 "category": "DONE"
21 }
22]
Language: json
Name: Example
Description:
[Warning: empty required content area]Add the following JSON fragments to the ruleset:
Create Ruleset
EvaluateRevisedOrder Ruleset
OrderRevision Ruleset
NewBillingAccount
ProcessBillingAccount
Process Billing Account CC JSON
OrderCancel
Note:
`<ACCOUNT_ID>`
Add the following JSON fragment to the statuses:
1"statuses": [
2 {
3 "name": "",
4 "entityType": "ORDER",
5 "category": "DONE"
6 },
7 {
8 "name": "CREATED",
9 "entityType": "BILLING_ACCOUNT",
10 "category": "BOOKING"
11 },
12 {
13 "name": "",
14 "entityType": "BILLING_ACCOUNT",
15 "category": "DONE"
16 },
17 {
18 "name": "",
19 "entityType": "RETURN_ORDER",
20 "category": "DONE"
21 }
22]
Language: json
Name: Example
Description:
[Warning: empty required content area]Check if the setting
`DEFAULT_TAX_TYPE`
Go to Admin > Settings and filter the list of settings by name.
To add a new setting click on Create Setting button and fill the following:
DEFAULT_TAX_TYPE setting
1{
2 "country": "AUS",
3 "group": "STANDARD",
4 "tariff": "GST"
5}
Language: json
Name: DEFAULT_TAX_TYPE setting
Description:
[Warning: empty required content area]Check if the setting
`EXCHANGE_REASON`
Go to Admin > Settings and filter the list of settings by name. To add a new setting click on Create Setting button and fill the following:
EXCHANGE_REASON setting
1[
2 {
3 "label": "fc.order.orderRevision.wrong.size",
4 "value": "wrong-size"
5 },
6 {
7 "label": "fc.order.orderRevision.change.mind",
8 "value": "change-mind"
9 },
10 {
11 "label": "fc.order.orderRevision.change.variant",
12 "value": "change-variant"
13 }
14]
Language: json
Name: EXCHANGE_REASON setting
Description:
[Warning: empty required content area]Note: Context Id = Retailer Id
Check if the setting
`GST`
Go to Admin > Settings and filter the list of settings by name. To add a new setting click on Create Setting button and fill the following:
Check if the setting
`fc.mystique.search.product.list`
Go to Admin > Settings and filter the list of settings by name. To add a new setting click on Create Setting button and fill the following:
fc.mystique.search.product.list setting
Mystique Search Product List Setting JSON
Parameters from which displayed columns can be configured in
`fc.mystique.search.product.list`
Note: In case
`fc.mystique.search.product.list`
'Add Item' dialogue default configuration
Check if the setting
`fc.mystique.search.product.query`
Go to Admin > Settings and filter the list of settings by name. To add a new setting click on Create Setting button and fill the following:
1{
2 "query": "query products {variantProducts (first: 5, status: \"ACTIVE\") {edges {node {id catalogue {ref} ref name gtin summary tax {country group tariff} attributes {name value} categories {edges {node {name}}} prices {type currency value}}}}}"
3}
Language: json
Name: fc.mystique.search.product.query setting (example)
Description:
[Warning: empty required content area]A base entity for Add item dialog query is VariantProduct. It has references with the following list of entities:
Database schema snippet
VariantProduct.graphql file contains max amount of VariantProduct attributes. It is possible to make custom configuration excluding unnecessary attributes.
Note: In case
`fc.mystique.search.product.query`
VariantProduct.graphql file containing a query which returns max amount of VariantProduct attributes.
Order Revision configuration steps:
Use Postman collection to do the following:
`DEFAULT_TAX_TYPE`
`EXCHANGE_REASON`
`GST`
`fc.mystique.search.product.list`
Post a basic Billing Account workflow (if necessary) using POST request of the same name.
Copyright © 2024 Fluent Retail Pty Ltd (trading as Fluent Commerce). All rights reserved. No materials on this docs.fluentcommerce.com site may be used in any way and/or for any purpose without prior written authorisation from Fluent Commerce. Current customers and partners shall use these materials strictly in accordance with the terms and conditions of their written agreements with Fluent Commerce or its affiliates.