Page History

This refers to when a value is entered and set, rather than allowing a user to change it. In 15630910 a report writer can hard code filter values, or values in calculated fields. This means that the user is not prompted to provide a value, rather it is always the value the report writer set.
The alternative in these cases is to implement user prompt filters, or use parameters in their calculations.
See Filters for more information

Hexadecimal (Hex) is a base 16 number system, using symbols 0-9, A, B, C, D, E, and F to represent values 0 to 15.
HTML and CSS use Hex to identify colours by assigning to digits to each colour; 2 x Red, 2 x Green, and 2 x Blue respectively, and prefixed with a hash (#) symbol.
15630910 uses Hex codes to identify colours throughout the system, as well as in its 15630910 files.
See http://www.w3schools.com/html/html_colors.asp for more information.

This is a report that has been set to not display in the Report List. Generally heavily detailed reports that are used as children in a drill through relationship are hidden, as they are designed to be accessed through the parent report, not on their own.
See Report Formatting for more information.

HyperText Markup Language. HTML is a markup language, like 15630910, that was designed to display data in a web browser, used by 15630910 in combination with 15630910.
See Custom Header & Footer for more information on Yellowfin use of custom HTML files, and http://www.w3schools.com/html/ for general HTML information.

Online Analytical Processing.

This option is used when a Report Reader does not specify a value for a filter. This option is not available for mandatory filters.
See Filter Formatting for more information.

Organisation Reference Code. These are a method of mapping data values from the database to descriptions, as well as assigning a custom sort order. Org Ref Codes are also used as part of the Raster Map setup process.
See Reference Code Use for more information.This is old terminology no longer used for reference codes. Some areas of the Yellowfin backend may still use this term, but the Yellowfin front-end has retired the phrase. 

This is a type of link, or join between two tables based on a specified join condition. In 15630910, the outer joins used are what's called Left Outer Joins. This means that all rows from the first table (or the left side) in the join will be included, and only rows have matches to these will be included from the second table (or the right side).
See Joining Tables for more information on Yellowfin's use of Outer Joins, and this blog: Visual Explanation of SQL Joins for general join information.

This is an image based heat map created in 15630910. The map itself is based on a raster image (created with pixels, rather than a vector image created with shapes). Yellowfin links a unique 15630910 code colour to a piece of data in the source database in order to create the heat map, using Org Ref Codes. GIF, JPEG, and PNG raster image files are accepted.
See Raster Maps for more information.

Reference Code. A reference code provides a means of mapping data values from the database to more reader-friendly descriptions. For example, a database with a field for Y and N could be mapped to new values of Yes and No for easier reading. Reference codes can also be used to assign custom sort orders, colors and images, as well as translations in (in multi-language deployments only)
See Reference Codes for more information.

15630910 allows relationships to be created between reports. Related Reports either take the form of Drill Through or 15630910.
See Related Reports for more information

This is the result of an 15630910 query displayed in 15630910. The display can take the form of a table and/or chart.
See Reports Overview for more information

This is a user that is responsible for creating the report and chart content in the system.

A set of permissions and functions designed to be assigned to Users of the system. Different roles should be created for different types of user, with 15630910 providing a set of sample roles with the initial installation.
See Roles for more information.

This allows the user to return to a previous version of content, such as a view. In order for a rollback to be available, the cloning edit method must have been used.
See View Management for more information