General Release Information

Release 1.12.8 (SuiteApp version 1.12.801) was released on September 12, 2025, and includes several bug fixes detailed below. Your Production account will be updated automatically, while you will need to manually update your Sandbox account at your convenience.

Bug Fixes

FFA-1728: Special Order / Drop Ship Purchase Order Not Undergoing Approval

Previously, a behavior was observed where Purchase Orders automatically created from Sales Orders containing Special Order or Drop Ship items were not undergoing approval correctly. This issue stemmed from the Sales Order's approval state being incorrectly copied to the newly created Purchase Order. This resulted in two scenarios: either the Purchase Orders would not enter the approval workflow at all or they would be created in an automatically approved state. This issue has now been fully resolved, and Purchase Orders created from Sales Orders with Special Order/Drop Ship items will now correctly enter the approval routing as expected.

FFA-1763: Multiple Approval Matrix Records Created on Save

When using the "Save as Draft" action for an Approval Matrix, a single save was sometimes incorrectly creating multiple records. This issue has been resolved. The system will now correctly create only one Approval Matrix record per "Save as Draft" action, ensuring data integrity and a seamless user experience.

FFA-1764: PO-Linked Vendor Bills Not Auto-Approved and Instead Requiring Approval

Previously, Vendor Bills linked to a Purchase Order and configured to be automatically approved would still require approval by following an incorrectly assigned matrix. This issue has been resolved. The system will now correctly apply the "Automatically Approve" setting resulting in auto-approved PO-linked Vendor Bills, ensuring consistent and predictable behavior.

FFA-1774: Redirecting Approval Based on Net Amount Restarts Workflow

Previously, when redirecting an approval, an unnecessary restart of the approval workflow would be triggered. The given reason was due to the transaction amount having been changed, even though no changes were made to the transaction and amount at all. This issue has been resolved. Now, when an approval is redirected, the workflow will only restart if actual transaction data that affects the workflow's criteria is manually edited.

FFA-1786: Vendor Bills from Integration Not Created Due Approval Status Error

Previously, Vendor Bills created by integrations were failing to import into NetSuite due to an error with the Approval Status field as our script was preventing the integration from setting the field's value, which resulted in the import failing. This issue has been resolved. The script has been updated to allow integrations to correctly set the Approval Status field, ensuring that transactions are imported and approved as expected.

FFA-1789: Approval Delegate Reverts Back to Original Next Approver

Previously, when an approval delegate was set, a scheduled script would incorrectly revert the "Next Approver" field back to the original approver. This behavior prevented the designated delegate from being able to approve transactions. This issue has been resolved. The script has been updated to correctly assign the delegate as the "Next Approver," ensuring that they can successfully approve transactions on behalf of the original approver.