We love hearing from our users. Tell us what you want to see next and upvote ideas from the community. * Bugs and troubleshooting should as usual go through InterSystems support.
We may run the rules chain by using Rule Editor with DTL, which is applicable if regarding protocols-transformation and fields-mapping from sources to targets
It is expected to run the rules chain by using Rule Editor without DTL, namely against a SINGLE cloned-object. It will be much efficient in case of hundreds or thousands of rules under same protocol, for example HL7 2.3, ORU_R01
ADMIN RESPONSE
Jul 22, 2024
Thank you for submitting the idea. The status has been changed to "Needs review".
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.
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.