Page History
...
Styleclass | ||
---|---|---|
| ||
A
Styleclass | ||
---|---|---|
| ||
...
Term | Description | ||||||
---|---|---|---|---|---|---|---|
| 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. | ||||||
| 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. |
E
Styleclass | ||
---|---|---|
| ||
Term | Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| This is the inclusion of Reports, Charts, and Dashboards in an external webpage using the Javascript API. | |||||||||||||
| This is a function that takes something outside of the system. There are two types of export in Yellowfin:
See Exporting Report Content, Exporting Your Dashboard, and Export & Import Repository Importing or Exporting Pre-existing Data for more information. |
F
Styleclass | ||
---|---|---|
| ||
...
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 Importing or Exporting Pre-existing Data for more information. | |||||||||||||
| 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 | ||||||
---|---|---|---|---|---|---|---|
| A Join is an SQL term that describes the logic around joining multiple tables together in order to return results from both tables. | ||||||
| This is what allows Yellowfin content to be embedded in external web pages. There is basic and advanced usage options. |
K
...
Term | Description | ||||||
---|---|---|---|---|---|---|---|
| This aggregation returns the largest value found in the field. | ||||||
| This is a field or filter that is required by a report in order to complete the building process or to return results. | ||||||
| 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. | ||||||
| A standard field in Yellowfin can either be classified as a Metric or 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. | ||||||
| This aggregation returns the smallest value found in the field. | ||||||
| This is a colour setting available to charts which, instead of using the default colours defined in Report Styles, the chart uses different shades of one colour selected by the user. | ||||||
| This is when a single instance of software runs to serve multiple clients or tenants. Yellowfin's multi-tenancy functionality is called Client Organisations. |
...
Term | Description | ||||||
---|---|---|---|---|---|---|---|
| This is an image based heat map created in 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 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. | ||||||
| Yellowfin allows relationships to be created between reports. Related Reports either take the form of Drill Through or Co-Display. | ||||||
| This is the result of an SQL query displayed in Yellowfin. The display can take the form of a table and/or chart. | ||||||
| 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 Yellowfin providing a set of sample roles with the initial installation. | ||||||
| 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. |
...
Term | Description | ||||||
---|---|---|---|---|---|---|---|
| This is a metadata layer created by an administrator that sits between the source connection and Report Builder that defines the fields available to report writers and the join logic required to generate SQL queries. | ||||||
| These are a View component that allows an administrator to enter an SQL query and treat the results as a table in the view. |
...
Term | Description | ||||||
---|---|---|---|---|---|---|---|
| Extensible Markup Language. XML is a markup language, like HTML, that was designed as a way transporting data, where HTML designs ways to display it. Yellowfin uses this language to create export files that transport report and other content definitions. |
Y
Styleclass | ||
---|---|---|
| ||
...