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 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 for more information. |
...
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
...