NexCommand AINexCom Knowledge Base
Field reference

Contract Template

How to use Contract Template in Contracts: access, working steps, fields, related records and troubleshooting.

Purpose and access

Record the contracting parties, validity dates and agreed terms. Associate the contract with the relevant commercial activity where supported. Uploading a signed document does not automatically change the status of an ERP order.

This page is a record page in Sales & Marketing → Contracts. 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 Contract Template from Sales & Marketing → Contracts, 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
TitletitleData
Optional
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Contract Terms and Conditionscontract_termsText Editor
Optional
Maintain formatted content for the record; review any public-facing output before publishing.
Requires Fulfilmentrequires_fulfilmentCheck
Optional
Enable or disable the named option only when it matches the intended record behavior.
Fulfilment Terms and Conditionsfulfilment_termsTable
Optional
Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Contract Template Fulfilment Terms

Child tables

Fulfilment Terms and Conditions — child-row fields
FieldType / behaviorHow to use it
RequirementrequirementData
Optional
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.

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.