Page History
...
Term | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
| Yellowfin content can have two possible states: Active and Draft. | ||||||||
| This is a user that manages the system. Generally Administrators create the source connections, views, and report categories and maintain all of the system options including users, security, and licences. Their role permissions are the least restricted, generally granting them access to all functionality available. | ||||||||
| These are predefined calculations that can be applied to fields in a report. They run after the results are returned from the database as they are not part of the SQL query. | ||||||||
| Rather than displaying each unique row (or all rows including repeats if 'Show Duplicate Records' is enabled), 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 is selected then Yellowfin will add all the numeric results together (or sum them) for each row. If Average is used, Yellowfin will display the average metric value for each row. | ||||||||
| This allows a view 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. | ||||||||
| These are User Prompt Filters that are applied to all reports on a single Dashboard Tab. | ||||||||
Animated Chart | . | ||||||||
| These are descriptions of an event attached to a date or date range and displayed on a report and/or chart. | ||||||||
| This is a sort option that moves from smallest/lowest to largest/highest value. This means that numeric values are sorted 0-9 and letters are sorted A-Z. | . | |||||||
| This aggregation returns the average value of a metric, ignoring NULL values. |
...
Styleclass | ||
---|---|---|
| ||
Term | Description | ||||||
---|---|---|---|---|---|---|---|
Benchmark | . | ||||||
| This is a method of distributing content. Email Broadcasts send emails to specified recipients that include a piece of content, such as a report. This is sent on a scheduled or once-off basis. |
...
Styleclass | ||
---|---|---|
| ||
Term | Description | ||||||
---|---|---|---|---|---|---|---|
Cache | . | ||||||
| This is a type of field that does not come directly from the database. It is created from a formula that may use database fields. | ||||||
| These are folders that are used to group content. Views, Reports, and Fields all use categories, with Reports using a Category > Sub Category structure to group and assign security. | ||||||
| A visual representation of data. Yellowfin has a wide range of chart types available. | ||||||
| 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 solution. | ||||||
| This is a report output option that allows metrics to be aggregated by multiple categories, displayed as Row and Column headers. | ||||||
| This function allows you to display multiple reports on the one Report Preview page. | ||||||
| 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. | ||||||
| This is a note attached to a report in order to discuss its design or results. | ||||||
| This is formatting that is triggered when a condition is met. A rule is applied to a field in the report and special formatting, such as highlighting, is applied if the data matches the rule. | ||||||
| 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. | ||||||
| This aggregation returns the total number of records in a field in a report. | ||||||
| This aggregation returns the total number of unique records in a field in a report. This means that if a record is found twice, it will only be counted the first time. | ||||||
| This method of linking two tables matches each row from the first table in the join to each row in the second table, multiplying the number of rows returned in the result. | ||||||
| Create, Read, Update, Delete. These options are used to define role permissions and relate to SQL statements, allowing the user to create (INSERT records), read (SELECT records), update (UPDATE records), and delete (DELETE records). | ||||||
| Cascading Style Sheet. This is a type of file used by 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. | ||||||
| Comma Separated Values. These files store data in plain text form, with each value, or column, separated by a comma character. Yellowfin allows you to import these files in order to report off their data. |
...
Term | Description | ||||||
---|---|---|---|---|---|---|---|
| This is a space to display multiple reports and charts in one place, allowing for interactive features to be used across them all at once. | ||||||
| This is where the data for your reports is stored, called a Data Source within Yellowfin. | ||||||
| This is the database Yellowfin retrieves results from. Administrators create a Source Connection in order to access the data. | ||||||
| This is a sort option that moves from largest/highest to smallest/lowest value. This means that numeric values are sorted 9-0 and letters are sorted Z-A. | ||||||
| A standard field in Yellowfin can either be classified as a 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. | ||||||
| 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. | ||||||
Distinct | . | ||||||
| Yellowfin content can have two possible states: Active and Draft. | ||||||
| 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. | ||||||
| This drill allows you to move up and down a hierarchy that is defined by the user during the drill process. | ||||||
| This drill allows you to move up and down a predefined hierarchy within a single report. | ||||||
| This drill allows you to click on a row in a summary report and open a related detail report, filtered by what made the row in the summary report unique. | ||||||
| These are rows with the same values across all columns in a result set. By default, Yellowfin applies DISTINCT to the SELECT SQL statements it generates, meaning that duplicate rows are not displayed. This can be changed on the Report Data page of the Report Builder. |
...
Styleclass | ||
---|---|---|
| ||
Term | Description | ||||||
---|---|---|---|---|---|---|---|
GeoPack | . | ||||||
. | |||||||
| GIS (Geographic Information System) Maps in Yellowfin refer to several chart types that make use of geographical information, in the form of Points or Polygons. | ||||||
| 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 uses points in GIS Mapping. | ||||||
| Polygons are sets of Points used to define a geographical shape. Examples of polygon shapes include the outlines of countries, states, territories, and regions. Yellowfin uses polygons in GIS Mapping. | ||||||
| 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 is used to summarise data. | ||||||
| These are the dashed lines displayed across the chart's plot background by default on charts with an x & y axis. | ||||||
| This is the alternating shading displayed with gridlines across the chart's plot background by default on charts with an x & y axis. | ||||||
| This is a list of users that is created in Yellowfin to assign content and security to. |
...
Term | Description | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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:
See CSV Data Imports and Export & Import Repository for more information. | In Memory DB | . | |||||||||||||
| This is a type of link, or join between two tables based on a specified join condition. Only rows that match the condition in both tables will be returned. | |||||||||||||||
| This is a single installation of 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. | |||||||||||||||
| This is the process of combining Yellowfin with an existing OEM system to create a system that feels seamless to the end user. | |||||||||||||||
| This is what the user interacts with. The Yellowfin interface is viewed through a web browser and contains all navigation and content. |
...
Term | Description | ||||||
---|---|---|---|---|---|---|---|
| This is what controls the y axis of a chart, determining the first and last values, as well as the increments used. | ||||||
| These allow you to break up a report into sub reports. The table and/or charts will be broken up so there is one per section, rather than one overall. | ||||||
Session | . | ||||||
| This is a piece of content created by an administrator which defines the method of accessing the reporting data source. | ||||||
| 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. | ||||||
| These are folders that reside within report categories and contain reports. Security is applied at this level in order to restrict access and functions available. | ||||||
| This aggregation adds all of the field values and returns the total. | ||||||
| Structured Query Language. This is the language Yellowfin uses to retrieve results from the database, returned as results in table and/or chart. | ||||||
| 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, report, and chart level. |
...
Term | Description | |||||||
---|---|---|---|---|---|---|---|---|
| These are used to index content to aid in searches.Timeline | . | ||||||
Tooltip | . |
U
Styleclass | ||
---|---|---|
| ||
Term | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
| This is an account created in order to allow a person to access the Yellowfin system. | ||||||||
| This is a type of filter that requires users to provide one or more values to restrict report results. | UUID | . |
V
Styleclass | ||
---|---|---|
| ||
...