Preference - Revision history

Wikiadmin: /* Preferences Values */

2018-10-22T07:05:53Z

‎Preferences Values

2018-10-22T07:05:38Z

‎Preference Priority

2018-10-22T07:04:15Z

‎Introduction

2018-10-22T07:03:48Z

‎Preference

2018-10-22T07:03:30Z

‎Preferences Definition

2018-10-22T07:02:43Z

‎Preferences Values

2018-10-22T07:01:38Z

‎Preferences Values

2018-10-22T07:01:12Z

‎Preferences Values

2018-10-22T07:00:45Z

‎Preference Priority

2018-10-22T06:59:25Z

‎Preference Priority

@@ Line 122: / Line 122: @@
 ** If all the above levels are same then it will and will consider preference with column '''"selected"=true'''.
-=== Preferences Values ===
+=== '''Preferences Values''' ===
 ----
 When logging in Openbravo or changing the role or the organization, the preferences visible for that user, role, client, organization or window are stored in the Openbravo session. Those session values can be obtained by using the method: org.openbravo.erpCommon.utility.Utility.getContext method.

@@ Line 97: / Line 97: @@
 * Window - if this level is set to a given window, only that window will be able to see that preference.
-=== Preference Priority ===
+=== '''Preference Priority''' ===
 ----
 Preference Priority section defines priority of multiple preferences defined for same Property

@@ Line 1: / Line 1: @@
 {{BackTo|General Setup}}
-=== Introduction ===
+=== '''Introduction''' ===
 ----
 A preference is a type of session value which can either be an attribute or a property.

@@ Line 22: / Line 22: @@
 * Above preference means that every user loging in Openbravo will get that feature working regardless its role and user and the client or the organization it is working on.
-=== Preference ===
+=== '''Preference''' ===
-<hr>
+----
 Preference window allow to define and maintain session values which can be visible and therefore applied to different levels such as Client, Organization, User, Role and Window.

@@ Line 26: / Line 26: @@
 Preference window allow to define and maintain session values which can be visible and therefore applied to different levels such as Client, Organization, User, Role and Window.
-=== Preferences Definition ===
+=== '''Preferences Definition''' ===
 ----
 [[File:Preference1.png]]

← Older revision		Revision as of 07:02, 22 October 2018
Line 137:		Line 137:

	{{BackTo\|General Setup}}		{{BackTo\|General Setup}}
−
−	~~[[Category:User_Guide]] [[Category:Generated Doc]]~~

@@ Line 127: / Line 127: @@
 Additionally:
-* It is possible to look for the value of a given preference by using the method: org.openbravo.erpCommon.businessUtility.Preferences.getPreferenceValue.<br />
+* It is possible to look for the value of a given preference by using the method: org.openbravo.erpCommon.businessUtility.Preferences.getPreferenceValue.<br />This method shows an exception in case:
 ** a preference property has not a value defined for the required visibility level
 ** or there is a conflict caused by the definition of more than one property values for the same preference property for a given visibility level

← Older revision		Revision as of 07:00, 22 October 2018
Line 121:		Line 121:
	* '''SAME PRIORITY''':		* '''SAME PRIORITY''':
	** If all the above levels are same then it will and will consider preference with column '''"selected"=true'''.		** If all the above levels are same then it will and will consider preference with column '''"selected"=true'''.
		+
		+	=== Preferences Values ===
		+	----
		+	When logging in Openbravo or changing the role or the organization, the preferences visible for that user, role, client, organization or window are stored in the Openbravo session. Those session values can be obtained by using the method: org.openbravo.erpCommon.utility.Utility.getContext method.
		+
		+	Additionally:
		+	* It is possible to look for the value of a given preference by using the method: org.openbravo.erpCommon.businessUtility.Preferences.getPreferenceValue.
		+	This method shows an exception in case:
		+	** a preference property has not a value defined for the required visibility level
		+	** or there is a conflict caused by the definition of more than one property values for the same preference property for a given visibility level
		+	Conflicts can be manually resolved by checking and modifying the preference.
		+