Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] A. Platformminorhave not tried2019-05-06 09:352019-05-07 10:30
ReporteralostaleView Statuspublic 
Assigned Toplatform 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0040784: provide a consistent mechanism to load messages in client

DescriptionCurrently, messages defined in AD_Message are loaded in the client side according to one of these two mechanisms:

1. Back-office
  * Messages in core module: only those flagged as "Force Availability in Client"
  * Messages in any other module: all of them are loaded

2. Mobile applications (such as WebPOS or AWO)
  The messages available in the client are [1]:
    * The ones defined in Mobile Core Infrastructure module
    * The ones defined in current mobile application module
    * The ones defined in any module depending (at any level) on current mobile application module

This has some inconveniences:

1. Inefficiencies: messages intended to be used only by backend processes are also loaded in the client
2. Some cases are not covered: for example, having a module A that depends on mobile.core, and a module B that depends on A and WebPOS, messages defined in A cannot be made available in WebPOS client

[1] [^]
Steps To Reproduce-
Proposed SolutionThere should be a single mechanism to decide which messages are loaded in the client, being the same for back-office and mobile applications.

AD_Message.isIncludeIni18n column should be replaced by another one defining the application the message is for. In case it is null, the message should not be loaded in any client at all (those messages would be only usable from backend processes).

We would need to provide a good mechanism (module script?) to populate this column with proper defaults in order to make a transparent transition where continue being loaded in the client following current rules.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks design defect 0040785 newRetail Retail Modules Move camera barcode scanner messages to its module 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2019-05-06 09:35 alostale New Issue
2019-05-06 09:35 alostale Assigned To => platform
2019-05-06 09:35 alostale Modules => Core
2019-05-06 09:35 alostale Triggers an Emergency Pack => No
2019-05-06 09:40 alostale Status new => acknowledged
2019-05-06 09:45 alostale Description Updated View Revisions
2019-05-06 10:23 jarmendariz Relationship added blocks 0040785
2019-05-07 10:30 alostale Type defect => design defect

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker