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.
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