How to Reorder Greenlight Approval Rule Steps in NetSuite

Move a Group step above a Supervisor step in an existing Greenlight Approvals rule, check Unsaved Changes, then Save and confirm the acknowledgement.

The quick answer

In the installed Greenlight Approvals rule builder, open an existing rule's Steps section. Choose the up arrow in the Group step's row, check the new Order values and the yellow Unsaved Changes warning, then choose Save. Confirm the Saved. acknowledgement. This procedure verifies the displayed configuration and acknowledgement; transaction routing needs its own test.

Person and operating-company names in these screenshots are fictional example data. Use your own rule, step names and approver group.

Before you start

Use an account with the Greenlight Approvals application installed and a role that can view the rule and update its steps. Exact permissions and navigation depend on your installation and role. This installation-specific example opens the builder under Admin & Settings > Approval Rules.

Start with the existing PO threshold review rule and two steps displayed after their earlier Save. Draft was observed earlier on the rule creation form; this procedure does not establish its current top-level status. Work in the existing rule's criteria and Steps view and check the displayed Save acknowledgement.

The example's purchasing criteria show Purchase Order, Example Supply US, Operations, Equipment Programs, and a minimum amount of $18,000.00. The procedure changes the step order only. It does not test those criteria against a transaction.

01. Check the existing steps

In Steps, read the Order, Name, Type and Approver columns. The original list has:

  • 10 — Manager check, with type Supervisor and a dash in Approver.
  • 20 — Purchasing review, with type Group and Group: Procurement Reviewers in Approver.
Check the existing order, step type and Group approver before changing the list.

Manager check is a step name. Supervisor is its configured type. Keep those separate when identifying the row. Both rows show conditional unchecked and delegation allowed checked; this procedure leaves those settings alone.

02. Move the Group step up

Find Purchasing review and choose its up arrow once. Use the arrow in that row so you move the intended step.

Choose the up arrow in Purchasing review's row.

Check the result: Purchasing review is now 10, above Manager check at 20. The rows turn yellow and the Unsaved Changes banner says to click Save. That warning is the next check to act on.

Verify the new order and the unsaved warning together.

03. Save the changed order

Choose Save below the Steps table. The changed Order values and the warning are still visible before this action.

Use Save under the Steps table to submit the reordered list.

Check the Saved. acknowledgement. That is the final result shown here. The underlying view still shows the yellow reordered rows and Saving approval steps... while the acknowledgement is open. This guide does not show a later clean list or a reopened rule.

Saved. is the observed acknowledgement after the explicit Save action.

The final displayed list places the Group step above the Supervisor step. Verify any enabled or active requirements for your installed version, rule matching, transaction routing and durable persistence separately before relying on an operational approval result.

Common questions

Is this the native SuiteApprovals rule screen?

This guide uses the installed Greenlight Approvals application's custom builder. Use the navigation and permissions for that application. The demonstrated controls do not establish a native SuiteApprovals procedure.

Does moving a step save the order automatically?

In the demonstrated builder, moving the step produces yellow rows and an Unsaved Changes banner. Choose the separate Save under Steps and check its acknowledgement.

Does Group above Supervisor prove the Group will approve first?

It establishes the displayed step order. The example does not submit a purchase order, test rule matching or execute an approval route. Verify those behaviors with the intended rule and transaction separately.

Does Saved. prove the rule survives a reload?

The message is the acknowledgement shown after Save. The demonstration ends there and does not reopen or reload the rule. Check that separately when durable persistence is part of your acceptance criteria.

Does Draft mean the rule cannot route transactions?

Draft is the status recorded during the example's rule configuration. This procedure does not establish its runtime meaning. Confirm the status behavior for your installed Greenlight version before making that assumption.