Like what you see? Have a play with our trial version.

Overview

In addition to the UI configuration options within Yellowfin, a number of SQL-provoked settings exist, outlined below.

Enforce a global language

You can override the global language of a Yellowfin instance, but beware that this applies to all organizations within the instance — primary and clients alike. This forces Yellowfin to be translated into the specified language without any exceptions. To do so, add the following SQL into your configuration database:

INSERT INTO Configuration VALUES (1, "SYSTEM", "OVERRIDE_LANGUAGE", "zh_CN");

In this sample, “zh_CN” refers to the Java language locale code for the language you wish to enforce.

Also in this sample, 1 denotes the primary/default organization. This is a system-wide setting that cannot be enabled for specific client organizations; Therefore, this value must always be set to 1.

Hide JS API details

You can hide the Java version and OS version from the JS API response by setting HIDEJSAPIDETAILS. to true. In this case, the following components of the serverInfo object 

javaVersion, operatingSystem, opertatingSystemArch, operatingSystemVersion, releaseVersion, schemaVersion, subVersion, buildVersion

Note: This will not hide the base and loaded resources values because they are always required by the browser to load further parts of the JS API. 

To make use of this option, start by running this SQL on your database (this is a system-wide setting, so the IP Org is set to 1):

INSERT INTO Configuration(IpOrg, ConfigTypeCode, ConfigCode, ConfigData) values(1, 'SYSTEM', 'HIDEJSPAPIDETAILS', 'true');

Next, restart your Yellowfin instance, then embed a piece of content from the JS API. It doesn't matter what it is; you just need to load the JS API. You could even do this with the basic script tag:

<script src="http://yourYfServer/JsAPI/v3"></script>

To test this has worked, open your browser console and type: 

yellowfin.serverInfo

The console should display some empty components for the serverInfo object, apart from the base and loaded resources values (required by the browser).

Limit cached filter context

Use this parameter to force the filter formatting options 'Ignore Report Filters when Loading Cached Value' and 'Restrict SQL Context to Filter Columns Only' on (see the Dimension filter settings table of events on this page for more info). 

When set to FALSE (default), these two options are displayed within the UI and the user can choose whether toggle them on or off.

When set to TRUE, these two options are both forced to be enabled on all filters on all reports on all datasources, and the options within the UI are hidden from display. In this situation, users don't need to remember to switch these settings on, and the only way they can be switched off is by changing this advanced configuration from TRUE to FALSE.

INSERT INTO Configuration(1, 'SYSTEM', 'LIMITCACHEDFILTERCONTEXT', 'TRUE');

In this sample, 1 signifies the primary/default organization.

Allow empty or null value to be used for cached filter

Use this parameter to get parent filter results to persist when a child filter result contains empty or null values.

When set to FALSE (default), cached filters will ignore empty or null values.

When set to TRUE, cached filters will not ignore empty or null values.

INSERT INTO Configuration values(1, 'SYSTEM', 'ALLOWNULLCACHEFILTERS', 'TRUE');

In this sample, 1 signifies the primary/default organization.

Disable URL title fetching 

This parameter prevents Yellowfin from fetching a URL title when sharing links in discussions. When set to TRUE, only the URL will be displayed in the discussion. When set to FALSE (or omitted, which is the default),  the title of the URL will be displayed in the discussion.

INSERT INTO Configuration VALUES (1, 'SYSTEM', 'DISABLEURLTITLEFETCH', 'TRUE')

In this sample, 1 signifies the primary/default organization.

Conserve memory during export

To ensure that the memory does not get exhausted when exporting a large report to XLSX, you can enable the Low Memory Export option. This processes reports in parts in memory, rather than as a whole. To enable this feature, add the following SQL code into your configuration database:

INSERT INTO Configuration(IpOrg, ConfigTypeCode, ConfigCode, ConfigData) values(<IP_org>, 'SYSTEM', 'REPORTLOWMEMORYEXPORT', 'ON');

Remember to set your value for <IP_org> to either the primary org (1) or a client org.

Disable outer join check

During the creation of views, you can configure outer joins to be treated as inner joins when creating View relationships in the database.

The following is the SQL command for this:

INSERT INTO Configuration(IpOrg, ConfigTypeCode, ConfigCode, ConfigData) values(1, 'SYSTEM', 'DISABLEOUTERJOINCHECK', 'TRUE');

In this sample, 1 signifies the primary/default organization.

Conserve memory during report broadcast

Broadcast reports are run for each of the multiple recipients separately, taking into account their access filters, languages or other factors. To conserve memory usage and system performance, use the following configuration so that each recipient’s report is delivered as soon as it’s generated (instead of waiting for all the recipients’ reports to get done before sending them together).

Warning: This may result in emails being delivered to recipients across a long period of time.

INSERT INTO Configuration VALUES (1, 'SYSTEM', 'BROADCASTSENDINLINE', 'TRUE');

In this sample, 1 signifies the primary/default organization.


Enable carbon copy on broadcast emails

This enables the carbon copy option on broadcast emails, so multiple users who have access to the same data are sent a single email which is sent to the first user, with the remaining recipients being sent a carbon copy. Note that all recipients will be visible to one another.

INSERT INTO Configuration VALUES (1, 'SYSTEM', 'COMBINEEMAILGROUPS', 'TRUE');

In this sample, 1 signifies the primary/default organization.

Disable row limit on filtered queries

Yellowfin restricts the number of rows returned from queries that involve filter values. This is the same limit that is applied for all database queries (even those without any filters) and is configurable by the user in the View builder and at the Report level. However, there is a hidden configuration option that allows users to remove this limit from filtered queries, thereby allowing Yellowfin to return all matching rows. To apply this, add the following SQL into your Configuration database:

Warning: Be careful when disabling the limit. If the filtered query returns a large amount of values, it might hang the system.

INSERT INTO Configuration VALUES (1, 'SYSTEM', 'DISABLEFILTERPROMPTLIMIT', 'TRUE');


Change historic schedule record limit

Scheduled tasks that track historic executions maintain the records for the past 30 days. To change this time limit, use the following configuration.

INSERT INTO Configuration VALUES (1, "SYSTEM", "HISTORICSCHEDULERECORDSLIMITDAYS", "60");

In this sample, 1 is the organization ID, and 60 is the number of tracking days.


Disable calculated field validation

Calculated fields are validated before they are saved into the database to determine the data type of their resulting field. However, it is possible to disable this validation for all calculated fields (including those created via Freehand SQL).

Use the following SQL to do so:

INSERT INTO Configuration(IpOrg, ConfigTypeCode, ConfigCode, ConfigData) values(1, 'SYSTEM', 'VALIDATECALCONSAVE', ‘FALSE’);

In this sample, ConfigData = TRUE enables validation, and ConfigData = FALSE disables it. 


Force Yellowfin to use legacy RC4 128 PDF encryption

When set to TRUE, this forces Yellowfin to use legacy RC4 128-bit encryption for PDFs rather than the default  of AES 256-bit encrypted PDFs.

Use the following SQL to do so:

INSERT INTO Configuration VALUES (1, 'SYSTEM', 'USELEGACYPDFENCRYPTION', 'TRUE');

In this sample, 1 signifies the primary/default organization.



Log failed login events

When set to FALSE (default), only failed login attempts made via a valid username are recorded in the system log files. 

When set to TRUE, all failed login attempts to Yellowfin are recorded in the system logs, whether the username is valid or not, allowing for more accurate auditing of login activity.

Use the following SQL to do so:

INSERT INTO Configuration VALUES (1,'SYSTEM', 'LOGFAILEDLOGINEVENTDETAILSENABLED','TRUE')

In this sample, 1 signifies the primary/default organization.



  • No labels