Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0040784Openbravo ERPA. Platformpublic2019-05-06 09:352022-02-01 08:07
alostale 
Triage Platform Base 
normalminorhave not tried
acknowledgedopen 
5
 
 
Core
No
0040784: provide a consistent mechanism to load messages in client
Currently, 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] http://wiki.openbravo.com/wiki/Mobile_Internationalization#Available_Labels [^]
-
There 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.
No tags attached.
blocks design defect 0040785 new Retail Retail Modules Move camera barcode scanner messages to its module 
Issue History
2019-05-06 09:35alostaleNew Issue
2019-05-06 09:35alostaleAssigned To => platform
2019-05-06 09:35alostaleModules => Core
2019-05-06 09:35alostaleTriggers an Emergency Pack => No
2019-05-06 09:40alostaleStatusnew => acknowledged
2019-05-06 09:45alostaleDescription Updatedbug_revision_view_page.php?rev_id=18710#r18710
2019-05-06 10:23jarmendarizRelationship addedblocks 0040785
2019-05-07 10:30alostaleTypedefect => design defect
2022-02-01 08:07alostaleAssigned Toplatform => Triage Platform Base

There are no notes attached to this issue.