This release uses XSD Revision 232.

Enhancements

EagleML

EagleML Entity Accounting Mashup Extract Workflow

Previously, three separate extracts in EagleML were required to determine if the accounting periods for an entity was open. The code was enhanced. The separate extracts were replaced with a new workflow that uses already existing SQL to access the necessary table and run the extracts with the proper filters to keep the extracted information to the relevant entities.
This issue was tracked as Item #144042.

Support for Entitlements and Partitions Filters in Extracts

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.

Added Additional Details to STAR Event TSR

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.

Added logic to Hierarchy Flag

EagleML was enhanced with logic to be able to extract all child elements from entities with types of "COMP" or "LIST". The extract_filter_entity.inc file was edited to allow for the logic to take effect.
This issue was tracked as Item #145390.

Support for Delete Logic in POSITION_DETAIL_ANL_USER

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 Generic Issue Analytics extract had some missing fields as well as some fields that did not match the input originally used in the Generic Issue Analytics load. The eagle_default/in/xml/ xml-ref_genericissueanalytic.xml and eagle_ml-2-0_cm/out/xml/ t_generic_issue_analytic.xml rules were updated to resolve these issues.
This issue was tracked as Item #133284.

Shortened Timeout Interval in ref_custom_field.inc File

There was a timeout interval that was set to sixty seconds in the ref_custom_field.inc file that was triggered when waiting for the extension file. However, it was not necessary for the interval to be so long. The code was updated to make the interval only 10 seconds.
This issue was tracked as Item #136727.

Modified Security Resolution Option for UnderlyingSecurity

It is now possible to map the underlyingSecurity tag from an underlyingSecurity value from an incoming message instead of only relying on resolution logic that used tag 1141. This change was made because in some cases when tag 1141 was calculated to be null there was a benefit in taking an incoming value for underlyingSecurity and mapping it into the tag instead. The logic in the smf_egl_gen_interface_template.xsl has been changed to allow for mapping from both tag 1141 (still preferential) and from an incoming value of the underlyingSecurity.
This issue was tracked as Item #143149.

Fixed Automated Installer Stream's Handling of Recently Updated Files

There were issues with the automated installer stream not picking up on the files with more recent update dates than the package being sent to the stream. This could negate the functionality of the stream since the newest files would not actually be changed. There were four small changes made to the eagle_mc\installer\eagle_mc_installer.prf rule which allowed the installer to recognize and handle newer update dates.
This issue was tracked as Item #143650.

Resolved Issue with Filter Not Registering All Entity Xref Selection Values

When the entityselectionvalue parameter was used with the entityselectiontype set to "EntityXrefId", the SQL did not use all the provided values. The extract_filter_entity.inc file was updated to allow the SQL to properly search for records containing all the provided xrefs, not just the first one.
This issue was tracked as Item #143903.

Addressed Backwards Compatibility Issue for the Numeric Tag Values in Generic SMF Outgoing Messages

In earlier versions of EagleML , there was a certain format of tags that were present in the outgoing SMF message. However, in the more recent versions of EagleML only tags that are present in the rule as variables make it to the outgoing message. To address this issue, a a new flag called W_SMF_GENERICSMF_DEBUG was introduced. This flag has two values: Y and N. The default is N. When the flag is changed to Y, the new xslt smf_genericsmf_debug.xsl is used to make the outgoing message appear as it would have in the earlier releases.
This issue was tracked as Item #143944.

Issue with Redefining Incoming Tags for Generic SMF

Due to an issue, it was not possible to redefine most of the incoming tags in the generic SMF rule. To resolve this problem there were two solutions. The first requires defining any necessary variables in the xml-smf_generic_columns_before.inc file, while the other utilizes an xslt within the rule.
This issue was tracked as Item #144107.

Added Mapping to tag 989 to Allow Redefinition by Auto Includes

Previously, it was not possible to redefine Tag 989 as the current logic handled the incoming value only. Sometimes it is necessary to redefine an incoming value for this tag in the autoincludes. The smf_egl_gen_interface_template.xsl stylesheet was changed to allow for redefinition logic and the msgxchg_sec_core.inc file was adjusted to allow for the new XSLT variable.
This issue was tracked as Item #144349.

Corrected Issue with Special Characters in XReference Resolution (Extracts)

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.

Corrected Issue with Special Characters in XReference Resolution (Loads)

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.

Corrected Issue with Record Count on SMF Extracts
There was an issue that caused an incorrect count of records on SMF extracts when using History mode (HistoryOnlyFlag = "Y"). This issue was due to a key issue. To resolve the issue, the key was switched from the old logic SECURITY_ALIAS + EFFECTIVE_DATE to the new key: SECURITY_ALIAS + EFFECTIVE_DATE + SOURCE_NAME. The count is now accurate in all cases.
This issue was tracked as Item #145135.

Performance Improvements to Warehouse Open Lot Large Data Query

An extract for the warehouse open lot was not working efficiently when the data set was large. The code was update to improve the performance. The approach to access the ENTITY_ID field was modified to leverage a direct join to the position table.
This issue was tracked as Item #144542.

Added Accounting Periods Section to Inbound and Outbound Rules Accounting Basis

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.

Note: Accounting Basis is NOT supported in MSSQL environments.
This issue was tracked as Item #144666.

Added Support for Colon Character in Generic SMF

If the colon character was used in the incoming message for a generic SMF, there was a failure to match the xref identifiers. The inbound generic SMF rule was fixed in order to handle the colon symbol.
This issue was tracked as Item #144689.

Resolved Issue with calculateValidateLastPaymentDate for Currency Swaps

There were issues related to tag 2237 (calculateValidateLastPaymentDate) when loading through the multileg EagleML interface. This tag was not being sent to the panel since by the time the panel was called the value in this tag had already been purged. The logic for purging the value for tag 2237 was changed so that this value is passed to the panel.
This issue was tracked as Item #144743.

Restored Missing Fields in Entity Extract

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.

Fixed Issue with Pipe Character in Generic SMF Load

If a pipe character was present in the incoming message for a generic SMF load, the load would fail. The inbound generic SMF rule was altered to allow for the pipe symbol to be recognized and handled correctly.
This issue was tracked as Item #144847.

Added Flexibility to Naming Extract Files

Previously, you did not have much flexibility in naming extract files. The logic was changed to allow you to have access to several different variables that you can include in the file name. You can order the variables in any way to satisfy your file naming needs. The new task parameter ExtractNamePatternEx was added. Below is an example of the use of this parameter:

<taskParameter>
<name>ExtractNamePatternEx</name>
<dataType>S</dataType>
<value>tst_DateTimeStamp_RecordCount_@EntityList-FeedType.xml</value>
</taskParameter>

This issue was tracked as Item #144910.

Resolved Issue with Trial Balance Extract

There was an issue were the trial balance record could incorrectly return no data. This was due to logic in the rule being incorrectly coded with a misspelling. The outbound trial balance rule was fixed to resolve this issue.
This issue was tracked as Item #145028.

Fixed Security Resolution Logic for Warehouse Open Lot

The resolution logic for warehouse open lot was unable to recognize between the legs of a swap and this would sometimes result in the wrong leg being resolved by the rule. To resolve this issue, the payRecInd field was added to the security resolution. This field makes it known which leg of the swap is really being processed.
This issue was tracked as Item #145058.

Fixed data integrity of Earned Income Extract

If the wrong primary asset id was passed as a parameter for the earned income extract, data was still returned. This was incorrect behavior since there should be no data returned if the primary asset Id is incorrect. This issue was due to incorrect logic that would allow data to still be returned even if there was no security alias resolved by the rule. This logic was changed so that if there is no security alias found the processing immediately returns no data.
This issue was tracked as Item #145148.

Added Streaming Support for Several Extracts

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

The I2I delta process was updated so that it will now delete position and open lot records from the date closing the transaction and current process date to ensure the warehouse data is in sync between hub and spoke.
This issue was tracked as Item #141620.