Release Notes

Version 1.2.0
19 November 2026

NEW FEATURES:
- Sign-in options are set per tenant on the new Sign-in tab of the admin panel's tenant page: Microsoft, Okta and NetSuite sign-in each turn on once their values are complete, unless switched off there, and email and password sign-in stays on for employees unless switched off, which also stops their one-time codes
- The login page offers only the sign-in options turned on for its tenant, and says so when none are; vendor logins offer email and password with a one-time code only
- The admin panel's tenant page is now in Connection, Sign-in, Customization and Features tabs; the Sign-in tab shows a Verified badge for each complete provider and the callback URL to copy into the identity provider
- Saving a tenant clears its cached data, so the portal may be slower for up to 10 minutes while the cache refills
- New Features tab on the tenant page in the admin panel and in Portal Configs, switching portal modules and pages on or off per tenant: PunchOut Purchasing, Requested Purchase Orders, Other Links, the Mine / My Department / All filter, Bulk Approvals, and the Item Receipts and Vendor Bills tabs on a purchase order. A module switched off is hidden and refused by the server. Every switch is on by default, so each tenant keeps today's portal
- New Only Own Orders setting on the Features tab: each employee sees only the orders they created or are the employee on, in the purchase order, item receipt and vendor bill lists and when opening one by link, while approvers still open the orders they approve. Off by default, so every list shows as today
- New Session Length (hours) setting on the Features tab: how long an employee or vendor sign-in lasts, from 1 to 24 hours. Blank by default, which keeps the portal default, so sign-outs are unchanged
- New Approval Submit Field setting on the Features tab: on SquareWorks accounts, the NetSuite field a new purchase order writes to submit itself for approval. Blank by default, which writes nothing, so purchase orders are created as before; an account whose portal purchase orders were submitted to SquareWorks automatically needs it set
- Purchase orders load and save the custom header and line fields listed on the tenant's current purchase order form version, on create and edit. A version without custom fields works as before, and a listed field the account does not have does not stop the page or the save
- A form version can fill a dropdown from a NetSuite custom list, leaving inactive values out; a version without one is drawn as before
- The item picker lists only active, purchasable items with Include Item in Procurement Portal checked in NetSuite. An account with none checked, or without the field, shows no items, so check the items the portal should offer. Saved lines keep their item, and Copy clears an item no longer offered. The field ships with the PunchOut SuiteApp

IMPROVEMENTS:
- Passwords, one-time codes, password hashes, sign-in provider secrets and users' tokens are kept out of the server logs; sign-in debug logging is off unless switched on to diagnose sign-in
- A sign-in session works only on its own tenant's portal address; on another tenant's address it is refused and signed out
- Bulk approvals and vendor form accepts are kept per tenant, so one tenant's job can never be read or changed from another
- Changes to a tenant from Portal Configs are recorded in the portal's audit log
- The portal's NetSuite objects, its records, scripts and the vendor form review page, now ship in the PunchOut SuiteApp
- Node dependency updates clear the critical and high security findings, including in the sign-in library and the email templates; sign-in and emails work as before

BUG FIXES:
- Punchout from the portal works again: opening a supplier no longer fails with SERVER_ERROR, and a punchout or cart return failure message now reaches the buyer
- Portal searches and pages no longer fail on accounts set up without some NetSuite features, such as SuiteTax or single-currency accounts and accounts without classes, departments, locations, Expense Reports or Advanced Bin / Numbered Inventory Management
- The portal and the vendor form review page show an error message and a way forward, such as Try again, instead of a blank page or an endless spinner when loading fails
- Saving a transaction checks only the required header fields and names the one that is missing, instead of stopping with no message
- A form version that sets a page function as plain text is refused with the administrator message instead of breaking the page
- Lines added by hand on a new purchase order get Punchout Rate 0 again when the form leaves the field out
- On SquareWorks accounts the Approval History tab no longer shows, empty, on a new purchase order, and the approval's background action status now reads
- The portal's background cache refresh runs as a real portal employee, so it no longer logs failed queries in the account's script log every 10 minutes, and approval details are now cached
- Recent Approvals now loads for employees whose name contains an apostrophe
- Accepting a vendor form request runs in the background: the review page shows the vendor records being saved and waits for the result, so a long accept no longer ends in Failed to fetch. A failed accept shows its mapping error and leaves the request in Pending Review to accept again
- An accepted request cannot be accepted a second time from another tab, and other review actions wait while an accept runs
- The Vendor Form Requests list shows each request once, naming its last reviewer
- Vendor form builder: New Version and Copy open the new draft, and the editor has one header button, as in the return cart form builder: Save Draft, then Publish, then Copy Form
- Vendor form builder: a publish, copy or other version change the browser stopped waiting on is confirmed from the versions list, instead of showing Failed to fetch over a change that went through
- Vendor form builder: the Pre-set a value picker on a dropdown lists the choices of a NetSuite query or picklist source
- Vendor form builder: a custom dropdown list of whole numbers, such as internal ids, is saved as numbers, so accepting a form no longer fails with INVALID_KEY_OR_REF; existing versions pick this up when next saved
- The vendor form review page and form builder changes reach an account with the PunchOut update that carries the rebuilt page


Version 1.1.0
30 October 2026

NEW FEATURES:
- New NetSuite records hold the portal's purchase order, item receipt and vendor bill forms: NGPP Transaction Form Type (one locked type per transaction kind) and NGPP Transaction Form Version (the form as TOML, drafted, published and made current like vendor form versions)
- Deploying the portal's SDF project creates the three types and publishes a version 1 of each, matching the portal's current forms
- Types cannot be added, deleted, inactivated or re-keyed; published versions are read-only; the current version cannot be deleted; version numbers are never reused
- The portal server reads each tenant's current forms every 10 minutes and checks them; a form that cannot be used shows an error naming the reason, never a different form
- Transaction pages draw only from the NetSuite forms; when a form cannot be used, the page shows an error asking the user to contact their NetSuite administrator
- The portal's previous code-defined transaction form is retired
- Publishing a form version or making it current runs as the person who clicks the button, so it needs the same record permissions as editing the version; seeding the default forms by hand is limited to the Administrator role



Was this article helpful?