Lesley Dean

Small composable rules enable composition of business logic. This is important to maintain flexibility and minimise the cost of change over time. These are 2 of the most common reasons our customers choose Fluent Order Management!

So why is this so important? In this first article in the “Composable Rules Series”, I present “the why”. We’ll explore 7 reasons for building small composable rules.

By the end of this article, you will understand the benefits for both developers and our customers.

The Fluent CLI provides command line tooling for interacting with Fluent Accounts and Modules.

Usage

The Fluent CLI is activated by typing the keyword `fluent` into a terminal command line, followed by a Command, Subcommand, Argument, and Options:

`fluent <command> <subcommand> <argument> [options]`

• The `<command>` will refer to a noun (or “a thing”).
• The `<subcommand>` will refer to a verb (or action).
• The `<argument>` is the primary required name of the “thing” identified by the `<command>`.
• The `[options]` may include required or optional additional parameters to be used by the `<command>` and `<subcommand>`.

The Rules SDK is a Java based software development kit, which provides Java developers with a toolkit for creating custom Rules for the Fluent OMX Workflow Framework.

The Workflow Framework is a highly configurable and extendable part of the Fluent OMX Platform, which facilitates orchestration of business logic for the Fluent Order Management System.

This page describes how Event Execution works.

Events are a fundamental part of the Fluent Platform. Not only are they used to trigger workflow logic, but they also capture everything that happens within the system. Events are categorized by type.