Platform

This article explains what happens when an account is temporarily locked due to multiple failed login attempts, whether caused by a user entering the wrong password or an integration using outdated credentials.

After reading this article, you will understand:

• What triggers a username lockout in Fluent 
• How the lockout works 
• What actions users and integration owners should take

Key Points to Know:

• Lockouts are temporary (15 minutes).
• Applies to both web console users and API clients.
• A lockout is enforced even if the correct password is entered after the threshold is reached.

• Accounts are locked after multiple failed login attempts ( 5 attempts).
• Lockouts are specific to the username with failed login attempts
• The lockout period is 15 minutes, starting from the last failed attempt.
• Lockouts apply across all login methods (web, API, scripts) using the same username.
• During a lockout for a given username:
  • All logins (even with correct credentials) will return an error
  • The error message will be exactly the same as providing an incorrect username and password (even with correct credentials)
• The login screen and error messages will clearly reflect lockout status.
• Technical users maintaining integration code should ensure their code does not retry authentication more than 5 times. 
• Avoid account sharing between UI users and integrations to prevent cross-impact.
• Contact Support if you're locked out and need urgent access.

A detailed explanation of Fluent OMS entities and how they can be used throughout the order journey.

• Entities in Fluent OMS are data objects that store and process information throughout the order journey, such as orders, fulfilments, and financial transactions.
• Entities are managed via GraphQL, with mutations and queries used to create, update, and retrieve entity data.
• Entities should not be deleted but controlled using status fields, although some "remove" mutations can disconnect entities.
• Orchestrated Entities trigger a CREATE event upon successful creation, enabling workflow automation.
• Entities in Fluent OMS serve unique purposes to enable an end-end digital commerce journey and their statuses determine at what stage they sit.
• Entities have types and subtypes, types are rigidly defined, subtypes are more flexible.

Fluent platform functionalities are designed to be flexible by integrating with other APIs and Connectors and provides a real time view of the Inventory to the sales channels, enables integration with Warehouse Management Systems (WMS), carrier services, ERPs, etc.

• Some common interfaces, and the information shared between these interfaces and the Fluent Platform
• GraphQL, and understand its benefits over REST APIs.
• Events API, Inventory Batches, Webhooks, and Connectors

This document explains the GraphQL Error Codes used by Fluent Commerce.

• Understand the Error Code structure: Each code follows the Prefix + 4-digit Code + Suffix format (e.g., C0001E), which instantly reveals the source (Client/Server/Third-party) and type (Error/Warning) of the issue
• Quick diagnosis and resolution: Error Codes are grouped by category and purpose, helping developers diagnose and resolve issues faster without deep debugging or guesswork
• Self- vs. support-resolvable issues: 
  • Codes with a C prefix usually point to issues clients can fix on their own 
  • While S prefixed Codes may require platform support

The SSO Cutover Planning and Execution details the essential steps for migrating and transitioning to SSO in Fluent. The specifics may differ based on the client's implementation of Fluent. It is advisable to have discussions with your partner and the Expert Services contact to gain further clarification.

• Necessary prerequisites for migration and cutover
• Planning the user migration
• Availability during cutover
• SSO Activation and Testing

Fluent REST API returns specific HTTP Error Codes which may vary depending on the API endpoint and are explained in this document.

• Categorization by HTTP Status Code: The errors are organized by standard HTTP status codes (e.g., 400, 401, 403, etc.), which helps developers quickly understand the type of issue
• Coverage of Common Scenarios: The examples span a range of typical failure conditions, from authentication issues to plugin errors and timeouts, offering a practical reference for API consumers

The labs in this article will walk you through the following scenarios: GraphQL Introspection and Sending a Webhook

• Postman Configuration for auto-complete
• Access to mockable.io

Fluent integrates key Google Cloud Platform (GCP) services to enhance scalability, performance, and security across its infrastructure. By leveraging Compute & Serverless, Data & Storage, Networking & Delivery, and Security & Compliance solutions, Fluent ensures a reliable and efficient cloud environment.

• Google Cloud Platform components used by Fluent fall into the Compute & Serverless, Data & Storage, Networking & Delivery, and Security & Compliance categories
• Compute & Serverless: Run workloads with virtual machines (GCE), Kubernetes (GKE), and event-driven functions (Cloud Functions). 
• Data & Storage: Store and analyze data with Cloud Storage, BigQuery, Cloud SQL, and Cloud Spanner. 
• Networking & Delivery: Speed up content with Cloud CDN and balance traffic efficiently with Cloud Load Balancer. 
• Security & Compliance: Protect workloads with IAM, Cloud KMS, Secret Manager, and Audit Logs.

The Interface mapping document should clearly define what data will be exchanged between OMS and the external systems (e.g. middleware or eCom).

• The aim of the Interface Mapping document should keep it as simple as possible;

In this module, you will learn about a Plugin Project structure and JS GraphQL within the Plugin Project.  You will also learn how to modify and run a JS GraphQL query.

• Installed SDK
• GQL Basics

In this lesson, we'll look at the benefits of using GraphQL, as well as explore the differences between GraphQL and REST based APIs. We will also look at some examples of a GraphQL query and a GraphQL mutation. 

• Introduction to GraphQL
• Differences to REST
• Benefits of using GraphQL
• Basic structure of a query
• A GraphQL mutation
• Types of common integrations that use GraphQL

The support process at Fluent Commerce relies on integration partners to handle initial investigations for issues related to custom implementations. If platform-related problems are identified, partners must escalate them via a JIRA support ticket. Additionally, Fluent Commerce offers Expert Services for guidance during the design, implementation, and support phases.

• Partner Responsibility: Handle initial investigations of custom rules and configurations.
• Platform Issues: Escalate confirmed platform-related problems via JIRA with detailed logs.
• Fluent Expert Services: Consultants assist with complex issues during implementation and support.
• First-Time Partners: Fluent Expert Services provides additional support for new implementation partners.
• Customer Success Manager: Partners can seek guidance on using Expert Services.

This lesson covers key operational activities in Fluent Commerce, including Plugin Management, Workflow Versioning, and Audit Events. You’ll learn how to manage Fluent plugins, version workflows, and utilize audit events to debug and analyze processes within the Fluent platform.

• Plugin Management: Upload, activate, and manage plugin versions via Plugin API.
• Workflow Versions: Submit, view, and retrieve versions for effective workflow management.
• Event Categories: Includes snapshots, rulesets, rules, actions, and exceptions.
• Event Viewing: Access audit data via Event API, Event Search, or Fluent OMS Activity tab.

Fluent OMS and Postman are key tools for managing and troubleshooting the Fluent Commerce platform. Fluent OMS provides a web-based interface for managing orders, inventory, and workflows, while Postman facilitates advanced debugging and custom queries using GraphQL. Together, they help identify and resolve issues like stuck orders or workflow interruptions.

• OMS Application: Manage orders, inventory, and workflows in one place.
• OMS Dashboard:  Monitor entity statuses (orders, fulfillment, etc.).
• Postman Queries: Use GraphQL to query or correct data.
• Issue Investigation: Identify stuck orders using order states and filters.
• Workflow Re-triggering: Reset and restart workflows using the Events API.

This training introduces the tools and activities used in Fluent Commerce Support and Operations processes. You’ll learn how to use Fluent OMS and Postman for troubleshooting, identify common issues like stuck orders, and learn to resolve them effectively.

• Fluent OMS: Navigate and use built-in tools for issue resolution.
• Postman Queries: Run custom API queries for debugging.
• Stuck Orders: Learn to identify orders that are not processing.

API, Integration, and Connectors

This lesson covers the various integrations and connections with the Fluent platform.

• Fluent is designed to integrate flexibly with other API's and connectors
• Fluent provides connectivity via Rest and GraphQL API's
• Webhooks provide outbound connectivity from Fluent

This topic describes the cloud native nature of the Fluent platform

• Scalable
• Secure
• Versionless software
• Zero downtime

This guide helps to select the correct IDP configuration and plan SSO implementation.

• Single sign-on (SSO) is exclusive to the OMX framework, and API users are managed in Fluent IdP, not Corporate IdP, with creation possible through API.
• SSO, enabled for each Fluent account, involves creating a corresponding SSO Ping Identity environment managed by the SRE team, covering admin user setup, password policy configuration, branding, and application enablement.
• SSO Environment Admin Users, Fluent IdP Configuration, Password Policy, and other guides provide comprehensive details for SSO enablement, Corporate IdP integration, user management, authentication policies, multi-factor authentication, and configurations with Azure AD and Okta.

In this module you'll learn about how events are executed on the Fluent platform.

• A workflow represents the journey of a root entity, and related sub-entities, through various stages in its lifecycle.  These stages are represented by statuses.
• Rulesets are collections of rules forming tasks within a process, dictating movement from one state to another based on business logic.
• When an orchestration event is received, the Workflow Engine loads the associated workflow and searches for a matching ruleset based on event name, entity type, subtype, and status.  Matched rulesets are executed, and may produce additional events to trigger further rulesets in sequence.

This is a guidepost for Developers highlighting important guides and articles to speed up Fluent Commerce's learning process. 

• Workflows that consist of states, rulesets, triggers, user actions, and Modules, used for distributing workflows and it's artifacts, are a key part of the Fluent Commerce platform.
• Settings are used to adjust Workflow execution

GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. It provides a complete and easy-to-understand description of the data in your API. Its ability to return select fields enables it to be used with powerful developer tools and ensures that APIs are easily scalable.

Fluent's GraphQL API has two operations:

• Queries 
• Mutations

Queries include predefined Queries and Custom Queries, both of which will be covered below.

• Operations
• Queries
• Mutations
• Custom Queries

If a company has an internal IdP then this IdP can be integrated with our SSO Vendor and used for future user authentication.

API user is always managed in the SSO vendor environment and doesn't have an MFA authentication option.

• For SSO to work, you need to establish a connection between your Corporate IdP and our vendor IdP. Once the relationship is established then your password policies and MFA configuration will be used during user authentication in Fluent.

The Ready for Launch process (RFL) is an engagement with the Fluent Commerce Expert Services team throughout the lifecycle of a Fluent project. The process is initiated at the beginning of a Fluent Commerce project and completed with the go-live of the project in production.

The final review ("RFL Launch Gate") should be planned for 3-4 weeks before the desired Go-Live event to receive the approval to move into production.

• The Kickoff stage covers the introduction to the Ready for Launch process and the initial project & solution overview.
• The Design Review stage covers a detailed presentation of the solution by the partner and the review of the implementation by Fluent Commerce.
• The Launch Gate stage covers the presentation of the final solution and performance test results as well as the confirmation of the desired launch date. After a final review, Fluent Commerce provides the production go-live approval.

The following guidelines and specifications apply to the entire schema, with any exceptions documented in the schema of the relevant entity.

• The GraphQL request size is limited to 2MB
• There is no validation on any of the GraphQL fields (except for enums)
• The GraphQL query complexity is limited and checked in accordance with the Query Complexity Calculation Algorithm (11,111 Total Complexity is Max)

The Fluent platform generates unique IDs internally, which serve as the primary key for each new record. They are unique and enforced to avoid ambiguity. Users cannot set these via API. Whereas refs are typically from third-party integrations, they represent external system IDs and occasionally are generated internally with guaranteed uniqueness. It is the integrator's responsibility to ensure refs are unique in Fluent Commerce.

• IDs are generated by the Fluent platform and are guaranteed to be unique at the time of creation. 
• Refs are typically values passed in via third-party integrations and should represent the IDs from external systems.
• Despite the system not enforcing the uniqueness of refs, it is highly recommended to have unique refs for all entities. Every ref should be unique within it's nearest container, for example Retailer refs need to be unique across all . Catalogue or Account.
• If your refs are not unique then there are API's that will not work as expected. This means that our reference modules may not work as expected if you set ref's as non-unique values.

Exponential backoff is a standard error handling policy for network communications such as the Fluent APIs. 

Exponential backoff involves a client periodically retrying a failed request over an increasing amount of time.

• Retries & Exponential Back-offs

The Fluent Order Management Cloud Platform is underpinned by a comprehensive infrastructure designed to support order management and inventory availability processes, comprising of technical capabilities organized into Services and Frameworks, each facilitating specific functionalities critical to platform operations.

• Included Services and Frameworks:
  • Orchestration Engine, APIs, Logging, SSO, Cloud Infrastructure
  • Workflow, UX and Connect Frameworks