Knowledge Tracks
Test
View Category with assigned Products in OMS Webapp
How-to GuideStep-by-step guides to achieve a specific scenario or setup.- Standard Product Page: A standard product page typically includes detailed information about a single product, such as descriptions, specifications, images, pricing, and customer reviews. They are essential for providing customers with all the necessary information to make an informed purchase decision.
- Variant Product Page: A variant product page is used when a product comes in different versions, such as sizes, colors, or models. These pages allow customers to choose their preferred variant while viewing the product's overall information. This approach simplifies the shopping experience and helps customers find the exact product they need.
- Consistent Layout: When adding both standard and variant product pages to a product category page, it's crucial to maintain a consistent layout and design. This consistency ensures a seamless user experience and makes it easier for customers to navigate and compare products.
- Clear Navigation: Implement clear navigation elements, such as filters and sorting options, on the product category page. This helps customers quickly find the specific products or variants they are looking for, improving their overall experience.
Adding a Ruleset to your Workflow
How-to GuideStep-by-step guides to achieve a specific scenario or setup.- The Ruleset, defining the executed actions for matching events, can be added through the UI using either an existing Ruleset list or the Entity Workflow Swimlane.
- Green icons in the Status rectangles represent Rulesets triggered on that State, while those outside a status transition the entity to the indicated state.
- Adding a Ruleset via JSON requires inclusion in the Workflow JSON's Rulesets Array, following a schema with mandatory elements like name, rules, and triggers, and optional elements like description, type, subtype, eventType, and userActions.
Raise a Support Request for Reference Modules
How-to GuideStep-by-step guides to achieve a specific scenario or setup.- Before raising a ticket, review the reference module setup and configuration guides, Use the Event API to validate the workflow process executed, including source Event, Rulesets, and Rules, and Check all Settings, Users, Roles, Auth Tokens, etc. before raising an issue.
- Support is provided for reference modules, which are Core, Order, Fulfilment, and Inventory.
- Raise a Support Request for Reference Modules with a Fluent Retail Support (FRS) ticket.
Integration Tests with the Connect SDK
How-to GuideStep-by-step guides to achieve a specific scenario or setup.- End-to-End Test Orchestration: You will learn how to wire, configure, and execute automated integration tests using specialized Connect SDK test modules (
`connect-sdk-test-core`, `connect-sdk-test-core-aws`, and `connect-sdk-test-core-kafka`) to validate custom data handlers against simulated API footprints and containerized queue systems. - Execution Command Restrictions: Standard unit test triggers like
`mvn test` will completely ignore these integration suites. You must invoke the pipeline using `mvn clean integration-test` and explicitly declare or preset the targeted active Spring profiles (such as `aws,localstack` or `kafka`) to instantiate the proper environment dependencies and messaging beans. - Isolated Bootstrapping Requirements: When building integration tests inside a decoupled code module that lacks a primary application runner, you must manually deploy an executable bootstrap class annotated with
`@SpringBootApplication` and `@EnableScheduling` inside your `src/test/java` directory. Additionally, you must place three mandatory configuration manifests (`application.yml`, `application-connector.yml`, and `bootstrap.yml`) into the `src/test/resources` folder. - Automated Environment Isolation: The test suite leverages
`Testcontainers` and `WireMock` to manage external asset lifecycles dynamically. Activating specific environment flags like `localstack` inside the configuration settings instructs the SDK to auto-provision localized mock instances of cloud services (including Amazon SQS queues, Amazon S3 buckets, and secrets vaults), eliminating the need to manage external persistent test infrastructure.
Replace the Orders Search Bar with the Filter Panel in Fluent OMS
How-to GuideStep-by-step guides to achieve a specific scenario or setup.- The standard Orders screen filters through the search bar built into List Component. This guide replaces it with a Filter Panel that shows every filter at once, takes several exact values in one field, fills its dropdowns from Settings, filters dates by range, and searches products and customers
`fc.filterPanel` is a sibling of `fc.list`, not a child: it goes first in the same `descendants` array, and is tied to the list by matching `filtersSource` to the list's `dataSource`- The panel builds its fields from the arguments of that connection: the reference, type, status, date and tag fields appear with no extra wiring, and the product and customer filters are configured through overrides
- Dropdown options come from platform Settings that you create and configure yourself
`allowReadWriteUrlParams` keeps the active filters in the URL, so a filtered view can be bookmarked or shared- The same component filters an inner list, for example the fulfillments of one order inside an expanded row