NexCommand AINexCom Knowledge Base
Field reference

Workflow Transition Tasks

How to use Workflow Transition Tasks in Workflow & Automation: access, working steps, fields, related records and troubleshooting.

System AdminUpdated 12 October 2026Configuration-aware guidance
Open Workflow Transition Tasks ↗Module guide

Purpose and access

Configure workflow states, transitions, assignments and notifications against the correct record type. Define which role may act at each step and test the complete lifecycle in staging.

This page is a record page in System Admin → Workflow & Automation. Use the link above to open the configured destination; permissions are checked by the destination service.

ERP links open in a new tab. Sign in with your own account; record visibility, actions and approval authority follow your assigned permissions. Screens can differ by company and configuration.

Before you start

Review the current settings or existing records and prepare the information needed for the change.

Confirm the company, party, dates, units and source references that apply. Select existing links carefully and check for an existing record before creating a duplicate.

Working steps

  1. Open Workflow Transition Tasks from System Admin → Workflow & Automation, or use ERP Search.
  2. Filter the list and open the relevant record. To add a record, use Add/New when your role provides that action.
  3. Complete the editable fields described below. Required fields and validation conditions must be satisfied; read-only values are set by the system or their source records.
  4. Add the required child rows. Review each row’s identifiers, linked records and values, using the child-table field reference below.
  5. Save the record and address validation messages. Reload and verify the saved values and relationships.
  6. Use any additional workflow actions only when the record and your role provide them. Saving this record does not automatically complete a related transaction or external action.

Field reference

These fields come from the installed ERP definition. Hidden fields and password inputs are omitted. Additional conditions, custom scripts and workflow rules can make a field required or read-only in a particular context.

FieldType / behaviorHow to use it
TaskstasksTable
Optional		Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Workflow Transition Task

Child tables

Tasks — child-row fields
FieldType / behaviorHow to use it
TasktaskSelect
Required		Choose one of the configured list values. Status fields may be controlled by the record workflow.
AsynchronousasynchronousCheck
Optional		Spawns actions in a background job
EnabledenabledCheck
Optional		Enable or disable the named option only when it matches the intended record behavior.
LinklinkDynamic Link
Optional		Select the record identified by the associated document-type field. Verify both the type and the linked record.

Troubleshooting

  • Not permitted: verify the account, role and source-document permission. Do not share an administrator login.
  • Missing record or address: inspect the relevant Link or Dynamic Link fields; a matching title alone does not establish a relationship.
  • Cannot save or change status: review required fields, read-only values, document status and the configured approval transition.
  • Unexpected report or portal result: review company/date filters, source-document submission and the approved party or Employee link.
Was this useful?