Talk:Data Rule (Node Type)

Randall Kinard 2026-04-21

What’s Good

• Clear, accurate introduction
  • Does a great job explaining what a Data Rule is and how it differs from extractors
  • The “finding vs fixing data” distinction is especially useful

• Strong explanation of Scope (major strength)
  • Clearly explains how rules run at:
    • Data Model level
    • Data Section level
    • Data Table row level
  • This is critical to understanding Data Rules and is handled well

• Good breakdown of Trigger / True / False logic
  • Easy to follow and logically structured
  • Explains execution flow clearly, including child rule behavior

• Helpful conceptual positioning
  • Differentiates Data Rules from:
    • Extractors
    • Batch Process logic
  • Reinforces that Data Rules operate inside the Data Model

• Practical configuration steps
  • Step-by-step setup is clear and usable
  • Includes optional elements (Trigger, False Action, Shortcut Keys) without overwhelming

• Nice inclusion of testing/troubleshooting tips
  • Covers real-world issues:
    • Rule not appearing
    • Trigger not firing
    • Errors not clearing
  • This is very useful and something we could probably do more of

• Good structure and readability so far
  • Flows logically from concept to configuration to usage
  • Easy to follow for intermediate users

What Could Be Improved

• This is obviously still an article in progress.

• Lacks a quick “what should I use this for?” summary
  • Good explanations exist, but no quick guidance
  • Suggestion:
    • Add a short section like:
    • “Use Data Rules when…”
      • You need if/then logic
      • You’re working across multiple fields
      • You need row/section-level logic

• Could use a simple example early on
  • Maybe a simple use case would help?
  • Suggestion:
    • Add a quick example near the top:
      • “If Payment Type = PO → require PO Number”

• Data Actions section could use stronger framing
  • Suggestion:
    • Flesh out a stronger explanation of what the Actions are and what they're for

• Minor redundancy and wording tightness
  • A few areas repeat similar ideas (especially around Trigger behavior)
  • Some sentences could be slightly tighter
  • Suggestion:
    • Light editing pass to streamline phrasing

• Perhaps it's coming eventually, but a tie in to validation might help?