Versions Compared

Key

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

ESP-317 - Correct XSD schema for the CASHPROJECTIONSEXTRACT

...

<xsd:element name="reportType" type="xsd: normalizedString" minOccurs="0">


ESP-356: EagleML - WRHSTRADEEXTRACT - Add Task Parameter on the TradedCashActivity Extract to have the ability to exclude cash from Trades

Originally delivered in March 2017, the EagleML TradedCashActivity Extract was validated to include a task parameter which will exclude cash from trades. To exclude Cash, the value of CashEventSpawned is leveraged in the table.  The optional parameter, ExcludeTradeCash, filters out the data set.  If set to Y or null, then all records are returned.  If set to N, then only the events where the CashEventSpawned <> Y are returned. 

               <taskParameter>
                  <name>ExcludeTradeCash</name>
                  <dataType>S</dataType>
                  <value>N</value>
               </taskParameter>

...

Files changed:
xml-ref_line_of_credit.xml
xml-ref_loc_entity.xml
xml-ref_loc_issuer.xml


ESP-394 and ESP-396 - Real-Time processing: Develop logic for RTR task parameters processing and realtime_task_reporter

A new approach for processing RTRs with embedded data was implemented. The major change is the introduction of RealTime Processing which eliminates the unnecessary creation of files on the back end. This opens up the potential to process all reference data in one straem as long as proper dependencies are observed.  

...

tpe\dynamic\msgcenter\eagle_default\in\xml\xml-create_tsr.xml
tpe\dynamic\msgcenter\eagle_default\in\xml\xml-ref_generic_ca.xml
tpe\dynamic\msgcenter\eagle_default\in\xml\xml-ref_issuevarrate.xml
tpe\dynamic\msgcenter\eagle_default\in\xml\xml-ref_objects.rsf
tpe\dynamic\msgcenter\eagle_default\in\xml\include\generic_smf_fields_logic.inc
tpe\dynamic\msgcenter\eagle_default\in\xml\include\reference_common_header_aliases.inc
tpe\dynamic\msgcenter\eagle_default\in\xml\include\set_transaction_id_content.inc
tpe\dynamic\msgcenter\eagle_default\in\xml\xslt\eagleml_smf_gen_fields.xsl
tpe\dynamic\msgcenter\eagle_default\include\collect_transation_ids.inc
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\cm_checks.inc
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\collect_task_parameters.inc
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\reporter_dist.inc
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\reporter_dist_methods.inc
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\in\xml\eagleml_load.xml
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\in\xml\realtime_rtr.rsf
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\in\xml\realtime_rtr.xml
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\in\xml\runtaskrequest.xml
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\task_reporter.xml
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\task_reporter_gen_step_summary.inc
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\task_reporter_gen_task_unit_realtime.inc
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\task_reporter_generate_task_unit.inc
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\taskacknowledgement.xml


ESP-404: EagleML - XREFEXTRACT - incorporate the Asset Properties Model

To provide additional content on an opt-in basis, the Asset Properties Model was added to the XREFEXTRACT.  The following fields have been added to XREFEXTRACT: 
<issueDescription>
<investmentType>
<processingSecurityType>
<securityType>
<releaseStatus>
<issueCountryCode>
<couponTypeCode>
<smSettlementCurrency>
<smSecurityType>
<securityType2>
<securitySubType>
<maturityDate>

...


This issue has been resolved by renaming the file within the exec_ndfa stream. Modified the read_datamaps.inc and improved support for replacing date timestamp.


ESP-433 Improve the delete functionality for the IssuerRole interface

Added support within the IssuerRole interface to be able to delete multiple records at a time. 

Introduced the following rules:
xml-ref_delete.xml
Created the following rules:
ref_issuerrole_delete_aliases.inc
ref_issuerrole_delete.inc

Modified the xml-ref_objects.rsf rule to utilize the new rules.

In order to delete records, the EagleML/referenceTransaction/header/action tag must be set to DELETE.

Example:

<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="ReferenceTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0eagleml-main-2-0.xsd" xsi:type="ReferenceTransactionMessage">
<referenceTransaction>
<header>
<objectType>IssuerRole</objectType>
<action>DELETE</action>
</header>
<issuerRole>
<objectType>IssuerRole</objectType>
<objectId>IssuerRole</objectId>
<sourceName>EAGLE PACE</sourceName>
<updateSource>MCADMIN</updateSource>
<effectiveDate>2014-11-17</effectiveDate>
<noLoadValidationFlag>N</noLoadValidationFlag>
<accountingValidationFlag>N</accountingValidationFlag>
<primaryAssetId>ESP433_SMF</primaryAssetId>
<primaryAssetType>INTERNAL</primaryAssetType>
<issueName>ESP433_SMF NAME</issueName>
<issueDescription>ESP433_SMF DESC</issueDescription>
<primaryExchange>US</primaryExchange>
<primaryExchangeCode>US</primaryExchangeCode>
<assetCurrency>USD</assetCurrency>
<issuerId>ESP433_ISORG_ID</issuerId>
<issuerName>ESP433_ISORG_NAME</issuerName>
<roleType>P</roleType>
<startDate>2014-11-17</startDate>
<endDate>2014-12-17</endDate>
<percentOwned>622.432</percentOwned>
<irdUpdateDate>2014-11-23</irdUpdateDate>
<irdChar1>Comment</irdChar1>
</issuerRole>
</referenceTransaction>
</EagleML>


ESP-444: Add mask and translator for Warehouse Cash Activity and Cancel Cash Activity objects in XMLDBAPI format to the eagle_wrf_generic_load workflow

A translator and translator mask were added for the Warehouse Cash Activity and Cancel Cash Activity object into the eagle_wrf_generic_load workflow and routed to the eagle_ml-2-0_default_in_xml_warehouse .xml in order to be loaded via xmldbapi.

List of files changed:
• /eis/ejmwf/eagle_wrf_generic_load.ejmwf
• /eis/ejmwf/eagle_wrf_generic_load_warehouse_objects.ejmwf


ESP-450: Correct XSD schema for the GENCORPACTIONSEXTRACT

XSD validation for the GENCORPACTIONSEXTRACT was producing an error during validation.  The transType value SINKSCHED was invalid against the XSD. There were several values identified in the transtype element that were used in the rules, but were not present in the current XSD.

The values SINKSCHED, CREDITEVENT, CASHDIV, ADDPUT, ADDCALL, TENDER, EXCHANGE, ACORPACTION, DIVREINVEST, ASSIMILATION, ADDFACTOR, SHARECASHTENDER, BSSB, UNITSEP, NOMINAL, PREREFUNDING and REDENOMINATION were added to the CATransTypeEnum in eagleml-enum-2-0.xsd

File changed:
eagleml-enum-2-0.xsd


ESP-451: Correct XSD schema for the WRHSTRADEEXTRACT

The WRHSTRADEEXTRACT was failing the validation against the XSD. Analysis revealed that the elements in the result extracts had improper data types.

A new custom element type, named DateOrDateTime, was created to support values of the atomic types [xs-date] and [xs-dateTime].

File changed:
eagleml-wh-shared-2-0.xsd


ESP-452: Correct XSD schema for the SMFEXTRACT

SMF records containing gicsSector elements were failing validation against the XSD due to an incorrect ordering of elements in the rule files. 

The order of the PRIVATE_REGISTRATION_RIGHTS and EQ_CALL_PUT_FLAG elements was switched in the ‘t_smf.xml’, ‘t_smf_streaming.inc’, and ‘t_smf_streaming_eml.inc’ rules to conform to their orderin the XSD.

Files changed:

t_smf.xml
t_smf_streaming.inc
t_smf_streaming_eml.inc


ESP-453 Create a new stream for XSD validation

Created a new validation stream for XSD validation, eagle_ml-2-0_default_cm_validate_by_xsd.

Features include:

  1. Windows support
  2. Error handling when the incorrect path is used for XSD or for data location
  3. Error description messages in the TSR

Files changed:

  • eagle_default_cm_validation_by_xsd.xml
  • validation_by_xsd.inc


ESP-831 Improve the delete functionality for the GenericSMF and MultilegSMF interfaces

Support for deleting multiple GenericSMF and MulitlegSMF records through the eagle_ml-2-0_default_in_xml_smf_generic stream was added.

The following rules were created:
xml-smf_delete.xml
parse_security_xrefs.inc
smf_genericsmf_delete.inc
smf_multileg_delete.inc
We changed:
xml-smf_generic_objects.rsf

To delete records the EagleML/referenceTransaction/header/action tag has to have a value of 'DELETE'.

Example:

<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="ReferenceTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0eagleml-main-2-0.xsd" xsi:type="ReferenceTransactionMessage">
<referenceTransaction>
<header>
<action>DELETE</action>
<objectType>GenericSMF</objectType>
</header>
<genericSMF>
<objectType>GenericSMF</objectType>
<objectId>GenericSMF</objectId>
<objectDescription>SMF</objectDescription>
<sourceName>EAGLE PACE</sourceName>
<updateSource>AFASTOVICH</updateSource>
<effectiveDate>2014-11-22</effectiveDate>
<accountingValidationFlag>Y</accountingValidationFlag>
<issueName>ESP831_SWP1 NAME</issueName>
<primaryAssetId>ESP831_SWP1</primaryAssetId>
<primaryAssetType>INTERNAL</primaryAssetType>
<xrefIdentifiers>
<xId>
<xId>ESP831_SWP1xId</xId>
<xIdType>SWPXTYPE1</xIdType>
</xId>
</xrefIdentifiers>
<primaryExchangeCode>ALL</primaryExchangeCode>
<assetCurrency>USD</assetCurrency>
<investmentType>FI</investmentType>
<processingSecurityType>SWCDCO</processingSecurityType>
<securityType>ABS</securityType>
<settlementCurrency>USD</settlementCurrency>
<incomeCurrency>USD</incomeCurrency>
<quantityType>PAR</quantityType>
<priceMultiplier>0.01</priceMultiplier>
<quantityScale>1</quantityScale>
<issueCountryCode>US</issueCountryCode>
<issueTaxType>ALL</issueTaxType>
<maturityDate>2033-11-30</maturityDate>
<tradingFlat>N</tradingFlat>
<optiondescr>B</optiondescr>
<FixedIncomeModel>
<coupon>2</coupon>
<couponTypeCode>F</couponTypeCode>
<dayCountBasis>30/360</dayCountBasis>
<paymentFrequencyCode>MAT</paymentFrequencyCode>
<issuePrice>100</issuePrice>
<issueDate>2014-11-04</issueDate>
<datedDate>2014-11-04</datedDate>
<firstCouponDate>2033-11-30</firstCouponDate>
<lastCouponDate>2033-11-30</lastCouponDate>
<maturityPrice>0</maturityPrice>
<sinkFundIndicator>N</sinkFundIndicator>
<delayDays>14</delayDays>
<floaterFlag>N</floaterFlag>
</FixedIncomeModel>
</genericSMF>
</referenceTransaction>
</EagleML>

ESP-833 Improve the delete functionality for the IssuerOrganization interface

Added support within the IssueOrganization interface to be able to delete multiple records at a time. 

Introduced the following rules:
xml-ref_delete.xml
parse_issuer_xref.inc
ref_issuerorganization_delete.inc

Modified the xml-ref_objects.rsf rule to utilize the new rules.

In order to delete records, the EagleML/referenceTransaction/header/action tag must be to DELETE.

Example:
<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="ReferenceTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0eagleml-main-2-0.xsd" xsi:type="ReferenceTransactionMessage">
<header>
<sentBy>http://www.eagleinvsys.com/</sentBy>
</header>
<referenceTransaction>
<header>
<objectType>IssuerOrganization</objectType>
<action>DELETE</action>
</header>
<issuerOrganization>
<objectType>IssuerOrganization</objectType>
<objectId>IssuerOrganization</objectId>
<objectDescription>IssuerOrganization</objectDescription>
<updateTimestamp>2018-03-05T13:15:21</updateTimestamp>
<sourceName>EAGLE PACE</sourceName>
<updateSource>MCADMIN</updateSource>
<effectiveDate>2018-03-09</effectiveDate>
<issuerId>ESP833_1</issuerId>
<issuerName>ESP833_1 NAME</issuerName>
<countryOfIncorporationCode>US</countryOfIncorporationCode>
<currency>USD</currency>
</issuerOrganization>
</referenceTransaction>
</EagleML>


ESP-855: Adjust switch DERIVE_OPT_PST to populate ProcessingSecurityType for Options

There was previsouly no logic that would allow derivation of the processing security types for options.

The DERIVE_OPT_PST switch was utilized to create the W_GENERICCMF_DERIVE_OPT_PST parameter. When this is set to a value of "Y" the following logic will be applied:

  • if <processingSecurityType> for Underlying SMF starts with “DB” - for the main SMF tag 3931 should become OPOPDB;
  • if <processingSecurityType> for Underlying SMF starts with “IN” - for the main SMF tag 3931 should become OPOPIX;
  • if <processingSecurityType> for Underlying SMF starts with “FT” - for the main SMF tag 3931 should become OPOPCM;
  • if <processingSecurityType> for Underlying SMF starts with “EQ” - for the main SMF tag 3931 should become OPOPEQ;

This functionality is only available when <accountingValidationFlag> = N.

List of files changed: 

eagle/estar/tpe/dynamic/msgcenter/eagle_default/in/xml/include/smf_core_mapping_tmp.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_default/in/xml/include/smf_derive_opt.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_default/in/xml/include/underlying_smf_ins_upd.inc


ESP-858 Enable a conditional parameter to manage the routing for splitting and processing for the Generic Loader Workflow

When the RealTime RTR processing stream receives an RTR there is now an option to resend that RTR to the eagle_ml-2-0_default_cm_control_message stream.

To turn on this option the W_RESEND_TO_REQUEST_STREAM variable  should be added to the w_config_custom.inc with the desired value.

Example: <CODE>:W_RESEND_TO_REQUEST_STREAM: :='EXPR#iif(Find(\5C3AIN_MESSAGE\5C3A,\'&lt;value&gt;some_workflow_name&lt;/value&gt;\')\5C21=-1,\'Y\',\'N\')'; </CODE>

Rule affected:

tpe\dynamic\msgcenter\eagle_ml-2-0_cm\in\xml\realtime_rtr.xml


ESP-859 Enable a new RTR parameter to make the ACK generation conditional during the generic load workflow

To improve real time processing, a task parameter was introduced to control the ACK generation.  The EnableACKSwitch now allows control within an RTR to return an ACK. When the EnableACKSwitch is Y or omitted then the ACK will be produced.  If theEnableACKSwitch = N, the ACK will not be sent.

<taskParameter>
   <name>EnableACKSwitch</name>
   <dataType>S</dataType>
   <value>N</value>
</taskParameter>

Rule affected:
tpe\dynamic\msgcenter\eagle_ml-2-0_cm\in\xml\realtime_rtr.xml


ESP-860 Add Split Rule to Entity

A split key was added to the inbound entity interface for cases when HistoryMode = "N". The split key expression is the concatenation of the entityId and effectiveDate fields. 

Simulataneously loading sever GenericEntity objects with the same entity id would create errors in the journaling step in the stored procedure. The addition of the split key mitigates these errors. 


ESP-872 Entity Extension - insert/update logic not matching entity core logic

Previously entity extension fields with blank values would override already populated non-blank values in the database. 

Logic was changed to allow skipping the update of such fields that already have a value populated in the database but do not have any value for the same field present in the incoming message.



ESP-987 Include Tag 1418 - nra_tax_country into the EagleML Security Resolution

Incorporated the nra_tax_country as an option for security resolution. 

The following rules were modified.

match_all_new_record_check.inc
match_all_sec_resolution.inc
security_resolution_generic.inc


ESP-989: WarehousePerfomance records failed to load with statusFlag = F

Errors were noticed when loading warehouse performance records outside of batch mode and with statusFlag and reloadFinalFlag both set to "Y". These errors were being caused by the roll-up since this functionality is only available in batch mode.

Logic was changed for when this load is executed with the statusFlag and reloadFinalFlag both set to "Y". Now this load will only be executed in batch mode. 

File changed:
xml-dbdirect_common.inc


ESP-998 Problem after changes in ndfa stream in Feb 2018 EagleML release 

Code was changed to truncate file names that had no GUID prefix whose length exceeded 17 characaters. 

The logic for renaming files was changed. A new fileGUID parameter was added to the ndfa.prf file and corrected renmaing conventions were added to the read_datamaps.inc file.  


ESP-1005:  Eliminate duplicate mapping for the legalName node in the xml-ent_entitygeneric.xml

Entity records contain two references to the same database field. These have different paths: legalName and legalEntityId\legalName. Previously if one of these nodes was left blank the RULESDBO.ENTITY.LEGAL_NAME would not be populated. 

New logic was added that allows the inbound entity record to have no value in the leaglEntityId\legalName node and still load the value from the legalName root node to the database. 

Files changed:
xml-ent_entitygeneric.xml
eagleml_entity.xml



ESP-1023 Write of the Task Status Response (TSR) failing during FTP distribution with a success status displayed in EJM

When the FTP delivery method was used for the reply message in the Task Status Response (TSR), the TSR was failing, but reflecting success in EJM.  Updated the underlying logic to display a status of Failed if the TSR distribution also fails.  

Modified the reporter_dist_methods.inc to include new parameters.  Added the parameters varDistributionErrors and varDistributionStatus for the FTP method. The variables are set during the distribution step in the reporter_dist.inc file. After the distribution step is completed, the task reporter rule evaluates the distribution status.  If the distribution fails, the task reporter modifies the TSR message (setting the status to FAILED and adds the error description) and updates the overall task status to "FAILED". The w_ignore_distribution_errors parameter should be set to 1 to disable this feature (by default the parameter is undefined) in the "w_config_custom.inc".


ESP1035 W_CREATE_UNDERLYING should work for SMF MI stream and be able to prevent underlying shell security creation

The SMF MI stream was not preventing the creation of underlying shell security records even when the W_CREATE_UNDERLYING parameter was set to "N".

The logic for creating underlying shell records was moved from the SMF MI stream to the generic SMF stream. This stream already had support for the W_CREATE_UNDERLYING_FLAG and would skip creation if the parameter was set to a value of "N".

Files changed:
smf_core_mapping_tmp.inc
smf_egl_gen_interface_template.xsl
smf_egl_gen_interface_template_mssql.xsl
underlying_link_ins_upd.inc
underlying_smf_ins_upd.inc
xml-smf_generic_batch.prf
eagleml_smf.xsl



ESP-1056 - Performance Improvements for the EagleML - SMFEXTRACT when the historyonlyflag passed with a Source filter

Improved the logic within the Generic SMF extract when the historyonlyflag set to Y and a source or sources included.

        <taskParameter>
               <name>historyonlyflag</name>
               <dataType>S</dataType>
               <value>Y</value>
        </taskParameter>
        <taskParameter>
               <name>datasources</name>
               <dataType>S</dataType>
               <value>EAGLE PACE,STARDIRECT</value>
        </taskParameter>

The original logic was updated:

Original Logic:

FROM SECURITYDBO.SECMASTER_HISTORY SECMASTER_HISTORY,
 ...
WHERE (1=1)
 ...
 AND EXISTS (SELECT I.SHORT_DESC
   FROM PACE_MASTERDBO.INTERFACES I
   WHERE I.INSTANCE = SECMASTER_HISTORY.SRC_INTFC_INST
 AND TRIM(I.SHORT_DESC) IN ('EAGLE PACE','STARDIRECT'))
 
Updated logic:
FROM SECURITYDBO.SECMASTER_HISTORY SECMASTER_HISTORY,
 PACE_MASTERDBO.INTERFACES INTERFACES,
 ...
WHERE (1=1)
 AND SECMASTER_HISTORY.SRC_INTFC_INST = INTERFACES.INSTANCE(+)
 ...
 AND SECMASTER_HISTORY.SRC_INTFC_INST in (:1,:2)

Files changed:
- extract_smf.inc
- extract_filter_sources.inc


ESP-1180 Regression -  The Extract file name in the TSR intermittently not matching the actual name of the extract file created when the ExtractNamePatternEx task parameter uses the @DateTimeStamp

When applying the ExtractNamePatternEx parameter (e.g. SMPL_EML_@FeedType_@DateTimeStamp_@CorrelationID_@RecordCount.xml), the extract file name created in the Extract file name in the TSR did not match at times the actual name of the extract file.

<taskParameter>
<name>ExtractNamePatternEx</name>
<dataType>S</dataType>
<value>SMPL_EML_@FeedType_@DateTimeStamp_@CorrelationID_@RecordCount.xml</value>
</taskParameter>

The modification was to update the extract_eofw.inc file by removing duplicate code that was managing the transformation of the extract file name


ESP 1181: Issuer Role non-parametrized select in eagle_ml-2-0_default_in_xml_reference stream

IssuerRole objects received an increase in performance. 

The select for this interface was not utilizing bind parameters, causing it to not execute as fast as it could if it did use them. 

Once the bind parameters were added, a significant performance improvment was noted.


ESP-1192 Support additional columns in the XSD for pricing and pricing center

Updated the XSD to support new fields in the SECURITYDBO.PRICE and SECURITYDBO.PRICE_EXCHANGE tables.

The following elements have been added to the IssuePrice.model (included to IssuePrice and ExchangePrice XSD complex types):
percentChange1m
percentChange3m
percentChange6m
percentChange1yr
percentChangeWtd
percentChangeMtd
percentChangeQtd
percentChangeYtd
pxDirtyClean
pxSettle
pxSettleLastDate
quotedSpec

File changed: eagleml-ref-shared-2-0.xsd

ESP-1193 Update the analytics XSD to reflect additional elements

Additional fields have been introduced into the analytics functionality.  The new fields incorporated into the SECURITYDBO.SECURITY_ANALYTICS_FI, SECURITYDBO.SECURITY_ANALYTICS_DERV and SECURITYDBO.SECURITY_ANALYTICS_EXT DB tables have been added to the XSD schema.

1. The following elements have been added to the AnalyticFI.model (included in the GenericIsueAnalyticModel.model group):
dv01Bid
dv01Ask
dv01Mid
sdv01Bid
sdv01Ask
sdv01Mid
dv100Bid
dv100Ask
dv100Mid
2. The group AnalyticDerv.model has been added to the schema and to the complex type AnalyticDervModel with the following elements:
deltaBid
deltaAsk
deltaMid
deltaLast
gammaBid
gammaAsk
gammaMid
gammaLast
vegaBid
vegaAsk
vegaMid
vegaLast
impliedVolatility
impliedVolatilityBid
impliedVolatilityAsk
impliedVolatilityMid
impliedVolatilityLast
intrinsicValue
tradeMatchVolatilityPrice
theoreticalValue
optionUndNotionallRisk
optionBeyRisk
optionPointValue
daysToExpiration
ctdBeyRisk
financeRate
financeRateCurrency
3. The group AnalyticExt.model has been added to the schema and to the complex type AnalyticExtModel with the following elements:
roundLotSize
priceToCashFlow
tradeLotSize
sortinoRatio
abbrevTradingPeriod
averageVolume5d
averageVolume20d
interpolYieldSpread
interpolYieldSpreadGovt
zBasisConstMaturity
assetSwapSpread
ytmBid
ytmAsk
ytmMid
pricePositionMultiplier
maxDrawdownLength
maxDrawdownPercent
dvdYield12m
peRatioEst
epsLtg
downsideRisk
totalVotingShares
totalNonVotingShares
4. Created the analyticDervModel to include the complex type AnalyticDervModel and analyticExtModel of complex type AnalyticExtModel. These elements have been added to the GenericIssueAnalyticModel.model.

The group GenericIssueAnalyticModel.model is included in the GenericIssueAnalytic complex type.

Files changed: eagleml-ref-2-0.xsd, eagleml-ref-shared-2-0.xsd, eagleml-shared-2-0.xsd.