Versions Compared

Version Old Version 7 New Version Current
Changes made by

Former user

Kinga Huszno

Saved on

Key

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

This release uses XSD Revision 232.

Info

There are four overlay files that are currently packaged as part of the EagleML monthly release. Please refer to About EagleML Overlays for specific details and impact to you.

Enhancements

EagleML

EagleML Entity Accounting Mashup Extract Workflow

...

Several feed types received support for the entitlement and partitions filters in the feed types extract. The extract_filter_entity_entitlement.inc rule was changed to allow this filter to work with the following feeds:

  • FINANCIALEVENTEXTRACT

  • GLACTIVITYEXTRACT

  • SUBSCRIBEREDEEMEXTRACT

  • DAILYYIELDMILLRATEEXTRACT

  • DISTRIBUTIONACTEXTRACT

  • NAVFORNASDAQEXTRACT

  • ACCRUEDINCOMEEXTRACT

  • INTRADAYNAVEXTRACT

  • UNAPPROVEDVARMARGINEXTRACT

  • CUSTLEGERACCTEXTRACT

This issue was tracked as Item #144543.

...

Additional detailed information was included on the TSR for STAR events. The following information was added as part of each task unit in the TSR:

  • Start Time

  • End Time

  • Start Date

  • End Date

  • User Name

  • Report Group

  • Message Type

  • Event Type

  • Entry Profile Name

  • Result Profile Name

  • Entry Profile Panel Name

  • Result Profile Panel Name

  • Schedule Group

  • Report Viewer Group

  • Server IP

  • Process ID

  • Process Address

  • Process Port

This issue was tracked as Item #145112.

...

The POSITION_DETAIL_ANL_USER table is expected to be part of Eagle core in a future release and therefore the table needs to be accessible by delete logic. The xml-dbdirect_wrhs_delete_statement.inc file was updated to include this table.
This issue was tracked as Item #142131.

Software Fixes

EagleML 

Fixed Missing and Mismatched Fields in Generic Issue Analytics Extract

...

The xref resolution within GenericSMF and MulitLeg extracts had issues when the xref identifiers contained special characters. The following rules were fixed in order to allow for handling of the special characters in the xref resolution:

  • t_xrefidentifiers_fields_start.inc

  • t_xid_xidtype_start.inc

  • t_asset_identifiers_fields_streaming.inc

  • extract_financial_event.xml

  • extract_forwardpoints.xml

  • extract_xref_fields.inc

  • extract_filter_bind_pars_sql.inc

This issue was tracked as Item #144191.

...

The xref resolution within GenericSMF and MulitLeg loading had issues when the xref identifiers contained special characters. The following rules were fixed in order to allow for handling of the special characters in the xref resolution:

  • get_xrefs_list.inc

  • ins_upd_smf_req.inc

  • ins_upd_xrefs.inc

  • get_smf_all_xrefs_list.xsl

This issue was tracked as Item #144427.

...

Previously, the entity acct basis pulled back only the primary acct basis. The accountingPeriodsModel was added to both inbound and outbound accounting basis rules to resolve this issue. The repeated section <accountingPeriodsModel> has been added to Accounting Basis:

  • XSD type

  • inbound rule

  • outbound rule

Also, the streaming outbound t-rule has been created. The common code for load Accounting Periods has been moved to new include file ins_upd_acct_period.inc.

...

There were four fields that were no longer being included in entity extracts. These fields included:

  • CLIENT_ID

  • CASH_RULE_NAME

  • EARN_THRU_RULE_NAME

  • MONTH_RULE_DESC

The code was updated to resolve this issue. The fields were all added back into the extract via logic that involved using look up results and mapping.
This issue was tracked as Item #144757.

...

There were several feeds whose extracts were not being compressed even though the parameter to do so was specified. This was caused by the fact that these feeds did not have streaming rules and therefore, since the logic for the old t rules was not the same as that in the streaming t rules, the compression parameter was ignored. The following feeds were updated with streaming rules for extracts:

  • RATINGSEXTRACT

  • ISSUERORGEXTRACT

  • CODEVALUEEXTRACT

  • CASHPROJECTIONSEXTRACT

  • ISSUERRATINGEXTRACT

This issue was tracked as Item #145480.

EJM

Resolved Issues with Extract Location and Naming Parameters

CustomExtractLocation and ExtractNamePattern parameters were not working properly. The parameters were fixed for every feed type. A CustomWhere parameter was also added for all feed types.
This issue was tracked as Item #144933.

I2I

Modification of the I2I Delta Process

...