System settings control the behavior of the Portfolio Data Center application. You can view and change the system settings as per your environment needs.
View System Settings
To view the 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 allow you to customize the PDC application and engine behavior.
Modify System Settings
PDC allows only users who belong to Portfolio Data Center administrator's role to change system settings in the Settings workspace.
To change system settings:
- In Portfolio Data Center, from the left navigation, click Setup > System Settings.
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.
Important System Settings
The list below describes the system settings that help you to customize the PDC application and engine behavior.
| Setting ID | Name | Description | Values |
|---|---|---|---|
| 21 | Data loaded as is for Portfolio Data Center. If value is 1, then data will be translated by PDC engine. | It is a code driven setting used by the PDC DB selector for converting field value. | 0: No, 1: Yes. Default is 1. |
| 22 | Commit Data Language ID. | PDC identifies the language by using this setting to display or save multilingual fields data. For example, to view in Chinese Simplified language, set the language ID here. | L_ID from pace_masterdbo.egl_languages. Default is 0.) |
| 24 | Write Rejection Process. | When enabled, PDC writes exceptions into the ESTAR.ESTAR_EVENT_REJECTION table. | 0: No, 1: Yes. Default is 1. |
| 25 | Process Only Deltas. | Used while processing a policy. If this system setting is enabled, then only the unprocessed entities (i.e. the delta entities) alone are processed. | 0: No, 1: Yes. Default is 1. |
| 27 | Check for conflicting entities between Policies. | PDC Engine checks for conflicts only when this setting is enabled. When this option is set with '0' the red color indicator is not shown when you manually do the policy Conflict Check. | 0: No, 1: Yes. Default is 1. |
| 28 | Time out period in minutes for locking entities. | Used to specify the time out period in minutes for locking entities. | > 0. Default is 10 minutes |
| 29 | Data limit to enable bulk updater [MERGE] mode. | PDC Engine uses this row limit to switch between bulk updater and row by row updater. If the number of rows are greater than this limit then the system switches to bulk updater. | > 0. Default is 10 |
| 30 | Time out period in minutes for engine locked entities. | The number of minutes used in Entity Handlers for Locking Entities. | > 0. Default is 60 minutes |
| 31 | Maximum bulk data size of rows, for database bulk read [SELECT] operation. | This controls how many rows you need to select in bulk while fetching data. | > 0 and < 100,000. Default is 10,000 |
| 32 | Maximum bulk data size of rows, for database bulk write [INSERT] operation. | This controls how many rows you need to include for bulk inserts. | > 0 and < 100,000. Default is 10,000 |
| 34 | Entity Name field | There are multiple places where the entity name is shown without having to specify a field. By default the value for internal field 389 (entity name) is shown. You can change it to legal name or long name or reporting name by resetting the field attribute ID. | Default is 389. |
| 35 | Delta Process: Number of days to go back historically, and go forward in future for effective dates. | This controls how far back and far into the future the delta process looks for changes. Delta process will look to only entities that have been updated since the last time the entity was processed by the engine. This setting allows control processing when making changes to older records or ones made in advance. | >= 0. Default is 7 days. |
| 36 | Component Access: Enable Journal Write Process. | When you enable this, PDC Engine writes all changes of data into PACE_MASTER.DBO.JOURNAL_MASTER and PACE_MASTER.DBO.GENERIC_JOURNAL_DETAILS tables | 0 or 1. Default is 0. |
| 37 | New Account underlay days till expiration | Newly created entities are established using underlays. The duration of the underlay (the end date of the underlay) is determined by this setting. | Default is 30 days. |
| 38 | Authorize new fund setup | Controls whether manually created entities require entity level authorization before being released. A value of 0 means that the new entities does not generate an entity level authorization. A value of 1 means the authorization are generated for entities created with policies enabled to do so. | 0 or 1. Default is 0. |
| 39 | Authorize duplicate history | When a history record is duplicated (to a new change date) you can generate an entity level authorization. Conceptually, some clients consider the creation of a new history as worthy or requiring authorization. However, since the duplicate history process runs all field validations automatically, the setting is defaulted to no, that is, when you duplicate history records, an entity level authorization is not generated. | 0 or 1. Default is 0. |
| 1000 | Client: Fields to display on entity summary screen | The fields that are available as columns in the display area when you have selected the All left navigation category. | |
| 1001 | Client: Fields to filter on entity summary screen | The fields that are available as filters in the search area when you have selected the All left navigation category. | |
| 1004 | Client: Entity fields to display during entity lookup from Logic Builder | These are the entity columns displayed in Logic Builder area when you use the Test: Evaluate/Show Details option. | |
| 1005 | Field types supported in PDC | This setting is used while loading the fields for PDC, that is, we specify the field types that are allowed in PDC while adding to the Field Groups. | Default value is E, DE, EX, EC, PR, CM, EL |
| 1006 | The default prefix to use for migration ids of PDC meta data elements | Allows a custom prefix to be added to the instance numbers of metadata components. | |
| 1007 | Restrict what fields are available in the logic builder when configuring setup items. | This setting is used in PDC for restricting the fields displayed in logic builder (i.e., in Policy Criteria screen). | Default value is E, DE |
| 1008 | Client: Fields to display on Accounts entity summary screen | The fields that are available as columns in the display area when you have selected the Portfolios left navigation category. | |
| 1009 | Client: Fields to filter on Accounts entity summary screen | The fields that are available as filters in the search area when you have selected the Portfolios left navigation category. | |
| 1010 | Client: Fields to display on Composites entity summary screen | The fields that are available as columns in the display area when you have selected the Composites left navigation category. | |
| 1011 | Client: Fields to filter on Composites entity summary screen | The fields that are available as filters in the search area when you have selected the Composites left navigation category. | |
| 1012 | Client: Fields to display on Market Indexes entity summary screen | The fields that are available as columns in the display area when you have selected the Indices left navigation category. | |
| 1013 | Client: Fields to filter on Market Indexes entity summary screen | The fields that are available as filters in the search area when you have selected the Indices left navigation category. | |
| 1014 | Client: Fields to display on Lists entity summary screen | The fields that are available as columns in the display area when you have selected the List left navigation category. | |
| 1015 | Client: Fields to filter on Lists entity summary screen | The fields that are available as filters in the search area when you have selected the List left navigation category. | |
| 1016 | Client: Default panel path location | This is the default path to store PDC panels on Linux Server under ..\estar\tpe\dynamic\dat\ folder. We are using \eagle\pdc\accounts\ as default path. This path should never be changed. | |
| 1017 | Client: Fields to filter on manage overrides screen | The fields that are available as filters in the search area when you are viewing the manage overrides screen. | |
| 1018 | Client: Fields to filter on manage released exceptions screen | The fields that are available as filters in the search area when you are viewing the released exceptions screen. | |
| 1019 | Client: Entity summary show release levels greater than this value as green | The summary screen has different color coded symbols for entities that are fully or partially released, while the highest level representing fully released. Since it is possible to add additional release levels, this setting allows you to decide which level(s) is show as green. | Default is 3 |
| 1020 | Client: Fields to display on Accounts mutual fund summary screen | The fields that are available as columns in the display area when you have selected the Mutual Fund left NAV category. | |
| 1021 | Client: Fields to filter on Accounts mutual fund summary screen | The fields that are available as filters in the search area when you have selected the Mutual Fund left NAV category. |
Add Comment