LogoLogo
CommunitySupport PortalYouTubeStart a free trial
OE
  • Welcome
  • Commerce Engine
  • Orchestration Engine
  • API Documentation
  • Release Notes
  • Changelog
OE
  • Orchestration Engine
  • Getting Started
    • What is OE?
      • What are the benefits?
      • Use Cases
    • Provisioning
    • Understanding Make
    • OE Learning Trails
      • Setting up a First Digital Process
      • Adding a Conditional Step in a Digital Process
  • Management Dashboard
    • Accessing OE
    • Orchestration Center
    • Forms
    • KPIs and Analytics
    • Rulestore
    • Events
      • Event Registry
      • Event Log
      • Cloud Events in OE
      • Events Authentication and Configuration
      • Working with Event Data
    • Admin
      • Users and Roles
      • Integration with Celonis
      • Make Team
      • Task Inbox and Tasks
  • Digital Processes
    • Digital Processes Dashboard
    • Digital Processes Example
    • Working with Digital Processes
      • Digital Process Components
      • Creating a Digital Process
      • Editing a Digital Process
      • Testing a Digital Process
      • Conditional Process Runs
      • OE Make Modules
      • Configuring a Connection between OE and Make Modules
      • Setting a Trigger to Wake Up a Paused Digital Process
      • Cloning of Make Scenarios in OE Digital Processes
    • Data Flow between OE and Celonis
      • Retrieving Data from Celonis
      • Sending Data from OE to Celonis
      • Sending Form Submission Data from OE to Celonis
      • Sending Forms Magic Links Data from OE to Celonis
    • Process Context
    • Datastore
    • Versioning
    • Data Retention Policy
  • Troubleshooting
    • Firewall Allowlisting
    • Digital Processes Debugger
    • Generating a HAR File with Logs
    • FAQ
      • Receiving Alerts for Scenario Errors
      • Make Scenario Not Valid in OE
      • Digital Processes Blocked by Scenario Errors
      • Invalid Digital Processes
Powered by GitBook
LogoLogo

Resources

  • Emporix.com
  • Developer Policy
  • Terms of Use

Find us

  • LinkedIn

© 2025 Emporix. All Rights Reserved.

On this page
  • Introduction
  • Creating a business rule
  • Simple mode
  • Advanced mode
  • Rules examples
  • Rule for returns approval
  • Rule for a delivery date

Was this helpful?

Export as PDF
  1. Management Dashboard

Rulestore

Create and store business rules that govern the digital processes.

PreviousKPIs and AnalyticsNextEvents

Last updated 22 days ago

Was this helpful?

Introduction

The Rulestore is a repository for creating and managing static business rules to be used in digital processes. They are not active until referenced by a digital process. The business rules can be reused multiple times, in different digital processes. Business rules can be changed without changing the digital process that references it, they are completely independent. Business rules can be created by users with the OE Rule Editor and OE Admin roles.

You can filter the rules by the ID and name. Additionally, you ca also see which digital processes are actively referencing each rule.

If you choose the Go to Digital Process button, it opens the digital process in a separate tab. Business rules cannot be deleted if there's any digital process using the rule.

Creating a business rule

There are two options when creating a business rule, simple and advanced mode:

  • Simple - this is a wizard interface that lets you create rules without needing any technical understanding of the underlying expression language

  • Advanced - lets you create a rule using a comprehensive expression language called JsonLogic

It's possible to add and edit the same rule in both modes as long as the expression can be represented in the simple mode. If you create a more complex, advanced expression, it cannot be viewed in the simple mode.

Simple mode

  1. In the Management Dashboard, go to OE -> Rulestore.

  2. Choose the Create Rule button. Simple mode opens by default.

  1. First, the Name block gets activated in the wizard. Enter the name for the rule in the Rule Name field. You can see it displayed in the block. This name is important because it is used as the variable name, when referenced by a digital process.

  2. Add a Description for the rule. Use this to help you select the correct rule to reference in your digital process.

  3. Choose a Unit for the rule. Units can be of different formats - boolean, string, number, date or list.

  4. Enter the rule Expression. You can choose from a list of the predefined expressions depending on the selected unit. For instance, to decide whether the value of a number should be less, greater or equal to the specified value.

Advanced mode

  1. In the Management Dashboard, go to OE -> Rulestore.

  2. Choose the Create Rule button.

  1. Go to Advanced mode and enter a name for the new rule.

  2. Add a Description for the rule. Use this to help you select the correct rule to make sure it reflects the rule behavior, not to mistake it with a different rule when you reference it in your digital process.

  3. Enter a rule expression. The rule should be created in a JsonLogic format.

A JsonLogic expression for the above order rule:

{">": [{"var": "order"},1000]}

If you add a JsonLogic expression to create a rule, a syntax validation takes place. If the expression is not a valid JsonLogic format, you get an error message and the rule cannot be created.

Rules examples

You can define a variety of different rules for your business purposes, they can include dealing with orders, work processes, effectiveness and many others.

Rule for returns approval

As an example, you can define a rule that works as a condition that filters return reasons. In this rule, the only reasons to approve a return are a damaged product, wrong price, or a wrong product.

Rule for a delivery date

You can set up a rule that will work for products delivered only after a specified date and time.

To learn how the rules can be added to a digital process in OE, see the section in documentation.

Conditional process runs
Creating Digital Processes