Space Properties

The Logo Image displays in the upper left corner of the Home page, Admin, and Designer for a space. Browse to select a replacement image and click Upload to add it. Click Save and refresh your browser to see the change.

The Process Engine is a component of Birst that handles the data processing that occurs when source data is pulled into the Birst data store (warehouse). The Process Engine is versioned separately from the main Birst application. Normally, the Process Engine Version can be a few versions behind the main application version.

Birst does not automatically upgrade the Process Engine Version. Space Administrators normally update the Process Engine Version when there are particular features that require a newer version, such as to support a certain database for the warehouse.

To upgrade the Processing Engine version, select one from the dropdown list.

After checking the box, click the Generate Password button to generate an SSO Password.

By default the space is enabled for using dynamic groups to control user access. You can manage users and groups dynamically if you upload a table of users and groups that defines which users participate in which group. See Dynamic Groups.

If you do not want to use dynamic groups, you can create standard static groups, assign users to groups, and assign permissions to groups from the Space Groups module, even if this option is enabled.

The maximum number of records to return from a query against the data store (warehouse) is by default 10,000. Change this setting if you need to see more results, up to the maximum of 500,000.

The maximum query time is the time that a query can run before it either completes or is terminated. If a query exceeds the time limit that is set, Birst terminates it. The setting is 300 seconds (5 minutes) for the Cloud environment and cannot be changed. In Appliance environments, the main AccountAdmin user can change this setting for a space.

If a maximum query time has been set at the database level that is smaller than the one set here, the database level setting overrides this setting.

You can set a minimum year and a maximum year for filters that use the built-in Time attributes and time series measures in the space.

The defaults values are -1 and -1, which means the default 150 year span from 1900 - 2050.

Best Practice: Change these values to match the time frame of your reporting requirements for the space. Restricting the time frame makes your reports more efficient and easier to develop. For example, if the source data for the space goes back only to the year 2000, you could set the minimum year to 2000, and you won't see previous years in the Time filters on a report.

Enabling Always On ensures high availability and simultaneous access to reports and dashboards while a space is processing. Birst replicates and creates a "shadow space" for this purpose. Because it replicates the data, Always On requires additional space resources.

By default Always On is not enabled for all accounts; it is an add-on feature for Advanced spaces. To get Always On contact your support or your Customer Success Manager. See Enabling an Always On Space.

The "As Navigates" feature is an enhancement for Visualizer (and Designer) reporting that enables users to create a report that includes a measure in a logical query that only has grains available on a subset of dimensions that are included in the query.

This feature must be enabled for the account. To use the As Navigates feature, please contact your Birst representative to have it turned on for your account.

You can lock packages in a space so that they cannot be deleted or modified. This lock applies to both parent and child spaces. It disables auto sync for the package definition. For example, if a package is locked in a parent space, then any child space that uses the package cannot remove it from their space.

Best Practice: Enable this option in production environments.

Column Level Security allows admins to control the granularity of shared data across dashboards. Column Level Security has the following three security levels:

• Display all columns in a report. This is the default. It will display all columns in a report even if the user does not have the column in their Custom Subject Area.
• Hide only secure columns in a report. This setting will hide any columns in a report the user does not have access to in their Custom Subject Area. The user will only see the columns they have access to through their Custom Subject Area.
• Hide entire report containing secure columns. If a report contains any columns that are not listed in a user's Custom Subject Area, the entire report will be hidden from the user.

The processing time zone for all input files for the space.

You can change this setting even after the space has been published.

The Local Server Time is set to the Coordinated Universal Time (UTC) time standard across all cloud applications, per an Infor standard.

Before data has been processed in the space, you can change the processing time zone for the space to your corporate time zone. This transforms all datetime fields in a file to the selected time zone. The difference between this time zone setting and each source's time zone (set at Manage Sources > Properties) is how Birst determines the offset to apply when loading datetime fields into the system.

See KB Article 2303325 for more information on the time zone change.