But if you think about it the sense of the system element table are cases where words are used in different contexts. And one problem is that often these different contexts cry for different help texts.
e.g. every table in the database uses "Org_ID". There is a very universal helptext for this. But there are some tables that do make more sense using this field and some don't. There are some tables that could profit from a better documentation which wonderful things you can do with the Org_ID field exactly at this point. But we can not enhance the help text for a single instance of Org_ID. In toto this leaves the help facility mostly useless for users. I would like to enhance the documentation in this point.
One solution could be to let the language pack importer export/import the System Element references and "centrally maintained" value too. So we can break it up where we write specialized texts in the translation.
Another solution could be to globally divide up most of the Elements that are used by more than one table into many Elements. We could do this in one big turn or one after each other while enhancing the help texts. This will also enhance the standard texts - But: this will break all other language packs.
Thomas
Environment
None
Attachments
1
16 Jan 2013, 09:58 PM
Activity
Carlos Ruiz
April 15, 2015 at 11:15 PM
same workaround seems to be valid here - uncheck IsCentrallyMaintained to change specific contexts
Hiep Lq
August 26, 2013 at 3:03 PM
Hi Thomas Bayen. I don't know way communicate in wiki. because I comment here.
nmicoud, can you explain what the "manual" checkbox is for? I understand that the record becomes unused (and useless) when "manual" is not activated. Then you can not activate it with the bulk Context Transfer but only with the "Modifier" Button in the Translation Context window.
Nicolas Micoud
January 16, 2013 at 9:58 PM
As discussed in today meeting, here a quick documentation on the functionnality i've made
There are reasons for the system elements to be divided up. One example are words that are used in different contexts but are not translateable in one single word in every language (see my "rate" issue https://idempiere.atlassian.net/browse/IDEMPIERE-551#icft=IDEMPIERE-551).
But if you think about it the sense of the system element table are cases where words are used in different contexts. And one problem is that often these different contexts cry for different help texts.
e.g. every table in the database uses "Org_ID". There is a very universal helptext for this. But there are some tables that do make more sense using this field and some don't. There are some tables that could profit from a better documentation which wonderful things you can do with the Org_ID field exactly at this point. But we can not enhance the help text for a single instance of Org_ID. In toto this leaves the help facility mostly useless for users. I would like to enhance the documentation in this point.
One solution could be to let the language pack importer export/import the System Element references and "centrally maintained" value too. So we can break it up where we write specialized texts in the translation.
Another solution could be to globally divide up most of the Elements that are used by more than one table into many Elements. We could do this in one big turn or one after each other while enhancing the help texts. This will also enhance the standard texts - But: this will break all other language packs.
Thomas