Docs
Author:
Fluent Commerce staff
Changed on:
25 Oct 2023
This article introduces the concept of a fluent module and describes the basic structure and contents of a fluent module
A Module is a group of Artifacts bundled together to achieve a domain functionality. Artifacts can be:
Artifacts also include Settings.
A valid Module can contain any combination of Artifacts, however, they must also contain Metadata. Together, the Artifacts in a Module should provide a single package of domain capability or a reference to create or extend domain capability. Modules work together and extend each other.
There are two categories of Module, Reference Modules and Extensions.
A module must contain Metadata, but can otherwise have any combination of the following Artifacts:
Artifact Name | Mandatory |
Metadata | Yes |
Rules | No |
Workflows | No |
Settings | No |
Web App Manifests | No |
Translations | No |
UI Components | No |
Structural data | No |
Metadata contains information about the Module's name, publisher, version, author(s), Dependencies, and Contracts.
Dependencies are either Modules or Contracts that must exist on an account before the Module with the dependency can be installed.
A Contract is a document that defines what input and output events are required for a Module to work. Contracts offer a convenient way to specify workflow compatibility between Reference Modules, Extensions and Connectors”
A Rule represents an atomic piece of business logic which can be configured and reused. A commonly used analogy for describing Rules is LEGO bricks which we can click together in different configurations to create a different outcome. Learn more about Rules here.
Workflows describe business process orchestration that underpin specific feature sets and functionality for each of the Fluent apps. Workflows run on the Workflow Engine.
Settings are key-value pairs set in a Context (Account, Retailer, Location/Agent) that the Fluent Platform, Workflows and Web App Manifests use to drive their logic. Learn more about Settings.
A Web App Manifest is a type of Setting that describes an App. A Web App Manifest may extend an existing app, like Fluent OMS or Fluent Store, or could create an entirely new app. The Manifest also describes the layout and components of a page within an app. Learn more about the UX Framework.
Translations are a type Setting that enables the translation of an app into another language. Learn more about Translations.
Components are referenced in Web App Manifests and used to control how a user interacts with an app. See available components in our Component Library. Learn more about building UI Components.
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.
