NexCommand AINexCom Knowledge Base
Field reference

Comment

How to use Comment in Platform Settings: access, working steps, fields, related records and troubleshooting.

System AdminUpdated 12 October 2026Configuration-aware guidance
Open Comment ↗Module guide

Purpose and access

Review platform defaults and dependencies within the administrator’s authority. Record the reason and tested impact of changes. Authentication, session settings and security-sensitive configuration need a controlled change process.

This page is a internal/admin record in System Admin → Platform Settings. 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: Comment Type.

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 Comment from System Admin → Platform Settings, 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. Save the record and address validation messages. Reload and verify the saved values and relationships.
  5. 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
Comment Typecomment_typeSelect
Required		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Comment
  • Like
  • Info
  • Label
  • Workflow
  • Created
  • Submitted
  • Cancelled
  • Updated
  • Deleted
  • Assigned
  • Assignment Completed
  • Attachment
  • Attachment Removed
  • Shared
  • Unshared
  • Bot
  • Relinked
  • Edit
Comment Emailcomment_emailData
Optional		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
SubjectsubjectText
Optional		Provide the required record description or content. Keep operational instructions clear and applicable.
Comment Bycomment_byData
Optional		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
PublishedpublishedCheck
Optional		Enable or disable the named option only when it matches the intended record behavior.
SeenseenCheck
Optional		Enable or disable the named option only when it matches the intended record behavior.
Reference Document Typereference_doctypeLink
Optional		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: DocType

Reference Namereference_nameDynamic Link
Optional		Select the record identified by the associated document-type field. Verify both the type and the linked record.
Reference Ownerreference_ownerData
Optional · Read-only		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
ContentcontentHTML Editor
Optional		Complete the value according to the field label and the record’s validation rules.

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?