DMN in Action with OpenRules: A Practical Guide for Development of Business Rules and Decision Management Applications using Decision Model and Notation ... and OpenRules (Business Decision Modeling) by Feldman Jacob

Author:Feldman, Jacob [Feldman, Jacob]
Language: eng
Format: epub
Published: 2017-02-14T16:00:00+00:00

As you can see, this decision table has a new type defined by the keyword “DecisionTableAssign”. This kind of table is used when you want to make multiple assignments using DMN FEEL formulas or OpenRules snippets. However, in our case, the standard decision table in Fig. 4-8 is a better choice, because if later on we decide to add conditions dealing with liver function, immune state, etc., a regular decision table will work much better than simple assignments.

READER. Now I can add a decision table “DefineDosing” by copying/pasting the table “DefineMedication”. We already have a condition for “Patient Age”. Wait a minute! How could I tell that a Patient Age is between 15 and 60? Should I add another column and use two different operators for “less” and “more”?

AUTHOR. You certainly could do that, but it would be more compact just to use the operator “Within” with a value cell specified as the interval “15..60”. By default, the bounds 15 and 60 are included but you always can define your interval explicitly, for example “[15..60]” as required by DMN.

READER. No problems. Now I will replace condition “Patient Allergies” with “Patient’s Creatinine Level” (as you called it in the formula above). Then I will add another condition for “Patient Creatinine Clearance” and replace the conclusion “Recommended Medication” with “Recommended Dose”. My new decision table “DefineDosing” is presented in Fig. 4-10.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.