Date: Fri, 29 Mar 2024 03:24:59 -0600 (MDT) Message-ID: <1319127310.2803.1711704299635@confluence-external-wiki> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2802_2123656788.1711704299635" ------=_Part_2802_2123656788.1711704299635 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Yellowfin is an easy-to-use report writer for non-technical users, deliv=
ering drag-and-drop simplicity for formatting and data selection. With Yell=
owfin, 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.
Business intelligence (BI) platforms allow organizations to build BI app= lications through analysis, information delivery (such as reports and dashb= oards) and platform integration (such as metadata management).
Here are some commonly used words that you will need to familiarize yourself with:
This is the database Yellowfin retrieves results from. Adminis= trators create a Source Connection in order to access the data. = See Data Sources for more information.
This is a me= tadata layer created by an administrator that sits between the&nbs= p;source connection and Report Builder that defines the = ;fields availa= ble to report writers and the join logic required to generate SQL queries.
See Prep= aring Data using Views for more information.
This is a space to display multiple reports and charts in one place, allowing for interac= tive features to be used across them all at once.
See our Dashboa= rd section for more information.
This is the result of an SQL query displayed in Yellowfin. The disp=
lay can take the form of a table and/or chart.
See our Reports section =
for more information
A visual representation of data. Yellowfin has a wide range of chart typ=
es available.
See Charts=
for more information
This is a single installation of Yellowfin running. Some syste= ms may have multiple instances of Yellowfin running. In this case there is = often a development instance, testing instance, and production instance. Th= ere may also be multiple instances for different production purposes, depen= ding on requirements.
This is the process of combining Yellowfin with an existing OEM system t= o create a system that feels seamless to the end user.
See Integrati= on for more information.
Key Performance Indicator. This is a figure used to monitor business per=
formance, such as sales in dollars or units. Performance is tracked against=
a target and makes use of Conditional Formatting alerts.
See=
KPI Reports for more=
information.
This is when users work together to share insights into their data and t=
he decision making process. Yellowfin provides features to assist the colla=
borative process including Comments, Discussions, and Annotations.
See Collaboration for more information.<=
/em>
Drill refers to the action performed by a user by clicking on a hyperlin=
k in a report that either steps into more detail in the same report, or ope=
ns a separate detail report related to the row that was selected.
There are three forms of Drill available in Ye=
llowfin; Drill Down, Drill Anywhere, and Drill Through.
=
See Dashboard Drill Analy=
sis for more information.
This is the way in which users move around the Yellowfin&=
nbsp;interface. There are various menus and buttons designed to move the us=
er between pages and components of the system.
See Navigation for more information
This is when a single instance of software runs to serve multiple client=
s or tenants. Yellowfin's multi-tenancy functionality is called&n=
bsp;Client Organis=
ations.
See Client Organisations for more information.
Yellowfin has functionality called Client Organisations which allow=
s multiple virtual instances of Yellowfin to reside in the same server inst=
ance. This provides a way to create content isolated within one organisatio=
n, hidden from other organisation users logging into the same server. This =
is Yellowfin's Multi-Tenancy solution.
See Client Organisations for more informat=
ion.
This is what allows Yellowfin content to be embedded =
;in external web pages. There is basic and advanced usa=
ge options.
End users can access the basic functionality through the Yellowfin interface by=
copying the generated embed javascript and pasting it in their external pa=
ge.
Advanced users and administrators can access the advanced functionality by=
following the examples outlined here.
See JavaScript API - old for more information.
This is a column in the database that will be used to build reports. Fie=
lds can be used as Columns/Rows, Sections, and Filters. They are =
defined either as Metrics or Dimensions. Calculations can also be created to use as fields, t=
hese are called Calculated Fields.
See Prepare Views for more information
A standard field in Yellowfin can either be classified as a&nb=
sp;Metric or Dimension. Numeric and Dat=
e fields are classified as Metrics by default, but can be changed to Dimens=
ion if required. Metric fields have the full range of aggregations availabl=
e to them. They also have different functionality available to them when us=
ed as filters. Metrics do not allow for prompts, as there are generally too=
many possible values available, so they have slider options available in o=
rder to allow users to easily define ranges. Metric filter values cannot be=
cached.
See View Builder - Field Types for more information.=
A standard field in Yellowfin can either be classified as a&nb=
sp;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 analysi=
s in a report. Dimensions typically retrieve character-type data (employee =
names, company names, etc.), or dates (years, quarters, etc.)
See&nb=
sp;View=
Builder - Field Types for more information.
These are fields that are being used to restrict the results r= eturned in your report or dashboard. There are several types= of filter in Yellowfin:
See Filters for mo= re information
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.
Basic rules can also be applied to charts.
See Conditional Formatting fo=
r more information.
Visit the glossary to learn abo= ut more Yellowfin terminologies.