Parameter editors

Every activity parameter is edited in the Properties panel (to the right of the canvas). You don’t pick the editor: the Designer shows the most suitable one based on the parameter’s type and use. Most are a text/expression field, but some open visual editors so you don’t have to write structures by hand.

Collection editors

When a parameter accepts a literal list, dictionary or table — a value you type yourself, not the output of another activity — the panel shows an Edit button that opens a visual editor:

Type	Icon	Editor
List	[]	Add, remove and reorder items, one per row.
Dictionary	{}	Key → value rows.
DataTable	⊞	Define columns and rows, like a spreadsheet.

In all three, each cell accepts a fixed value (text, number) or an expression (starting with =), just like any parameter.

Expression mode

All of them also have an Expression mode: instead of designing the value cell by cell, you paste a single expression that returns the whole collection — for example, another activity’s output (= customers). Useful when the value is dynamic.

Row values: by column or by position

The Add Data Row activity uses a special editor for its Values parameter, with a toggle between two modes:

• By column — a dictionary { column: value }. Order-independent and validates the column name. Recommended.
• By position — a list of values in column order. Faster if you know the order; you must provide exactly one value per column.

Switching between modes does not lose data: what you had in each mode is kept.

Why position mode doesn’t show column names

The editor doesn’t know the table’s columns at design time, because the table is an expression that is only resolved at run time. That’s why position mode is an ordered list of values and you must know the order.

Conditions editor

Activities that filter or find rows — Filter DataTable and Find Data Row — use the conditions editor: you build one or more conditions visually, without writing the expression by hand.

Each condition is column · operator · value, combined with AND (all) or OR (any) logic. Available operators: equals, not-equals, contains, starts/ends with, greater/less than (or equal), is empty / is not empty.

Each condition’s value also accepts an expression (= …), so you can compare against a variable.

Other editors in the panel

Depending on the parameter, the panel may also show:

• Credential selector — for sensitive parameters, you pick a secret stored in Zoan Cloud without typing it into the playbook.
• Variable name — for parameters that name an output variable (not its value), instead of an expression.
• Hidden parameters — some internal parameters the activity manages on its own are not shown.

Remember: the editor is determined by each activity based on the parameter’s data type; it’s not a manual choice.

Next steps

• Data types — lists, dictionaries, DataTable and DataRow.
• Expressions — Expression mode and = … values.
• Add Data Row · Find Data Row — activities that use these editors.