NexCommand AINexCom Knowledge Base
Field reference

NexCom Application Event

How to use NexCom Application Event in Recruitment: access, working steps, fields, related records and troubleshooting.

Human ResourcesUpdated 12 October 2026Configuration-aware guidance
Open NexCom Application Event ↗Module guide

Purpose and access

Publish job openings with the relevant requirements, collect structured applicant profiles and review applications in the ERP. Advisory qualification comparisons support human review; they do not automatically make hiring decisions.

This page is a record page in Human Resources → Recruitment. 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: Application, Deduplication key.

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 NexCom Application Event from Human Resources → Recruitment, 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
ApplicationapplicationLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Job Applicant

Deduplication keyevent_keyData
Required		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Released atreleased_atDatetime
Optional		Record the date and time in the configured system/user time zone.
Public statuspublic_statusData
Optional		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Public messagepublic_messageText
Optional		Provide the required record description or content. Keep operational instructions clear and applicable.
Public detailspublic_dataCode
Optional		Administrator/integration field. Use a validated configuration or supported script and test its impact before deployment.
Email statenotification_stateData
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.
Was this useful?