Automate 2022.2
To prepare for an upgrade to the latest version, please review our upgrade process. If you would like to receive software update emails and release notifications, please subscribe to our mailing list.
Dashboard [452447]
Release 1.0.0
New Features:
Initial Release
Changes:
None
Bug Fixes:
None
Advanced Vendor Onboarding [448491]
Release 2.0.0
New Features:
Initial Release of Vendor Onboarding
Changes:
None
Bug Fixes:
None
OCR and Invoice Scanning [3400110]
Release 2.0.0
New Features:
Initial Release
Changes:
None
Bug Fixes:
None
Release 2.0.1
New Features:
Added setting to optionally show lines extracted from an invoice document which have an amount of $0. This can be enabled on the Advanced Bill Management settings screen.
Changes:
None
Bug Fixes:
Resolved issue preventing Vendor Bills from being created if OCR services are disabled in NetSuite (due to monthly OCR limits being reached).
Release 2.0.2
New Features:
Added support for automatic PO line matching when a PO is associated to the Vendor Bill. When enabled, lines on the invoice document will be auto-matched to open lines on the selected PO. Non-matching lines will set quantity/amount to zero.
Changes:
None
Bug Fixes:
None
Release 2.0.3
New Features:
None
Changes:
Improved inbound email logging to show the subject line from inbound emails.
Bug Fixes:
None
Release 2.0.4
New Features:
Added support for vendor-specific OCR rules. This allows the OCR results to be modified dynamically based on vendor-specific rules in your account. Rules have been added to allow lines to be removed, lines to be merged and custom data to be extracted from the OCR results.
Changes:
Updated Vendor and PO number lookup to run at Vendor Bill create time (in order auto-select the correct Vendor and PO). This is useful if the Vendor or PO didn’t exist at the time an invoice is uploaded to NetSuite.
Bug Fixes:
Fixed error when a document failed to be scanned using OCR. The solution has been updated to still allow a Vendor Bill to be created with split screen view.
Fixed error related to the number of open POs. When a Vendor had more than 4k open POs, a script error was being reported.
Release 2.0.5
New Features:
None
Changes:
The split screen viewer has been updated to stay stationary on the screen when the user scrolls down on the Vendor Bill screen.
Bug Fixes:
None
Release 2.0.6
New Features:
The PDF split screen viewer has been updated to use Adobe’s PDF browser-based viewer instead of native browser functionality. This leads to a better experience when adjusting the size of the split screen view.
Changes:
None
Bug Fixes:
None
Release 2.0.7
New Features:
Added a new OCR Rule: Text Extraction (PO Number) to override how the PO number is extracted for specific vendors.
Changes:
None
Bug Fixes:
None
Release 2.0.8
New Features:
None
Changes:
None
Bug Fixes:
Added support for accounts with expense categories not enabled.
Release 2.0.9
New Features:
Added optional feature (enabled on the ABM Settings page) to capture shipping/freight costs as an additional item or expense line on Vendor Bills.
Changes:
None
Bug Fixes:
None
Release 2.1.0
New Features:
Added support for invoice line consolidation. This can be optionally enabled on the ABM Settings page. This can also be enabled at a Vendor level by setting up OCR rules.
Changes:
None
Bug Fixes:
None
Release 2.1.1
New Features:
The invoice document uploaded is now attached to the Vendor Bill on the Communication > Files tab for any new Vendor Bills created.
Changes:
None
Bug Fixes:
None
Release 2.2.0
New Features:
On the Invoice Queue screen, an “OCR Status” column has been added to show the status of the OCR scan
You will see rows with an “In Progress” status if they were uploaded via email or you pressed the cancel button after dragging and dropping invoices into NetSuite (before the uploading dialog finishes). There is a background process that will update the status once every 15 minutes. You can always continue to create the bill before the OCR scan is complete if needed.
The limit on the number of PDFs that can be uploaded via email (attachments per email) has been increased from 10 to 20 attachments.
If there’s any issues scanning a document, it’s status will be set to “Failed”. You can still generate a Vendor Bill, but OCR data will not be used.
Changes:
None
Bug Fixes:
None
Release 2.2.1
New Features:
When Auto Fill Line is enabled on the ABM Settings screen (to code non-PO Vendor Bill lines), the location will also be auto filled based on prior Vendor Bills entered.
Changes:
None
Bug Fixes:
None
Release 2.2.2
New Features:
When creating a Vendor Bill associated to a PO, the PO lines’ current available quantity, rate and amount will be saved on the Vendor Bill’s lines in read-only fields (PO Quantity, PO Rate, PO Amount). These values can be seen while creating a Vendor Bill from a PO. By default, these new fields are not shown on custom forms. These fields will automatically be hidden on the form if a Vendor Bill is not associated to a PO.
A “Restore PO Lines” button has been added to the item and expense line tab. When creating a Vendor Bill from a PO, this button will restore the lines’ quantity, rate and amount that were open at the time the Vendor Bill was created. This button is not available if a Vendor Bill is not associated to a PO.
Changes:
None
Bug Fixes:
None
Release 2.2.3
New Features:
None
Changes:
Added additional logging to log the name and type of all attachments included in an email.
Updated PDF filtering logic for email attachments to determine PDF files based on the file extension (e.g. “.pdf”) or the sender-specified attachment data type.
Bug Fixes:
None
Release 2.2.4
New Features:
Added support for accounts without Advanced Receiving enabled.
Added support for accounts with Advanced Receiving’s Bill In Advanced of Receipt setting enabled.
Changes:
None
Bug Fixes:
None
Release 2.3.0
New Features:
Email details are now tracked (From Address, To Addresses, Cc Addresses, Reply To Address, Date, Subject and Text Body) in NetSuite for each email received. When viewing an Invoice Document or Vendor Bill, a “View Email” button will be available if the invoice was uploaded via email. Clicking on the “View Email” button will show the email details in a PDF split screen view. You can switch back to seeing the invoice in split screen view by pressing the “View Invoice” button.
Changes:
Clicking on “View Invoice” when viewing or editing a Vendor Bill no longer requires the page to be reloaded in order to see the invoice in split screen view.
Bug Fixes:
None
Release 2.4.0
New Features:
A new rules engine has been added to all version of ABM. The OCR Rules functionality found under the Settings menu has been deprecated and will be removed in a future version of ABM. Any rules setup using the legacy OCR Rules functionality should be re-created using the new rules engine functionality. New rules can be added by going to Lists > ABM > Rules or by clicking on the Create Rule button when viewing a document in the invoice queue. Using the Create Rule button on the invoice document has the added benefit of pre-populating common conditions and giving visibility into the text extracted from a PDF document – this is useful when trying to add rules.
Added a Custom PO Number Field setting on the ABM Settings page. This optional setting allows you to specify the PO field id to additionally use when looking up a PO on the Vendor Bill. This is useful if Vendors include a PO number on invoices that is stored in a custom field on your PO record.
Added the ability to see the OCR-extracted PO number and rules-engine selected subsidiary on the standard invoice queue. Both can be manually changed before creating a Bill by editing the document in the queue.
Changes:
Clicking on “View Invoice” when viewing or editing a Vendor Bill no longer requires the page to be reloaded in order to see the invoice in split screen view.
Bug Fixes:
The default position of the Purchase Order drop down (when creating Bills) has been changed to work around NetSuite form display issues seen in Sandbox accounts.
Release 2.4.1
New Features:
Added an Attach Invoice Documents to POs setting on the ABM Settings page. When enabled, the uploaded invoice document will be automatically attached to the related PO when a Vendor Bill is created. Invoice documents will still be attached to the Vendor Bill.
Added a Custom PO Name Formula setting on the ABM Settings page. Optionally enter a saved search formula (text) to override the format of PO names which appear in the "Purchase Order (Cannot Change After Save)" drop down when creating Vendor Bills.
Changes:
Logic to lookup Vendor, PO and Subsidiary has been improved.
If using POs, ABM will first attempt to find a matching PO before looking up the Vendor to assign to a document in the queue.
Improved lookups for vendors that have been replicated across subsidiaries.
Updated the layout of the standard invoice queue. The view button has been replaced with a link on the document name. Uploaded By has been renamed to Owner.
Updated the format of the uploaded invoice documents file name in the file cabinet from “<uniqueid>-<originalfilename>.pdf” to “<originalfilename>.<uniqueid>.pdf”. This improves the experience when receiving the invoice documents via email for approval.
Bug Fixes:
None
Release 2.4.2
New Features:
Added a new rule action called Set Field Value, which lets you set any field on the bill to a static value.
Changes:
Selecting no conditions on a rule will cause the rule to apply to all documents uploaded.
All whitespace detected within extracted PO numbers or invoice numbers will be removed automatically.
If a rule selects a specific vendor, but doesn’t define a subsidiary as well, the subsidiary will default on the queue and bill to the Vendor’s primary subsidiary.
This document has been updated to provide more detail about the invoice queue and rules.
Bug Fixes:
If a PO number could be extracted from the document but no PO could be found in NetSuite, the vendor selected by a rule was being ignored and defaulted to looking up the vendor by name.
Release 2.4.3
New Features:
None
Changes:
The Invoice Document record type has been updated to allow for inline editing. If the Invoice Queue’s search is setup not to group results (not default functionality), it’s possible to enable inline editing in the queue (e.g. to select a different subsidiary)
Improvements to the split screen view to condense the width of the page. This can help prevent the need to scroll from side to side on a small screen.
Bug Fixes:
File names longer than 199 characters no longer result in upload errors via email and drag and drop (due to NetSuite limits). File names will be truncated to 199 characters when stored in the file cabinet.
Release 2.4.4
New Features:
Added an Auto Fill Fields setting on the ABM Settings page. This field can be used to enter a comma separated list of body or line field ids to auto fill when creating a Bill (in addition to the standard fields auto-filled at the line level)
Added a Copy Lines From Prior Bill setting on the ABM Settings page. When enabled, all lines will be copied from the prior bill (for the selected Vendor and Subsidiary) when entering non-PO bills. The lines will not be modified based on information in the invoice document.
Changes:
Legacy OCR rules (found on the setup menu) have been disabled and will no longer be used starting in this version.
The Auto Fill Line and Show Zero Dollar Lines settings have been hidden and set to default values. Non-PO Bills will always auto-fill lines. Zero dollar lines extracted via OCR will never be shown when creating a Bill.
The native Auto Fill button has been removed when creating bills to avoid conflict with our included auto-fill functionality.
Bug Fixes:
None
Release 2.4.5
New Features:
Added Subsidiary and Vendor-level settings to the ABM Settings screen. A default Vendor Bill form can be defined for specific Subsidiaries. The ability to consolidate invoices lines or copy lines from the prior bill can be defined for specific Vendors.
Improved support for tax codes for non-PO Vendor Bills. The tax code will now automatically default on expense and item lines if an account or item is selected.
Changes:
Updated the ABM Rules screen to disable the following actions if the Transaction Vendor Is or Transaction Subsidiary Is conditions are selected: Extract PO Number from Email, Extract PO Number from Document, Extract Invoice Number from Email, Extract Invoice Number from Document
Bug Fixes:
Resolved script error creating Vendor Bills found in v2.4.4 if the extracted invoice has no amount extracted.
Release 2.4.6
New Features:
Added a Prioritize PO over Rules setting on the ABM Settings page. When enabled, subsidiary and vendor set using rules will be ignored when searching for a PO. The subsidiary and vendor defined on the PO will always take priority over rules.
Changes:
Improved tax handling for consolidated lines when freight is broken out from the consolidated line.
Improved tax handling when a Vendor Bill is associated to a PO and the PO lines have been modified based on invoice lines.
Changing the Vendor when a PO is selected on a Vendor Bill is now allowed.
When installing ABM into a new account, a folder will be automatically generated to store ABM documents uploaded and automatically referenced on the ABM Settings page.
The ABM Settings form has been reorganized and help text has been updated.
Bug Fixes:
Prevented the Custom PO Name Formula from causing duplicate POs to appear in the PO drop down when creating Vendor Bills when formula join syntax is used.
Release 2.4.7
New Features:
None
Changes:
Improved tax calculation performance when generating Vendor Bills.
Bug Fixes:
None
Release 2.4.8
New Features:
Rule conditions can specify the matching logic to use (in the past the conditions only supported regular expressions): Match All (Comma Separated), Match Any (Comma Separate), Advanced Match (RegEx). Existing rules (unless updated to define condition logic) will by default still match based on RegEx logic.
Changes:
Updated the position of NetSuite’s Drag and Drop area if using the NetSuite Drag and Drop bundle so that it doesn’t overlap with buttons on the screen.
Selecting a different vendor when entering a vendor bill will always default to the new vendor’s primary subsidiary (instead of the subsidiary that’s currently selected).
The subsidiary selected on the queue will be ignored when generating a vendor bill if the selected vendor on the queue doesn’t belong to the selected subsidiary. The vendor’s primary subsidiary will be used instead.
Rule conditions using Regular Expression matching logic have been updated to be case insensitive.
Bug Fixes:
Resolved issue preventing CAD tax codes from being selected when creating bills.
Resolved issue causing the extracted freight line to overwrite the PO line when entering a PO-related bill.
Release 2.4.9
New Features:
Added support for SuiteTax calculations.
Changes:
Improved Vendor lookup logic to include IBAN, VAT or Phone Number when searching for a Vendor to select.
Improved PO lookup logic to exclude closed POs and the ability to generate a bill against a PO with no open lines.
Improved performance of tax code lookup when items/accounts are the same across lines.
Bug Fixes:
None
Release 2.4.10
New Features:
None
Changes:
The ABM Vendor Invoice Document field types and form have been updated to allow for editing of the PO, PO Number, Invoice Number, Invoice Total and Invoice Date.
Bug Fixes:
None
Release 2.4.11
New Features:
None
Changes:
None
Bug Fixes:
Added checkbox to the ABM Settings screen to optionally disable record redirection. This setting should be checked if using Approval Workflow Automation’s auto-submission feature. This was added to work around a NetSuite defect related to record redirection.
Release 2.4.12
New Features:
Added the ability to specify multiple fields on the PO to reference when looking up a PO by PO number. The Custom PO Number Field setting (found on the ABM Settings screen) now supports multiple field ids by listing them in a comma separated list.
Changes:
Improved handling of line-level quantity, rate and amounts. Rate and amount will be backed into automatically if either rate or amount are missing (missing or $0) from the OCR extraction.
Bug Fixes:
None
Release 2.5.0
New Features:
Improved the functionality to lookup subsidiary automatically when uploading invoices. Subsidiary will now automatically be selected based on who the invoice is billed to (if an ABM Rule or PO does not take priority). This functionality will rely on prior uploaded invoices to determine the subsidiary. The reduces the need to create ABM Rules for each subsidiary.
Added a Default Subsidiary setting on the ABM Settings page. When defined, if no subsidiary can be identified when uploading an invoice, the subsidiary defined in the Default Subsidiary field will be assigned.
Changes:
None
Bug Fixes:
None
Release 2.5.1
New Features:
Added an Auto Match PO Override Items setting on the ABM Settings page. If enabled, item lines copied from the PO will not have their quantity and amount zeroed out and will be ignored by matching logic. This feature is only applicable if the Auto Match PO Lines feature is enabled.
Changes:
Added ability to enable detailed performance logging to help troubleshoot NetSuite performance issues if they occur. This feature is not enabled by default.
Bug Fixes:
None
Release 2.5.2
New Features:
None
Changes:
Performance improvement to speed up the process of opening the Vendor Bill create screen (for standalone bills with line-level consolidation enabled)
Bug Fixes:
An error was being encountered when creating a Vendor Bill if a memorized Vendor Bill existed for the selected Vendor/Subsidiary. Memorized transactions are now ignored when looking at historical Vendor Bills.
Resolved error encountered in new accounts when trying to setup ABM settings for the first time.
Release 2.5.3
New Features:
None
Changes:
If a line-item amount is extracted via OCR as $0 ABM will no longer try to back into a calculated amount based on the quantity and rate extracted.
Bug Fixes:
None
Release 2.5.4
New Features:
Added a Find Vendor By Currency setting on the ABM Settings page. When enabled, the currency of the invoice will be used when determining the vendor associated to the invoice. This feature should be enabled if your account has one vendor entity for each currency (vs a single vendor entity associated to one or more currencies).
Added a Date Field Mapping Override setting on the ABM Settings page. The date field will be populated to the field listed here. When this setting is enabled, the trandate will default to today's date.
Changes:
None
Bug Fixes:
Resolved issue preventing the lookup of a Vendor when no Vendor Name could be extracted from an invoice. This issue only impacted the Invoice Queue. Pressing Create Bill on the Invoice Queue worked around this issue in prior versions (the Vendor Bill create screen would correctly select a Vendor even though there was no Vendor shown on the Invoice Queue).
Corrected issue that would cause some invoices to fail to be scanned in non-One World accounts (starting in v2.5.0)
Release 2.5.5
New Features:
None
Changes:
None
Bug Fixes:
Resolved issue introduced in v2.5.4 that prevented scanning of invoices in accounts with multi-currency not enabled.
Release 2.5.6
New Features:
None
Changes:
None
Bug Fixes:
POs meeting the following criteria were not appearing in the PO drop down when creating a Vendor Bill: Bill before receipt is disabled, the PO has a combination of billable and non-billable items and the PO hasn’t been received.
Release 2.5.7
New Features:
None
Changes:
Updated our scripts that execute on the Vendor Bill screen to work around a NetSuite defect (Error reported by NetSuite via an unrelated client script: ReferenceError currentRecordService is not defined).
Bug Fixes:
None
Release 2.5.8
New Features:
None
Changes:
None
Bug Fixes:
Invoices that failed to extract a vendor name would sometimes fail to be scanned via OCR for new vendors.
Release 2.5.9
New Features:
Added support for blanket POs (new setting added to the ABM settings screen). This feature is enabled by default upon upgrade unless explicitly set to Disabled.
Added support for the default expense account specified on the Vendor record. If defined and no expense account can be determined automatically via historical bills, the default expense account will be used if expense lines are to be captured on a non-PO bill.
Added new Invoice Details Confirmation screen to capture missing invoice details before creating a Vendor Bill. This is currently an optional beta feature that can be enabled on the ABM settings screen.
Changes:
Reduced governance usage.
Bug Fixes:
Fixed rounding issues for CAD bills where the consolidated total is used to back into the net amount and the net amount is entered into the quantity field for consolidated POs.
Fixed issue for CAD consolidated bills trying to enter a consolidated item line and the selected item has a default quantity/rate/amount.
Release 2.5.10
New Features:
None
Changes:
None
Bug Fixes:
When creating a bill in a non-One World account, the user is no longer shown the error message "You do not have permission to access the subsidiary 'Parent Company'
Release 1.1.10 (Legacy Version)
New Features:
None
Changes:
None
Bug Fixes:
Resolved breaking change in NetSuite 2022.1 that impacted our ability to show loading dialogs on the screen.
Release 2.5.11
New Features:
Added new Vendor-level setting: Vendor Bill Lookback. This setting can optionally specify the number of prior bills to search when auto-filling line fields. This is only applicable when consolidation is disabled, lines are not copied from the prior bill and no PO is associated to the Vendor Bill. If not specified, the lookback is 5.
Changes:
Vendor Invoice Documents records have been removed from the global search.
Bug Fixes:
None
Release 2.5.12
New Features:
None
Changes:
None
Bug Fixes:
When a PO number extracted from an invoice document was the word “null”, an error was reported when trying to load the Vendor Bill screen.
Release 2.5.13
New Features:
None
Changes:
OCR accuracy checkboxes have been added to the ABM Vendor Invoice Document record (to track when the Vendor, Subsidiary, PO, Date, Amount or Invoice Number are changed by the user when entering a Vendor Bill). This information is not currently visible when viewing an ABM Vendor Invoice Document record and is sent to SquareWorks for internal reporting purposes.
Bug Fixes:
None
Release 2.5.14
New Features:
Added an Override Default Auto Fill Fields setting on the ABM Settings page. When enabled, only the fields specified in Auto Fill Fields will be automatically populated. No default fields will be automatically populated when this is enabled.
Changes:
None
Bug Fixes:
None
Release 2.5.15
New Features:
None
Changes:
Updated the process used to validate license keys.
Added automated analytics collection to give SquareWorks more visibility into features being used. This helps with future support and maintenance. Analytics are collected weekly and are automatically sent to SquareWorks. The following is collected:
PDF invoices uploaded via email (total count)
PDF invoices uploaded via drag and drop (total count)
Number of invoices scanned successfully (total count)
Number of invoices scanned unsuccessfully (total count)
Bug Fixes:
None
Release 2.5.16
New Features:
Added OCR rule action to allow for the custom extraction of a vendor’s name from the invoice document.
Changes:
None
Bug Fixes:
None
Release 2.5.17
New Features:
None
Changes:
Fixes the NetSuite Drag and Drop bundle which was overlapping page elements when viewing a Vendor Bill’s invoice document.
Bug Fixes:
Resolved issue that was resulting in failed scans when no vendor name could be extracted from an invoice PDF.
3-Way Match [325035]
Release 1.0.0
New Features:
Initial Release
Changes:
n/a
Bug Fixes:
n/a
Release 1.0.1
New Features:
None
Changes:
None
Bug Fixes:
Resolved issue when comparing multiple bills with inventory items to the PO/receipts.
Release 1.0.2
New Features:
None
Changes:
None
Bug Fixes:
Resolved issue causing 3-way matching fail and report variances in non-OneWorld accounts.
Release 1.0.3
New Features:
Added support for items coded to Other Current Liability, Long Term Liability, Equity, Income, Other Income and Deferred Revenue accounts.
Changes:
None
Bug Fixes:
None
Release 1.0.4
New Features:
None
Changes:
None
Bug Fixes:
Excluded 3-way match from running when entering Item Receipts for non-POs (e.g. Transfer Orders)
Release 1.0.5
New Features:
None
Changes:
None
Bug Fixes:
Resolve issue with item receipts reporting negative amounts and quantities when comparing to Vendor Bills.
Release 1.0.6
New Features:
None
Changes:
The terminology “error” has been changed to “variance” on all screens and dialogs.
Bug Fixes:
None
Release 1.0.7
New Features:
The ability to exclude all non-po items/accounts has been added to the settings page.
Changes:
None
Bug Fixes:
None
Release 1.0.8
New Features:
Added support for accounts without Advanced Receiving enabled.
Changes:
None
Bug Fixes:
None
Release 1.0.9
New Features:
Added support for PO receiving using Item Fulfilments.
Changes:
None
Bug Fixes:
None
Release 1.0.10
New Features:
None
Changes:
None
Bug Fixes:
Resolved issue preventing variances from appearing on item receipts records after the receipt is saved.
Release 1.1.0
New Features:
When checking for total variances, the billed total will now be compared to the received total (instead of only the PO total). This only applies if bill before receipt is disabled and advanced receiving is enabled.
If a receipt has not been approved (through SquareWorks Approval Workflow Automation) and approvals are enabled, the receipt will not be included when checking for variances.
Changes:
When checking for variances when saving a bill, any bills that were entered after the saved bill (based on internal id order) will not be included in the variance check.
When checking for variances when saving a receipt, any receipts that were entered after the saved receipts (based on internal id order) will not be included in the variance check.
Bug Fixes:
Canceled Bills are no longer included when checking for variances.
Release 1.1.1
New Features:
The setting Exclude Item Receipts Not Approved has been added to the settings screen. When enabled, Item Receipts not approved using Approval Workflow Automation will be excluded when checking for variances. By default this feature is not enabled.
Changes:
None
Bug Fixes:
Using Approval Workflow Automation without enabling approvals on Item Receipts was resulting in an error when checking for variances in v1.1.0 (when advanced receiving is enabled and bill before receipt is disabled). This has been avoided by adding an optional setting to enable or disable the exclusion of Item Receipts based on approval status.
Release 1.2.0
New Features:
Added support for Receipt and Vendor Bill lines where the unit entered is different from the item’s base unit.
Added ability to define settings (including thresholds) at a Subsidiary and/or Vendor level on the 3-Way Match settings screen.
Added ability to place Vendor Bills on payment hold if variances are detected. Functionality has also been added to automatically and/or manually detect and remove the payment hold if variances have been resolved.
Added ability to force 3-way match even if the NetSuite Bill Before Receipt preference is enabled.
Added ability to exclude non-PO Vendor Bill lines (based on items and expenses) from the total threshold comparison.
Changes:
Updated help text of all 3-Way Match settings fields along with this user guide.
Updated the layout and field labels on the 3-Way Match settings screen.
Improved support for including variances detected within emails sent from Approval Workflow Automation and within Saved Searches.
Bug Fixes:
Disabled 3-way match validation when records are being deleted.
Release 1.2.1
New Features:
Variances now show links to the related POs when viewing variances from within NetSuite.
Changes:
Currency amounts have been updated to be formatted according to NetSuite preferences.
Bug Fixes:
Fixed issue with manually added bill lines when the item or account matched one of the po-related lines.
Release 1.2.2
New Features:
None
Changes:
None
Bug Fixes:
Updated to exclude Transfer Orders and RMAs from 3-way match validation when saving Transfer Orders and RMAs.
Release 1.2.3
New Features:
None
Changes:
None
Bug Fixes:
Added support for single-currency accounts with multiple subsidiaries.
Release 1.2.4
New Features:
None
Changes:
None
Bug Fixes:
Accounts with multiple units of measure using different received rates for a single PO line were resulting in the error “[big.js] Invalid number” when attempting to run 3-way match validation.
Release 1.2.5
New Features:
Added support for item-specific thresholds using Override Settings on the 3-Way Match settings screen.
Changes:
None
Bug Fixes:
Resolved error trying to perform 3-way match when rate was not defined at the line-level.
Release 1.2.6
New Features:
Added two new hidden fields to Bills and Receipts that capture the total amount variance when the bill is saved. These can be used as part of an Approval Workflow Automation process.
3WM PO Variance (Amount): custbody_sw_3wm_po_variance_amt
3WM Receipt Variance (Amount): custbody_sw_3wm_receipt_variance_amt
Changes:
None
Bug Fixes:
None
Release 1.2.7
New Features:
Added a hidden text field to Bills and Receipts (3WM Override Key) that can be used to define more granular override settings beyond Subsidiary, Vendor and Item. Override Settings have been updated to allow you to limit override settings to a specific 3WM Override Key value. This can be used in combination with Subsidiary, Vendor and/or Item. To leverage the Override Key feature, the 3WM Override Key field must be set on a custom before load event via script/workflow.
Changes:
None
Bug Fixes:
Resolved issue where the Hold Payment of Bills with Variances feature was forcing the payment hold check box to be unchecked on non-PO bills.
Resolved error seen when a currency code was selected on the 3-Way Match settings screen in a non-multicurrency account.
Release 1.2.8
New Features:
New variance “PO Is Not Approved” has been added: If a Bill/Receipt is associated to a PO that’s pending approval, a variance will always be reported when saving the Bill/Receipt. This can happen if a Bill/Receipt is entered against an approved PO, but the PO is later unapproved (e.g. due to a change to the PO). This will prevent unapproved changes to a PO from removing all variances detected on the Bill/Receipt.
Changes:
None
Bug Fixes:
None
Release 1.3.0
New Features:
Thresholds can be configured to be both positive and negative. A new setting has been added to the settings screen called Enable Positive and Negative Thresholds to enable this feature. When enabled, all thresholds defined on the settings screen will be both positive and negative thresholds. Do not use this feature if multiple bills/receipts are entered against the same PO. This setting has no impact to rate thresholds, which are always positive and negative.
Thresholds can be configured to vary based on Threshold Type (e.g. Bill vs PO, Bill vs Receipt, Receipt vs PO) using override settings.
Changes:
None
Bug Fixes:
None
Release 1.3.1
New Features:
None
Changes:
Reduced governance usage.
Improved the layout of the 3-way match dialog in 2022.1.
Bug Fixes:
None
Release 1.3.2
New Features:
None
Changes:
None
Bug Fixes:
Fixed a rounding issue when multiple vendor bills and/or item receipts are summed while calculating variances.
Release 1.3.3
New Features:
None
Changes:
None
Bug Fixes:
Fixed a bug when calculating variances on items that have "Generate Accruals" enabled and multiple Vendor Bills are entered against a PO.
Release 1.3.4
New Features:
None
Changes:
None
Bug Fixes:
Fixed a bug introduced in 1.3.2. When evaluating Total Thresholds, variances were not being triggered.
Release 1.3.5
New Features:
None
Changes:
Decreased governance usage to allow for a larger (~5x) number of lines to be evaluated when checking for variances.
Bug Fixes:
Updated an error dialog that was showing an incorrect label when an unexpected error occurred.
Release 1.3.6
New Features:
Added support for POs with item group line items.
Changes:
Updated the process used to validate license keys.
Added automated analytics collection to give SquareWorks more visibility into features being used. This helps with future support and maintenance. Analytics are collected weekly and are automatically sent to SquareWorks. The following is collected:
Enabled status of 3-Way Match (Enabled/Not Enabled)
Bug Fixes:
None
Approval Automation [310718]
Release 1.1.0
New Features:
Adds support for Role-based approvals
Changes:
None
Bug Fixes:
Resolves the issue of approvals posting to locked periods
Release 1.2.0
New Features:
Added support for group approvals. You can define a group with one or more employees either as static list or based on a saved search. When requesting a group for approval, the first 10 employees will receive approval request emails. However, any member of the group can log into NetSuite to approve. Only one member is required to approve before moving onto the next approval process step.
Improved role based approval buttons in NetSuite. An employee can now see and press the Approve / Reject buttons even if they aren't logged in as the required role. As long as their employee record is assigned the required role, they will be allowed to approve.
Added ability to specify specific roles which can edit records when they are locked during submission and/or approval. Prior to this change, no roles (including admin) where able to edit locked records.
Added support for rejection emails. Rejection emails can include the rejection reason. They can be sent to either the employee who submitted the record for approval, or a custom employee via a lookup field.
Added support for approval emails. Approval emails are sent once a record has been fully approved. They can be sent to either the employee who submitted the record for approval, or a custom employee via a lookup field.
Added pre-built dashboard reminder which shows all transactions pending your approval. This supports employee, role and group based approvals.
You can add this by adding the “My Transactions Pending Approval” reminder.
Transactions are now automatically linked to their latest approval request via a list/record field on the transaction body. This allows for easy reporting to see what's currently pending approval. The reminder above uses this information.
Added logic to prevent custom email attachments from being included in the email if they are more than 10MB (to avoid hitting NetSuite attachment size limits)
Added an optional feature to the employee hierarchy approval type to take into account purchase limit. When enabled, if the first employee in the hierarchy has a purchase limit greater than or equal to the transaction total, the entire approval step will be skipped.
You can now specify what keyword indicates the end of an email body (to prevent automated mail server disclaimers from getting added to comments when approving / rejecting via email)
Added ability to specify multiple employees on the approval step definition. Previously you could only select or lookup a single employee.
Added the ability to require all approvers (with a role, group or list of employees) to approve instead of just one on the approval step definition screen.
Improved the super approver override window when overriding approvers. The window now allows you to change approver type (e.g. Employee, Role, etc), indicate if all approvers are required, and an option to suppress approval emails from being sent to the changed approvers.
Added ability to lookup approvers via saved searches. This allows complex approval conditions to be supported, including looking up approvers via line-level information on a transaction.
Changes:
Reorganized all setup screens. Updated process definition screens to dynamically hide/show fields based on the approval type selected.
The approval history tab has been improved to provide more details about the type of approval (e.g. employee vs role), the date/time approved, and better handling of long comments.
Bug Fixes:
None
Release 1.2.1
New Features:
Added new approval type: Employee Hierarchy (Expense). This type is the same as Employee Hierarchy (Purchase), except that it uses the expense approval fields on the Employee record (Expense Limit, Expense Approval Limit, Expense Approver)
Added optional fields to the Employee Hierarchy step definition to specify custom fields to lookup limits and approval limits. If not populated, the default employee fields will be used. This is useful for defining approval limits in a custom record (e.g. Job Codes) and linking to the custom record on the employee record.
Added optional field to specify a delegate approver field for all step definitions. This can be used to define a delegate approver on employee records to handle out of office needs. When a delegate approver is used within an employee hierarchy approval, the original employee’s hierarchy is still followed after the delegate approves.
Added ability to super approve individual approval requests (there are more options now when pressing the Super Approve button).
Added ability to exclude specific employees from an approval step.
Added ability to exclude employees from an approval step if they have previously approved in the current approval process.
Added ability to specify specific employees at a step level who has access to use the change approvers link (without seeing the Super Approve button)
Added support for 3-way match validation (advanced version of Approval Workflow Automation only)
Added Single Level Only setting to the Employee Hierarchy approval type. When enabled, only one approval will be required for the hierarchy to be complete. Approval limits are ignored. As long as you don't have Employee Must Approve enabled, this functions the same as NetSuite's basic approval routing.
Changes:
Updated the look and feel of the approve, reject, cancel and super approve dialog boxes.
Improved performance of approval submission.
Bug Fixes:
None
Release 1.2.2
New Features:
Added ability to limit approvals to specific subsidiaries at a record-type level. If no subsidiaries are selected, it’s the same as selecting all subsidiaries.
Added ability to automatically reroute approvals to specific employees or role if there are exceptions during the approval routing process.
Added option to treat missing approval limits (applicable only to hierarchy approval type) as an exception.
Added delegation begin and end dates to the employee record, allowing delegates to only be enabled during a period of time.
Added option to the approval process step definition to enable/disable delegation. When enabled, the bundle-provided delegation fields (begin, end, delegate) on the employee record.
Added an out of office self-service screen allowing any employee to set their out of office begin date, end date and delegate without needing access to edit their own employee record.
Changes:
Improved performance of approval submission and routing. Reduced the number of required lookups/searches against NetSuite.
Bug Fixes:
The logic to automatically set the posting period on approval (for gl posting transactions) has been updated to correctly handle multi-subsidiary accounts. There was an issue that was preventing records from being fully approved.
Release 1.2.3
New Features:
If the transaction being approved has NetSuite Approval Routing enabled, the standard Next Approver field will be populated automatically with the current approver. This is only supported for Employee Hierarchy and Employee approval types. If multiple employees are required to approve, the first employee in the list of approvers will be specified as the Next Approver. This functionality enables employees to approve when using an Employee Center role.
Changes:
Bug Fixes:
None
Release 1.2.4
New Features:
None
Changes:
Updated saved search / reminder name from “Transactions Pending My Approval” to “Transactions Pending My Approval (AWA)”
Updated saved search name from “Transactions Pending Approval” to “Transactions Pending Approval (AWA)”
Bug Fixes:
Updated Transactions Pending My Approval (AWA) search / reminder to run unrestricted, allowing employee center users to view transactions pending their approval in the search results.
Release 1.2.5
New Features:
None
Changes:
None
Bug Fixes:
Resolved script error reported when copying records. Users were unable to copy records due to a script error (Reported error message: ReferenceError: "approvalSobjRecordctionFieldId" is not defined). This only impacted implementation setup to automatically submit or re-submit approvals.
Release 1.2.6
New Features:
None
Changes:
Delegation logic has been updated to only send email notifications to the delegate instead of both the original approver and the delegate. The delegate always gets set as the Next Approver on POs and Expense Reports. When delegate is no longer applicable, the original approver will automatically receive an approval request email if the delegate never approved.
Bug Fixes:
None
Release 1.2.7
New Features:
If exception handling is enabled (on the approval process record type’s definition), the employee or role handling the exception now has a new button available: “Continue Approval”. The “Approve” button has been removed for the exception handler to avoid the exception handler accidently approving the step. Once the issue has been resolved, the exception handler can press “Continue Approval” to retry the next applicable step in the process. If an exception occurs in the middle of an employee hierarchy approval, the hierarchy approval will continue where it left off.
Added optional exception (enabled on the process step definition) if approvers are missing from an approval step. For example, if the approval step definition is looking up an approver, and the field referenced is empty, an exception can be reported. This exception will also be reported if an employee in a hierarchy approval is marked as inactive.
Changes:
Updated the logic used by the approver search functionality (which enables you to dynamically look up approvers via a saved search)
Bug Fixes:
If no rejection reason is provided, the rejection email no longer leaves the “{{SW_AEA_COMMENTS}}” placeholder in the email.
No comments were being captured via email if the Inbound Email End of Message Keyword was defined and the keyword was not found in the body of the email.
Release 1.2.8
New Features:
Added beta version of bulk approval support (AWA Bulk Approval) for transactions. This page is not deployed to any roles / employees by default. If you would like to try out this functionality, please reach out to SquareWorks.
Changes:
None
Bug Fixes:
When a transaction is transformed from another record (e.g. PO to VB) and both record types have approvals enabled, fields related to approvals were not properly cleared, possibility leading to conflicts with the approval process.
Release 1.2.9
New Features:
The bulk approval screen has been documented in the user guide.
Added the ability to specify a custom search and title for the bulk approval screen.
Changes:
The default version of the bulk approval screen has been updated to specify columns common across all transactions.
Bug Fixes:
None
Release 1.2.10
New Features:
None
Changes:
None
Bug Fixes:
An “Unexpected Error” was being reported when attempting to send emails to employees with no email address defined. Email handling has been updated to skip over these employees when trying to send emails. An error message will still be logged, however, this error will not prevent other approver emails from being sent.
Release 1.2.11
New Features:
Added setting to the Approval Process Step Definition to exclude the submitter (the employee who pressed the Submit button) from being included as an approver. Supports Role, Group and Employee approval types.
Changes:
None
Bug Fixes:
None
Release 1.2.12
New Features:
An optional action field (when configured on Approval Record Type Settings) now accepts APPROVE and REJECTION actions (in addition to existing SUBMIT, RESUBMIT and CANCEL actions). The processing of these actions has been updated to happen via a background job (map/reduce) instead of within the user event context.
Changes:
Comments are now required when pressing Reject or Super Approve via the NetSuite UI.
Bug Fixes:
When a custom saved search was used to lookup approvers on a multi-select field, some NetSuite accounts were returning unexpected delimiters. A fix was added to support both commas and /u0005 as possible delimiters. Example error message logged: You have entered an Invalid Field Value 2681\u000525564\u000539849 for the following field: custrecord_sw_aea_resp_employee
Release 1.2.13
New Features:
Added ability to optionally to specify an “Approver Filter Search” to assist with looking up approvers via search. The results of this search result are made available to the Approver Search Filter via a search.results freemarker variable. The variable contains a list of search result hashes and individual column results can be accessed via searchcolX_value and searchcolX_text hash keys (where X represents the column index, zero based). This is useful for getting access to summarized line-level information required to define a search filter.
Changes:
None
Bug Fixes:
None
Release 1.2.14
New Features:
A hidden transaction body field called “AWA Purchase Order” has been added to Vendor Bills. When a Vendor Bill is created from a PO, this hidden field will contain a reference to the PO. If the Vendor Bill is associated to multiple POs, only the first found will be specified in this hidden field. This field is useful for reporting purposes and in the Approval Step Definition’s Enabled Condition.
Changes:
None
Bug Fixes:
None
Release 1.2.15
New Features:
Added ability to define an email template preset when setting up record type approval settings. When used, email templates will be automatically generated and selected. Presets are available for Transactions (Generic), Vendor Bills, POs and Expense Reports.
Added ability to define record details (below email) by using a comma separated list of field ids on the record type settings page (vs a separate PDF template). The email template preset will default the record detail fields.
Changes:
None
Bug Fixes:
Allow custom attachments to be defined on record type settings while having the Template Attachment Mode set to Do Not Attach.
Only set the Close Date on the Approval Process record when it reaches a state that’s not pending approval.
Release 1.2.16
New Features:
None
Changes:
None
Bug Fixes:
Updated style of approval email templates to be compatible with Gmail. Gmail was failing to show table and button styles.
Release 1.2.17
New Features:
Added the ability to hide the approval step’s order on the Approval History tab.
Added info-only notification email support. A new email template can be referenced on the approval record type settings page. When creating an approval step definition, it can be configured to send email notifications only, without requiring approval.
Changes:
None
Bug Fixes:
None
Release 1.2.18
New Features:
When a transaction hasn’t been submitted for approval, the status at the top of the page now says “Not Submitted” instead of “Pending Approval”.
Changes:
None
Bug Fixes:
None
Release 1.2.19
New Features:
The approver lookup field (on Approval Process Step Definitions) has been enhanced to allow for multiple levels of table joins.
All email communication will now be attached to the record being approved (found under the Communications tab). The email communication will continue to be attached to the employees sending/receiving the email.
Changes:
None
Bug Fixes:
Resolved issue with “Not Submitted” appearing on transactions that were approved prior to AWA being installed.
Release 1.2.20
New Features:
Added support for enabling approval resubmission (after a record has been submitted for approval or approved) based on edits to the record’s total. This only supports transactions and can be setup to be based on percent or amount based thresholds.
Changes:
None
Bug Fixes:
None
Release 1.2.21
New Features:
Added support for integration with SquareWorks’ Check Printing addon.
Changes:
None
Bug Fixes:
None
Release 1.2.22
New Features:
None
Changes:
Exclusion of approvers (using the Exclude Employees and Exclude Employee if Already Approved fields on the Step Definition) can no longer cause an exception to be reported when “Missing Approver is Exception” is enabled. The employees are excluded on purpose and should not be treated as missing approvers. The Exclude Submitter field will still result in an exception being reported.
Bug Fixes:
Resolved issue preventing transactions from allowing resubmission when the native Approval Status field is manually changed from Approved to Pending Approval.
Resolved issue seen in Sandbox which impacted how multiselect fields are accessed via SuiteScripts.
Release 1.3.0
New Features:
Added support for custom approval matrixes for Employee type Approval Steps. See the Approval Matrixes section in the user guide for more details.
Changes:
None
Bug Fixes:
None
Release 1.3.1
New Features:
None
Changes:
Updated Approval Step Definition form to hide fields when approval type is not selected.
Approval Step Definition Type “Matrix” has been added, replacing the use of an approval matrix on the “Employee” type.
Bug Fixes:
None
Release 1.3.2
New Features:
None
Changes:
When a Vendor Bill is created using NetSuite’s “Bill Purchase Orders” screen, the user isn’t automatically redirected back to the “Bill Purchase Orders” screen. This allows for easier submission of the Vendor Bill.
Bug Fixes:
The PO a Vendor Bill was created from was not being tracked in a custom hidden field starting in v1.3.0 (custbody_sw_awa_po). This hidden field is sometimes used in approval routing conditions to determine if a Vendor Bill was created from a PO.
Release 1.3.3
New Features:
None
Changes:
None
Bug Fixes:
Resolve issue causing group-based approval steps to not find any approvers in the group.
Release 1.3.4
New Features:
Approval Matrix Definitions can now reference record types that do not have an “Is Inactive” field (e.g. transaction). This is to support a special use case where you want to use a matrix to lookup approvers on a non-custom approval matrix record.
Changes:
None
Bug Fixes:
Resolved issue causing approvers to receive approval request emails even if they have delegation enabled. This only impacted approval steps which lookup approvers via a saved search.
Resolved issues preventing currency based approval re-routing from working as expected. This was an issue when the currency of the transaction being created/routing doesn’t match the currency of the re-routing threshold.
Release 1.4.0
New Features:
Added an approval status to all record types when approvals are enabled (see screenshot below). This includes record types that do not natively have a status shown next to the record’s name. Statuses include: Not Submitted, Pending Approval and Approved. If a record natively has other statues (e.g. Open, Paid in Full, Cancelled), these statuses will still appear and will not be replaced.
The custom approval status field (including the native field on transactions) is now hidden when editing the record. This can be disabled for Administrators using the Disable Field Display Changes for Administrators approval setting.
The Next Approver field (native field) is now hidden automatically to avoid confusion with Approval Workflow Automation's approval functionality. This can be disabled for Administrators using the Disable Field Display Changes for Administrators approval setting. This field is for reporting purposes only and should not be used to try to change the next approver.
Added support to make records inactive (if supported by NetSuite) when they are pending approval. Once approved, the record is automatically made active. This feature can be enabled using the Inactivate Unapproved Records setting on the Approval Record Type Settings. By default, this feature is not enabled.
Added support to enable Vendor Bill payment hold when Bills are pending approval. Once approved, the Bill is automatically taken off payment hold. This feature can be enabled using the Hold Payment for Unapproved Bills setting on the Approval Record Type Settings. By default, this feature is not enabled.
Added ability to automatically submit a record for approval at creation time. This can also be limited to non-UI contexts as well (e.g. CSV). This feature can be enabled using the Submit for Approval on Creation (All) or Submit for Approval on Creation (Non-UI) settings on the Approval Record Type settings. By default, this feature is not enabled.
Added ability to require resubmission when a record is edited. This feature can be enabled using the Any Change Requires Resubmission setting on the Approval Record Type Settings. By default this is not enabled.
Administrators can be excluded from trigging resubmission using the Exclude Administrators from Resubmission Logic setting on the Approval Record Type Settings. By default this is not enabled.
Added ability to mark a transaction as natively approved (via the native Approval Status field) once a specific step in an approval process is complete. This can happen before all steps in the approval process are complete. When this occurs, a transaction (e.g. Vendor Bill) can be posted to the GL but additional approval steps can still be required. This is enabled via the Approve Transaction After Step setting on the Approval Process Step Definition.
Changes:
Approval record type settings will now default additional fields when creating new approval record type settings: Edit Locked Submitted Records Roles, Edit Locked Approved Records Roles, and Route Exceptions to Role will all default to Administrator.
The "Submit" button's name has been changed to "Submit for Approval".
Added a custom field to all transactions and entities to store and display the current approval status in the body of the form (Approval Status (AWA)). If a transaction (e.g. Vendor Bill) has the native Approval Status field, the native field will be automatically hidden. Transactions approved prior to this update will continue to show the native approval status field. This new custom field will not be shown on custom forms by default, but can be configured to be shown by modifying your forms.
Removed ability to Cancel a Vendor Bill while a Bill is routing for approval. The approval process must be cancelled before a Bill can be cancelled.
Bug Fixes:
None
Release 1.4.1
New Features:
Journal Entries, Intercompany Journal Entries and Advanced Intercompany Journal Entries have been updated to store their line-level total (sum of debits) in the custom field custbody_sw_awa_submitted_total. This field can be referenced via Approval Step Enabled Condition. This also enables the use of Approval Resubmission logic based on the transaction total and the use of approval matrices.
Purchase Requisitions have been updated to use the native field estimatedtotal instead of total to determine the transaction’s total.
Changes:
None
Bug Fixes:
None
Release 1.4.2
New Features:
None
Changes:
None
Bug Fixes:
Resolved issue with the Only Send Group Approvals To approval step setting. The setting was not emailing the specified employee(s) as expected. This only applies to approval steps of type Group.
Release 1.4.3
New Features:
Added Approval Record Type setting Attach All Files, allowing you to attach all files from the native Communication > Files tab to approval emails.
Up to 10 files can be attached, based on the order they are uploaded to the file cabinet (e.g. first file uploaded will be attached first). Additional files will not be attached.
Up to 10mb of files (combined) will be attached
Only files 10mb or less will be attached
Added the ability to approve records in bulk via email.
Changes:
None
Bug Fixes:
None
Release 1.4.4
New Features:
Added Approval Process Step Definition setting Custom Delegate Start Date Field. Enter the field id to look at to determine the delegate approver start date on the Employee record. If no field is specified, the included Delegate Approver Start Date field on the Employee record will be used.
Added Approval Process Step Definition setting Custom Delegate Start Date Field. Enter the field id to look at to determine the delegate approver end date on the Employee record. If no field is specified, the included Delegate Approver End Date field on the Employee record will be used.
Changes:
Improved defaulting of AWA Approval Status field when new records are created.
Bug Fixes:
None
Release 1.4.5
New Features:
When a record is rejected, the record’s banner now shows “Rejected” instead of “Not Submitted”
Changes:
None
Bug Fixes:
Corrected sorting issue related to approval process requests that was causing the approve / reject buttons to not appear in some accounts.
Release 1.4.6
New Features:
None
Changes:
A recent NetSuite defect impacting a subset of customer accounts (related to core search functionality) was conflicting with our solution. Changes have been made to work around this defect. The easiest way to know if your account is impacted is to check to see if the Super Approval functionality works as expected in your account. In impacted accounts you can press Super Approve, but no change is made. The NetSuite search defect (related to joining to records to retrieve a multi-select value) is not specific to this solution, and could possibility impact other bundles / scripts in your account.
Bug Fixes:
None
Release 1.4.7
New Features:
Added a new approval step type called System. The System type is used when you want to check if a condition is met before moving onto the next step of an approval process. If the condition is not met, NetSuite will check every 15 minutes until the condition is met. (Example use case: Wait for a bill to have all variances removed before routing to the next step of an approval process)
Changes:
Disabled all approval functionality for Voiding Journals since Voiding Journals cannot natively be made pending approval.
Bug Fixes:
Resolved issue with the Only Send Group Approvals To approval step setting. The setting was not emailing the specified employee(s) as expected. This only applies to approval steps of type Group.
Resolved issue when comments or approver names contained single quotes. This was preventing the approvers name or comments from being shown fully on the Approval History tab.
Release 1.4.8
New Features:
None
Changes:
Super Approve and Cancel Approval functionality has been updated to support records stuck in an approval process: In rare cases, it’s possible for a record to become stuck in an approval process where NetSuite thinks the record hasn’t been approved, but our solution thinks it has been approved. This type of issue is always caused by other scripts, workflows or native NetSuite preventing updates to the record being approved. Once the underlying issue has been resolved, pressing the Super Approve button on the record will mark the record as fully approved. Pressing the Cancel Approval button will mark the record as approval canceled (regardless of the approval history status). Prior to this change, the Super Approve and Cancel Approval button took no action.
Bug Fixes:
None
Release 1.4.9
New Features:
Added support for auto-submitting drop ship / special order POs when auto-submission is enabled.
Changes:
Added the word “Optional” to the comments box when approving via the NetSuite UI.
Bug Fixes:
Resolved error encountered when trying to view memorized transactions in NetSuite with approvals enabled.
Release 1.5.0
New Features:
The ability to define approval coordinators for an Approval Process Step Definition has been added. This feature supports the approval use case where an approval request email needs to be sent to an employee (who is often not the approver). Then, the coordinator can forward the email to the appropriate approver internally. This feature replaces the feature to “Only Send Approvals To” for Role and Group approvals.
When approvals are enabled on Vendors, approved Vendors will automatically be resubmitted for approval if Entity Bank Details are added or updated.
Changes:
If a record fails to submit for approval, pressing the Submit for Approval button again will now attempt to submit the record for approval.
Vendor Bill, Expense Report, Journal Entry, Intercompany Journal Entry and Advanced Intercompany Journal Entries will no longer change their native approval status (which impacts posting) if they are already approved and have been linked to payment transactions. They can still be resubmitted for approval (if using approval resubmission functionality), but the native approval status will not change. This change was made to avoid approved transactions from unlinking from payment transactions due to approval resubmission.
Performance improvements to reduce the risk of a record failing to submit, cancel, reject or approve due to another user/process updating the same record in parallel. All record updates have been changed to use record.submitFields instead of record.save.
Bug Fixes:
Resolved issue where the approval resubmission thresholds did not work as expected when a record type was configured to reference a custom total field that sources its value from a saved search.
Release 1.5.1
New Features:
Approval Process Step Definitions (with exception of System type) have been updated to include a new optional feature: Prevent Approval if Period not Open. When enabled, the step cannot be approved if the period corresponding to the Transaction Date is not open (meaning locked or closed). This feature is disabled by default. If approved via email, the approver will be notified via email if the transaction cannot be approved due to this restriction.
Approval Process Step Definitions (with exception of System type) have been updated to include a new optional feature: Prevent Approval if Variances Exist. When enabled, the step cannot be approved if SquareWorks 3-Way Match Add-On has detected variances. This setting is only applicable for approvals on Vendor Bills and Item Receipts. This feature is disabled by default. If approved via email, the approver will be notified via email if the Vendor Bill/Receipt cannot be approved due to this restriction.
Approval Record Type Settings have been updated to include additional permission settings. Permissions can now be configured (by role) to hide/show the Cancel Approval button, Submit for Approval button, and the approval confirmation/comments dialog.
Record locking functionality has been extended to historical records that were not approved via Approval Workflow Automation.
The Approval History tab is now shown when editing a record.
Changes:
Increased the time confirmation/error messages appear on the screen after submitting/approving a record.
Improved the ability to select the record type when creating new Approval Record Type Settings. Prior to this change there was often a delay in seeing the list of available record types to select.
Improved support for the custbody_sw_awa_po field (PO) on historical Vendor Bills. Any edit or action (e.g. Submit for Approval) on a historical bill will now backfill the custbody_sw_awa_po field automatically. This is useful when trying to submit historical records for approval which depend on the custbody_sw_awa_po field being populated. Prior to this change, the custbody_sw_awa_po field was only populated when a bill was first created. Related to this change, a new field was added with ID custbody_sw_awa_is_stand_alone_bill (hidden check box) to indicate if a bill has a related PO or not.
Approval email default templates have been updated to change the variable ids from *_AEA_* to *_AWA_*. The old variable ids are still supported.
Bug Fixes:
Resolved issue preventing Vendor Bill Payments (to be printed via check) from auto-submitting when check printing approval is configured.
Release 1.5.2
New Features:
Added an Enabled Condition Validator which can be used to help write and test enabled condition formulas. An administrator can use it by navigating to Setup > Approval Workflow Automation > Enabled Condition Validator or using the Validate Enabled Condition button while editing an Approval Process Step Definition record.
Changes:
None
Bug Fixes:
None
Release 1.5.3
New Features:
None
Changes:
None
Bug Fixes:
Resolved issue: If a vendor was created prior to enabling AWA, changes to their bank details do not trigger the vendor to re-submit for approval.
Resolved issue: The Employees Allowed to Change Approver approval process step definition field causes approval submission errors when more than 1 employee is specified in the field.
Release 1.5.4
New Features:
None
Changes:
Reduced governance usage
Bug Fixes:
None
Release 1.5.5
New Features:
Additional configuration options have been added to the Matrix Definition. The new configuration settings (Prioritize Field Comparisons Over Levels, Empty Matrix Fields Match All) are enabled by default on all new Matrix Definitions. Existing definitions will have these new features disabled by default. Both of these settings will impact how approvers are looked up in an approval matrix.
Changes:
None
Bug Fixes:
None
Release 1.5.6
New Features:
Added a checkbox to the AWA Approval Record Type Settings page named “Include Approval History In Email Templates”. When enabled, an approval history table will be added to all emails sent out during the approval process. If a {{SW_AEA_APPROVAL_HISTORY}} placeholder is in the Email Template, the table will replace it in the email body. Otherwise, the record details will be added to the end of the email body.
Changes:
The {{SW_AEA_RECORD_DETAILS}} placeholder is no longer required in email templates. If the placeholder is present, the record details will replace it in the email body. Otherwise, the record details will be added to the end of the email body.
Reduced governance usage when sending emails to multiple approvers.
Bug Fixes:
None
Release 1.5.7
New Features:
None
Changes:
None
Bug Fixes:
Resolved exception reported when the addon attempts to send an exception email in 1.5.6 (Error message: Cannot read property "isInit" from undefined)
Release 1.5.8
New Features:
None
Changes:
Updated the logic which edits records (e.g. to mark as approved) to improve performance.
Bug Fixes:
Resolved issue which was preventing enabled conditions from knowing if a Vendor Bill was created from a PO if the Vendor Bill was in-line edited after creation.
Release 1.5.9
New Features:
None
Changes:
None
Bug Fixes:
Resolved an issue which was causing an exception when all approval steps are skipped for a record.
Release 1.5.10
New Features:
None
Changes:
None
Bug Fixes:
Resolved an issue which resulted in enabled conditions returning a false negative if the submitter or approver’s language preferences are configured to be non-English.
Release 1.5.11
New Features:
Approval emails now show a warning if any files cannot be attached. Files will be excluded if they are more than 10MB or more than 10 files are to be attached from the file cabinet.
Added support for Inventory Adjustment approval routing to remove GL / inventory impact while pending approval.
Changes:
Approvals in progress will now automatically re-route to delegates if a delegate is setup or becomes active.
Bug Fixes:
Resolved an issue which was preventing emails from being sent when files on the record in approval were over 15MB.
Release 1.5.12
New Features:
None
Changes:
When a record is approved, errors will now be logged if we fail to prevent NetSuite from posting to a locked period. The transaction will not become fully approved (posted) in this scenario. If this occurs, the error would first need to be resolved and then the transaction would need to be super approved.
Bug Fixes:
Email clients that failed to send a text version of the email body back to NetSuite were not being accepted as valid emails.
Release 1.5.13
New Features:
None
Changes:
None
Bug Fixes:
Resolved permission error introduced in v1.5.12 when trying to approve records that contain a posting period but do not support native approval routing functionality.
Release 1.5.14
New Features:
Added support for inventory detail bin numbers when routing Inventory Adjustments for approval.
Changes:
Updated the process used to validate license keys.
Added automated analytics collection to give SquareWorks more visibility into features being used. This helps with future support and maintenance. Analytics are collected weekly and are automatically sent to SquareWorks. The following is collected:
Record types using approvals (e.g. Vendor Bill, PO)
Number of approval requests (Total Count)
Number of approval responses through email (Total Count)
Bug Fixes:
None
Release 1.6.0
New Features:
Added budget based approval routing.
Changes:
Included additional saved searches used by the Automate dashboard (when installed)
Bug Fixes:
None
Release 1.6.1
New Features:
Added a Created By (AWA) field for transactions and entities that can be used to join on the employee that created the record.
Added ability to disable updates to the native Approval Status field.
Added ability to default the native Approval Status field to Approved when creating or copying transactions.
Changes:
Only perform a feature/license check for budget tracking on PO if budget tracking is enabled.
Removed budget related settings from the initial approval process step definition screen.
Bug Fixes:
None
Advanced Check Printing [288859]
Release 1.4.0
New Features:
Employees printing checks will only see transactions associated with their subsidiaries on the print checks screen.
Changes:
Added cpb-release-notes.txt
Bug Fixes:
None
Release 1.4.1
New Features:
None
Changes:
None
Bug Fixes:
When attempting to print memorized transactions, the script error "MEMORIZED_TRANS_ERROR" appears on the screen. This fix removes the ability to print checks for memorized transactions. Note, transactions created from a memorized transaction can still be printed.
Release 1.4.2
New Features:
None
Changes:
None
Bug Fixes:
When printing checks with vendor credits, the no applydate_value was supplied to the check template. This only impacted vendor bills fully paid via the vendor credit. The applydate_value field is sometimes used when sorting stub lines by date.
Release 1.4.3
New Features:
Add support for NetSuite Vendor Payment approval. If Vendor Payment approval is enabled in an account, only approved Vendor Payments ready to print are available for check printing.
Changes:
None
Bug Fixes:
None
Release 1.4.4
New Features:
Added check alignment settings to the Check Format record. These settings can be used to position the check/stub layout when using the Standard Template.
Changes:
None
Bug Fixes:
None
Release 1.4.5
New Features:
Added records[].payTo template variable to contain the check’s pay to value. See “Standard Pay To Logic” section for a description of how this variable is populated.
Added records[].entityType template variable to identify the type of entity being paid (e.g. “Vendor”)
Changes:
Updated the standard template to use the records[].payTo variable.
Removed cpb-release-notes.txt – added release notes to this document instead.
Bug Fixes:
The records[].entity field was not populated when sending Customer Refund checks. The field is now being populated.
Release 1.4.6
New Features:
Added three new template format variables: dateFormat, timeFormat, datetimeFormat and timeZone. These are populated based on company/user preferences. These are useful for parsing dates in the template using freemarker.
Changes:
Updated the standard template to define date, time, datetime and timezone settings. Adjusted stub layouts in standard template.
Bug Fixes:
None
Release 1.4.7
New Features:
None
Changes:
Updated the address positioning on the standard template.
Bug Fixes:
The payTo field added in 1.4.5 was not correctly looking up values if the NetSuite account was configured with different names for Customer, Vendor, Employee or Other Name record types.
Resolved issue preventing the bundle from looking up companyname on Customer record types. This issue prevented checks from printing.
Release 1.4.8
New Features:
The check printing license key is now automatically retrieved from SquareWork’s license server. You no longer need to update the license key each year.
Changes:
None
Bug Fixes:
None
Release 1.5.0
New Features:
Added configuration modes to the Check Template. There are now two modes: Standard and Advanced. Prior to v1.5.0, all templates use the Advanced mode (e.g. you defined the entire template via XML). Starting with v1.5.0, you can now select Standard mode when creating a PDF template. The Standard mode comes pre-configured with an ANSI compliant check layout, which can be customized as needed. Many of the common configuration changes can be completed directly on the Check Format (e.g. MICR line format) vs editing the template’s XML directly. No action is needed when upgrading to v1.5.0+. All existing templates will automatically be updated to use the Advanced mode.
Added new fields to the Check Format to control the Standard PDF template.
Added ability to remove Check Images and MICR Fonts without removing the entire Check Image or MICR Font record.
Changes:
None
Bug Fixes:
None
Release 1.5.1
New Features:
Removed the requirement to upload and specify a MICR font on the Check Format. If no MICR font is selected on the Check Format, our included E13B MICR front will be automatically used.
Enhanced Standard PDF template to allow for hiding overflow pages or only showing overflow pages. This change allows the Standard PDF template to be used when overflowing stub lines to an additional PDF.
Changes:
None
Bug Fixes:
Fixed error preventing used of the check printing screen when using the bundle on a non-OneWorld account.
Release 1.5.2
New Features:
The standard template layout has been updated for all new templates: The payee name has been moved up to support “positive payee” bank requirements. The fractional routing number has been moved to under the check number. An optional memo line has been added (commented out) to the check layout.
Changes:
Bank accounts with no check formats no longer appear on the print checks screen.
The bundle is now Managed.
Bug Fixes:
If the check numbers within a batch increased in digits (e.g. batch contained check no 8, 9, 10), they were printing out in the wrong order. In this example, they would be printed out in this order: 10, 8, 9. The sorting logic has been fixed in 1.5.2.
Voided payment transactions still with the “to be printed” check box checked no longer appear on the print checks screen.
Release 1.5.3
New Features:
Added Check Print Job to the Setup > Check Printing menu for Administrators.
Added logic to prevent users from reducing the check number shown in the First Check Number field when printing checks. If the next check number needs to be reduced, it can be changed directly on the related GL bank account. However, make sure there aren’t any existing transactions related to the GL bank account which might result duplicate check numbers in the future.
Changes:
Updated the Check Print Job and Check Print Job Data default list views
Bug Fixes:
Custom template fields using the Entity record type were unable to lookup fields when printing Customer Refund transactions.
Users were able to print from the summary screen (where the Manual Print button appears) even if they aren’t associated to the selected print job’s account’s subsidiary. This could happen in scenarios where two users are attempting to print concurrently or a user doesn’t press the Manual Print button right away.
Release 1.5.4
New Features:
None
Changes:
None
Bug Fixes:
Updated the Print Checks screen to show the payee name in the same format as used by the “Standard Pay To Logic” added in 1.4.5. Exception: Check transactions associated to an “Other Name” entity type will always show the Entity name seen on the Check Transaction, even if the Other Name’s company name field is different.
Release 1.5.5
New Features:
None
Changes:
None
Bug Fixes:
Roles using user-based subsidiaries (instead of selected subsidiaries) were getting stuck on the check printing screen. The Print Check button was showing “Print (In Progress)”. This bug impacted v1.5.3 and v1.5.4.
The Administrator role was not granted full access to Check Print Job and Check Print Job Data records by default. This had no impact to check printing.
Release 1.5.6
New Features:
Added the ability to automatically store a voided file copy of printed checks/stubs in the File Cabinet. This functionality only works out of the box (using settings on the Check Format) if using the Standard PDF template. The advanced PDF template can be updated to support this, but does not work out of the box. If enabled, the Check Print Job record will be updated to reference the file copy PDF file stored in the File Cabinet.
The following Template Global Assignments were added to the standard template to allow you to control the watermarks added to the file copies:
<#assign fileCopyStubText="FILE COPY">
<#assign fileCopyCheckText="VOID VOID VOID">
Changes:
None
Bug Fixes:
None
Release 1.5.7
New Features:
Added the ability to format the check date (on the standard template) following Canadian Standard 006 MICR standards. When creating new templates, you will find a new commented out line that can be used to enable this feature: <@printStd006Date date=check.trandate left=455 top=42/>. This line will generate a date format that looks like this on the check (assuming you hide the other date and fractional routing number on the layout).
The following Template Global Assignments have been added (but are hidden when creating new standard templates). They can be overridden in the Template Global Assignments field if required. These are used for formatting the date shown on the check. ansiDateFormat is for US checks and std006DateFormat is for Canadian checks (see feature above)
<#assign std006DateFormat="ddMMyyyy">
<#assign ansiDateFormat="M/d/yyyy">
Changes:
Removed the standard template’s Template Style and Template MIRC Layout default values when creating new standard templates. There’s no change to the look and feel of the standard template even though this content is no longer shown. This has no impact to existing standard template implementations.
The following Template Global Assignments have been hidden by default when creating new standard templates. They can be overridden in the Template Global Assignments field if required.
<#assign showPageSectionBorders=false>
<#assign showConvenienceAmountScanArea=false>
<#assign showMicrClearBand=false>
<#assign fileCopyStubText="FILE COPY">
<#assign fileCopyCheckText="VOID VOID VOID">
Bug Fixes:
The PCL5 overlay file specified on new PCL5 templates could not be read when printing checks. This had no impact to existing PCL5 template implementations.
Release 1.5.8
New Features:
None
Changes:
Updated the standard PDF template to disable PDF editing in Adobe Acrobat
Bug Fixes:
None
Release 1.5.9
New Features:
None
Changes:
Added retry logic when attempting to set the check number on payment transactions (when printing checks). If the update to the payment transaction fails, we will retry up to 2 times before failing.
Bug Fixes:
None
Release 1.5.10
New Features:
Added support for printing Vendor Prepayments. If not using the Standard PDF template in your implementation, your template may need to be updated to support the ability to print Vendor Prepayments. On the standard PDF template, no remittance table is shown.
Added support for Credit Memo and Customer Payment customer template fields.
Changes:
None
Bug Fixes:
None
Release 1.5.11
New Features:
None
Changes:
After pressing Print, the loading screen no longer says “Processing Vendor Credits” even if vendor credits are to be shown on the check remittance.
Bug Fixes:
Resolved issue causing check printing to sometimes stall when looking up vendor credits.
Release 1.5.12
New Features:
None
Changes:
None
Bug Fixes:
Fixed issue related to the payee name on the check: When a Vendor is associated to other entity types (e.g. Lead, Partner) the payee on the check does not always use the standard payee lookup logic defined for Vendors.
Release 1.5.13
New Features:
Updated Custom Template Fields to support Installments. This feature allows the template to optionally reference fields that exist on the Installments applied to a Vendor Bill Payment.
Changes:
None
Bug Fixes:
None
Release 1.5.14
New Features:
Added new preference (found under company settings) to only show the default entity name when viewing the print screen (instead of the standard pay to logic to lookup the payee name). This was added to work around performance issues in NetSuite and should only be enabled if the print checks screen is timing out when loading.
Changes:
None
Bug Fixes:
None
Release 1.5.15
New Features:
Added optional setting on the check format to specify a search to lookup Vendor Bill lines. This can be used to show line-level details from Vendor Bills applied to a Vendor Bill Payment.
Changes:
Removed Cancel button from the check printing processing/loading screen. If required check print jobs can be manually canceled by an Administrator by marking check print jobs as inactive.
Bug Fixes:
None
Release 1.5.16
New Features:
None
Changes:
The standard template has been updated to allow for the “checks” variable in the Template Global Assignments section to be overridden. This variable contains a list of the checks to be printed. This use useful when you need to override the order in which checks are printed.
Bug Fixes:
None
Release 1.6.0
New Features:
New custom template fields added now support the use of saved search formulas in the Search Field Id field.
Changes:
Performance improvements added to support additional vendor credit lines and applied transactions on checks. To take full advantage of these improvements, existing Custom Template Fields need to be marked as inactive and re-created.
All new standard templates added don’t remove commas by default from the check’s amount.
All new implementations of the bundle automatically break out vendor credits on the check’s remittance table.
All new standard templates show the applied transaction’s date instead of the due date.
Bug Fixes:
None
Release 1.6.1
New Features:
Added support for use of SquareWorks’ Approval Workflow Automation addon to approve payments prior to them appearing in the check print queue.
Changes:
None
Bug Fixes:
None
Release 1.6.2
New Features:
The standard template has been updated to support different page sizes (other than Letter). The following variable has been added to the standard template to control the page size: <#assign pageSize="Letter">. By default the page size is set to Letter (8.5x11)
The MICR line on the standard template has been updated to support no blank space between the routing number and account number. Most banks require a blank space, but some banks will require no space between the MICR account number and routing number.
Changes:
None
Bug Fixes:
None
Release 1.6.3
New Features:
None
Changes:
None
Bug Fixes:
Resolved issue with Vendor Bill Payments retrieving payee information from a Customer record (if the Vendor entity is linked to a Customer entity and the Customer entity was created first)
Release 2.0.0
New Features:
Checks can optionally be printed across bank accounts in a single batch. This setting must be enabled on the Setup > Check Printing > Settings page (Allow Printing Across Bank Accounts). Once enabled, the Bank Account on the Print Checks screen can be changed to "- Multiple -" to select payment transactions across accounts. If you would like to print across bank accounts by default, the setting Print Across Bank Accounts by Default can be enabled on the check printing settings. This feature is only compatible with account using the Standard PDF template and one check format per bank account.
Added check printing setting Print Mode. The print mode controls how checks are printed (via the Browser, One Click Print)
Added ability to optionally wrap text in the memo/description remittance row based on a fixed number of characters per row and/or a regular expression pattern. This feature can be enabled using the Memo Line Wrapping Enabled setting. The Memo Max Characters Per Line setting controls the max characters per line. Memo Line Break Pattern can be used to manually control when the lines in the memo should wrap to the next line.
Added ability to disable editing of the First Check Number using the Disable First Check Number Override field on the check settings.
Added ability to override the sorting of remittance lines using the Remittance Line Sort Order check setting. Lines can be sorted by Transaction Date (default) or by Invoice Number.
Added ability to default the Check Format and/or Check Printer (for One Click Print) by Role and/or Location on the check settings screen.
Added a confirmation screen after pressing Print on the check printing screen.
Added the ability to process up to 5 batches of checks in parallel.
Added a status screen to see the status of all batches of checks in process of being printed. By default, this screen will only show batches of checks created by the current user but can be adjusted to show all users.
Added support of a server-side version of One Click Print.
Changes:
Company-level settings have moved from Company General Preferences to Setup > Check Printing >e Settings. Existing settings on the Company General Preferences will be automatically copies to the new settings page.
The ability to enabled test mode (for development purposes) has been moved to the check print settings screen. Test mode at the template level is no longer used.
Ready to Print on the Check Print Job record remains checked after printing a batch of checks. Check Print Jobs only need to be made active again (by an Admin) to reprint a batch of checks.
Bug Fixes:
None
Release 2.0.1
New Features:
Remittance lines can now be sorted by up to two different criteria. This includes custom fields.
Changes:
Performance improvements when looking up Vendor Credits applied to a Vendor Payment.
Governance usage has been reduced.
Bug Fixes:
Fixed issue preventing submission of the check print queue in 2022.1.
Fixed a typo on the Check Format record. The “Fractional Routing Number Line” field was spelled as “Factional Routing Number Line.”
Fixed issue that allowed the check PDF to be refreshed once viewed.
Release 2.0.2
New Features:
None
Changes:
Vendor Credits included in the Check Template apply list now include the “appliedto” variable. This variable includes the transaction reference number the credit is applied against.
Bug Fixes:
None
Release 2.0.3
New Features:
None
Changes:
Updated the process used to validate license keys.
Added automated analytics collection to give SquareWorks more visibility into features being used. This helps with future support and maintenance. Analytics are collected weekly and are automatically sent to SquareWorks. The following is collected:
Number of checks printed (total count)
Number of check formats (total count)
Number of PCL5 templates (total count)
Number of PDF templates (total count)
Print mode enabled (e.g. PDF, OCP)
Bug Fixes:
None
Advanced Document Management [289838]
Release 1.2.5
New Features:
Added functionality for AAB CLI (1.2.5+) to generate upload configs from file cabinet files
Changes:
Added release-notes.txt
Bug Fixes:
None
Release 1.2.6
New Features:
None
Changes:
Removed use of MD5 when communicating with SquareWorks file service. Changed to SHA256.
Bug Fixes:
None
Release 1.2.7
New Features:
None
Changes:
Granted "SquareWorks AAB CLI" role access to the "SquareWorks: File API (RL)" restlet by default.
Bug Fixes:
None
Release 1.2.8
New Features:
None
Changes:
Enhanced ability to generate large upload configs from file cabinet files
Bug Fixes:
None
Release 1.2.9
New Features:
Added ability to automatically hide the file cabinet subtab (on the Communication tab) on all enabled record types. This feature can be enabled on the Advanced Attachments Settings page.
Changes:
None
Bug Fixes:
None
Release 1.2.10
New Features:
None
Changes:
None
Bug Fixes:
Fixed PDF inline display issues seen when using Google Chrome. Sometimes PDFs would fail to display when opening them inline.
Release 1.3.0
New Features:
The license key is now automatically retrieved from SquareWork’s license server. You no longer need to update the license key each year.
Changes:
None
Bug Fixes:
None
Release 1.3.1
New Features:
None
Changes:
None
Bug Fixes:
Prevented Outlook messages from being deleted (in Outlook) when dragged directly from Outlook into NetSuite.
Release 1.3.2
New Features:
None
Changes:
None
Bug Fixes:
Updated the included AAB CLI role’s permissions to allow view access to employee records (required in order to allow searching for the number of active licensed employees). This was preventing the included role from working with the CLI when using AAB v1.3+.
Release 1.3.3
New Features:
None
Changes:
None
Bug Fixes:
Fixed the file list’s ability to sort by created date.
Release 2.0.0
New Features:
The following features have been added to the AAB Basic edition:
Automatic organization of files in the File Cabinet based on subsidiary and record type.
Support for file cabinet folder permissions (Groups)
Improved settings screens in NetSuite (Settings v2). The Settings v2 screen is currently only applicable to AAB Basic.
Added support for split screen PDF viewing.
Added support for body-level drag and drop area.
Changes:
None
Bug Fixes:
None
Release 2.0.1
New Features:
If a File Cabinet folder is deleted within the SquareWorks Advanced Attachments folder, folders will automatically be re-created when new files are attached. If files were deleted, they will not be restored when the folder is re-created. This only applies to AAB Basic edition.
Changes:
None
Bug Fixes:
Body and line fields configured to reference attachments now correctly show links to view the file when viewing a record. This only applies to AAB Basic edition.
Release 2.0.2
New Features:
Files attached within AAB Basic edition will be attached to the record (native files tab) as well as the AAB files tab. If a file is removed from the AAB files tab (by using the delete link) the file in the file cabinet will be detached from the record and removed from the native files tab.
Changes:
The maximum number of files that can be uploaded when creating a record has be reduced from 20 to 10 to support attaching files to the record on the native files tab.
Bug Fixes:
None
Release 2.0.4
New Features:
The drag and drop area’s size can be updated via Advanced Attachments Record Type settings.
Added ability to disable files from being attached to the natives file tab when using the Basic edition.
Changes:
None
Bug Fixes:
None
Release 2.0.5
New Features:
None
Changes:
None
Bug Fixes:
Copy records sometimes resulted in a script error after the copied record had been saved.
Release 2.1.1
New Features:
Added ability flag a SquareWorks File record as being uploaded manually to AWS S3 (Standard Edition only). Checking this box will prevent Advanced Attachments from adding the internal id of the SquareWorks File record to the file name when looking up & downloading the file in AWS S3.
Changes:
Remove SquareWorks File and SquareWorks File Reference records from the global search in NetSuite.
Bug Fixes:
None
Release 2.1.2
New Features:
Record Type Settings (v2 Settings) has been updated to include all scriptable record types in the NetSuite account.
Changes:
Removed the need to grant view access to SquareWorks File Reference records when using body or line level SquareWorks File Reference fields.
Bug Fixes:
None
Release 2.1.3
New Features:
None
Changes:
Reduced governance usage.
Bug Fixes:
Resolved issue displaying the loading mask in 2022.1, preventing the ability to upload new files.
Resolved issue that was causing the page to scroll down to a custom attachment select field on page load.
Resolved issue that was causing open/download icons to appear in a custom attachment select field if no file is selected.
Release 2.1.4
New Features:
When viewing/editing a SquareWorks File Reference record (via script or UI) a View File URL field is now visible. This field displays a URL that can be used to view the file. For files stored outside of NetSuite, the URL shown is pre-signed (does not require additional authentication) and will expire after 5 minutes. The internal of this field is custrecord_sw_aab_view_file.
Changes:
None
Bug Fixes:
Our client scripts have been updated & redeployed to avoid running into a rare dependency conflict with other 3rd party client scripts. Prior to 2.1.4, an alert would open on the screen indicating that there were timeout issues loading our client script.
Release 2.1.5
New Features:
None
Changes:
The setup menu options have been updated. Settings v1 menu has been renamed to Settings (Legacy) and Settings v2 has been renamed to Settings.
Updated the process used to validate license keys.
Added automated analytics collection to give SquareWorks more visibility into features being used. This helps with future support and maintenance. Analytics are collected weekly and are automatically sent to SquareWorks. The following are collected:
Legacy settings used or not used (Yes/No)
Record types where files are attached (e.g. Vendor Bill, PO)
Storage location (e.g File Cabinet, SquareWorks, AWS)
Number of files uploaded (total count)
Bug Fixes:
None
Advanced Help [450079]
Release 1.0.0
New Features:
Initial Release
Changes:
None
Bug Fixes:
None
Vendor Request [289947]
Release 1.1.1
New Features:
Added ability to CC an email address on all vendor / address request approved emails. You can define the CC address in Setup > Company > General Preferences > Custom Preferences.
Changes:
None
Bug Fixes:
None
Release 1.1.2
New Features:
None
Changes:
None
Bug Fixes:
Prevented issue that required Company Name to be populated when creating “Individual” type vendors.
Release 1.1.3
New Features:
None
Changes:
None
Bug Fixes:
Added filtering the included state fields based on the country selected. This allows NetSuite to show country-specific states in the drop down vis US-only states.
Release 1.1.4
New Features:
Updated the bundle to automatically renew the bundle’s license key.
Changes:
None
Bug Fixes:
None
Release 1.1.5
New Features:
None
Changes:
None
Bug Fixes:
Added support for single-subsidiary accounts.
Release 1.1.6
New Features:
None
Changes:
The rejection modal now uses the standard N/ui/dialog module.
Bug Fixes:
None
Release 1.1.7
New Features:
None
Changes:
Updated the process used to validate license keys.
Bug Fixes:
None
Journal Reversal [289946]
Release 1.0.1
New Features:
Added functionality to auto-populate Memo and Posting Period based on the original Journal Entry.
Changes:
None
Bug Fixes:
Updated the bundle to only run when used via the NetSuite UI. Other execution contexts (e.g. Web Services, Scripts) were running into issues when creating Journal Entries.
Release 1.0.2
New Features:
Updated the bundle to automatically renew the bundle’s license key.
Changes:
None
Bug Fixes:
None
Release 1.0.3
New Features:
None
Changes:
Updated the process used to validate license keys.
Bug Fixes:
None
Last updated
Was this helpful?
