1.11 release notes

Submitted by ehu on Fri, 01/06/2023 - 13:35

This is Draft content, written for functionality that is in development and may not yet be released.

Be sure to check the UPGRADE NOTES below!

What's new in LedgerSMB 1.11

  • ...

New features

Feature 1

Description 1.

Note for upgrades: There is no impact on upgrades.

Reclassification of negative (current) assets to liabilities (and vice versa)

In it's common practice to present negative current assets as positive current liabilities. An example where this regularly happens is when a bank current account goes into overdraft: instead of the bank owing money to the company (an asset), the company owes money to the bank (a liability). This release adds a new configuration on the account settings screen: "Negative balance heading". This setting applies to asset and liability accounts.

When the "Negative balance heading" is set, when an asset account has a credit balance, it will be reported as a liability under the heading indicated in this option.

Note for upgrades: Users wanting to use this option need to explicitly set it on affected accounts after migration of the database completes.

Webservices for GIFIs, SICs, Types of Business, Price groups, Warehouses and Languages

Webservices have been created to manage configuration of a number of entities:

  • Countries (/erp/api/v0/countries)

These were created in support of moving the front-end to Vue3 components, with the intent to use them as a learning experience for further API development. Due to this approach, the services do not support filtering, sorting or paging yet. For more information on how to use these services, see  LedgerSMB Webservices.

Note for upgrades: There is no impact on upgrades.

Notable changes

Change summary 1

Explanation 1.

Note for upgrades: There are no consequences for upgrades: template sets used with 1.9 can be carried over without modification.

Upgrade notes

Sequences in System > Sequences switched to show "next value" instead of "last value"

If you use custom sequences, you need to increase the values in the Sequence column by 1 in order to prevent values from being used twice.

Background: The number shown in the "Sequence" column on the System > Sequences menu page, used to show the last value used. As of 1.11, it shows the next value that will be used. This ensures that value "1" in the sequence will be used now (it used to be skipped before), which helps auditability.