The quick answer
On entry to More Approvers? in this configured custom workflow, Current Approver is set from Current Approver.Supervisor. A nonempty Current Approver returns the record to State 1: Waiting for Approval. In the demonstrated final turn, the field becomes empty, the configured empty-field condition evaluates True, and the workflow enters State 2: Approved. For this test record, verify the saved Approved status, the terminal history visit and the final execution log together.
Before you start
Use an authorized synthetic Performance Review already waiting for its final approver. The custom workflow, supervisor hierarchy and earlier approval turns are prerequisites. This guide performs one final approval and reads earlier visits as saved history.
The example uses Q4 workflow test, subordinate Riley Chen and final approver Alex Morgan. Salary Change, rating B and amount 0.00 are illustrative fields on the custom test review. No employee or compensation update is performed. The record, buttons, statuses and lock behavior belong to this configured training workflow.
01. Match the pending review
Open Performance Review: Q4 workflow test. Match the subordinate and Review Date: 10/15/2026. Confirm Approval Status: Pending Approval.
In Active Workflows, locate Performance Review Multiple Approvals in State 1: Waiting for Approval. Its Options value identifies Current Approver: Alex Morgan, the signed-in test approver. A pending status alone does not identify whose turn it is.
02. Read earlier handoffs
Open Workflow History. Read the entered and exited dates alongside the state names and Current Approver values. The saved history shows earlier approver values for Casey Reed, Jordan Patel and Sam Rivera, followed by the current final visit for Alex Morgan. The newest row appears first, so read upward from the oldest visit when following the sequence.
The repeated Waiting for Approval and More Approvers? rows are separate state visits. The current Waiting visit has no exited date. These saved rows show earlier visits and approver values; this walkthrough does not perform those earlier approvals again.
03. Approve and reconcile
Return to the action bar and click Approve Review once for the authorized test. Confirm Approval Status: Approved on the same saved custom record. In this example the record shows a lock indicator and no longer presents Edit or the approval buttons.
In Workflow History, verify that State 2: Approved follows the final State 1A: More Approvers? visit. This is the workflow’s saved terminal path. Confirm it alongside the displayed Approval Status; the history and status are separate pieces of evidence for this outcome.
04. Verify the terminal condition
Open Log for the final State 1A: More Approvers? visit. Use its date to distinguish it from earlier visits to the same state. Expand SETFIELDVALUE and Transition to State 2: Approved.
The field assignment leaves Current Approver (Workflow) empty. The transition’s condition reads Workflow : Current Approver Is Empty.
In the same log’s Result column, confirm True for the condition and Executed for the transition. The following crop isolates that column; enlarge either image to match its results with the Entry rows.
Reconcile the log with State 2: Approved in history and Approval Status: Approved on the custom record. These observations establish the terminal path for this test record.
Common questions
Why did an approval return the record to Waiting for Approval?
On entry to More Approvers? in this configuration, Current Approver is set from Current Approver.Supervisor. A nonempty Current Approver value routes the record back to Waiting for Approval for another turn. Check the new visit’s Current Approver value and dates.
Does the first approval finish the whole review?
Not in this demonstrated hierarchy. Earlier visits route through additional supervisors. The final turn satisfies the empty-field transition and reaches Approved.
How do I avoid opening an earlier log for the same state?
Match the final More Approvers visit’s entered and exited dates with the newest Approved history row. Repeated state names alone do not identify the visit.
What if the record has a status but the history or log disagrees?
This example shows agreement between the saved status, final history and log. It does not establish how disagreements are handled. Retain the record and visit details and ask the workflow administrator to investigate the configured actions and transitions.
Does this test missing supervisors, hierarchy cycles or rejection and resubmission?
No. The empty Current Approver value after the final supervisor lookup does not establish what happens when the initial employee has no supervisor. Cycles, rejection, resubmission and permission failures require separate tests. These custom labels and rules do not establish universal native NetSuite approval behavior.