Content Comparison

This release uses XSD Revision 239.

Enhancements

EagleML

Introduced New Fields to the Generic Entity Extract

New fields were added to the Generic Entity Extract. The following fields are now included:

• RULESDBO ENTITY PORT_COMP_TYPE

• RULESDBO ENTITY_STAR_PROCESSING ENTITY_ID

• RULESDBO ENTITY_STAR_PROCESSING SECTOR_TYPE

• RULESDBO ENTITY LEI and RULESDBO ENTITY_DETAIL ENTITY_ID

This issue was tracked as Item #146472.

...

Additional elements were added to the shareholder mashup extract. The SUBSCRIBEREDEEMEXTRACT rule was edited to allow access to the RULESDBO.ENTITY_SHARE_CLASS table. The following elements were added to this extract:

• className

• classStatus

• transferAgency

• taCode

• classTerminationDt

• classTicker

• classCusip

Each one correlates to a field in the database.
This issue was tracked as Item #146683.

...

The NAV Month End Extract received the following new fields:

• Market Value Base Cash

• Market Value Foreign Cash

The elements were added to the WHNAV extract which allowed them to be leveraged in the NAV month end extract.
This issue was tracked as Item #146860.

...

All extracts will now use bind parameters on dates just like the SMF and entity extracts do. The following rules were updated to make the binding of dates possible for all extracts:

• extract_filter_bind_pars_sql.inc

• extract_filter_date.inc

• extract_filter_date_one.inc

This issue was tracked as Item #146927.

...

Note: This interface is only available to DIS clients.
This issue was tracked as Item #145130.

EJM

Added Separate Warning Line for Overlay Activity

The EagleML package may contain panel overlays. If the target environment contains custom overlays with the same name, the EagleML Installer applies conflict resolution logic. Depending on installation parameters, either existing overlays are backed up, or the ones delivered with the release get installed with a different name. It was not easy to find these details in the Message Center Console's Status tab because they were buried under a lot of information in the standard output of the command line. Now, a separate warning line has been added. This warning line shows only overlay-related activity.
This issue was tracked as Item #145742.

I2I

Added I2I Xref Output Inclusion or Exclusion Functionality

I2I was enhanced to allow you to include or exclude certain xreferences in the output. This feature is based on the configuration of the SPOKE and only available for the SMFEXTRACT feed type. It makes it possible to select the types of xreferences that will be available to the SPOKE. The t_smf.xml and t_streaming_smf.xml outbound rules as well as one common I2I include were all changed to allow for this enhancement.
This issue was tracked as Item #144432.

Software Fixes

EagleML

ENTITY_XREF Node Missed

The ENTITY_XREF node was missing from the TRDC_EGL_GEN_INTERFACE. This node is important for security resolution. The code was changed to ensure that the node would show in the Warehouse Trade Charges interface as well as other related Generic interfaces.
This issue was tracked as Item #131365.

...

Two fields from Entity Bank Relationship were not getting stored in the database upon load. These are:

and

in the XSD. dTCBankId was not mapped correctly and custodyBankAccountName did not have the necessary tag association. The code was updated to resolve these issues.
This issue was tracked as Item #138575.

...

There was in incorrect mapping for tag 676 which had the element name mapped as forwardBrokerCode. This is inconsistent with the schema which shows the element as fwdBrokerCode. The following rules were edited for the mapping change:

• generic_smf_fields_logic.inc

• msgxchg_sec_core.inc

• smf_egl_gen_interface_template.xsl

The mappings now have the field listed as fwdBrokerCode.
This issue was tracked as Item #144243.

...

Additional parameters were added to leverage the report execution filters on the Realized Gain Loss extract. The filters include:

• entityIdType

• entityId

• accountingBasis

• reportType

• reportPeriod

• reportStartDate

• reportEndDate

• reportFilters

• filterSecurityBy

• xrefid

• xrefidtype

• primaryassetid

• issuename

• longShort

• eventType

• assetCurrency

• investmentType

• securityType

• processingSecurityType

The extract_acct_realized_gain_loss.xml rule was edited to allow these filters to work properly with the realized gain loss extract.
This issue was tracked as Item #145490.

...

The localCurrency filter did not work for the Earned Income Extract. This issue was because the parameters were case sensitive. For example, LocalCurrency would work but locaLcUrrency would not work. There was the same issue in several other extracts as well. The following extracts were updated to allow the filters used to all be case insensitive:

• CASHJOURNALEXTRACT

• CONSEARNEDINCOMEEXTRACT

• OPENRECPAYMULTIEXTRACT

• REALIZEDGAINLOSSEXTRACT

This issue was tracked as Item #146527.

...

There was in issue with the debtToCapital mapping in the wrh_egl_gen_interface3.xsl.bThe incoming field was named as in_debt_to_capt which was not consistent with the database field name which was in_debt_to_capital. The mapping in the XSLTwas changed so that there would be consistency between the incoming parameter and the database field.
This issue was tracked as Item #147667.

EJM

Changes to Eas_distribution_light.xml Rule

...