Simple Annotation Example

This shows how to annotate images without custom JavaScript - just use a numbered diagram and list below it.

Decision Table Example

Below is a DMN decision table. The numbers correspond to the descriptions below:

Understanding the Decision Table

1. Hit Policy (U) - Unique hit policy means only one rule can match at a time
2. Rule Numbers - Each row is numbered (1-5) for easy reference
3. Decision Input - The Credit Score.FICO column checks the FICO score value
4. Decision Output - The Credit Score Rating column sets the output rating
5. Annotations - Optional notes that don't affect execution
6. FEEL Input Expressions - Range expressions like [650..700) use FEEL syntax
7. FEEL Output Values - String outputs in quotes like "Good" or "Excellent"

Key Concepts

Input Column (Credit Score.FICO)

The dot notation Credit Score.FICO extracts the FICO property from the Credit Score input data. Each rule below uses range expressions to check if the score falls within specific bounds.

Range Expressions

• [650..700) - Inclusive of 650, exclusive of 700
• [700..750] - Inclusive of both 650 and 750
• Use brackets [] for inclusive, parentheses () for exclusive

Output Column (Credit Score Rating)

When a rule matches, the corresponding output value is returned. For string outputs, use quotes: "Poor", "Fair", "Good", "Excellent".

---

Alternative: Use Figure with Caption

DMN Decision Table showing credit score rating logic. Rules evaluate FICO scores and assign ratings from "Poor" to "Excellent"

Then describe the parts in the text:

The decision table has several key components:

• Hit Policy (top-left "U"): Ensures only one rule matches
• Input column: Checks Credit Score.FICO value
• Output column: Sets Credit Score Rating based on ranges
• Rules 1-5: Define the rating thresholds

This approach:

✅ No JavaScript required ✅ No custom CSS needed ✅ Works on all devices ✅ Accessible to screen readers ✅ No maintenance burden ✅ Never overlaps sidebar

---

Option 3: Use Material Admonitions for Callouts

Instead of tooltips, use Material's built-in admonitions:

Understanding the Hit Policy

The "U" (Unique) hit policy means only one rule can match for any given input. This ensures predictable behavior.

FEEL Range Expressions

Range expressions like [650..700) use FEEL syntax:

• [ = inclusive (includes the number)
• ( = exclusive (excludes the number)
• .. = range operator

Output Values

String outputs must be quoted: "Poor", "Fair", "Good", "Excellent". Numbers and booleans don't need quotes: 42, true.

---

Recommendation

For your docs, I recommend Option 1 - just add numbers to your screenshot images and explain them in a list below. This is:

1. Simple - No custom code
2. Reliable - Works everywhere
3. Maintainable - Easy to update
4. Accessible - Screen readers can read the list
5. Fast - No JavaScript overhead

Want me to create a numbered version of your decision table image and convert the page to this format?

Was this page helpful?