Correction:

The "Enhanced Preferences Project" is not included in
2.50MP17<http://wiki.openbravo.com/wiki/ERP/2.50/Release_Notes/2.50MP17>and
it will be available in the next Maintenance Pack.

Gorka

On Fri, May 14, 2010 at 13:53, Gorka Gil <[email protected]> wrote:

> Openbravo ERP 2.50MP17 is available!
>
> These are some of the new features included in this release:
>
>    - Enhanced 
> Preferences<http://wiki.openbravo.com/wiki/Projects/Enhanced_Preferences/Functional_Documentation>:
>    Now preference define also role as visibility level. Values for preferences
>    can be set by modules. Note that preference loading has slightly
>    
> changed<http://wiki.openbravo.com/wiki/Functional_Documentation/General_Setup#Upgrade_from_a_previous_MP>and
>  this could cause some warnings during the upgrade process.
>    - Build Validations and Module 
> Scripts<http://wiki.openbravo.com/wiki/Projects/BuildValidationsAndModuleScripts>:
>    This feature will allow developers of modules to add an initial build
>    validation which checks if some particular rule is fulfilled by the system,
>    before starting the build. It will also allow developers to add module
>    scripts, which are processes executed while the module is being built. If
>    you want to know how to create a build validation or a module script, you
>    can find more information 
> here<http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/How_to_create_build_validations_and_module_scripts>
>    - Tax Posting as 
> Expense<http://wiki.openbravo.com/wiki/Projects/Tax_As_Expenses/User_Guide>:
>    This feature will allow end-user to post non-deductible tax as an expense 
> in
>    case of specific tax rates setup as non-deductible tax and also at
>    Organization level for those organizations do not allow to deduct taxes at
>    all due to Organization type/activity.
>    - Users are locked after X failed login 
> tryouts<http://wiki.openbravo.com/wiki/Functional_Documentation/General_Setup#Log_in_security>:
>    This feature will allow to block a user in case of x failed login tryouts.
>    It is optional (and disabled by default) and can be configured through the
>    
> Openbravo.properties<http://wiki.openbravo.com/wiki/Openbravo.properties#Log_in_security>
>    .
>    - *Log/report to show failure in login*: Failed login attempts are now
>    logged including the failure cause (incorrect user/password, limit
>    concurrent users reached, etc.) and can be queried from the *General
>    Setup || Security || Session* window.
>
> Check the release notes for more information:
> http://wiki.openbravo.com/wiki/ERP/2.50/Release_Notes/2.50MP17
>
> Gorka
>
------------------------------------------------------------------------------

_______________________________________________
Openbravo-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-development

Reply via email to