thinkwise-software-factory-tasks

Create the task row first (keyed by task_id), then bind it to a table via tab_task if it is a table task, then add parameters via task_parmtr. Only after all three exist can you generate the code group, assign a template, and generate the object code.

Add an explicit task_parmtr matching the table's primary key column id, then bind it with a tab_task_parmtr row so it auto-fills from the selected row. Unlike handlers, table tasks never receive the row's key automatically.

Only STORED_PROCEDURE tasks go through the control-procedure assignment flow and have a template to assign. FUNCTION, EXTERNAL_PROCEDURE, EXTERNAL_FUNCTION, EXTERNAL_PROGRAM, ITP, and DUMMY tasks have no generated template; their logic lives outside Software Factory code generation.

Both enablement gates must be on: the task-level use_layouts or use_defaults flag on the task entity, and the parameter-level layout_input/layout_type_output or default_input/default_output flags on task_parmtr. With either gate off, the template generates without error but never fires.

Not as plain table tasks, because tab_task is keyed by (tab_id, task_id) allowing only one row per task per table. To show two variants side by side, create separate table variants and select a different task variant in each via tab_variant_task_overview.

No. An unbound task remains reachable through the Indicium API even with no menu item, process flow, or start object wired up. Only role and rights configuration actually restricts who can call it; hiding it from the GUI is not security.