Page Comparison

{anchor:top}
{toc:class=glossaryContents}
h2. Overview
{styleclass: Class=topLink}[top|#top]{styleclass}
As with any new piece of software, there are new terms and names to learn. Here is a list of terms we use that are commonly asked about.

h2. A
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Active}*Active*|[Yellowfin|#Yellowfin] content can have two possible states: *Active* and [*Draft*|#Draft]. 
If the content is complete and the user has *Activated* it, the content will be in an *Active* state, which enables it to be used by other users. This means that the [View|#View] / [Report|#Report] / [Dashboard|#Dashboard] / [Category|#Category] / [Sub Category|#SubCategory], etc, can be used as designed.|
|{anchor:Administrator}*Administrator*|This is a user that manages the system. Generally Administrators create the [source connections|#SourceConnection], [views|#View], and [report categories|#Category] and maintain all of the system options including [users|#User], security, and licences. Their [role|#Role] permissions are the least restricted, generally granting them access to all functionality available.|
|{anchor:AdvancedFunction}[*Advanced Function*|Advanced Functions]|These are predefined calculations that can be applied to [fields|#Field] in a [report|#Report]. They run after the results are returned from the database as they are not part of the [SQL|#SQL] [query|#Query].
_See [Advanced Functions] for more information_|
|{anchor:Aggregate}*Aggregate*|Rather than displaying each unique row (or all rows including repeats if 'Show Duplicate Records' is enabled), [Yellowfin|#Yellowfin] will show one row per unique category (or combinations). You will select from a range of aggregation options to do this. For example, if [*Sum*|#Sum] is selected then Yellowfin will add all the numeric results together (or sum them) for each row. If [*Average*|#Average] is used, Yellowfin will display the average metric value for each row.
_See [Aggregation] for more information._|
|{anchor:Alias}*Alias*|This allows a [view|#View] [administrator|#Administrator] to provide a table with a new name during the first step of the View Building process. Aliases are often used when multiple copies of a table are used in the one view. 
_See [Aliases|Table Properties#Create Alias] for more information._|
|{anchor:AnalyticFilters}*Analytic Filters*|These are [User Prompt|#UserPrompt] [Filters|#Filters] that are applied to all reports on a single [Dashboard|#Dashboard] [Tab|#Tab]. 
_See [Analytic Setup] for more information._|
|*Animated Chart*|.|
|{anchor:Annotation}[*Annotation*|Report Annotation]|These are descriptions of an event attached to a date or date range and displayed on a [report|#Report] and/or [chart|#Chart].
_See [Report Annotation] for more information_|
|{anchor:Ascending}*Ascending*|This is a sort option that moves from smallest/lowest to largest/highest value. This means that [numeric|#Numeric] values are sorted 0-9 and letters are sorted A-Z.|

|[*Auto Chart*|Chart Type Selection#AutoChart]|This is a sort option that moves from smallest/lowest to largest/highest value. This means that [numeric|#Numeric] values are sorted 0-9 and letters are
sorted A-Z.|


|{anchor:Average}[*Average*|Aggregation]|This [aggregation|#Aggregate] returns the average value of a metric, ignoring [NULL|#Null] values.
_See [Aggregation] for more information_|

h2. B
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|Benchmark|.|
|{anchor:Broadcast}[*Broadcast*|Broadcasting]|This is a method of distributing content. Email Broadcasts send emails to specified recipients that include a piece of content, such as a [report|#Report]. This is sent on a scheduled or once-off basis.
_See [Broadcasting] for more information_|

h2. C
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|Cache|.|
|{anchor:Calculation}[*Calculated Field*|Calculations]|This is a type of [field|#Field] that does not come directly from the database. It is created from a formula that may use database fields.
_See [Calculations] for more information_|
|{anchor:Category}[*Category*|Content Categories]|These are folders that are used to group content. [Views|#View], [Reports|#Report], and [Fields|#Field] all use categories, with Reports using a Category > [Sub Category|#SubCategory] structure to group and assign [security|#Security].
_See [Content Categories] for more information_|
|{anchor:Chart}[*Chart*|Report Builder - Charts Step]|A visual representation of data. Yellowfin has a wide range of chart types available.
_See [Report Builder - Charts Step] for more information_|
|{anchor:ClientOrg}[*Client Organisations*|Client Organisations]|[Yellowfin|#Yellowfin] has functionality called Client Organisations which allows multiple virtual instances of Yellowfin to reside in the same server instance. This provides a way to create content isolated within one organisation, hidden from other organisation users logging into the same server. This is Yellowfin's [Multi-Tenancy|#Multi-Tenancy] solution.
_See [Client Organisations] for more information._|
|{anchor:CrossTab}[*Cross Tab*|Table Layouts]|This is a report output option that allows metrics to be aggregated by multiple categories, displayed as Row and Column headers.
_See [Table Layouts] for more information._|
|{anchor:Co-Display}[*Co-Display*|Co-Display Reports]|This function allows you to display multiple [reports|#Report] on the one Report Preview page. 
_See [Co-Display Reports] for more information_|
|{anchor:Collaboration}*Collaboration*|This is when users work together to share insights into their data and the decision making process. Yellowfin provides features to assist the collaborative process including Comments, Discussions, and [Annotations|#Annotation].
_See [Collaboration] for more information._|
|{anchor:Comment}*Comment*|This is a note attached to a [report|#Report] in order to discuss its design or results.
_See [Comments] for more information._|
|{anchor:ConditionalFormatting}[*Conditional Formatting*|Conditional Formatting]|This is formatting that is triggered when a condition is met. A rule is applied to a [field|#Field] in the [report|#Report] and special formatting, such as highlighting, is applied if the data matches the rule.
Basic rules can also be applied to [charts|#Chart].
_See [Conditional Formatting] for more information_|
|{anchor:Condition}*Condition*|This is a filter that limits the rows returned from a table, set at the view level. This filter cannot be seen or removed at the report level.
_See [Table Conditions] for more information._|
|{anchor:Count}[*Count*|Aggregation]|This [aggregation|#Aggregate] returns the total number of records in a [field|#Field] in a [report|#Report].
_See [Aggregation] for more information_|
|{anchor:CountDistinct}[*Count Distinct*|Aggregation]|This [aggregation|#Aggregate] returns the total number of unique records in a [field|#Field] in a [report|#Report]. This means that if a record is found twice, it will only be counted the first time.
_See [Aggregation] for more information_|
|{anchor:CrossJoin}[*Cross Join*|Joining Tables]|This method of linking two tables matches each row from the first table in the [join|#Join] to each row in the second table, multiplying the number of rows returned in the result. 
{color:#CC0000}*Note:*{color} this join should be used with extreme caution, as it's only appropriate in a handful of cases, and has negative effects on performance if used incorrectly.
_See [Joining Tables] for more information on Yellowfin's use of Cross Joins, and this blog: [Visual Explanation of SQL Joins|http://www.codinghorror.com/blog/2007/10/a-visual-explanation-of-sql-joins.html] for general join information._||
|{anchor:CRUD}[*CRUD*|Roles]|Create, Read, Update, Delete. These options are used to define [role|#Role] permissions and relate to [SQL|#SQL] statements, allowing the user to create (INSERT records), read (SELECT records), update (UPDATE records), and delete (DELETE records).
_See [Roles] for more information_|
|{anchor:CSS}[*CSS*|Custom Images & CSS]|Cascading Style Sheet. This is a type of file used by [Yellowfin|#Yellowfin] to define style options for the system that cannot be configured through Administration. Yellowfin's CSS files can be customised during the integration process.
_See [Custom Images & CSS] for more information on customising CSS files for Yellowfin integration purposes, and [http://www.w3schools.com/css/] for general CSS information._|
|{anchor:CSV}[*CSV*|CSV Data Imports]|Comma Separated Values. These files store data in plain text form, with each value, or column, separated by a comma character. [Yellowfin|#Yellowfin] allows you to import these files in order to report off their data. 
_See [CSV Data Imports] for more information._|

h2. D
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Dashboard}[*Dashboard*|Dashboard]|This is a space to display multiple [reports|#Report] and [charts|#Chart] in one place, allowing for interactive features to be used across them all at once.
_See [Dashboard] for more information_|
|{anchor:Database}*Database*|This is where the data for your reports is stored, called a [Data Source|#DataSource] within [Yellowfin|#Yellowfin]. 
_See [http://en.wikipedia.org/wiki/Database] for more information_|
|{anchor:Data Source}[*Data Source*|Data Sources]|This is the database [Yellowfin|#Yellowfin] retrieves results from. Administrators create a [Source Connection|#SourceConnection] in order to access the data.
_See [Data Sources] for more information_|
|{anchor:Descending}*Descending*|This is a sort option that moves from largest/highest to smallest/lowest value. This means that [numeric|#Numeric] values are sorted 9-0 and letters are sorted Z-A.|
|{anchor:Dimension}[*Dimension*|Views#Field Types]|A standard field in [Yellowfin|#Yellowfin] can either be classified as a [*Metric*|#Metric] or *Dimension*. All text fields are automatically classified as Dimensions. The View Builder allows you to define numeric and date fields as Dimensions in order to be used in Drill Hierarchies, and limit the aggregations available to *Count* and *Count Distinct*.
Dimension fields retrieve the data that will provide the basis for analysis in a report. Dimensions typically retrieve character-type data (employee names, company names, etc.), or dates (years, quarters, etc.)
_See [View Builder - Field Types|Views#Field Types] for more information._|
|{anchor:Discussion}*Discussion*|This is a stand-alone comment thread that allows users to discuss general topics and decisions while referring to multiple pieces of content if required.
_See [Discussion] for more information._|
|Distinct|.|
|{anchor:Draft}*Draft*|[Yellowfin|#Yellowfin] content can have two possible states: [*Active*|#Active] and *Draft*. 
If the piece of content is currently being created or edited by a user, then the report will be in *Draft* mode. This means that other end users will not be able to see or use the content until the editing process is completed by *Activating* the content.|
|{anchor:Drill}[*Drill*|Dashboard Drill Analysis]|Drill refers to the action performed by a user by clicking on a hyperlink in a report that either steps into more detail in the same report, or opens a separate detail report related to the row that was selected.
There are three forms of *Drill* available in [Yellowfin|#Yellowfin]; [*Drill Down*|#DrillDown], [*Drill Anywhere*|#DrillAnywhere], and [*Drill Through*|#DrillThrough].
_See [Dashboard Drill Analysis] for more information._|
|{anchor:DrillAnywhere}[*Drill Anywhere*|Drill Anywhere Reports]|This [drill|#Drill] allows you to move up and down a hierarchy that is defined by the [user|#User] during the drill process.
_See [Drill Anywhere Reports] for more information._|
|{anchor:DrillDown}[*Drill Down*|Drill Down Reports]|This [drill|#Drill] allows you to move up and down a predefined hierarchy within a single [report|#Report].
_See [Drill Down Reports] for more information._|
|{anchor:DrillThrough}[*Drill Through*|Drill Through Reports]|This [drill|#Drill] allows you to click on a row in a summary [report|#Report] and open a related detail report, filtered by what made the row in the summary report unique.
_See [Drill Through Reports] for more information._|
|{anchor:DuplicateRecord}*Duplicate Records*|These are rows with the same values across all columns in a result set. By default, Yellowfin applies *DISTINCT* to the SELECT [SQL|#SQL] statements it generates, meaning that duplicate rows are not displayed. This can be changed on the Report Data page of the Report Builder.
_See [Report Data|Report Builder#Report Data] for more information._|

h2. E
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Embed}[*Embed*|Javascript API]|This is the inclusion of [Reports|#Report], [Charts|#Chart], and [Dashboards|#Dashboard] in an external webpage using the [Javascript API|#JavascriptAPI].
_See [Javascript API] for more information_|
|{anchor:Export}*Export*|This is a function that takes something outside of the system. There are two types of export in [Yellowfin|#Yellowfin]: 
{panel:borderColor=white|bgColor=white} 
# [Export of Data|Exporting Report Content] - allows the user to save a piece of content, such as a [Report|#Report], [Chart|#Chart], or [Dashboard|#Dashboard], as a CSV, DOC, PDF, RTF, Text, or XLS file.
# [Export of Content Definitions|Export & Import Repository] - allows the user to save an [XML|#XML] file containing definitions of selected content in order to back it up or transfer it to another [instance|#Instance].
{panel}
_See [Exporting Report Content], [Exporting Your Dashboard|Dashboard#Exporting Tab from dashboard], and [Export & Import Repository] for more information._|

h2. F
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Field}[*Field*|View Fields]|This is a column in the database that will be used to build reports. Fields can be used as Columns/Rows, [Sections|#Section], and [Filters|#Filter]. They are defined either as [Metrics|#Metric] or [Dimensions|#Dimension]. Calculations can also be created to use as fields, these are called [Calculated Fields|#Calculation]
_See [View Fields] for more information_|
|{anchor:Filter}[*Filter*|Filters]|These are [fields|#Field] that are being used to restrict the results returned in your [report|#Report] or [dashboard|#Dashboard]. There are several types of filter in Yellowfin:
{panel:borderColor=white|bgColor=white} 
# [User Prompt|#UserPrompt] - these filters allow the [user|#User] to define the value used
# [Hard Coded|#HardCoded] - these filters have the value set at the report writing stage and cannot be changed by the report reader.
# [Source|#SourceFilter] - these filters are created by an administrator and use the report reader's user details to restrict results to what's relevant to them.
{panel}
_See [Filters] for more information_|

h2. G
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|GeoPack|.|
|GIS Base Layer|.|
|{anchor:GISMap}[*GIS Map*|GIS Map]|GIS (Geographic Information System) Maps in [Yellowfin|#Yellowfin] refer to several chart types that make use of geographical information, in the form of [Points|#GISPoint] or [Polygons|#GISPolygon]. 
_See [GIS Map] for more information._|
|{anchor:GISPoint}[*GIS Point*|GIS Map]|Points are sets of latitude and longitude values used to define geographical locations. Examples of points include the location of customers, staff, and other points of interest. [Yellowfin|#Yellowfin] uses points in [GIS Mapping|#GISMap].
_See [GIS Map] for more information._|
|{anchor:GISPolygon}[*GIS Polygon*|GIS Map]|Polygons are sets of [Points|#GISPoint] used to define a geographical shape. Examples of polygon shapes include the outlines of countries, states, territories, and regions. [Yellowfin|#Yellowfin] uses polygons in [GIS Mapping|#GISMap].
_See [GIS Map] for more information._|
|{anchor:Granularity}[*Granularity*|Common View & Join Design Issues]|The level of detail in the data. Described as *coarse* through to *fine*. The finer the granularity, the more detail and less summarised the data is. [Aggregation|#Aggregate] is used to summarise data.
_See [Common View & Join Design Issues] for more information._|
|{anchor:Gridline}*Gridlines*|These are the dashed lines displayed across the [chart's|#Chart] [plot|#Plot] background by default on charts with an x & y axis. 
_See [Gridlines|Chart Formatting#Gridlines] for more information._|
|{anchor:Gridband}*Grid bands*|This is the alternating shading displayed with [gridlines|#Gridlines] across the [chart's|#Chart] [plot|#Plot] background by default on charts with an x & y axis.
_See [Gridlines|Chart Formatting#Gridlines] for more information._|
|{anchor:Group}[*Group*|User Groups]|This is a list of [users|#User] that is created in [Yellowfin|#Yellowfin] to assign content and security to.
_See [User Groups] for more information_|

h2. H
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:HardCoded}[*Hard Coded*|Filters]|This refers to when a value is entered and set, rather than allowing a user to change it. In [Yellowfin|#Yellowfin] a report writer can hard code [filter|#Filter] values, or values in [calculated fields|#Calculation]. 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|#UserPromt] filters, or use [parameters|#Parameter] in their calculations.
_See [Filters] for more information_|
|{anchor:HEX}*HEX*|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. 
[Yellowfin|#Yellowfin] uses Hex codes to identify colours throughout the system, as well as in its [CSS|#CSS] files.
_See [http://www.w3schools.com/html/html_colors.asp] for more information._|
|{anchor:Hidden}*Hidden*|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|#DrillThrough] relationship are hidden, as they are designed to be accessed through the parent report, not on their own.
_See [Report Formatting|Report Formatting#Display] for more information._|
|{anchor:HTML}[*HTML*|Custom Header & Footer]|HyperText Markup Language. HTML is a markup language, like [XML|#XML], that was designed to display data in a web browser, used by [Yellowfin|#Yellowfin] in combination with [CSS|#CSS].
_See [Custom Header & Footer] for more information on Yellowfin use of custom HTML files, and [http://www.w3schools.com/html/] for general HTML information._|

h2. I
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Import}*Import*|This is a function that allows you to add something to the system from an external file. There are two types of import in [Yellowfin|#Yellowfin]: 
{panel:borderColor=white|bgColor=white} 
# [Import of Data|CSV Data Imports] - allows the user or administrator to import [CSV|#CSV] files containing data they wish to report off. This can be done at the [View|#View] or [Report|#Report] level.
# [Import of Content Definitions|Export & Import Repository] - allows the user to transfer a set of Yellowfin content into a system using an [XML|#XML] file, either to restore old content, or transfer content from another [instance|#Instance].
{panel}
_See [CSV Data Imports] and [Export & Import Repository] for more information._|
|In Memory DB|.|
|{anchor:InnerJoin}[*Inner Join*|Joining Tables]|This is a type of link, or [join|#Join] between two tables based on a specified join condition. Only rows that match the condition in both tables will be returned.
_See [Joining Tables] for more information on Yellowfin's use of Inner Joins, and this blog: [Visual Explanation of SQL Joins|http://www.codinghorror.com/blog/2007/10/a-visual-explanation-of-sql-joins.html] for general join information._|
|{anchor:Instance}*Instance*|This is a single installation of [Yellowfin|#Yellowfin] running. Some systems may have multiple instances of Yellowfin running. In this case there is often a development instance, testing instance, and production instance. There may also be multiple instances for different production purposes, depending on requirements.|
|{anchor:Integration}[*Integration*|Integration]|This is the process of combining Yellowfin with an existing OEM system to create a system that feels seamless to the end user.
_See [Integration] for more information_|
|{anchor:Interface}*Interface*|This is what the user interacts with. The [Yellowfin|#Yellowfin] interface is viewed through a web browser and contains all [navigation|#Navigation] and content.|

h2. J
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Join}[*Join*|Joining Tables]|A Join is an [SQL|#SQL] term that describes the logic around joining multiple tables together in order to return results from both tables. 
_See [Joining Tables] for more information for more information on Yellowfin's use of Joins, and this blog: [Visual Explanation of SQL Joins|http://www.codinghorror.com/blog/2007/10/a-visual-explanation-of-sql-joins.html] for general join information._|
|{anchor:JavascriptAPI}[*Javascript API*|Javascript API]|This is what allows [Yellowfin|#Yellowfin] content to be [embedded|#Embed] in external web pages. There is [basic|Basic Use] and [advanced|Advanced Use] usage options. 
End users can access the basic functionality through the Yellowfin [interface|#Interface] by copying the generated embed javascript and pasting it in their external page. 
Advanced users and administrators can access the advanced functionality by following the examples outlined [here|Advanced Use]. 
_See [Javascript API] for more information._|

h2. K
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:KPI}[*KPI*|KPI Reports]|Key Performance Indicator. This is a figure used to monitor business performance, such as sales in dollars or units. Performance is tracked against a target and makes use of [Conditional Formatting|#ConditionalFormatting] alerts.
_See [KPI Reports|KPI Reports] for more information._|

h2. L
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:LDAP}[*LDAP*|LDAP]|Lightweight Directory Access Protocol. This is a way that [Yellowfin|#Yellowfin] can access directory information for [User|#User] authentication and [Group|#Group] management purposes. This allows Yellowfin access to be controlled externally organisation-wide.
_See [LDAP] for more information._|
|{anchor:Legend}*Legend*|This is a key that displays values used in a [chart|#Chart] or [report|#Report]. In a chart it displays what value is assigned to each colour. In a report it can display the [filter|#Filter] values applied, as well as any [conditional formatting|#ConditionalFormatting] rules defined.
_See [Chart Legends|Chart Formatting#Legend], [Filter Legends|Filter Formatting#Format Menu], and [Conditional Formatting Legends|#Report Formatting#Display] for more information_|
|{anchor:LineShape}*Line Shapes*|These are shapes added to line [charts|#Chart] in order to draw attention to each point of data.
_See [Line Shapes|Styling Charts#Chart Line Defaults] for more information._|

h2. M
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Max}[*Max*|Aggregation]|This [aggregation|#Aggregate] returns the largest value found in the [field|#Field].
_See [Aggregation] for more information_|
|{anchor:Mandatory}*Mandatory*|This is a field or filter that is required by a report in order to complete the building process or to return results.
_See [Mandatory Field/Filter|Field Access & Usage] and [Filter Formatting] for more information._|
|{anchor:Metadata}*Metadata*|This is a piece of content's descriptive information. It generally contains the Name, Description, and Category details for a Field, Filter, Report, View, etc.|
|{anchor:Metric}[*Metric*|Views#Field Types]|A standard field in [Yellowfin|#Yellowfin] can either be classified as a *Metric* or [*Dimension*|#Dimension]. Numeric and Date fields are classified as Metrics by default, but can be changed to Dimension if required. Metric fields have the full range of aggregations available to them. They also have different functionality available to them when used as filters. Metrics do not allow for prompts, as there are generally too many possible values available, so they have slider options available in order to allow users to easily define ranges. Metric filter values cannot be cached.
_See [View Builder - Field Types|Views#Field Types] for more information._|
|{anchor:Min}[*Min*|Aggregation]|This [aggregation|#Aggregate] returns the smallest value found in the [field|#Field].
_See [Aggregation] for more information_|
|{anchor:Monochrome}*Monochrome*|This is a colour setting available to [charts|#Chart] which, instead of using the default colours defined in Report Styles, the chart uses different shades of one colour selected by the user.
_See [Chart Formatting] for more information._|
|{anchor:Multi-Tenancy}[*Multi-tenancy*|Client Organisations]|This is when a single instance of software runs to serve multiple clients or tenants. [Yellowfin's|#Yellowfin] multi-tenancy functionality is called [Client Organisations|#ClientOrgs].
_See [Client Organisations] for more information._|

h2. N
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Navigation}[*Navigation*|System Navigation]|This is the way in which [users|#User] move around the [Yellowfin|#Yellowfin] [interface|#Interface]. There are various menus and buttons designed to move the user between pages and components of the system.
_See [System Navigation] for more information_|
|{anchor:Null}*NULL*|This is used to indicate a lack of data, or gap. [Yellowfin|#Yellowfin] generally displays these as blank with a 'NULL' tooltip when returned in a report.|
|{anchor:Numeric}*Numeric*|This is a [field|#Field] or value composed solely of numbers (0-9), without the inclusion of any alphabetic or special characters.|

h2. O
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:OLAP}*OLAP*|Online Analytical Processing.|
|{anchor:Omit}*Omit*|This option is used when a Report Reader does not specify a value for a [filter|#Filter]. This option is not available for [mandatory|#Mandatory] filters.
_See [Filter Formatting] for more information._|
|{anchor:OrgRefCode}[*Org Ref Code*|Organisation Reference Codes]|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|#RasterMap] setup process.
_See [|Organisation Reference Codes] for more information._|
|{anchor:OuterJoin}[*Outer Join*|Joining Tables]|This is a type of link, or [join|#Join] between two tables based on a specified join condition. In [Yellowfin|#Yellowfin], 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|http://www.codinghorror.com/blog/2007/10/a-visual-explanation-of-sql-joins.html] for general join information._|


h2. P
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Parameter}[*Parameter*|Parameters]|Parameters are a type of user input field in [Yellowfin|#Yellowfin]. They are designed to pass a value input by the user to a calculated field or filter(s). This allows you create [What If|#WhatIf] reports.
_See [Parameters] for more information._|
|{anchor:Plot}*Plot*|This is the area of the [chart|#Chart] bound by the axes. It does not include the title and legend areas.
_See [Plot|Chart Formatting#Plot] for more information._|
|{anchor:Portlet}*Portlet*|This is the space that contains a [report|#Report] on a [dashboard|#Dashboard] [tab|#Tab].
_See [Report Portlet] for more information._|
|{anchor:Prefix}*Prefix*|This is a symbol or character displayed before a value in a field. A common prefix to use is *$*. Prefixes can be defined at the [view|#View], [report|#Report], and [chart|#Chart] level.|
|{anchor:Private}*Private*|This is a piece of content that has access restrictions applied directly to it. Depending on the type of content, different restrictions can be applied:
{panel:bgColor=white|borderColor=white}
* [Dashboard|#Dashboard] - private dashboard tabs can only be accessed by the user that created the tab.
* [Report|#Report] - private reports can only be accessed by the user that created the report.
* [Comment|#Comment] - private comments can only be accessed by users that have been assigned permission to see both the report and the comment.
* [Annotation|#Annotation] - private annotations can only be accessed by users that have been assigned permission to see both the annotation and the report/view/comment they're attached to.
* [Discussion|#Discussion] - private discussions can only be accessed by users that have been assigned permission to see the discussion area and the thread itself.
{panel}|
|{anchor:Public}*Public*|This is a piece of content that may or may not have access restrictions directly applied to it, but generally designed for a far broader audience than that of [private|#Private] content. Depending on the type of content, different restrictions may be applied:
{panel:bgColor=white|borderColor=white}
* [Dashboard|#Dashboard] - public dashboards can be set to *Secure* or *Unsecure*. Secure dashboards have a list of users with various levels of access. Unsecure dashboards can be accessed by any dashboard user.
* [Report|#Report] - public reports can be accessed by any user that has permission to see the category/sub category it's stored in.
* [Comment|#Comment] - public comments can be accessed by any user that has permission to see the report they're attached to.
* [Annotation|#Annotation] - public annotations can be accessed by any user that has permission to see the report/view/org they're attached to.
* [Discussion|#Discussion] - public discussions can be accessed by any user that has permission to see the discussion area.
{panel}|

h2. Q
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Query}*Query*|This is the [SQL|#SQL] request that [Yellowfin|#Yellowfin] generates and sends to the [database|#Database]. It defines what results are required for the [report|#Report].|

h2. R
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:RasterMap}[*Raster Map*|Raster Maps]|This is an image based heat map created in [Yellowfin|#Yellowfin]. The map itself is based on a raster image (created with pixels, rather than a vector image created with shapes). Yellowfin links a unique [HEX|#HEX] code colour to a piece of data in the source database in order to create the heat map, using [Org Ref Codes|#OrgRefCode]. GIF, JPEG, and PNG raster image files are accepted. 
_See [Raster Maps] for more information._|
|{anchor:RelatedReport}[*Related Report*|Report Builder - Related Reports Step]|[Yellowfin|#Yellowfin] allows relationships to be created between [reports|#Report]. Related Reports either take the form of [Drill Through|#DrillThrough] or [Co-Display|#Co-Display].
_See [Report Builder - Related Reports Step] for more information_|
|{anchor:Report}[*Report*|Report Builder]|This is the result of an [SQL|#SQL] [query|#Query] displayed in [Yellowfin|#Yellowfin]. The display can take the form of a table and/or [chart|#Chart].
_See [Report Builder] for more information_|
|{anchor:ReportWriter}*Report Writer*|This is a [user|#User] that is responsible for creating the [report|#Report] and [chart|#Chart] content in the system.|
|{anchor:Role}[*Role*|Roles]|A set of permissions and functions designed to be assigned to [Users|#User] of the system. Different roles should be created for different types of user, with [Yellowfin|#Yellowfin] providing a set of sample roles with the initial installation.
_See [Roles] for more information._|
|{anchor:RollBack}[*Rollback*|View Management#Rollback]|This allows the user to return to a previous version of content, such as a [view|#View]. In order for a rollback to be available, the cloning edit method must have been used.
_See [View Management|View Management#Rollback] for more information_|

h2. S
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Scale}*Scale*|This is what controls the y axis of a [chart|#Chart], determining the first and last values, as well as the increments used.
_See [Chart Formatting] for more information._|
|{anchor:Section}[*Section*|Sections]|These allow you to break up a [report|#Report] into sub reports. The table and/or [charts|#Chart] will be broken up so there is one per section, rather than one overall.
_See [Sections] for more information_|
|Session|.|
|{anchor:SourceConnection}[*Source Connection*|Data Sources]|This is a piece of content created by an administrator which defines the method of accessing the reporting [data source|#DataSource].
_See [Data Sources] for more information_|
|{anchor:SourceFilter}[*Source Filter*|Source Access Filters]|These are filters applied to reports based on the user running the report. This means that a user will only ever see the data that is assigned to them through the Source Filter.
_See [Source Access Filters] for more information._|
|{anchor:SubCategory}[*Sub Category*|Content Categories]|These are folders that reside within [report|#Report] [categories|#Category] and contain reports. Security is applied at this level in order to restrict access and functions available.
_See [Content Categories] for more information_|
|{anchor:Sum}[*Sum*|Aggregation]|This [aggregation|#Aggregate] adds all of the [field|#Field] values and returns the total.
_See [Aggregation] for more information_|
|{anchor:SQL}*SQL*|Structured Query Language. This is the language [Yellowfin|#Yellowfin] uses to retrieve results from the database, returned as results in table and/or chart.
_See [http://www.w3schools.com/sql/] for more general SQL information._|
|{anchor:Suffix}*Suffix*|This is a symbol or character displayed after a value in a field. A common prefix to use is *%*. Suffixes can be defined at the [view|#View], [report|#Report], and [chart|#Chart] level.|

h2. T
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Tag}*Tag*|These are used to index content to aid in searches.|
|Timeline|.|
|Tooltip|.|

h2. U
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:User}[*User*|Users]|This is an account created in order to allow a person to access the [Yellowfin|#Yellowfin] system.
_See [Users] for more information_|
|{anchor:UserPrompt}[*User Prompt*|Filters]|This is a type of filter that requires [users|#User] to provide one or more values to restrict report results.
_See [Filters] for more information_|
|UUID|.|

h2. V
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:View}[*View*|Views]|This is a [metadata|#Metadata] layer created by an administrator that sits between the [source connection|#SourceConnection] and [Report Builder|#Report] that defines the [fields|#Field] available to report writers and the [join|#Join] logic required to generate [SQL|#SQL] [queries|#Query].
_See [Views] for more information_|
|{anchor:VirtualTable}[*Virtual Table*|Virtual Tables]|These are a [View|Views] component that allows an administrator to enter an [SQL|#SQL] [query|#Query] and treat the results as a table in the view.
_See [Virtual Tables] for more information_|

h2. W
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:WebService}*Web Service*|Web Services are used for managing communication between an OEM application and [Yellowfin|#Yellowfin]. The Web Services are [XML|#XML] based and independent of the programming language used to develop the OEM application.|
|{anchor:WhatIf}[*What If*|What If Analysis]|What If Analysis is a method of creating reports that make use of [Parameters|#Parameter] and Calculated Fields in order to test scenarios.
_See [What If Analysis] for more information._|
|{anchor:WMS}[*WMS*|WMS Layers]|Web Map Service. A WMS layer is a georeferenced map image loaded from a WMS Server. These are used as backgrounds and overlays for [GIS Maps|#GISMap] in [Yellowfin|#Yellowfin].
_See [WMS Layers] for more information._|

h2. X
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:XML}*[XML|Export & Import Repository]*|Extensible Markup Language. XML is a markup language, like [HTML|#HTML], that was designed as a way transporting data, where HTML designs ways to display it. [Yellowfin|#Yellowfin] uses this language to create export files that transport [report|#Report] and other content definitions. 
_See [Export & Import Repository] for more information_|

h2. Y
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:Yellowfin}[*Yellowfin*|http://www.yellowfinbi.com/]|Yellowfin is an easy-to-use report writer for non-technical users, delivering drag-and-drop simplicity for formatting and data selection. With Yellowfin, you can access information from multiple data bases without special coding knowledge. This is easy because you work with data in business terms that are familiar to you without the need to understand complex technology principles.
_See [http://www.yellowfinbi.com/] for more information._|

h2. Z
{styleclass: Class=topLink}[top|#top]{styleclass}
||Term||Description||
|{anchor:ZChart}[*Z Chart*|Special Purpose Charts#Z Chart Creation]|This is a type of [chart|#Chart] that displays trends over a specified period of time in the form of straight values, accumulative total, and moving total.
_See [Z Charts|Special Purpose Charts#Z Chart Creation] for more information_|

\\
\\
{horizontalrule}
{styleclass: Class=topLink}[top|#top]{styleclass}