User action capability is used to revise an Order. It is possible to configure Order Revision functionality via both UI and Postman.
Step 1: Check Billing Account Flow
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).
Variable `[[retailerId]]` must be filled with the identifier of the retailer for which the Billing Accountworkflow is being added.Variable `[[account.id]]` should be replaced with Account name.
Check if the setting`DEFAULT_TAX_TYPE` exists. If not you need to add it.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
Check if the setting`EXCHANGE_REASON` exists. If not you need to add it.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
Check if the setting`GST` exists. If not you need to add it.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:
Note
Context Id = Retailer Id By default GST (Goods and services tax) value is 0, but it can be changed to necessary GST, e.g., if GST is 10%, the value should be set as 0.1
Step 6. Product list
Check if the setting`fc.mystique.search.product.list` exists. If not you need to add it.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 settingMystique Search Product List Setting JSONParameters from which displayed columns can be configured in `fc.mystique.search.product.list`setting:
imageURL
Product name
Product item reference
Attributes
Catalogue
Price
Note: In case `fc.mystique.search.product.list`setting doesn’t exist ‘Add Item’ dialogue will contain only a list of product items and their pictures (default configuration).'Add Item' dialogue default configuration
Step 7. Product Query
Check if the setting`fc.mystique.search.product.query` exists. If not you need to add it.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:
A base entity for Add item dialog query is VariantProduct. It has references with the following list of entities:
StandardProduct
ProductCatalogue
Category
Price
TaxType
Attribute
Database schema snippetVariantProduct.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`setting doesn’t exist ‘Add Item’ dialogue will contain data according to the default configuration.VariantProduct.graphql file containing a query which returns max amount of VariantProduct attributes.
Pre-requisites
You can just use this guide on any account. The provided Postman collection below is pre-configured to be used on a pre-provisioned training sandbox account so it is best is you can:
Use your "Using Fluent" training account OR a training sandbox that has been setup with the Jetpack/Launchpad
Import the following Postman collection to your Using Fluent training space in Postman:
Order Revision configuration steps:Use Postman collection to do the following:
Authenticate using POST request Fluent Auth - Retailer FC_FASHION.
Get Setting using GET request Get the Retailer settings.
Get workflow by Retailer Id and Workflow Name using GET request of the same name.
Create settings (if necessary) using POST requests:
Create `DEFAULT_TAX_TYPE` setting
Create `EXCHANGE_REASON` setting
Create `GST` setting
Create `fc.mystique.search.product.list` setting
Post a basic Billing Accountworkflow (if necessary) using POST request of the same name.
Same product Ref in multiple order lines
The Order Revision is only suitable for orders with order lines with unique product References. A new custom rule will be required if the same product Reference appears in multiple lines within the order.