Skip to content

Commit 9f8e93c

Browse files
eandzabeandzab
authored andcommitted
Added documentation about Rule Test page
1 parent a9effe4 commit 9f8e93c

File tree

2 files changed

+8
-3
lines changed

2 files changed

+8
-3
lines changed
Loading

src/main/resources/templates/jmesPathRulesSetUp.html

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,14 @@
1414
<div align="center">
1515
<label>JMESPath Rules setup</label>
1616
</div>
17+
<h3>Rule testing mechanism via "Test Rules" GUI inteface</h3>
18+
<p>Graphical User interface for rule tesing consists from two panes. Left pane is intended to upload the rule. To do this one will need to chose
19+
the rule type from dropdown menu, then insert the rule content and upload the rule. Right pane is intended for uploading the Eiffel events.
20+
After uploading the events one may check the result of applying rules by pressing "Find Aggregated Object" button specifying the UUID of
21+
this object.
22+
</p>
23+
<picture><img src="assets/images/GUI_frontend_example.jpg" alt="Test Rules Example" height="500"></img></picture>
24+
1725
<h3>Introduction</h3>
1826
<p>JMESPath is a query language for JSON. You can extract and transform elements from a JSON document.
1927
The result of applying a JMESPath expression against a JSON document will always result in valid JSON,
@@ -218,7 +226,6 @@ <h4>Creating new aggregated object from Eiifel event</h4>
218226
}</pre>
219227

220228

221-
222229
<h4>Inserting a JSON array to aggregated object</h4>
223230
<p>Lets consider that on receiving of EiffelConfidenceLevelModifiedEvent message, confidence levels array should be inserted to the aggregated
224231
object. Each time such eiffel message comes it should form a new element, and be inserted into aggregated object. Rule example is bellow</p>
@@ -499,7 +506,6 @@ <h4>Updating array of JSON objects where the some field is pointing to Eiffel me
499506
</details>
500507

501508

502-
503509
<h4>Upstream events</h4>
504510
<p>Under upstream events to some specified event in Eiffel we mean those event that were processed/issued before or were the cause to
505511
the specified event, such dependency works via
@@ -520,7 +526,6 @@ <h4>Downstream events</h4>
520526
</p>
521527

522528

523-
524529
<p>Rule examples</p>
525530
<pre>
526531
{

0 commit comments

Comments
 (0)