# RulesEngineEditor
**Repository Path**: bxb-l/RulesEngineEditor
## Basic Information
- **Project Name**: RulesEngineEditor
- **Description**: Microsoft RulesEngine 编辑器 - 用于集成到 Web 或桌面中的 Blazor UI 库。
GitHub地址:https://github.com/alexreich/RulesEngineEditor
- **Primary Language**: C#
- **License**: CC-BY-4.0
- **Default Branch**: main
- **Homepage**: https://github.com/alexreich/RulesEngineEditor
- **GVP Project**: No
## Statistics
- **Stars**: 0
- **Forks**: 0
- **Created**: 2025-02-05
- **Last Updated**: 2025-02-05
## Categories & Tags
**Categories**: Uncategorized
**Tags**: None
## README
# Rules Engine Editor

Editor for Microsoft Rules Engine - Blazor UI library intended for integration in Web or Desktop
[![CC BY 4.0][cc-by-shield]][cc-by]

## Overview
Rules Engine Editor is a library/NuGet package for use with [Microsoft Rules Engine](https://github.com/microsoft/RulesEngine) which itself is a package for abstracting business logic/rules/policies out of a system.
## Installation
To install this library, download the latest version of [NuGet Package](https://www.nuget.org/packages/RulesEngineEditor/) from [nuget.org](https://www.nuget.org/).
## How to use it
There are several ways to populate workflows for the Rules Engine Editor as listed below.
Rules are based on the [Microsoft Rules Engine schema definition](https://github.com/microsoft/RulesEngine/blob/main/schema/workflow-schema.json) and can be stored in anything deemed appropriate like Azure Blob Storage, Cosmos DB, Azure App Configuration, [Entity Framework](https://github.com/microsoft/RulesEngine#entity-framework), SQL Servers, file systems etc. For RuleExpressionType `LamdaExpression`, the rule is written as a [lambda expressions](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/statements-expressions-operators/lambda-expressions).
The Rules Engine Editor can also use a format for [Input Rule Parameters](https://github.com/microsoft/RulesEngine/wiki/Getting-Started#ruleparameter) based on the [schema defintiion](schema/inputRuleParameter-schema.json) and can likewise be stored as the aforementioned workflow schema. Input Rule Parameters allow the seeding of arbitrary input data to be used in the Rules Engine. Consider Input Rule Parameters like interactive "unit tests" which allow for "What-If" type analysis.
## Live Demo
### WebAssembly
https://alexreich.github.io/RulesEngineEditor
> This can also be installed as a standalone PWA and used offline.
### With Sample Data
https://alexreich.github.io/RulesEngineEditor/demo
## Features
* Works in conjunction with [Microsoft Rules Engine](https://github.com/microsoft/RulesEngine)
* Real-time evaluation
* Add, Edit, Delete in form view, JSON or switch between them
* Drag, Drop objects to change order
* Current Workflow dropdown, switch between workflows as well as [pass in current workflow as a parameter](https://alexreich.github.io/RulesEngineEditor/demo/Test%20Workflow)
* Nested Rule support
* Import, Download [compliant Workflow json](https://github.com/microsoft/RulesEngine/blob/main/schema/workflowRules-schema.json)
* Import, Download [compliant Input Rule Parameter json](schema/inputRuleParameter-schema.json)
* Entity Framework support for load and save ([example in Server project](https://github.com/alexreich/RulesEngineEditor/blob/main/demo/RulesEngineEditorServer/Pages/DemoEF.razor))
* Design Time Support:
* Pass pre-constructed instance of Rules Engine
* Supports 2-way binding of Workflows
* "Starter" Input Rule Parameter JSON
* Allows for non-supported types in Rules Engine Workflow JSON
* .NET 6 Support
## Usage
Simple:
```csharp