Designing a Marketing PMS: Activity Model, Rule Engine, Conflict Handling, and Allocation Mechanisms
The article explains the core responsibilities and three‑layer architecture of a marketing PMS, details the activity‑template model, walks through the rule‑engine execution flow with container‑component and needNum logic, compares self‑built and Drools solutions, and describes mutual‑exclusion, stacking, allocation strategies, and the three‑stage cal/use/rollback workflow with caching and consistency safeguards.
