You can see the listing for pre-defined functions in the Definitions Editor by selecting Functions and then choosing any module in the Module List Pane. You can define your own functions as well. The list of function names appears in the Edit - Context Entry dialog box when you configure the Function binding.
A Localized String binding evaluates to a string whose representation may change depending on the locale. This can be a simple string, or it can accept parameters that evaluate to a string. The parameters are similar to a String binding. When entering a Localized String, there are two input values:
The desired Localized String is edited differently depending on whether you are editing a view within a System Module or a User Module. In a System Module, the localized string is typed in, whereas in a User Module it is selected from a drop-down list.
The localizations are stored in a properties file associated with the wcf.xml file that defines the module. However, depending on the application, these files may be stored in the file system, or in a database. The English text files are named strings.properties.
Other languages have their own set of files. For example, the corresponding French files are named strings_fr.properties. If the files required for your language do not currently exist, contact your system administrator about how to copy and edit the existing strings.properties files into the desired filename for your language, and install those new files.
The values in the properties files are in the form key=value. The key is an internal code used by the system. If you use a key that contains spaces, precede them with a backslash. For example, the key cpu usage is entered as cpu\ usage. The localized value of the selected string is displayed in the binding drop-down list tree.
A tree of all of the data available for the given Data Source ID is displayed. You select the desired data object by expanding the tree as required, and then clicking on a data element. This could represent a list of data objects, a single data object, or a simple property of a data object, such as a string property. This is somewhat similar to the Path parameter on a Query, or Context, or the Root Path property of a Query.
There are some significant differences between the usage of a Query binding and a Data binding. You do not have to specify the Data Source ID for queries to enable them to select from the default Data Source. By contrast, Data bindings do have to have their Data Source ID specified. As a result, they are generally only used for testing or in User Modules, never in System Modules because the Data Source ID in System Modules is not known in advance. Queries are much more flexible and powerful than Data bindings.