Whats in the Box
Validation Engine
Order Alteration Validation
Enables validation of patch requests based on configuration.
PO Business Validation
Allows validation of ProductOrder objects using a configurable validation mechanism.
Order Processing Engine
Future Dated Order
Enables scheduling the execution of an order for a specific date.
FDO date change via GUI
Allows administrators to modify the scheduled execution date of an order directly through the GUI.
Decomposition
Conditional relationships
Each relation to executive step or higher level abstraction can be evaluated basing on order itself. Currently, it is based on SpEL expressions that are evaluated during plan generation.
Compensation mappings
During compensation stage, each executed step is mapped to it's counterpart with mapped operation type.
Auto-provisioning
Some steps may be needed to be executed despite lack of product item. Auto-provisioning allows that.
Conditional step affinity
It may be useful or even necessary to execute some steps only once but for many product order items. Those steps may be marked to be run together by default. Conditional affinity is also available. SpEL expressions (based on order payload) may be used to evaluate this flag also.
Order Alteration
Enables modification of an order during execution.
Order Alteration Decision Table
Provides a configurable mechanism for categorizing patch requests as those that modify only the payload or those that also alter the execution plan.
State machines modeller
Enables configuration of state machines within the order execution plan.
Inventory State as Plan Builder Input
Allows execution plan generation to dynamically adapt based on available inventory resources and their statuses.
Point of No Return
Allows configuration of a specific point in the execution plan after which order cancellation or modification requests are rejected by the system.
Service Order Creation
Enables creation of a ServiceOrder based on the ProductOrder, the execution plan, and the current inventory state.
Fullfilment
Order flow events
Each order's change is connected with specific event that is spread on event bus. This allows to create custom logic on each step of the order flow. Event driven architecture supports mechanism of replacing parts of the logic to custom. This approach supports also Audit Logs feature, which allows operator to track whole process.
Payload handling separation
Order flow is totally separated from payload model. This brings the order flow to the higher level of abstraction than order payload handling. This secures the whole process as order will be processed despite any problems with payload or each custom implementation like e.g. Step Executor.
Error Handling
Global Console
Provides a GUI for monitoring and managing errors.
Bulk Error Handling
Enables mass processing and resolution of multiple errors simultaneously.
Error History
Provides a complete history of errors along with all actions taken to resolve them.
User assignment
Each error may be assigned to an user. This is useful to balance work with potential problems.
Skip & Retry
Some errors are retryable, which means operator may choose to try to rerun previously failing step.
Automatic Rules
Allows configuration of automatic rules for error detection and handling.
Error Rules GUI
Provides a graphical interface for managing and configuring automatic error handling rules.
Error Creation via GUI
Allows system administrators to manually create errors on execution plan steps directly through the GUI.
GUI
Multilingual Support
Enables adding and managing multiple languages through configuration.
Service Order visibility and modification
Product & Service Order visibility and modification.
Catalogue
Product Catalogue is a place which hold all business paths of handling each order item fulfilment. It is kept in the MS Excel/cvs format, but functionally it is a graph of dependencies of executive steps with additional attributes on edges and nodes. This graph is combined with the order product items (also provided in form of graph) to produce a fulfilment plan. This plan is exclusive for each order.
Hot deployment
The product catalogue definition is versioned, new versions can be deployed with out system restart. Existing order will be processed on old version new will benefit from product catalogue definition update.
Multiple formats
Both MS Excel and CVS formats are supported. During catalogue import modeler chooses if he wants to send 1 XSL file or many CSV files. CVS format is easier to track using code control.
Import and deploy decoupling
Modeler can import many catalogues. Each will be validated. Then modeler can choose if he wishes to deploy one of them.
Testing Framework
Provides tools for testing and validating the Product Catalogue.
Addons
Dynamic Maper
Dynamic Mapper externalises mapping definitions to a database. Operators can create or amend input‑to‑output pairs through a web panel (GUI) or the BFF-API, without rebuilding or redeploying any service.