43% of Part I — the exam's largest section, split across 4 modules.
this deck covers 3 of 3 sub-topics in this module
↑ Module 4 OverviewObjects and Lists are Workflows' two structured data types, each with its own function category — and both flow through cards, the basic building block of every flow.
"Sets a key of an object to a specified value, creating a new key if it doesn't exist already." Inputs: object (starting value), path (a top-level key, a dot-delimited path like customer.id or items.5 for a list index, or a List of Text of key names), and value. Output: the updated object.
If path is typed as a single dot-delimited string, dots traverse into nested objects. But if you instead set path's type to a List of Text and pass keys like "foo" and "bar" as separate list items, dots inside those strings are treated literally as part of the key name — so a list containing "foo.bar" produces a distinct "foo.bar" key rather than nesting.
"Combine the contents of two or more lists. The output is a List of every element in the preceding Lists, including potential duplicates." Inputs are List 1, List 2, and so on (each additional list adds a new input field). If {Alan, Bob, Charles} is combined with {Alicia, Brittany, Catherine}, the output is all six items in order. For a duplicate-free merge, the docs point to a separate function: Union (Combine Unique).
"Each card represents one specific step in a flow," with input fields that accept values and output fields that other cards can consume — "the ability to map the output field from one card to the input field of another card" is core to how Object/List transformations chain into the rest of a flow. Per-card options include Collapse, Run this card (action/function cards only), Duplicate, and (under the gear icon) Choose fields, Run When, and Error handling. Save with Ctrl+S, run with Ctrl+Shift+Enter.
Sources: help.okta.com — Set (ext-object-method-set), Combine All (ext-list-method-concat), Cards in flows (ext-about-cards)