Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0034042 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] 09. Financial management | major | always | 2016-09-20 18:28 | 2016-09-21 13:58 | |||
| Reporter | ngarcia | View Status | public | |||||
| Assigned To | Triage Omni OMS | |||||||
| Priority | urgent | Resolution | no change required | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Merge Request Status | ||||||||
| Review Assigned To | vmromanos | |||||||
| OBNetwork customer | OBPS | |||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Support ticket | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0034042: Documentation about how to manage error messages in accounting templates is needed | |||||||
| Description | Documentation about how to manage error messages in accounting templates is needed: Should IllegalStateException be launched or what should be returned instead? | |||||||
| Steps To Reproduce | * | |||||||
| Tags | OB3 Documentation | |||||||
| Attached Files | ||||||||
Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
Notes |
|
|
(0090135) vmromanos (viewer) 2016-09-21 13:58 |
Creating accounting templates is targeted only for advanced developers who know what they are doing. The wiki already has a well explained documentation about how to create this kind of classes: http://wiki.openbravo.com/wiki/How_to_create_a_Module_that_Overrides_Accounting [^] Managing exceptions inside the concrete implementation of an accounting template is a decision that must be taken by the developer in charge of developing the code, who can: silently ignore it, log it or raise it to be managed by the Accounting framework. There is no possible guide about it, and it's a business logic decision. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2016-09-20 18:28 | ngarcia | New Issue | |
| 2016-09-20 18:28 | ngarcia | Assigned To | => Triage Finance |
| 2016-09-20 18:28 | ngarcia | OBNetwork customer | => Yes |
| 2016-09-20 18:28 | ngarcia | Modules | => Core |
| 2016-09-20 18:28 | ngarcia | Triggers an Emergency Pack | => No |
| 2016-09-20 18:28 | ngarcia | Issue Monitored: networkb | |
| 2016-09-20 18:29 | ngarcia | Tag Attached: OB3 Documentation | |
| 2016-09-21 13:58 | vmromanos | Review Assigned To | => vmromanos |
| 2016-09-21 13:58 | vmromanos | Note Added: 0090135 | |
| 2016-09-21 13:58 | vmromanos | Status | new => closed |
| 2016-09-21 13:58 | vmromanos | Resolution | open => no change required |
| Copyright © 2000 - 2009 MantisBT Group |