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

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

"80000" is an example of the limit only, please change it to suit your needs.

Set a default broadcast format

Use the following configuration to set a default format for broadcasts.

Code Block
INSERT INTO Configuration (iporg, configtypecode, configcode, configdata) 
VALUES (1, 'SYSTEM', 'BROADCASTDEFAULTCODE', 'XLSX');

XLSX is an example of the format. You can choose from the following formats: 'HTML', 'CSV', 'DOCX', 'PDF', 'LINK', 'XLSX, 'TXT'.

Restrict guest users from being redirected to the Browse page

The following configuration can be used to limit guest users from being directed to the Browse page when canceling a report, thus not allowing the user to see all public reports.

Code Block
RESTRICTGUESTUSER = TRUE

The default would be false, and still allow exit to the Browse page. Setting to TRUE would redirect users to a “Not available” page.

Prevent license refreshes when deleting users

The following configuration can be used to prevent License Refreshes from cascading across the cluster upon user deletion. This approach serves as an alternative to a bulk delete web service that could efficiently delete multiple users with just one license refresh.

Code Block
INSERT INTO Configuration VALUES (1, "SYSTEM", "SKIPUSERDELETELICENCEREFRESH", "TRUE");

Disable Long File Name handling for AS400 Databases 

Version 9.11 introduced a change to handle long file names on AS400 databases. This impacted some Views created on AS400 data sources prior to 9.11. To enable those Views to work correctly, the long file name handling logic needs to be disabled. This can be done with the following configuration change:

Code Block
INSERT INTO Configuration VALUES ( 1, 'SYSTEM', 'USE_LEGACY_AS400_TABLE_NAMING', 'TRUE');

Enable Millisecond logic for Oracle databases

This setting, when true, enables milliseconds to be correctly handled in Oracle, however turning it on can impact the performance of queries. If you do not need milliseconds in your reports, it is recommended to not set this or set it to FALSE. TO_DATE functionality will be the default if ENABLEMILLISECONDLOGIC logic is unset or FALSE. TO_TIMESTAMP functionality is enabled when ENABLEMILLISECONDLOGIC is TRUE.

Code Block
INSERT INTO Configuration VALUES ( 1, 'SYSTEM', 'ENABLEMILLISECONDLOGIC', 'TRUE');

Enable the Access Filter Toggle in a Client Org

Version 9.11 introduced a change to automatically disable the ability for anyone building a report in a client organisation against a Primary Org Data Source to enable or disable any Access Filter applied to that report. This behaviour can be reverted to pre-9.11 behaviour using the following:

Code Block
INSERT INTO Configuration VALUES ( 1, 'SYSTEM', 'ENABLECLIENTORGACCESSFILTERTOGGLE', 'TRUE');