| Age | Commit message (Collapse) | Author |
|---|
|
* analytic accounts can be shared among companies
* amount on analytic lines always refer to amount in company currency of which it belongs to
* add analytic groups (hierarchical way to classify analytic accounts)
* analytic tags:
- only present on analytic lines, not anymore on analytic accounts
- can be used to distribue/split an analytic lines among several analytic accounts
- enabled by a dedicated res.group
- added on several objects (vouchers, expenses, analytic defaults...) as well as in bank statement reconciliation widget (manual counterpart and account.reconcile.model)
* bunch of fixes made related to analytic
Was PR #22124. Was task 32386. Original work by tbe.
|
|
Major changes:
- Remove reports
- Simplify models
Reason: complete rewrite of the Sale module.
Responsible: fp, dbo, nim
|
|
|
|
Unify and refactor exception handling in framework and addons.
The generic `except_osv` is now deprecated, and replaced by more specialized exception subtypes:
- `UserError` (renamed from Warning, as it conflicts with the built-in `Warning`) raised when a non-technical error occurs during a business operation. It could be a missing information in the data provided by the user, or a misconfiguration.
- `AccessError`: raised when any operation is denied because the user conducting it does not have the required access rights.
- `AccessDenied`: raised when an operation that requires authenticated access is attempted via an unauthenticated request.
- `MissingError`: raised when an operation is attempted on a record that does not exist.
- `ValidationError`: raised when an operation violates a SQL or Python constraint.
- All other exceptions are internal errors due to a system problem or bug, and raised untouched to the client-side, which should display a traceback.
All exceptions take a single message argument.
The `test_exceptions` module has been updated to showcase both new and old (deprecated) exceptions.
A great many old `except_osv` had a useless title with "Error!" or "Warning", those have been removed, as this is handled by the client-side widget that displays the messages.
This commit introduces a more consistent policy for logging errors and warnings:
- All messages that do not require administrator attention should be logged at INFO level or lower. This includes all errors that are notified to the user in a friendly manner, even for access right problems or validation errors during business operations.
- All messages that indicate a likely misconfiguration or malicious use by the users should be logged at WARNING level, as they typically require administrator attention.
- All other unhandled internal errors cannot typically be handled by the user and should be logged at ERROR or higher level, as they require immediate administrator attention.
|
|
bzr revid: fp@tinyerp.com-20111212181113-mhnnbps3ip8ls6pp
|
|
bzr revid: ara@tinyerp.com-20101004111801-o8dw16eiiprukkou
|
|
group to account module.
bzr revid: vra@tinyerp.com-20100914122438-npaqxmpfqiemufgv
|
|
account module.
bzr revid: vra@tinyerp.com-20100914112946-6166xvm1lp1xy881
|
|
[REM] Extended group for analytic related menus.
[FIX] Analytic Entries date Order.
[FIX] Assigning sale price with proper sign in product_id onchange in analytic line.
bzr revid: vra@tinyerp.com-20100907115728-n09gkjycdr32ej77
|
|
on menus related to analytic accounting, removed access rules for anaytic accounting
bzr revid: pap@tinyerp.co.in-20100903124403-o1gbrd38nc047vhx
|
|
for it
bzr revid: pap@tinyerp.co.in-20100901073017-w54ys7g3v1qzr7tp
|
|
bzr revid: fp@tinyerp.com-20100206184737-4mbipft7xk3cv5f2
|
|
account from project and add analytic module + improvement in account_anglo_saxon
bzr revid: hda@tinyerp.com-20100205150927-ztj0oaw3d3mv4f34
|
