Rule files
Each rule editor—entity rule editor and component rule editor—contains the respective rule file. The rule files include imported Drools packages, which are crucial for embedding sophisticated business logic into the system that allows you to define rules in a format that can be processed by the system.
Entity rule file
The entity rule editor contains the entity rule file. For more information on how to access it, please see Rule editors.
Structure of the entity rule file:
Imports: Drools package and global DocuMine imports
Queries
Headline rules
General DocuMine rules (This is where you can enter your customized rules.)
Manual changes rules
Entity merging rules
Component rule file
The entity rule editor contains the entity rule file. For more information on how to access it, please see Rule editors.
Structure of the component rule file:
Imports: Drools package and global DocuMine imports
Queries
Guideline mapping object
Default component rules (This is where you can enter your customized rules.)
Component merging rules
Security and rule functionality
Ensuring the security and optimal functionality of our rule editors and the DocuMine rule set is paramount. That is why we have implemented the following security measures:
Entity rule file:
Changes to the following sections/rules are not recommended, as this could affect the correct execution of the rules:
Import packages,
Global settings,
Queries,
Headline rules,
Manual changes rules,
Entity merging rules,
LDS.0.0. rule.
Component rule file:
Changes to the following sections/rules are not recommended, as this could affect the correct execution of the rules:
Import packages,
Global settings,
Queries,
Guideline mapping object,
Component merging rules.
Component rule file:
Changes to the following sections/rules are not recommended, as this could affect the correct execution of the rules:
Import packages,
Global settings,
Queries,
Guideline mapping object,
Component merging rules.
If users modify a rule, it will be compiled to ensure the correct functionality of the rule set.
We use a blacklist to validate new rules and prevent the execution of malicious code along with the import of unauthorized Java subpackages.