Rule Uses Optional Root And Mandatory Simulation Rule Postfix
Simulation system is now under refactoring, and for new implementation, we use
the following naming convention for Rule Classes (and portal types).
- any rule should end with ' Simulation Rule' (not like current 'XXX Rule')
-
root applied rule should end with ' Root Simulation Rule' (not like current
'Delivery Rule' for root version of 'Delivering Rule')
- rule name should refer expected delivery of its child simulation movement
Good Example:
Order Root Simulation Rule (current Order Rule)
Invoice Simulation Rule (current Invoicing Rule)
Invoice Root Simulation Rule (current Invoice Rule)