NexCommand AINexCom Knowledge Base
Field reference

NexCom GRC Sync Event

How to use NexCom GRC Sync Event in Governance, Risk & Compliance: access, working steps, fields, related records and troubleshooting.

Purpose and access

Maintain risks, controls, owners and evidence relationships within the ERP entry point. Link quality, HR, training and document evidence as appropriate. A recorded control or uploaded document does not by itself prove compliance.

This page is a internal/admin record in GRC & Quality → Governance, Risk & Compliance. 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 NexCom GRC Sync Event from GRC & Quality → Governance, Risk & Compliance, 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
Evidence referenceevidence_linkLink
Required · Read-only
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: NexCom GRC Evidence Link

Idempotency keyevent_keyData
Optional · Read-only
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Snapshot SHA256content_hashData
Optional · Read-only
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
StatestateSelect
Optional · Read-only
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Pending
  • Synchronized
  • Failed
  • Cancelled
AttemptsattemptsInt
Optional · Read-only
Enter a whole-number value.
Native evidence receiptnative_evidence_idData
Optional · Read-only
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Last errorlast_errorSmall Text
Optional · Read-only
Provide concise contextual information relevant to the record. Avoid unrelated personal or confidential data.
Approved reference snapshotpayloadCode
Optional · Read-only
Administrator/integration field. Use a validated configuration or supported script and test its impact before deployment.

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.