You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,6 +117,8 @@ Supported. This is the native format for `dmnmd`.
117
117
118
118
ASCII has its limitations. In graphical decision tables, output columns are separated from input columns by a double bar; most GUI implementations use colour and other formatting to distinguish input, output, and annotation columns. In `dmnmd` syntax, output columns are optionally labeled with an `(out)`; annotation columns are prefixed with a `#`. By default, if the columns are unlabeled, the rightmost column will be taken to be the output, and columns to the left will be taken to be inputs. (Leaving out annotation columns.)
119
119
120
+
You can also prefix output columns with a `>` character.
121
+
120
122
Columns are optionally typed using a colon. You will see `Column Name : String`, `Column Name : Number`, and `Column Name : Boolean`. If you omit the type definition, `dmnmd` will attempt to infer the type.
121
123
122
124
In some decision tables, the input and outputs are enumerated in a sort of sub-header row. The order matters.
@@ -131,7 +133,7 @@ For hit policy "O", the order of results in the output is determined by the orde
131
133
132
134
The column enums are giving in a subhead row between the top row and body data row "1".
133
135
134
-
| O | Age | Risk Category | Debt Review :Boolean| Routing (out)|Review level (out)| Reason (out) |
136
+
| O | Age | Risk Category | Debt Review :Boolean|> Routing | > Review level | Reason (out) |
0 commit comments