Learn

Architecture & pattern guides

Read the idea, build it on a Grid, prove it in a challenge. Short, practical guides — illustrated with RodGrid's own nodes — on system design, design patterns, flow modeling, and how to get the most out of the app.

All articles

Data, documents & manual input

Show where data crosses a flow's boundary and who produces it: Input/Output, Manual Input, documents read or produced, and the setup step that primes what follows.

One flow, drawn twice

A survey team comes back from a field trip to Norway, and each member files an expense claim for the kroner they spent. Finance needs each claim converted to euros and a statement for the month. Here is that flow with nothing but Process boxes.

Every step a Process

It is accurate, and for a quick sketch it is fine. Now try to review it. Which number could a person have mistyped? Which step depends on something finance does not control? What comes out that somebody will read and file? What has to be settled before the rest can run? The verbs in the titles hint at some of this, but the shapes say the same thing five times: some work happens here. Below, the same titles with four of the five boxes swapped.

Same titles, four other symbols

Who produced the data

Enter expense and Read bank rates both bring data across the flow's boundary. What differs is who produces it. Manual Input is data a person types in: here, the amount and date copied from a hotel invoice. That is where a date lands in the wrong month, or 2,400 becomes 24,000. The symbol does not catch those. It tells the reader where to expect them, so that a check can follow; Decisions & branching shows how to draw one.

Its title says what is entered, never the value. Title the card "2,400 NOK" and the diagram describes one claim instead of the flow every claim goes through, and nobody can see at a glance what the step asks for. Work a person does, not data they type, is a Manual Operation, which Stored data, displays & manual steps separates from this.

Input/Output marks data crossing the boundary, in either direction. Read bank rates takes in a file of the day's exchange rates, sent from a system finance does not run. Draw it as a Process and the reader loses the signal that data crosses the boundary here, and with it the obvious question: what does this flow do when the file is late or malformed?

A statement to keep, a month to set first

Document is a human-readable document the flow reads or produces (an invoice received, a receipt or report generated). Issue statement is the produced kind: a page the employee and the accountant will read, query and file. The hotel invoice is the kind a flow reads. The bank's file is not a Document: it is structured data for a program, not a page meant for people to read. A set of several documents has its own symbol, compared with this one in Storage & ordering stencils.

Preparation is the odd one of the four, because it marks no crossing at all. It is a setup step that primes what follows. Set up month fixes which month is being closed and which currency the statement reports in, and the later steps rely on both. Run it with last month's setting and every step after it can work as designed while the statement comes out wrong. Nightly Batch Report opens the same way, preparing the reporting period before it reads a record.

TipThese shapes are documentation, not new control flow: on the Grid they still connect one-in, one-out like a Process. Use them to make what kind of step each one is obvious at a glance.

A form that sends you back

Open the Form Validation Flow challenge and mark the submitted fields with Manual Input rather than a generic Process, so the shape alone shows where a person enters data. Its palette has no Display symbol, so send the validation errors back through Input/Output. The way back to the input needs a Merge in front of the Manual Input, which takes one incoming edge. You have ten nodes for all of it.

Practice this