v1.0.0-beta-3

What's Changed

• RC Readiness Improvements: Post-Audit Fixes by @Sendipad in #13
• feat: FlexiRule RC Refactor by @Sendipad in #14
• FlexiRule RC Refactor — Implementation Plan (v2) by @Sendipad in #15
• feat: fix schema serialization and detection for reports and lists by @Sendipad in #17
• feat: implement rule schema logic and frontend refactor by @Sendipad in #18
• feat: improve query output schema resolution by @Sendipad in #19
• Refactor: Rule Builder 3-Panel UI, Contract-Driven Validation, and Schema Optimization by @Sendipad in #20
• Normalize process operation DTOs and adapt frontend parsing by @Sendipad in #21
• feat: implement architecture review improvements and security fixes by @Sendipad in #22
• feat: v0.1 release constraints and enhanced graph validation by @Sendipad in #23
• feat: FlexiRule Trigger Model & RC Schema Refactor by @Sendipad in #25
• v1.0.0-beta.3: Core Refactor and Trigger Model Enhancement by @Sendipad in #26
• feat: rule builder enhancements and advanced flow tests by @Sendipad in #27
• feat(rule-builder): Rule Builder UX enhancements and bug fixes by @Sendipad in #28
• fix(builder): resolve entry action and node positioning by @Sendipad in #29

New Contributors

• @Sendipad made their first contribution in #13

Full Changelog: https://github.com/Sendipad/flexirule/commits/v1.0.0-beta-3

v1.0.0-beta-2

FlexiRule v1.0.0-beta.2: The Unified Process Era
We are thrilled to announce the release of v1.0.0-beta.2. This milestone represents a significant leap forward in the maturity of FlexiRule, featuring a complete overhaul of our core execution architecture.

💎 Key Highlights
📦 Unified Process Architecture
We have officially retired the legacy @ProcessMethod decorator and its associated DocType. In their place is a unified, file-backed Process & Operations system. This new model mirrors Frappe's robust Report and Dashboard mechanisms, allowing for:

Version Control: Your business logic now lives in
.py
files, making it traceable via Git.
Performance: Logic execution is significantly faster and more memory-efficient.
Boilerplate Generation: Developing new "Standard Processes" is now automated via Frappe's boilerplate system.
🏗️ Simplified Rule Engine
The Rule Engine has been streamlined. By purging legacy branching logic, the execution flow is now deterministic and easier to audit. The engine exclusively executes modern Processes, ensuring that "what you see in the builder is exactly what runs in the background."

🎨 Metadata & UI Cleanup
We performed a deep "spring cleaning" of the codebase:

Metadata Purge: Removed legacy fields (process_method, configures) from the Rule Action and Data Review Task DocTypes, resulting in a cleaner UI and a smaller database footprint.
Frontend Optimization: The Vue-based Rule Builder has been optimized, with the Pinia store purged of legacy state management.
Rebuilt Assets: Frontend bundles have been rebuilt to support the modernized architecture.
📝 Detailed Changes
🔧 Backend & Engine
Removed: Legacy @ProcessMethod decorator and flexirule.ruleflow.decorators.
Removed: 9 legacy process method modules (Validation, Enrichment, etc.) in favor of the new Process system.
Refactored:
RuleEngine
to strictly follow the new execution flow.
Updated:
Rule
controller validation logic to support new Process operations.
Optimized:
api.py
purged of legacy endpoints.
📄 Metadata & Database
Schema Update: Cleaned up Rule Action and Data Review Task JSON schemas.
Migration: Successfully removed "Process Method" from the database via bench migrate.
💻 Rule Builder (UI)
State Management: Optimized Pinia
store.js
for better performance.
Modern Documentation: A completely revamped
README.md
and
CONTRIBUTING.md
reflecting the new architecture.
⚠️ Breaking Changes
Legacy Decorators: All logic using @ProcessMethod is discontinued. Please migrate code to the new Process system.
Rule Actions: Rules created in Beta 1 using the process_method link must be updated to use the new Process and Operation fields.

Full Changelog: v1.0.0...v1.0.0-beta.2

V1.0.0-beta

Full Changelog: v1.0.0...v1.0.0

V0. 9.0 beta-Pre released

Full Changelog: v1.0.0-beta...v1.0.0-beta

Pre-realsed

This initial release represents the culmination of more than two years of development focused on building a flexible, user-driven rule engine on top of the Frappe framework.

The journey began with the first application, UPH, which served as the early foundation for experimenting with rule-based logic.
Later, the project was separated and rebuilt into a standalone application named Business Rule Hub (BRH), with the goal of creating a truly flexible rule engine designed around the needs of end users rather than the preferences of developers.

After multiple refinements, BRH evolved and was re-engineered into a more advanced version under the name Bolton(with the help of AI) , expanding the rule engine’s capabilities and improving overall structure.

Today, the project reaches its most mature form with the introduction of FlexiRule, which replaces Bolton and becomes the official and maintained version moving forward.

FlexiRule delivers a robust, extensible rule engine designed with a cleaner architecture and greater adaptability than all previous versions.