Versions Compared

Old Version 1

changes.mady.by.user Pamela Totas (Deactivated)

Saved on

compared with

New Version 2

changes.mady.by.user Pamela Totas (Deactivated)

Saved on

Key

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


SYSTEM_INSTAreaNameDescription
1DebuggingDump 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
1010DisplayClient : History results default number of days to look backThis numeric setting can be used to determine the date range used to display historical data in the detail screens.  The default is 30.
1017DisplayClient: Fields to filter on manage overrides screenThis can be used to create the list of available fields to use as a filter in the manage overrides screen
1019DisplayClient: 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
 1025 DisplayClient: Fields to filter on manage released exceptions screenThis can be used to create the list of available fields to use as a filter in the manage released exceptions screens
 4Engine ProcessingData 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
 22 Engine ProcessingCommit 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
 24 Engine ProcessingWrite Rejection Process. ( values: 0: No, 1: Yes )( default: 1 )Used to enable the engines's rejection process component, which writes rejection statuses.
 26Engine ProcessingAuto 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 ProcessingCheck 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 ProcessingTime 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.
 30 Engine ProcessingUpdate 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 ProcessingTime 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 ProcessingNew 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 ProcessingNew 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.
 44 Engine ProcessingDelta 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 ProcessingComponent 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 ProcessingComponent 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.
 51 Engine ProcessingNumber 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.