Implement Fluent OMS

Some how to guides for implementing Fluent OMS

Configure Retailer Switching and Default Retailer in Fluent OMS

Retailer switching requires both manifest configuration and retailer context assignment to the user.
The switcher is visible only to users with multiple assigned retailer contexts.
Devices can automatically open Fluent OMS in a predefined retailer using a URL parameter.
URL-based configuration does not override role-based access permissions.

The `tag1`, `tag2`, and `tag3` filters allow users to filter orders based on an exact match of the entered value.
These filters can be configured to use predefined values instead of a text input field that is available out of the box, enhancing usability and consistency.

This use case is for users who want to look up orders using the order ID.
Typically, the graphQL query orderById is used to look up an order by ID. However, it can only look up one order at a time without a wildcard search.
This article provides an alternative approach that allows users to search for orders by ID or even with a wildcard.
This approach utilises the new UI component fc.filterPanel, which does not require custom rules.
An alternative way to achieve the outcome is to use `order.ref2`. Click here for the how-to guide.

This document describes how to enable the Chinese language in Fluent OMS webapps.
There are 2 Chinese Languages in writing: Traditional and Simplified. The Simplified Chinese are mainly used in Mainland China and Traditional Chinese are typically used in Taiwan, Hong Kong and Macau.

In the default reference mystique manifest, a store user can log in to OMS web apps, and sometimes, the user can see other location data within the OMS web apps.
One way to solve this issue is to introduce the “`role`” in the `fc.mystique.manifest.oms` context.