Processes and tracked items

A process defines identity, fields, templates and generated table/dashboard/detail/workflow/history views. Creation returns data.process and the initial draft defaultTemplateId; discover generated IDs from that response. Configure names, icon/color, field definitions and views before creating tracked items. skipProcessSetup records the intentional skip; it does not create completed work. Reorder processes with exact IDs/member versions; Orders is the reserved system process and cannot be archived as an ordinary custom process.

Templates are draft, published or archived configuration. Publish an intended structure before selecting it for new items, and set a default explicitly when appropriate. Template edits do not change existing tracked items. New items copy template structure and version into a snapshot; changing one item's title, fields or workflow does not change its source template or another item.

Items have independent completion/archive/restore lifecycle. An archived parent process makes its children read-only. Process archive preview names impacted work; archival records which active children were automatically archived. Restoration can restore those children according to its documented option, without silently reopening independently archived work. Permanent process deletion retains the required read-only snapshot/history until the separate final-deletion path is explicitly confirmed; inspect each preview because effects depend on current state.

Item duplication preserves the source and creates independent work. Item division creates one copied workflow per requested title and archives the source; it is not quantity allocation. Orders division instead creates a linked full copy without partitioning the source. Neither changes a source template. Use fresh previews and returned IDs; see division.

For fields and table/dashboard/detail configuration see fields and views. For copied stage/task actions, schedule effects, progress and history see workflow states. For explicit template propagation see maintain template.