Fluent Commerce Docs

This page will guide you through placing the Setting Form Component on a page and customizing it for use by a business user. Key topics covered include:
- Adding the component to a page
- Using the component within an Accordion component
- Generating a schema for a setting
- Adding titles to individual fields
- Using the component with custom fields

Steps

You will need:

A setting of any type (Other than LOB)
A web app page where you want to add the setting

Step 1 - Generating a schema for the setting

To generate a schema for your setting, we recommend using an online tool that converts JSON into a JSON schema. You can retrieve an example here.Here’s how to use it:

Copy and paste an example setting into the tool.
The tool will generate the schema for the setting.

Once you have the schema, store it as its own setting. The setting type should be JSON, and we recommend storing it at the account level to ensure global accessibility.Example:Let’s use the RETURN_REASON setting as an example. This setting is made up of label-value pairs, represented in schema terms as an array of objects. Each object contains two strings: one for the label and one for the value. Using a JSON schema converter, you should expect a schema that looks something like this:As explained above, you can now take the generated schema and create a new setting with the following details:

Name	RETURN_REASON_SCHEMA
Context	ACCOUNT
Context ID	0
Type	JSON
Value	{{schema from above}}

Step 2 - Adding titles to each field

In the schema, you can assign titles to each field using the `title` property. The value in the `title` property is passed to the field's `label` property, which controls how the title is displayed.Depending on the JSON schema generator you used, titles may already be present in your schema. In this example, only the top-level title was added initially, but we also need titles for the `label` and `value` fields. Titles for `object` types can be skipped, as they do not require labels. Here's an example:(Note: i18n strings are currently not supported)For schemas that already include titles, you can use this step to update them with more appropriate labels. Ensure that each field has a clear and descriptive title.We will later demonstrate how these titles are reflected in the settings component when we review how it is laid out on a page.

Step 3 - Adding the Settings Component onto a Page

To add the settings component to a page, you need to open the manifest fragment for that page. In this example, we will incorporate the return reason setting into a new tab called Settings under the Retailer detail page in OMS.The retailer page is located in the `fc.mystique.manifest.oms.fragment.admin` setting. Since this doesn't exist by default, first retrieve the default manifest by referring to this guide. Once you’ve created the setting, the next step is to edit the Retailer details page to split it into two tabs. The first tab will be named Details and will retain the existing layout currently defined in the manifest. The second tab, called Settings, will host the new component for editing the return reasons. No alt provided

Step 4 - Styling the Page

Now that you have added the settings component to the page, it doesn't look very appealing on its own, as it currently occupies the entire screen while the form only takes up about half of that space. To enhance the appearance, you can place the settings component within an Accordion Component, adjust its width, and use empty components to center the Accordion.In the snippet above, we've enclosed the settings component in an Accordion with a width set to 8. Additionally, we've added empty column components on either side of the Accordion. This arrangement allows us to center the Accordion, resulting in a more aesthetically pleasing layout. No alt provided

Now it looks much better.

Default Setting Override

If a setting is available at a higher context level compared to the configured context of the component, the component will automatically highlight that a default setting is being edited. Overriding this default setting creates a new setting at the configured context level. No alt provided

Advanced

Advanced - Using a Custom Component

At this point, the page is functional for business users to edit return reasons.However, there's some room for improvement here. For example, there's the fact that return reasons consist of a label and a value. The setting structure was designed this way so that the dropdown label could be changed without changing the value sent to the backend. Since our audience are business users, they are primarily concerned with editing the label, which affects what is displayed in the dropdown menu. This raises the question: can we configure the form so that users only need to input the label, and the value auto-populates? The answer is yes, and we can achieve this by using a custom field.

Setting Up the Custom Field:

1. Components SDK
First, ensure you have access to the Components SDK. If you don't already have it, you can download it from the Components SDK page.2. Create the Custom Field
We will design a field that outputs a JSON object similar to the following:You can use the following boilerplate code to get started on creating the new custom field:3. Register the Custom Field
To register this field in the field registry, add the following line to your `index.tsx`:4. Use the Custom Field in the Schema
Now you can utilize this custom field in your schema. To do this, add the `fcField` keyword to your items, which allows you to specify the field by its name in the `name` property. The updated schema will look like this:5. Add UI to Your Field
Let's add some UI to the field. You can use the label prop, which gets passed the value of the item's `title` from the schema. Then you can add a simple text field next to the label to capture the user's input to change or add a return reason.6. Handle Value and Label Logic
Next, you need to pass both the label and value back to the form via the `onChange` method. The label will come from the text field, and you will also initialize the text field with the existing label value if it exists.7. Managing Value State
For the value, we want it to equal the label when creating a new entry, but it shouldn't change if we're editing an existing return reason. To achieve this, we'll use state to track whether the value should be the label or the previous value.Conclusion
By following these steps, you have created a custom field that simplifies the editing process for return reasons, allowing users to focus on changing the label while automatically managing the value. This approach enhances the usability of your form for business users, aligning the technical functionality with user-friendly design.Feel free to expand or adjust this implementation based on user feedback or additional requirements! No alt provided

Advanced - Enhancing the Field with Custom Properties

We now have a custom field for return reasons that can be utilized wherever a label-value pair is needed, with the user only able to modify the label.However, what if we want the value field's functionality to change dynamically based on the label? In some instances, we may want the value to automatically update whenever the label is changed.To accommodate this, we can introduce an extension to the field that allows toggling this behavior on and off. Here’s how we can implement this.Extensions can be added through the `fcField`'s `extension` keyword. The extension is a dictionary of key-value pairs, allowing you to specify any keys and values you desire. Everything defined in the `extension` keyword will be passed to the field via its `extension` prop.Let's modify our field to include an `alwaysChangeValue` property:And here’s how the schema would look:Now we have a field that can adapt its behavior based on the `alwaysChangeValue` property in the schema.

Christopher Tse

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

This page will guide you through placing the Setting Form Component on a page and customizing it for use by a business user. Key topics covered include:
- Adding the component to a page
- Using the component within an Accordion component
- Generating a schema for a setting
- Adding titles to individual fields
- Using the component with custom fields

Steps

You will need:

A setting of any type (Other than LOB)
A web app page where you want to add the setting

Step 1 - Generating a schema for the setting

To generate a schema for your setting, we recommend using an online tool that converts JSON into a JSON schema. You can retrieve an example here.Here’s how to use it:

Copy and paste an example setting into the tool.
The tool will generate the schema for the setting.

Name	RETURN_REASON_SCHEMA
Context	ACCOUNT
Context ID	0
Type	JSON
Value	{{schema from above}}

Step 2 - Adding titles to each field

Step 3 - Adding the Settings Component onto a Page

Step 4 - Styling the Page

Now it looks much better.

Default Setting Override

Advanced

Advanced - Using a Custom Component

Setting Up the Custom Field:

Advanced - Enhancing the Field with Custom Properties

1{
2  "path": "retailers/:id",
3  "type": "page",
4  "component": "fc.page",
5  "data": {
6    "query": "query ($id: ID!) {  retailerById(id: $id) {    id    ref    tradingName    createdOn    websiteUrlName    websiteUrl    supportContactName    supportEmail    primaryEmail    supportPhone    summary    updatedOn  }}",
7    "variables": {
8      "id": "{{params.id}}"
9    }
10  },
11  "props": {
12    "title": "Retailer - {{retailerById.ref}}",
13    "backButtons": [
14      {
15        "path": "retailers",
16        "menuLabel": "i18n:fc.admin.retailers.detail.breadcrumb.backToRetailers"
17      }
18    ]
19  },
20  "descendants": [
21    {
22      "component": "fc.tabs",
23      "props": {
24        "layouts": [
25          {
26            "label": "Summary"
27          },
28          {
29            "label": "Settings"
30          }
31        ]
32      },
33      "descendants": [
34        {
35          "component": "fc.page.section",
36          "descendants": [
37            {
38              "component": "fc.card.attribute",
39              "props": {
40                "title": "i18n:fc.admin.retailers.detail.card.summary.title",
41                "width": "half",
42                "dataSource": "retailerById",
43                "attributes": [
44                  {
45                    "label": "i18n:fc.admin.retailers.detail.card.summary.attribute.id.label",
46                    "template": "{{id}}"
47                  },
48                  {
49                    "label": "i18n:fc.admin.retailers.detail.card.summary.attribute.ref.label",
50                    "template": "{{ref}}"
51                  },
52                  {
53                    "label": "i18n:fc.admin.retailers.detail.card.summary.attribute.creationDate.label",
54                    "template": "{{dateStringFormatter createdOn}} ({{dateRelative createdOn}})"
55                  },
56                  {
57                    "label": "i18n:fc.admin.retailers.detail.card.summary.attribute.updatedDate.label",
58                    "template": "{{dateStringFormatter updatedOn}} ({{dateRelative updatedOn}})"
59                  }
60                ]
61              }
62            },
63            {
64              "component": "fc.card.attribute",
65              "props": {
66                "title": "i18n:fc.admin.retailers.detail.card.details.title",
67                "width": "half",
68                "dataSource": "retailerById",
69                "attributes": [
70                  {
71                    "label": "i18n:fc.admin.retailers.detail.card.details.attribute.tradingName.label",
72                    "template": "{{tradingName}}"
73                  },
74                  {
75                    "label": "i18n:fc.admin.retailers.detail.card.details.attribute.websiteUrl.label",
76                    "template": "{{websiteUrl}}",
77                    "link_template": "{{websiteUrl}}",
78                    "condition": "{{and websiteUrl}}"
79                  },
80                  {
81                    "label": "i18n:fc.admin.retailers.detail.card.details.attribute.supportPhone.label",
82                    "template": "{{supportPhone}}"
83                  },
84                  {
85                    "label": "i18n:fc.admin.retailers.detail.card.details.attribute.supportEmail.label",
86                    "template": "{{supportEmail}}"
87                  }
88                ]
89              }
90            }
91          ]
92        },
93        {
94          "component": "fc.page.section",
95          "descendants": [
96            {
97              "component": "fc.settingForm",
98              "props": {
99                "context": "RETAILER",
100                "contextId": "1",
101                "setting": "RETURN_REASON",
102                "schema": "RETURN_REASON_SCHEMA"
103              }
104            }
105          ]
106        }
107      ]
108    }
109  ]
110}

1{
2  "path": "retailers/:id",
3  "type": "page",
4  "component": "fc.page",
5  "data": {
6    "query": "query ($id: ID!) {  retailerById(id: $id) {    id    ref    tradingName    createdOn    websiteUrlName    websiteUrl    supportContactName    supportEmail    primaryEmail    supportPhone    summary    updatedOn  }}",
7    "variables": {
8      "id": "{{params.id}}"
9    }
10  },
11  "props": {
12    "title": "Retailer - {{retailerById.ref}}",
13    "backButtons": [
14      {
15        "path": "retailers",
16        "menuLabel": "i18n:fc.admin.retailers.detail.breadcrumb.backToRetailers"
17      }
18    ]
19  },
20  "descendants": [
21    {
22      "component": "fc.tabs",
23      "props": {
24        "layouts": [
25          {
26            "label": "Summary"
27          },
28          {
29            "label": "Settings"
30          }
31        ]
32      },
33      "descendants": [
34        {
35          "component": "fc.page.section",
36          "descendants": [
37            {
38              "component": "fc.card.attribute",
39              "props": {
40                "title": "i18n:fc.admin.retailers.detail.card.summary.title",
41                "width": "half",
42                "dataSource": "retailerById",
43                "attributes": [
44                  {
45                    "label": "i18n:fc.admin.retailers.detail.card.summary.attribute.id.label",
46                    "template": "{{id}}"
47                  },
48                  {
49                    "label": "i18n:fc.admin.retailers.detail.card.summary.attribute.ref.label",
50                    "template": "{{ref}}"
51                  },
52                  {
53                    "label": "i18n:fc.admin.retailers.detail.card.summary.attribute.creationDate.label",
54                    "template": "{{dateStringFormatter createdOn}} ({{dateRelative createdOn}})"
55                  },
56                  {
57                    "label": "i18n:fc.admin.retailers.detail.card.summary.attribute.updatedDate.label",
58                    "template": "{{dateStringFormatter updatedOn}} ({{dateRelative updatedOn}})"
59                  }
60                ]
61              }
62            },
63            {
64              "component": "fc.card.attribute",
65              "props": {
66                "title": "i18n:fc.admin.retailers.detail.card.details.title",
67                "width": "half",
68                "dataSource": "retailerById",
69                "attributes": [
70                  {
71                    "label": "i18n:fc.admin.retailers.detail.card.details.attribute.tradingName.label",
72                    "template": "{{tradingName}}"
73                  },
74                  {
75                    "label": "i18n:fc.admin.retailers.detail.card.details.attribute.websiteUrl.label",
76                    "template": "{{websiteUrl}}",
77                    "link_template": "{{websiteUrl}}",
78                    "condition": "{{and websiteUrl}}"
79                  },
80                  {
81                    "label": "i18n:fc.admin.retailers.detail.card.details.attribute.supportPhone.label",
82                    "template": "{{supportPhone}}"
83                  },
84                  {
85                    "label": "i18n:fc.admin.retailers.detail.card.details.attribute.supportEmail.label",
86                    "template": "{{supportEmail}}"
87                  }
88                ]
89              }
90            }
91          ]
92        },
93        {
94          "component": "fc.page.section",
95          "descendants": [
96            {
97              "component": "fc.page.section.column",
98              "props": {
99                "width": 2
100              }
101            },
102            {
103              "component": "fc.accordion",
104              "props": {
105                "width": 8,
106                "summary": "Return Reasons",
107                "details": {
108                  "direction": "column",
109                  "components": [
110                    {
111                      "component": "fc.settingForm",
112                      "props": {
113                        "context": "RETAILER",
114                        "contextId": "1",
115                        "setting": "RETURN_REASON",
116                        "schema": "RETURN_REASON_SCHEMA"
117                      }
118                    }
119                  ]
120                }
121              }
122            },
123            {
124              "component": "fc.page.section.column",
125              "props": {
126                "width": 2
127              }
128            }
129          ]
130        }
131      ]
132    }
133  ]
134}

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

Using the Setting Form Component

Using the Setting Form Component

Key Points

Steps

You will need:

Step 1 - Generating a schema for the setting

Step 2 - Adding titles to each field

Step 3 - Adding the Settings Component onto a Page

Step 4 - Styling the Page

Advanced

Advanced - Using a Custom Component

Setting Up the Custom Field:

Advanced - Enhancing the Field with Custom Properties

Christopher Tse

Knowledge Tracks Related To This Topic

Building Blocks

By Type

Helpful Resources

Quick Links

Key Points

Steps

You will need:

Step 1 - Generating a schema for the setting

Step 2 - Adding titles to each field

Step 3 - Adding the Settings Component onto a Page

Step 4 - Styling the Page

Advanced

Advanced - Using a Custom Component

Setting Up the Custom Field:

Advanced - Enhancing the Field with Custom Properties