System settings control the behavior of the Reference Data Center application, such as additional fields to use for queries and display in query results. You can view and change system settings for your environment.
View System Settings
Reference Data Center analysts, managers, and administrators can view system settings in the Settings workspace.
To view system settings, click Setup in the left navigation to access the Setup workspace, then click System Settings in the left navigation pane. You see the current list of system settings for the environment. There are several important system settings that customize application and engine behavior.
Change System Settings
Reference Data Center administrators can change system settings in the Settings workspace.
To change system settings:
- From the Setup workspace, click System Settings in the left navigation pane.
You see the System Settings workspace with all the available settings for the current environment. - Select the setting you wish to change and double click the Value field. The Value field becomes available for data entry.
- Enter the new value for the setting.
- Click anywhere on the workspace to save the change. The Last Modified On and Last Modified By fields updated to display your user ID and the current timestamp.
System Settings
The table below includes system settings by area, name and description.
| SYSTEM_INST | Area | Name | Description |
|---|---|---|---|
| 1 | Debugging | Dump Process info for Debugging. ( values: 0: No, 1: Yes )( default: 0 ) | This can be used to get more useful information in the log file if needed for debugging purposes. Set to 1 and submit events at log level 10 to get the maximum amount of debugging information in the log files |
| 4 | Engine Processing | Data Keys limit: For one rule engine process. ( values: > 0 )( default: 10,000 ) | This setting determines how many data keys are handled by one event. The engine will automatically create multiple parallel processing child events if the number of items to be processed by one Data Strategy exceeds the set value. Default value is 10,000 |
| 5 | Converter Process | ||
| 21 | Engine Processing | Enables/disables code values translations during the compositing. | |
| 22 | Engine Processing | Commit Data Language ID. ( values: L_ID from pace_masterdbo.egl_languages )( default: 0 ) | This setting is used to determine what language ID to use for _ML (multi lingual) fields during commit |
| 23 | Write Process Additional Information ( values: 0: No, 1: Yes )( default: 0 ) | ||
| 24 | Engine Processing | Write Rejection Process. ( values: 0: No, 1: Yes )( default: 1 ) | Used to enable the engine's rejection process component, which writes rejection statuses. |
| 26 | Engine Processing | Auto fix data keys move between Data Strategies. ( values: 0: No, 1: Yes )( default: 0 ) | When set to 0, a security that has changed criteria and now is part of a new data strategy will show the error message “MULTIPLE DATA STRATEGIES APPLY TO THE SAME KEY INSTANCE. DATA STRATEGIES" when opened in RDC. To automatically move a security to the new data strategy and mitigate this error, this setting can be seto to 1. |
| 27 | Engine Processing | Check for conflicting data keys between Data Strategies. ( values: 0: No, 1: Yes )( default: 1 ) | if set to 0, the data key (assuming there is one in conflict and falls in to multiple data strategy criteria) will simply be processed by the last data strategy to run. If set to 1, the engine will log the conflict and the data key won’t be processed |
| 28 | Engine Processing | Time out period in minutes for locking data keys. ( values: > 0 )( default: 10 ) | Determines how long an item that is opened in RDC in edit mode is locked (to prevent two users editing the same security at the same time), before it is unlocked. When an item is unlocked, the user who has it open will now only be in view mode and another user will be able to edit the item. |
| 29 | Data limit to enable bulk enabler (values >0) (default:10) | ||
| 30 | Engine Processing | Update underlying data release levels. ( values: 0: No, 1: Yes )( default: 0 ) | If set to 1, any release level on linked underlying securities will also be updated |
| 31 | Engine Processing | Time out period in minutes for engine locked data keys. ( values: > 0 )( default: 60 ) | In addition to items that are manually locked (by users opening them via the RDC screens), the engine also needs to be able to lock items while processing them. This determines how long an item is locked by the engine before being unlocked. |
| 32 | Engine Processing | New Security underlay days till expiration (default:30 days) | This sets the default value for how long the underlay values when a new security is created manually will last before expiration. The default is 30 days. |
| 33 | Engine Processing | New Security perform unique xref check (values 0 = No, 1 = Yes default:1 Yes) | This determines whether the engine should do a unique xref check when a new security is manually created. |
| 34 | Maximum bulk data size of rows, for database bulk read (SELECT) operation (values >0 and <100,000) (default = 10,000) | ||
| 35 | Maximum bulk data size of rows, for database bulk read (INSERT) operation (values >0 and <100,000) (default = 10,000) | ||
| 36 | Entity Name Field | ||
| 37 | Issue Name Field | ||
| 38 | Issuer Name Field | ||
| 39 | Summary | Number of days summary query should look back. ( default: 30 ) | Sets the value of the number of days the Summary screens queries should look back for as of day results. |
| 40 | The underlying type for primary relationship (default: Primary) | ||
| 41 | Should new analytics data create an underlay on new data creation ( values: 0: No, 1: Yes ) (default: 1 ) | ||
| 42 | Should new rating data create an underlay on new data creation ( values: 0: No, 1: Yes ) (default: 1 ) | ||
| 43 | |||
| 44 | Engine Processing | Delta Process: Number of days to go back historically, and go forward in future for effective dates. ( values: >= 0 )( default: 7 ) | Used to determine how far back to look back and forward from the processing date, when processing in delta mode. |
| 45 | Engine Processing | Component Access: Enable Journal Write Process. ( values: 0: No, 1: Yes )( default: 1 ) | This setting is a flag used to determine whether the journal write process is enabled. |
| 46 | Engine Processing | Component Access: Enable Earnings Handler Process. ( values: 0: No, 1: Yes )( default: 0 ) | This setting is a flag used to determine whether the earnings handler process is enabled. |
| 48 | |||
| 49 | |||
| 50 | |||
| 51 | Engine Processing | Number of days to look back for validating the data. ( values: -1: Always. 0: Never. >1: Days to validate )( default: -1 ) | This is used to set the value that RDC should look back when validating data. If data is older than the date determined using this setting, historical data will be released without validation. |
| 52 | |||
| 53 | Third Party Cash Flow | This is a flag used to determine whether to use the begin and end dates data from the source data for Schedule Dates validation | |
| 54 | Schedules | New Schedule underlay days till expiration (default: 1 day) | New Schedule underlay days till expiration (default: 1 day) |
| 55 | |||
| 56 | |||
| 57 | |||
| 58 | |||
| 59 | |||
| 60 | |||
| 1000 | Securities | Client: Fields to display on security summary screen | This can be used to manage fields that are available as display columns in the Securities summary screen |
| 1001 | Securities | Client: Fields to filter on security summary screen | This can be used to manage field that are available as filters in the Securities summary screen. |
| 1002 | |||
| 1003 | Summary | Client: Virtual page size | This setting determines how many records are in one virtual page, for display purposes |
| 1005 | Setup | Client: Default panel path location | This setting determines where panels will automatically be saved to when creating and editing Data Strategies |
| 1006 | Setup | Client: Security fields to display during security lookup from Logic Builder | This setting determines what fields are displayed for security lookup from Logic Builder |
| 1007 | The processing security types (PSTs) to exclude from the security summary query results | The default is SWLEAC,SWLEIF,SWLXEQ,SWLEDB. | |
| 1009 | Summary | Allow case insensitive search on the summary screens. ( values: 0: No, 1: Yes) (default: 1) | Use this setting to allow case insensitive search on the summary screens |
| 1010 | Display | Client : History results default number of days to look back | This numeric setting can be used to determine the date range used to display historical data in the detail screens. The default is 30. |
| 1011 | |||
| 1012 | |||
| 1014 | |||
| 1015 | |||
| 1016 | |||
| 1017 | Display | Client: Fields to filter on manage overrides screen | This can be used to create the list of available fields to use as a filter in the manage overrides screen |
| 1019 | Display | Client: Security summary show release levels greater than this value as green (default : 3) | This setting can be used to help with RDC workflow. By default, a security's status will only show as a green circle if the release level is set to 3 or higher. To set the value to green if release level is eg at 2 (Released for Trading and Back Office), you can change this value |
| 1021 | Setup | The default prefix to use for migration ids of RDC meta data elements ( default: EGL_ ) | The default prefix to use for migration ids of RDC meta data elements ( default: EGL_ ) |
| 1022 | Setup | Value used to identify a currency security (default: CRCRCR) | Value used to identify a currency security (default: CRCRCR) |
| 1025 | Display | Client: Fields to filter on manage released exceptions screen | This can be used to create the list of available fields to use as a filter in the manage released exceptions screens |
| 1026 | Third Party Cash Flow | Client: Fields to display on cash flow summary screen | This is used to define what columns are available to display in the cash flow summary screen |
| 1027 | Third Party Cash Flow | Client: Fields to filter on cash flow summary screen | This is used to define the list of available fields to use as a filter in the cash flow summary screen. |
| 1028 | Legal Entity | Default fields to show on the legal entity search page | Use this setting to manage what columns are available to display in the legal entity summary screen |
| 1029 | Legal Entity | Default filter fields for the legal entity summary search page | Use this setting to define the list of available fields to use as a filter in the legal entity summary screen |
| 1030 | Prepayment Speeds | Default fields to show on the prepayment time series search page | Use this setting to define what columns are available to display in the Prepayment Time Series search page |
| 1031 | Prepayment Speeds | Default filter fields for the prepayment time series search page | Use this setting to define the list of available fields to use as filters in the Prepayment Time Series search page |
| 1032 | Third Party Cash Flow | Default fields to show on the cash flow details screen (middle section) | This is used to define the list of field to show on the cash flow details screen |
| 1033 | Legal Entity | Client: Issuer fields to display during issuer lookup | Use this setting to define what issuer fields are displayed as reference information during issuer lookup |
| 1034 | Legal Entity | Client: Fields to filter on the Legal Entity manage overrides screen | Use this setting to define the list of available fields to use as a filter in the legal entity manage overrides screen |
| 1035 | Legal Entity | Client: Fields to filter on the Legal Entity manage released exceptions screen | Use this setting to define the list of available fields to use as a filter in the legal entity manage released exceptions screen |
| 1036 | Pricing | Client: Fields to display on pricing summary screen | Use this setting to define what columns are available to display in the Pricing summary screen |
| 1037 | Pricing | Client: Fields to filter on pricing summary screen | Use this setting to define the list of available fields to use as filters in the Pricing summary screen |
| 1038 | Pricing | Client: Fields to display on pricing summary screen (view by vendor) | Use this setting to define what columns to display in the Pricing summary screen (view by vendor) |
| 1039 | Pricing | Client: Fields to filter on pricing summary screen (view by vendor) | Use this setting to define the list of available fields to use as filters in the Pricing summary screen (view by vendor) |
| 1040 | |||
| 1041 | Pricing | Client: Fields to display on exchange rate summary screen | Use this setting to define what columns to display in the Exchange Rate summary screen |
| 1042 | Pricing | Client: Fields to filter on exchange rate summary screen | Use this setting to define the list of available fields use as filters in the Exchange Rate summary screen |
| 1043 | Pricing | Client: Fields to display on exchange rate summary screen (view by vendor) | Use this setting to define what columns to display in the Exchange Rate summary screen (view by vendor) |
| 1044 | Pricing | Client: Fields to filter on exchange rate summary screen (view by vendor) | Use this setting to define the list of available fields use as filters in the Exchange Rate summary screen (view by vendor) |
| 1045 | |||
| 1046 | |||
| 1047 | Schedules | Add Sink Schedule to Corporate Actions ( values: 0: No, 1: Yes )( default: 1 ) | This setting determines whether sink schedules will be added to Corporate Actions |
| 1050 |
Add Comment