This Is A Custom Widget

This Sliding Bar can be switched on or off in theme options, and can take any widget you throw at it or even fill it with your custom HTML Code. Its perfect for grabbing the attention of your viewers. Choose between 1, 2, 3 or 4 columns, set the background color, widget divider color, activate transparency, a top border or fully disable it on desktop and mobile.

This Is A Custom Widget

This Sliding Bar can be switched on or off in theme options, and can take any widget you throw at it or even fill it with your custom HTML Code. Its perfect for grabbing the attention of your viewers. Choose between 1, 2, 3 or 4 columns, set the background color, widget divider color, activate transparency, a top border or fully disable it on desktop and mobile.
Loading...
Home 2016-12-30T14:23:52-08:00
Learn more

Stop wasting time on process mapping and decision requirements!

Learn standards-based business modeling the right way, from the start
Learn more

Commentary

DMN: What’s a Hit Policy?

Newcomers to the Decision Model and Notation (DMN) standard may be put off by the notion of a decision table’s “hit policy.”  What the heck is that?  It sounds technical.  Add to that the idea that the modeler is supposed to select the “best” one.  Too complicated!

Well, it’s actually not.  Here is what’s going on.

Each row in a decision table is a rule.  The columns represent inputs and, at the end, one (or occasionally more than one) output.  Each input cell in a rule represents a true/false condition for the input: Does it match a particular value, fall into a specified range, etc.?  (A hyphen in the cell means the input is irrelevant in this rule; the cell value is true by default.)  If all input cells for the rule evaluate to true, the rule is said to match, and the output cell value is selected as the decision table […]

Professionalize your business modeling

Get your whole team on the same page with the Method and Style approach

A few of our training clients…