Order Amount Rules

With High Demand defined, you continue to work on the Order Amount rules with Mark. Open the definition in Camunda Modeler from the DRD overview. You can see that Mark and Loes have already added an input for the result of the High Demand decision. At the moment, an item being in high demand is irrelevant, because all of the rules have a dash in the input entry.

"We know we need to change rule 2 because it’s about T1 items," Mark says.

"At what level will you not order, even with high demand?"

"We think that 150 is fine."

Change the rule to reflect the new level above which there will be no order for T1 items.

"What happens between 100 and 150?" Mark asks, pointing at the two rules that cover the T1 storage tier cases.

"You need an extra rule with the range from 100 to 150," Loes completes, as she walks through the open door. "I was just thinking about it and now I get it."

"Clever girl!" Mark exclaims.

"Great movie reference," you say with a smile. "And you’re right, Loes, we do need an extra one. Two, actually, both covering the range from 100 to 150, but one is when high demand is true, the other when it’s false. You can enter a range between brackets. Let me show you."

The range you add in the new rule runs from 100 (inclusive) up to 150 (exclusive). The expression in FEEL for that is: [100..150).

Add the new rules to the decision table. The order amount for high demand items is the same.

Save the model once more and deploy it to the process engine. Now you can test the final result.