Configuration, Extension and Integration

Configuring the server side automation that makes FSM behave the way a particular business needs. A rule is a delivered process with customer value sets: inputs, conditions and the values or performs to apply when they match.

Changing what the smart client shows. FSM 6 customisations add, hide, relabel and rearrange fields on delivered screens, add buttons and tabs, set constraints and child relations, and bind events to scripts.

Writing the code that runs in the client when something happens on a screen. FSM 6 client scripts are a restricted JavaScript dialect with a fixed function library, bound to screen and control events.

Building the guided sequences that walk a user through a task. FSM 6 workflows are client side wizards stored as Windows Workflow XAML, made of question steps, lookup screens, XML messages and branching expressions written in Visual Basic.

Extending the data model. FSM 6 lets customers add columns to delivered tables, create new tables, define relations and lookups, set defaults and constraints, and configure copy and import maps, all as metadata.

Building the pages people look at rather than the screens they type into. FSM 6 lobbies are near real time overview pages made of elements fed by data sources, alongside ad hoc reports and the older dashboards.

Moving data in and out. FSM Connect maps external structures onto FSM tables and columns, and routing rules decide which handler carries each message and how failures are retried.

Turning device telemetry into service action. FSM 6 registers IoT devices against products, receives observations, and applies observation rules that raise requests, update meters or trigger actions.

Moving configuration between environments. FSM 6 packages business rules, client scripts, custom metadata, functions, integrations, lobbies, menus, perform messages, reports, screens and workflows into a single deployable file.