Core Reference Module
Changed on:
17 Feb 2025
Publisher: | Fluent Commerce |
---|---|
Website: | Fluent Commerce |
Download reference module
Version History
Key Changes:
- All the "" Rules no longer produce a custom Audit Event if the Rule condition is not met:
`IfProperty...`
- The Rule now correctly evaluates to false when the specified
`IfPropertyNotEquals`
property is missing (i.e.,`jsonpath`
). This change improves Workflow design by preventing unintended Event duplication when used alongside other "`null`
" Rules (e.g.,`IfProperty...`
).`IfPropertyIsNotPresent`
- The Rule no longer triggers an exception when the
`SetState`
value is missing from the Event. This change specifically applies to the`entitySubType`
Event for Variant and Standard Products within the Product Catalog Workflow.`CREATE`
Key Changes:
JsonPath provision for Event attributes has been fixed for the following Rules:
Improved Integrity Checks: The jar file in the Core Module now complies with standard integrity verification tools.
- Benefit: This ensures that the jar file passes CRC checks, preventing errors when verifying or reading the jar file.
- Technical Fix: Previously, tools like and standard Python libraries might fail to verify or read the jar file due to integrity issues. This update resolves these issues, ensuring smooth operation.No changes were made to the rules or any other files within the Core Module.
`unzip`
Bug fixes:
- Fixed issue with rule not handling GraphQL failure responses gracefully.
``SetState``
- Enabled Rubix retry mechanism to work properly with the rule, reducing errors related to concurrent updates when the same entity is updated via different processes.
``SetState``
Enhancement:
- Added a new ScheduledEvent rule to Core Reference Module. This rule will allow you to schedule an event to occur after a specified amount of time has passed.
Bug fixes:
- The rule will no longer fail with an ActionException unexpectedly
`SendWebhook`
- The rule now works correctly with the INVOICE entity
`SetState`
Bug fixes:
- The rule now works correctly in Locations Workflows.
`SetState`
- The rule no longer causes some statuses in a Workflow to need to be removed in order to pass validation.
`SetState`
- The rule no longer causes orchestration events to get stuck in Pending status and Audit events to no longer be logged.
`SetState`
- The rule no longer causes an exception to be thrown when an entity level is changed.
`SetState`
Overview
The Core Reference Module is a foundational Reference Module.
It provides a base set of general purpose Rules:
- that other Modules are built upon
- or that can be included in your own Workflows
Extensible by design, use this Module as a base to build a solution for the needs of your customers.
Detailed Technical Description
Features
The Core Reference Module contains a collection of general purpose Rules to power your Workflows:
- Change the state of an Entity
- Send an Event to trigger a Ruleset for the same Entity
- Send a Webhook
- Create conditional logic based on the value or presence of a property
Workflows
The Core Reference Module doesn't provide any Reference Workflows.
Its Rules are designed as follows:
- to work cross-Domain
- to be utilized in other Reference Modules Workflows or your own ones.
Rules
The Rules below make up the Core Module:
Name | Description |
Change the status field of this entity to the value provided. | |
Send an event to trigger another Ruleset on the same entity. | |
Conditionally trigger another Ruleset when the specified entity field or event attribute matches the provided value. | |
Conditionally trigger another Ruleset when the specified entity field or event attribute does not match the provided value. Typically used as an "else" case for the "IfPropertyEquals" rule. | |
Conditionally trigger another Ruleset when the specified entity field or event attribute is not null. | |
Conditionally trigger another Ruleset when the specified entity field or event attribute is null.Typically used as an "else" case for the "IfPropertyIsPresent" rule. | |
Conditionally trigger another Ruleset when the specified entity field or event attribute is greater than the provided value. A usage example includes pushing an order through a fraud-check flow only when the
| |
Conditionally trigger another Ruleset when the specified entity field or event attribute is less than the provided value. | |
Conditionally trigger another Ruleset when the specified entity field or event attribute is between the provided values. | |
Send a configurable Webhook based on a setting. | |
Send an event after a specified amount of time has passed. |
Capability type: | Module |
---|