Foundation Projects

A few UI enhancing features by intern Prssanna: 1. Group By in Reports, 2. Link Popovers, 3. Show assignments by user in list view

Frappe Accounting is a simple stand-alone Desktop based accounting application for micro businesses. Interacting with ERPNext users over the years, a need for a simpler version has been felt multiple time and other than GNU Cash, there has been no good Free and Open Source Accounting Application. Frappe Accounting which is in "beta" currently is based on FrappeJS and Electron. The foundation has supported this project via the ERPNext Summer of Code 2018.

The goal is to enable business-to-business (B2B) discovery / communication and transaction inside ERPNext and convert it into a network. This project has been conceptualized long ago and has been built in spurts. The foundation has invested resources into pushing the project forward, but is still in "alpha" stage.

Merging DocType (schema) changes by merging JSON files was problematic and repetitive problem. This feature tries to resolve it by separating layout and ignoring falsy values resulting in much smaller diffs

A commonly requested feature was built-in support for qz-tray, a popular library for printing barcodes and labels from thermal printers. See details here

Item taxes in ERPNext were handled on the parent level and led to a complex data structure that made it hard to configure item specific taxes in the Item Master. With this feature, the user can select taxes in invoices per line item leading a much clear feature. The design is inspired from Frappe Accounting and included in Version 12.

Added first-class Subscription Management features including creation of Subscription Plans and Subscriptions that are independent of invoices. Until this feature, the only way to manage subscriptions in ERPNext was to set an invoice to "Auto Repeat" it self. Also separated Auto Repeat as a first class feature that could be applied to any document type.

Frappe Kotlin is a Frappe backed framework that was developed to build native mobile app for ERPNext. It was led by Foundation director Revant. Ultimately it was realized that the full scale of customization would be expected on the mobile app and refactoring the current framework in JS to build mobile views was a better idea.

There was no configurable "Cash Flow Statement" available in ERPNext. This feature allowed the user to configure accounts into "Financial", "Operational" and "Investing" activities and then generate a statement based on the configured structure.

Since Python 2 supporting is ending in 2020, the entire code base was migrated to support both Python 2 and 3. Version 11 of ERPNext is Python 3 ready and subsequent versions will drop Python 2 support. This project was helped by interns along with Foundation developers.

To help the ERPNext Foundation manage its members and memberships, non profit domain was added to ERPNext by the foundation developers. This module can now be used by any non profit looking to manage its members and volunteers in ERPNext

One of the primary expectations of foundation members was to improve the test coverage and stability of the product. To this effect, one of the first big investments of the foundation was to setup client side testing scripts in Selenium. Test were written by 3 engineers over a period of 3-4 months. Unfortunately Selenium tests were found to be extremely brittle and used to fail randomly on CI due to varying loads on the VMs provided. Ultimately it was decided to abandon this.

Create a new table in all sales and purchase transactions to define the payment schedule in case the payment was expected to be made in multiple steps. This feature was missing in ERPNext and now allowed users to map their receivables based on the payment schedule date.