Design and Implementation of a Drools-Based Rule Engine for Sales Performance Management

Background The company’s sales performance accounting previously required manual data collection, calculation, and offline verification across multiple business systems, leading to low communication efficiency, poor security supervision, inaccurate calculations, incomplete approval processes, and high operational costs. To address these issues, a standardized, secure, and convenient rule‑engine management system was planned to provide a unified rule control center, simplify frequent rule changes, and improve data safety, accuracy, and compliance.

What Is a Rule Engine A rule engine is a component derived from inference engines that separates business decision logic from application code. It accepts data input, interprets business rules, and makes decisions based on those rules. Popular open‑source options include Drools, while commercial alternatives include Visual Rules and ILog.

Why Use a Rule Engine Traditional development embeds business logic in Java or SQL, making maintenance costly and preventing online debugging. A rule engine enables online rule editing, version tracking, hot updates, and reduces the need for code changes, thereby improving flexibility and reducing risk.

Rule Definition A Drools rule must start with a package declaration, followed by rule "RuleName" , optional attributes, when (LHS), then (RHS), and end . Example structure:

package com.example.rules rule "SampleRule" when eval(true) then System.out.println("SampleRule"); end

Performance Calculation Implementation The workflow extracts data from media, CRM, and HR systems on a scheduled basis, filters contracts belonging to the dealer‑marketing department, and inserts qualifying records into a base performance table (A1). Subsequent steps determine contract version, signing nature, zero‑day renewal status, and finally classify performance types such as "Upgrade Version Renewal" or "Level‑off Renewal".

Practical Integration (SpringBoot + Drools)

Environment: IDEA, JDK 1.8, SpringBoot 2.0, Drools 7.0.0.Final, MyBatis, Ant Design Pro, Maven 3.

1. Add Drools dependencies to pom.xml :

<dependency>
    <groupId>org.kie</groupId>
    <artifactId>kie-spring</artifactId>
    <version>7.0.0.Final</version>
</dependency>

<dependency>
    <groupId>org.drools</groupId>
    <artifactId>drools-compiler</artifactId>
    <version>7.0.0.Final</version>
</dependency>

2. Create a Drools auto‑configuration class to obtain KieServices , build a KieContainer , and expose a KieSession bean:

@Configuration
public class DroolsAutoConfiguration {
    @Bean
    @ConditionalOnMissingBean(KieContainer.class)
    public KieContainer kieContainer() throws IOException {
        KieUtils.setKieServices(getKieServices());
        KieUtils.setKieRepository(getKieServices().getRepository());
        new ReloadRules().reloadAll();
        return KieUtils.getKieContainer();
    }
    // other beans omitted for brevity
}

3. Implement ReloadRules to load all DRL files dynamically and verify them:

public class ReloadRules {
    public static void reloadAll() {
        KieServices kieServices = KieUtils.getKieServices();
        KieRepository kieRepository = kieServices.getRepository();
        kieRepository.addKieModule(new KieModule() {
            @Override
            public ReleaseId getReleaseId() {
                return kieRepository.getDefaultReleaseId();
            }
        });
        KieHelper kieHelper = KieUtils.getKieHelper();
        for (Map.Entry
entry : getRules().entrySet()) {
            kieHelper.addContent(entry.getValue(), "rules/" + entry.getKey() + ".drl");
        }
        Results results = kieHelper.verify();
        if (results.hasMessages(Message.Level.ERROR)) {
            System.out.println("Rule update error: " + results.getMessages());
            throw new IllegalStateException("Rule update error");
        }
        KieSession kSession = kieHelper.build().newKieSession();
        KieUtils.setKieSession(kSession);
        KieContainer kieContainer = kieServices.newKieContainer(kieRepository.getDefaultReleaseId());
        KieUtils.setKieContainer(kieContainer);
    }
}

4. Provide utility methods in KieUtils for obtaining sessions, loading specific agenda groups, and disposing sessions (code omitted for brevity).

5. Execute rules:

KieSession kieSession = KieUtils.getKieSession("RuleGroupName");
kieSession.fireAllRules();
KieUtils.disposeKieSession(kieSession);

Rule Management Through the visual rule management interface, users can modify conditions (e.g., adding a contract start date filter) without touching code, enabling online validation, hot updates, version tracking, and rollback capabilities.

Conclusion The rule‑engine‑driven sales personnel management system standardizes HR‑sales sequence management, achieves end‑to‑end performance data flow, supports multi‑dimensional assessment, automates commission calculation, and provides transparent online approval processes. The project accumulated rich business and technical experience, demonstrating how rule engines can accelerate digital transformation in fast‑growing enterprises.

References

Drools Rule Engine Technical Guide, Liu Zhihui, Peking University Press.

Official Drools Documentation: https://docs.jboss.org/drools/release/7.0.0.Final/drools-docs/html_single/index.html

Drools 7.0.0.Final Tutorial: https://blog.csdn.net/wo541075754/article/category/9269332/2