Jake 11.27 note - info taken from below:
\\thenest\users\jmathews\DOC Team\RDC_PRICING CENTER\JIRAs\DOC-1625_Engine Processing
The ultimate goal of RDC Prices is to produce Gold Copy Price records for a given effective date and a fixed set of securities out of raw prices received from multiple vendors, or by using prior day Gold Copy prices. To achieve this goal , RDC Prices uses Data Strategies, and the concepts of a Main Engine and Rule Engines, to process activity.
Is it ok to use H2’s and H3’s for the below sections? Or is there a standard for detailing the sections
Data Strategies
Data Strategies are composite data processing rules made up of Processing Rules. Data Strategies are applied at an individual security level, while Processing Rules are defined based on individual data fields. Data Strategies work by processing activity through the below phases:
...
A typical set of input parameters includes data strategy identification, effective date, specific phase identification, and a security alias selector. The security alias selector is either a range of security aliases, or a list of values.
Jake note - would it help to have an example here, or reference the system configuration that determines the maximum number of securities processed by a single rule engine?
Add label