NexCommand AINexCom Knowledge Base
Field reference

Shift Request

How to use Shift Request in Attendance & Shifts: access, working steps, fields, related records and troubleshooting.

Human ResourcesUpdated 12 October 2026Configuration-aware guidance
Open Shift Request ↗Module guide

Purpose and access

Set shifts and attendance rules, configure approved worksites, and review check-ins before producing attendance records. Geolocation accuracy and the allowed radius affect check-in acceptance; the worksite radius is configurable in HR.

This page is a record page in Human Resources → Attendance & Shifts. 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: Shift Type, Employee, Status, Company, Approver, From Date.

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 Shift Request from Human Resources → Attendance & Shifts, 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. When the draft is complete and you are authorized, submit it through the available approval process. Submission can create operational or accounting effects. Use the permitted cancellation/amendment process for later corrections.

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

Linked record: Shift Type

EmployeeemployeeLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Employee

Employee Nameemployee_nameData
Optional · Read-only		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
DepartmentdepartmentLink
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: Department

StatusstatusSelect
Required		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Draft
  • Approved
  • Rejected
CompanycompanyLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Company

ApproverapproverLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: User

From Datefrom_dateDate
Required		Choose the business date required for this field. Confirm its relationship to other dates on the record.
To Dateto_dateDate
Optional		Choose the business date required for this field. Confirm its relationship to other dates on the record.
Amended Fromamended_fromLink
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: Shift Request

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?