InterSystems Ideas
Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.
The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.
💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.
🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.
Start by sharing what could be better - the community and our teams will help take it from there.
The discussion here https://community.intersystems.com/post/how-apply-huge-amount-biz-rules-cloned-object-using-rule-editor does summarize the current capabilities pretty well. Virtual Documents like HL7 are implemented in a very efficient way while still supporting inmutable objects (an important feature). Messages can be chained very effectively with the Rule Engine, but values remain inmutable here for a good reason.
William have you tried to send your messages through a DTL and can be you more clear about what you mean with overhead? It seems this is more relevant to be investigated.
Thanks for your suggestion!
I'm writing to propose an enhancement to the Rule Editor Framework that would enable efficient rule chaining without the need for DTL in specific scenarios. Currently, the Rule Editor and DTL combination is a powerful tool for protocol transformation and field mapping between sources and targets. However, for certain use cases, DTL can be heavyweight and unnecessary.
Proposal:I propose extending the Rule Editor Framework to support light-weight rule chaining without DTL when working within a single protocol (e.g., HL7). This would involve:
Assigning value to an object cloned from source message, e.g., EnsLib.HL7.Message (functionality to be developed)
Passing a cloned object from one rule to another, and so on (functionality to be developed).
Sending the final modified object to the next process or operation (functionality to be developed).
Benefits:This approach would offer several advantages:
Simplified and Efficient: Eliminates the overhead of DTL when working within a single protocol.
Improved Maintainability: Separates rule logic from code, allowing for easier editing through the Business Rule List page's export and import functionality.
Potential Customer Acquisition: Provides a compelling alternative to open-source solutions like Drools, attracting their customer base.
Call to Action:I believe this enhancement would significantly benefit users working with large rule chains and high volumes of concurrent processes. I kindly request the team to consider this proposal and explore the feasibility of developing the mentioned functionalities within the Rule Editor Framework.
William, thanks for the idea.
This seems to be related to your question in the Developer Community: https://community.intersystems.com/post/how-apply-huge-amount-biz-rules-cloned-object-using-rule-editor
I've added a link to the question in case readers of the idea need more information on the topic of the idea.