This page (revision-11) was last changed on 13-Jun-2014 17:49 by Albrecht Striffler

This page was created on 07-Mar-2013 06:26 by Volker Belli

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
11 13-Jun-2014 17:49 2 KB Albrecht Striffler to previous
10 13-Jun-2014 17:45 2 KB Albrecht Striffler to previous | to last
9 07-Mar-2013 19:58 2 KB Volker Belli to previous | to last
8 07-Mar-2013 17:05 2 KB Volker Belli to previous | to last
7 07-Mar-2013 16:16 2 KB Volker Belli to previous | to last
6 07-Mar-2013 16:10 2 KB Volker Belli to previous | to last
5 07-Mar-2013 06:46 2 KB Volker Belli to previous | to last
4 07-Mar-2013 06:31 1 KB Volker Belli to previous | to last
3 07-Mar-2013 06:30 1 KB Volker Belli to previous | to last
2 07-Mar-2013 06:29 1 KB Volker Belli to previous | to last
1 07-Mar-2013 06:26 1 KB Volker Belli to last

Page References

Incoming links Outgoing links
Doc Conditions
Doc Conditions

Version management

Difference between version and

At line 2 changed one line
At this page you can find the documentation for conditions. Conditions are an essential part of several markups, e.g. [rules | Doc Rules], [covering lists | Doc SetCoveringKnowledge], and checks in [test cases | Doc TestCaseTable]. Conditions are used to define a logical expression on some findings and/or outcomes of a d3web diagnostic session, to tell d3web how to action under specific circumstances.
At this page you can find the documentation for conditions. Conditions are an essential part of several markups, e.g. [rules | Doc Rules], [covering lists | Doc CoveringList], and checks in [test cases | Doc TestCaseTable]. Conditions are used to define a logical expression on some findings and/or outcomes of a d3web diagnostic session, to tell d3web how to action under specific circumstances.
This page (revision-11) was last changed on 13-Jun-2014 17:49 by Albrecht Striffler Top