1. open
day august 2012
erpnext.com anand doshi

2. what’s • supplier quotation
[released]
new
# new feature
• newsletter
[send newsletters to customer contacts, leads or
blog subscribers]
# new feature, unicode branch

3. fixes • check permissions in tree view
• save report filters in forms having multiple fields
with same name
# bug fix
• password reset
# unicode branch
• optimized patch to repost stock due to packing
list bug

4. in-house - users who are halfway into their erpnext trial
• auto-send reminder emails to
- paid users whose accounts are about to expire
[mails are also stored in communication and
tagged against serial nos.]
• auto-create lead on trial account setup
• blog - how erpnext uses erpnext

5. [ver. 3] headway • refactored - doc, controller, mapper, utils and
purchase request
what’s • complete purchase cycle
• versioning, audit trail
next • print formats - server side
• a better HR
• reports

6. some • Document is abehavior -of dict and dict]
[doc has dual
subclass
object
technical dictionary elements and object attributes
# coding is less verbose as python auto-segregates
details DocList is a subclass of list
•
[doclist has dual behavior - object and list]
# filtering a doclist is very intuitive
• DocListController parent class is the gatekeeper -
controls loading, validations, saving of a doclist
# better document integrity

7. didn’t
quite
get
that? Salman with bodyguards
Salman is now a bodyguard

8. thoughts store difference as json
• versions for masters, transactions
[doctype, name, modified, modified by, difference]
# effects: audit trail, knowledge base more wiki
like, allow on submit option deprecated, cancel
deprecated, auto-save after the first save, revert to
previous version
• print formats - server side
using jinja templates, can inherit / include other
print formats
# effects: predefined styling can be applied to any
print format, recurring invoices sent using selected
print format

9. little shifted to permissions, instead of doctype
• allow email, allow print, allow copy should be
things
• default print format option to be shifted to a
checkbox in the print format form
• address / contact to be a child table of party, lead,
employee
• refactor db schema generation
• email thread as a component of contact
mark / create contact based on raised by against
support ticket

10. wish-list • visual representation using d3.js)data with
interactivity (possibly
of report
• in developer mode, edit docfields from within the
form (possibly a form builder)
• wiki pages / knowledge base - tree style display
• print format editor with draggable elements
• scheduled reports