43% of Part I — the exam's largest section, split across 4 modules.
this deck covers 2 of 3 sub-topics in this module
↑ Module 4 OverviewTables are Okta Workflows' built-in persistence layer — accessed via the Tables tab at the top of any folder view, used "to store data across flows."
Click + New Table, give it a name/description, then + New Column for each field. Column types: String, Number, Date, Boolean, and Counter. A Counter field is special — it's built for add/subtract updates where "multiple flows can make updates to the same record at the same time without risk for conflicts or loss of data."
Straight from the docs: "A maximum of 100 tables are available in an org." This is a hard org-wide ceiling, not per-folder — plan your table design accordingly.
Resize columns by dragging the header border, sort by clicking a header (again to reverse), drag-reorder headers, and use Columns to show/hide fields or Filter to view matching records only. Import reads a CSV into the table; Export writes one out. Edit inline by clicking a cell; the red trash-can icon deletes a row. Fields marked (Auto) — like row ID or creation date — are system-generated and can't be edited. All changes save immediately.
Add function cards from the Tables category (via Add Function) to create, read, update, and delete records. One example is Delete Row: choose the table (or supply a Table ID at runtime for flows that operate on different tables), then supply the Row ID to delete (found via Search Rows). It has no output fields — it's a pure side-effect card.
Tables are also shareable: duplicate or delete a table via the hover controls in its folder view, and place a table in a shared tab if other users in your org need access to the same data store.
Sources: help.okta.com — Create and edit a table (ext-create-table), Delete Row (ext-stash-method-deleterow)
Next: Objects & Lists →