NexCommand AINexCom Knowledge Base
Field reference

Assignment Rule

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

System AdminUpdated 12 October 2026Configuration-aware guidance
Open Assignment Rule ↗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

Prepare the required information: Document Type, Description, Assign Condition, Assignment Days, Rule.

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 Assignment Rule 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
Document Typedocument_typeLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: DocType

Due Date Based Ondue_date_based_onSelect
Optional		Value from this field will be set as the due date in the ToDo
PrioritypriorityInt
Optional		Higher priority rule will be applied first
DisableddisabledCheck
Optional		Enable or disable the named option only when it matches the intended record behavior.
DescriptiondescriptionSmall Text
Required		Example: {{ subject }}
Assign Conditionassign_conditionCode
Required		Simple Python Expression, Example: status == 'Open' and issue_type == 'Bug'
Assign Condition JSONassign_condition_jsonCode
Optional		Autogenerated field by Helpdesk App
Unassign Conditionunassign_conditionCode
Optional		Simple Python Expression, Example: status in ("Closed", "Cancelled")
Unassign Condition JSONunassign_condition_jsonCode
Optional		Autogenerated field by Helpdesk App
Close Conditionclose_conditionCode
Optional		Simple Python Expression, Example: status == "Invalid"
Assignment Daysassignment_daysTable
Required		Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Assignment Rule Day

RuleruleSelect
Required		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Round Robin
  • Load Balancing
  • Based on Field
  • Weighted Distribution
FieldfieldSelect
Optional		Choose one of the configured list values. Status fields may be controlled by the record workflow.
UsersusersTable MultiSelect
Optional		Select the permitted linked entries; the stored rows associate those records with this document.

Linked record: Assignment Rule User

Usersweighted_usersTable
Optional		Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Assignment Rule User

Last Userlast_userLink
Optional · Read-only		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: User

Current Indexcurrent_indexInt
Optional · Read-only		Enter a whole-number value.

Child tables

Assignment Days — child-row fields
FieldType / behaviorHow to use it
DaydaySelect
Optional		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Monday
  • Tuesday
  • Wednesday
  • Thursday
  • Friday
  • Saturday
  • Sunday
Users — child-row fields
FieldType / behaviorHow to use it
UseruserLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: User

WeightweightInt
Optional		Enter a whole-number value.
Users — child-row fields
FieldType / behaviorHow to use it
UseruserLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: User

WeightweightInt
Optional		Enter a whole-number value.

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?