Configuring system settings

You can configure various StoredIQ® for Legal system settings.

Before you begin

Procedure

To configure the system settings, complete the following steps:

  1. Go to Admin > System Settings.
  2. Change the system settings as needed.
    Settings Description
    Dashboard caching options
    Caching
    If set to Yes, the metrics on the dashboard are updated by default, every 30 minutes. However, the refresh of the dashboard takes less time than without caching. If set to No, you always see the most recent metrics when you open the dashboard. However, a large number of matters, notices, interviews, and data requests increase the response time of the dashboard.
    Refresh cache immediately
    To avoid an increase in the response time of the dashboard, select Yes only if you expect few changes to the matters. If set to Yes, the dashboard always shows the most recent metrics. If set to No, the metrics on the dashboard are updated by default, every 30 minutes. The advantage is that the dashboard is displayed faster.
    In-memory caching
    If set to Yes, the cached metrics are stored in memory, which decreases the response time of the dashboard. However, if you have a large number of matters, the response time might increase again. If set to No, the persistent storage is used to store the cache, which increases the response time of the dashboard. However, the latency for the retrieval of the dashboard pages is more consistent.
    Report settings
    Enable scheduling
    If scheduling is enabled, the reporting database is refreshed and scheduled reports are generated according to the specified schedule. Generated reports are available from Reports > Scheduled Reports.

    When you disable report scheduling, the refresh schedule is suspended and cannot be changed. This setting becomes active after all currently running tasks are completed. After that, the reporting database is not refreshed and no reports are automatically generated until you enable scheduling again. However, you can manually refresh the database by using Run Now. Also, you can still request reports that are not scheduled.

    Run frequency
    Determine how often the scheduled reports are to be generated and the reporting database is to be refreshed. You must be signed in as the default system administrator ilgadmin to change the schedule.
    First run
    Set the time of day at which scheduled reports are generated for the first time.
    Report retention period
    Set the number of days that reports are kept.
    Database customization file
    Store a file that contains all of your customizations to the reporting database. When you add a customization file, these customizations are applied after every refresh of the reporting database. It is to preserve any custom views, roles, permissions that are granted to those roles, or other changes that are made. To apply any customization immediately, you must manually refresh the database.
    Important: It is your responsibility to ensure the integrity of the customization file.

    When you delete the customization file, customizations such as custom views, sequences, triggers, functions, and roles are removed the next time the reporting database is refreshed.

    For more information about the customization file, see Planning for reports.

    Audit settings
    Low-level auditing
    By default, each action that a user performs and each action that the system performs as a result of a user action is recorded. Therefore, it is no longer necessary to enable low-level auditing. Low-level auditing creates a separate record for each operation that stores data and can increase the response time considerably.
    Matter security settings
    Security groups
    If you enable the use of security groups, the access to the matters is restricted to the members of a security group. New matters must be assigned a security group. Existing matters are associated with the default security group. To restrict the access further, a matter can be changed to a sensitive matter.

    If you do not enable this option, matters can be accessed by any user with the appropriate privileges. To restrict the access, a matter can be changed to a sensitive matter.

    Important: You cannot disable the use of security groups later.
    Key-based access control
    Specify whether the access to any matter can be restricted based on access key information in the request.

    Before you enable key-based access control, make sure that a custom matter attribute for holding the key is defined. The custom matter attribute must be of the data type drop-down list (single-select) or drop-down list (multiple-select). This attribute must then be set as key attribute.

    In addition, ensure that a system external to StoredIQ for Legal such as a single sign-on (SSO) system provides the required key value in the header of all incoming user sign-in requests. The lookup key defines the HTTP header field to be checked by StoredIQ for Legal. For each access request, the value of the specified field is compared to the keys set for the matter. If there's a match, access to the matter is granted. Otherwise, access is denied.

    If you change the lookup key later, you must restart StoredIQ for Legal for this change to take effect.

    Matter settings If you set Allow to reopen matters to Yes, users with the Matters: Close privilege can reopen closed matters.
    File attachment settings Define the maximum file size for attachments in MB. It is recommended that the file size can be within 50 MB.
    Help information settings If you provide your own help information, specify the URL of that help information. Any links in the product that lead to IBM Documentation are then also replaced with this URL.
    Licensed programs You can hide any feature for which you don't have a license.
    SSO settings
    Redirect URL
    To prevent unauthorized access to StoredIQ for Legal in a single sign-on (SSO) environment, you might require people to authenticate again when they try to access StoredIQ for Legal in the same browser where they signed out. Specify the URL that invalidates a session in your SSO environment.
    Unique ID for catalog entries To import people, you must select a person attribute that uniquely identifies each person in the catalog, regardless of whether this person is imported from the directory server or by using the import API. All predefined and custom person attributes with data type String are available for selection. For more information, see Customizing attributes.

    To preserve data integrity, do not select another person attribute after you start importing people.

    User interface
    Enable incremental search

    If Enable incremental search is enabled, search is triggered automatically with some delay after the user types a character in the quick search text box. When the user types characters continuously, search is not triggered even though the incremental search is enabled. The Incremental search is applicable for quick search except for the Matter pane and Task pane. The incremental search can be configured independently from prefix search settings. It is not applicable for Advanced search.

    Enable prefix search
    If you enable prefix search, search is done when the user searches for a string with the prefix. The Enable prefix search is applicable for quick search text box. This feature is not available in Custodian portal, Tasks or in Admin Workflows. The prefix search can be configured independently from incremental search settings. It is not applicable for Advanced search.

    By default, this option is set to No.

    Default filter of custodian portal
    Specify the option that you want to set for default filter of custodian portal in the system settings. For example, you can choose any of the following options; Attention required, New, Read, Done or All. The option set in the system settings is available as default when the user accesses the custodian portal and the user can also change the options according to their requirement. Also, the set option takes effect only after the next login. The last changed option remains the same even if the user moves between the screens and get back to the custodian portal page. Only after you log out and log in next time, you can see the default set option. Any changes that are made to the options within the custodian portal either manually or automatically, apply to all types of notifications irrespective of the default option set in the system settings until the user logs out.
    By default, Attention required is set as the default filter of custodian portal.
    Data requests
    Enable release data requests
    If you enable release data requests, users can create release requests for data of completed preservation or preservation and collection data requests.
    Important: After you enable release data requests, you cannot disable the option again.
    Start of
change
    Restrict date ranges of custodian, client, and shared data
    If you enable restrict date ranges of custodian, client, and shared data, overridden date range of custodian, client, and shared data must be within the date range specified in the data request, that is the start date of the override date range must be equal or grater than the start date of the date range of the data request, and the end date must be equal or earlier than the end date of date range of the data request. The restriction is applicable only when the date range is specified in the data request.
    By default, Restrict date ranges of custodian, client, and shared data is set to No or disabled.
    End of change
    Allow to release data by date ranges
    Users can specify date ranges for the data to be released.

    This option is available only if release data requests are enabled.

    Enable override data source category per custodian, client, and shared data
    If you enable override data source category, users can override the data source category that is set earlier and assign different data source categories to the custodian, client, and shared data.
    By default, Enable to override data source category per custodian, client, and shared data is set to No or disabled. If you enable this option first, you cannot disable it again.
    Data request types available for interactively created matters
    If you select the option, Custom, a predefined set of data request type is displayed by default with the Name, No hold obligation, and data request types, Identification, Collection, and Deletion. You can edit the details by clicking the pencil icon and update it. You can also specify a new set of data request types by clicking Add. If needed, edit or delete the details by using options from Actions. To set the default data request types, click the radio button that is displayed and save your changes. The set data request types are displayed in Type when you create the data request.

    The configured restrictions are applicable only to the matters that are created interactively and the existing matters are not impacted.

    By default, Data request types available for interactively created matters is set to All.
    Comment and attachment deletion If you enable deletion of comments and attachments, users can delete task comments and attachments in the task view.
    Matter information
    Assign external ID automatically
    If you enable assign external ID automatically, users need not provide the external ID for creating the matter. The ID is displayed by default.
    Note: External ID is mandatory for creating a new matter.
    Display settings of matter
    Provides the option for the users to choose from the displayed options: External ID, Name, or External ID and Name. Users can specify the required option for the matter by selecting it.
    Migration portal settings If you set Show migration portal to Yes, the migration portal becomes available to users with the Notices: Manage or Interviews: Manage privilege. For the matters for which they have access to, they can check the items that are migrated from IBM® Atlas Policy Suite.