Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0034042Openbravo ERP09. Financial managementpublic2016-09-20 18:282016-09-21 13:58
Reporterngarcia 
Assigned ToTriage Omni OMS 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tovmromanos
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0034042: Documentation about how to manage error messages in accounting templates is needed
DescriptionDocumentation about how to manage error messages in accounting templates is needed: Should IllegalStateException be launched or what should be returned instead?
Steps To Reproduce*
Proposed Solution
Additional Information
TagsOB3 Documentation
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-09-20 18:28ngarciaNew Issue
2016-09-20 18:28ngarciaAssigned To => Triage Finance
2016-09-20 18:28ngarciaOBNetwork customer => Yes
2016-09-20 18:28ngarciaModules => Core
2016-09-20 18:28ngarciaTriggers an Emergency Pack => No
2016-09-20 18:28ngarciaIssue Monitored: networkb
2016-09-20 18:29ngarciaTag Attached: OB3 Documentation
2016-09-21 13:58vmromanosReview Assigned To => vmromanos
2016-09-21 13:58vmromanosNote Added: 0090135
2016-09-21 13:58vmromanosStatusnew => closed
2016-09-21 13:58vmromanosResolutionopen => no change required

Notes
(0090135)
vmromanos   
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.