Fluent Commerce Docs

The best practice for controlling the visibility of the user action button should be driven by the entity status within the ruleset.
However, if the customer does not want to enhance the list of statuses, this trick can be used to control the User Action button visibility by using the entity's attribute value.
This article will demonstrate the following in an Order entity:
- Display a user action button: once clicked, it will add an attribute (SENT_TO_WMS) to the order entity
- Update the manifest to check the attribute (SENT_TO_WMS), if the value is not "True", then display the button.
the sample source code will be provided in this article.

Prerequisites

UX Framework - Configuration Guide

Adding a Ruleset to your Workflow

Steps

Ensure your account has a rule that will add an attribute into the entity

The RULE SDK package contains a rule: `DemoAddAttributeToOrder`Alternatively, feel free to create your own rule to fir your purpose.

Create a new Ruleset in the workflow

In this example, a CC Order workflow will be used:

Update order management mystique manifest to control the button visibility

Result

The User action button will be displayed if the order attribute's SENT_TO_WMS value is not True: No alt provided

Otherwise, the button will not be displayed: No alt provided

Fluent Commerce

Knowledge Tracks Related To This Topic

Getting Started Configuring Fluent OMS Web Apps

Fluent OMS Overview

Getting Started Configuring Fluent OMS (webapps)

Overriding the default manifest

Settings Creation and Editing Mutations

Setting Editing Mutation

Create a Simple List Page in OMS Webapp

Enable bulk order Cancel in the UI by using the action property in the LIST component

Webapp User Action visibility by using entity's attribute value

Hide UserAction button via OMS Manifest

Configure a drawer via manifest

Using the Setting Form Component

Adding Header Components to an OMX Web App (Store, OMS, Inventory etc)

Configure UI for Mixed Baskets

Building Better Filters: From Reusable Components to Customer Search

Copyright © 2024-2026 Fluent Retail Pty Ltd (trading as Fluent Commerce). Unless otherwise expressly stated in a current written agreement with Fluent Commerce or any of its affiliates or on any single page of the docs.fluentcommerce.com site, use of the materials on this site is strictly limited to viewing by individuals over 18 years old for legitimate commercially appropriate reasons; and any downloading, copying or other actions or uses of any kind or by any means of the materials on this site, including by artificial intelligence tools, is strictly prohibited. All other rights reserved.

Key Points

The best practice for controlling the visibility of the user action button should be driven by the entity status within the ruleset.
However, if the customer does not want to enhance the list of statuses, this trick can be used to control the User Action button visibility by using the entity's attribute value.
This article will demonstrate the following in an Order entity:
- Display a user action button: once clicked, it will add an attribute (SENT_TO_WMS) to the order entity
- Update the manifest to check the attribute (SENT_TO_WMS), if the value is not "True", then display the button.
the sample source code will be provided in this article.

Prerequisites

UX Framework - Configuration Guide

Adding a Ruleset to your Workflow

Steps

Ensure your account has a rule that will add an attribute into the entity

The RULE SDK package contains a rule: `DemoAddAttributeToOrder`Alternatively, feel free to create your own rule to fir your purpose.

Create a new Ruleset in the workflow

In this example, a CC Order workflow will be used:

Update order management mystique manifest to control the button visibility

Result

The User action button will be displayed if the order attribute's SENT_TO_WMS value is not True: No alt provided

Otherwise, the button will not be displayed: No alt provided

1    {
2      "name": "SendCanceltoWMS",
3      "type": "ORDER",
4      "subtype": "CC",
5      "eventType": "NORMAL",
6      "rules": [
7        {
8          "name": "<AccountId>.<PackageName>.DemoAddAttributeToOrder",
9          "props": {
10            "name": "SENT_TO_WMS",
11            "type": "String",
12            "value": "true"
13          }
14        }
15      ],
16      "triggers": [
17        {
18          "status": "BOOKED"
19        }
20      ],
21      "userActions": [
22        {
23          "context": [
24            {
25              "label": "SendCanceltoWMS",
26              "type": "PRIMARY",
27              "modules": ["adminconsole"],
28              "confirm": false
29            }
30          ],
31          "attributes": []
32        }
33      ]
34    },

1  "actions": {
2    "primary": [
3
4        {
5            "type": "userAction",
6            "label": "SEND CANCEL TO WMS",
7            "name": "SendCanceltoWMS",
8            "condition": "{{ne orderById.attributes.byName.SENT_TO_WMS 'true'}}"
9        },
10

Content in this track:

Fluent OMS Overview

Getting Started Configuring Fluent OMS (webapps)

Overriding the default manifest

Settings Creation and Editing Mutations

Setting Editing Mutation

Create a Simple List Page in OMS Webapp

Enable bulk order Cancel in the UI by using the action property in the LIST component

Webapp User Action visibility by using entity's attribute value

Hide UserAction button via OMS Manifest

Configure a drawer via manifest

Using the Setting Form Component

Adding Header Components to an OMX Web App (Store, OMS, Inventory etc)

Configure UI for Mixed Baskets

Building Better Filters: From Reusable Components to Customer Search

End Of Track

Webapp User Action visibility by using entity's attribute value

Webapp User Action visibility by using entity's attribute value

Key Points

Prerequisites

UX Framework - Configuration Guide

Adding a Ruleset to your Workflow

Steps

Ensure your account has a rule that will add an attribute into the entity

Create a new Ruleset in the workflow

Update order management mystique manifest to control the button visibility

Result

Fluent Commerce

Knowledge Tracks Related To This Topic

Building Blocks

By Type

Helpful Resources

Quick Links

Key Points

Prerequisites

UX Framework - Configuration Guide

Adding a Ruleset to your Workflow

Steps

Ensure your account has a rule that will add an attribute into the entity

Create a new Ruleset in the workflow

Update order management mystique manifest to control the button visibility

Result