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.


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 a 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.

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. However, 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

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 (i.e. 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 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 number of values, it might hang the system.

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

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

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