It is with great delight to announce that after many months of developments we are now releasing an enhanced version of OpenERP 6.1 webclient + server. A video perhaps can tell more than 1000 words, so there we go, but below is the list of some features that come with it, out future plans and where to get it from/how to install. Enjoy!
Technical libraries enhancements:
- Latest Jquery 2.0.3 library.
- Ckeditor for rich text editing. In line with OpenERP v8 version.
- Grunt theme selector. Now you can have multiple web-themes.
- Google closure compiler for JS minification. Compression and optimisation of JS
- Webhostinghub Glyph icons. Tons of new icons can be used.
- Multiple web-tabs.
- Right-click in lists views – copy, paste, duplicate.
- Right-click on lists – custom functions: can do reconcile/unreconcile for example.
- Right click – export to excel.
- New business theme – inspired by v7/v8.
- Ability to permanently hide or expand top filters.
- Hide or show right hand side bar.
- Company logo as ERP logo – inspired by v7/v8.
- Users avatar – inspired by v7/v8
- Editable and working one2many and normal list views.
- Server with subdomains – ability to deploy as a SAAS.
- soft_readonly on fields – this is to be set on field definition of the model as soft_readonly=[‘group_id1’, ‘group_id2’]. when this is set, the field will be readonly when seen by user, but writeable by on_change functions for this particular group. other groups will see this field as read and write. If we also set readonly_priority=True, then this works the other way around: all groups will see read, but the ones defined in soft_readonly will be both: read/write. When is set soft_readonly = “1? in view, that field will be not editable for all groups.
- access_groups – This is to be used when we want a certain field fully hidden from the operator in xml. the normal groups=”group1,group2? will still need that particular model that this is linking to be granted access to, whereas access_groups=”ea_support.support_admin,ea_support.support_manager,ea_support.support_developer” will not require and thus won’t give warning messages that the operator that doesn’t have access to read the target model.
- Bold – To make tree view lines text have bold font add attribute colors=”bold:state==’‘”. Condition In brackets can be specified.
- move_forward – This can be added to a many2one or date field in xml as . When the operator selects a value from such field, the cursor will automatically move to the next field, thus saving him from having to press tab or moving the mouse to the next field.
- PostgreSQL 9.3+ materialised views. The server comes with functions that enable the use and refresh of materialised views.
In terms of future enhancements we have on the list:
- Clean up more code.
- Optimise the memory utilisation on both: server and browser.
- Enable mobile web views.
- Optimise/replace and clean up more libraries: Calendar, Gantt, Graphs etc.
Enapps OpenERP v6.1 Maintenance service
At the same time we are now also preparing to launch ‘Enapps OpenERP v6.1 Maintenance service’ to those that have OpenERP 6.1 and do not want to migrate to v7 or v8. The service is designed for OpenERP partners that need to support their 6.1 implementations. This will be a subscription based service and will allow partners and companies to submit bugs, feature enhancement requests and have access to our latest development branches. Please email us for more info.
Where to get it from?
How to install it?
Github repositories have the necessary instructions.