EagleML Release Notes - May 2015

Owned by Natalie Gesin (Deactivated)
Last updated: Dec 22, 2017 by Former user (Deleted)
7 min read

This release uses XSD Revision 201.

Enhancements

EagleML

New EagleML General Ledger Balances Interface

General Ledger Balances interface is now available in EagleML. Both inbound and outbound are supported.

This issue was tracked as Item #128899.


New Warehouse NAV MULTI Interface

EagleML support has been added for the interface Warehouse NAV_MULTI for both inbound and outbound. The load function (inbound) allows new additions or modifications to existing data. The extract function (outbound) creates a file.

This issue was tracked as Item #128987.


Additional Tags for Corporate Action Rules

Two tags have been added to the generic interfaces for Corporate Action rules. These tags are:

  • cp_pay_dt
  • cp_pay_crncy

cp_pay_dt can have a maximum of 11 characters and cp_pay_crncy can have a maximum of 3 characters.

This issue was tracked as Item #127058.


Added Support of Dynamic Entity Lists in EagleML Entity Extracts

EagleML Entity Extracts was enhanced to support dynamic entity lists. Previously, it supported only static lists. With this change, both static and dynamic entity lists are now supported in Entity Extracts.

This issue was tracked as Item #129499.


Added Checks in Client Inbound Interface for Contact Id, Entity Xref Identifiers and Entity Id

Checks to following have been added to the relationship section of the Client inbound interface:

  • Contact Id (element client/clientRelationship/relClientId)
  • Entity Xref Identifiers (elements in client/clientRelationship/entity/entityXrefs/entityXref node)
  • Entity Id (element client/clientRelationship/entity/entityId)

The Contact Id, Entity Xref Identifiers and Entity Id are now individually checked against the existing information within the database and are only considered successfully if they are located in the database. In addition, Contact Id or Entity Id are also checked to ensure they are not null.

This issue was tracked as Item #127428.


New Trade Quotes XSD Model to Reflect Trade Quotes Table

XSD inbound and outbound rules have been created for the new database table TRADESDBO.TRADE_QUOTES. This table is designed to include the following fields:

  • trade Id
  • bid
  • bid rate
  • bid spread
  • ask
  • ask rate
  • ask spread
  • quote type
  • broker
  • update date
  • update source

This issue was tracked as Item #129846.


Added Support for Warehouse NAV to inbound Warehouse Interface

EagleML was enhanced to include support of Warehouse NAV on the inbound rule of the warehouse interface. This enhancement included a new NAV XSL transformation template.

This issue was tracked as Item #129990.


Added Support of Custom Security Resolution Logic in EagleML

EagleML was enhanced to support custom security resolution logic. To leverage this feature, the variable var_mid_custom_res must be set to "Y" in the file eagle_ml-2-0_custom_cm/w_config_custom.inc. If this variable is not set to "Y", the default Eagle algorithm will be used. When the variable is set to "Y", the Eagle algorithm will be replaced by the custom algorithm. The custom algorithm must be defined in the file customer/eagleml/security_resolution_custom.inc.

This issue was tracked as Item #130010.


EagleML Extracts Support Custom Where Clause

EagleML Extracts now support a custom where clause. This is an optional parameter. To leverage this feature, you should add a CustomWhere task parameter in incoming RTR. For example:

<taskParameter>
<name>CustomWhere</name>
<dataType>S</dataType>
<value>[put_your_specific_where_expression]</value>
</taskParameter>

This issue was tracked as Item #130933.

EJM

EJM - ServiceNow Alerting Project Work

Eagle is currently working on a project that will allow EJM to send eight key alerts to our ServiceNow ticketing system to help identify potential issues in production environments. EJM was modified so we can configure which of these key alerts should be sent to ServiceNow, as the needs may differ by client. Please note that this project is still in progress and currently in a testing phase.

This issue was tracked as Item #128768.

Software Fixes

EagleML

Record Count Issue with EagleML Security Master Extract

When the Held Securities filter was used for EagleML Security Master extract, it did not fetch the correct number of matching securities. The code was updated to resolve this issue and the record count is now accurate.

This issue was tracked as Item #118917.


Issues With Generic Entity Inbound (SQL Platform Only)

There were issues with the EagleML Generic Entity inbound interface on the SQL Platform only. These issues were resolved and the interface is now works as expected on the SQL Platform.

This issue was tracked as Item #119306.


Issue Updating Issue Role Data (SQL Platform Only)

There was a problem when attempting to update existing issue role data on the Microsoft SQL platform. It was possible to add new data, but you could not change existing data. This issue was resolved by updating the eagle/star/reference/pan-chgissuer_role.htm panel to allow for existing data modification.

This issue was tracked as Item #119997.


Issue Adding Entity Accounting Periods

There was an issue with Entity Accounting Periods interface. The stored procedure parameter in_type was not defined in the Accounting_Periods database and would always carry a value of 'CHG'. This created a problem with uploading new information to the database. The code was updated so that information can now be added. If the information does not already exist, the value of the in_type parameter will be set to 'ADD' and the data will be added. If the data is already present, it will be set to 'CHG' and the data will be modified rather than added as a new entry.

This issue was tracked as Item #127049.


Generic SMF Rule Updates for HistoryOnly Flag and Improved Error Message

The generic SMF rule file (xml-smf_generic.xml) was updated for two minor issues. Mapping was added for the historyOnlyFlag. This field is now mapped to the in_trans_type parameter. In addition, the error message when security alias was not resolved in the case of multilingual was updated to be more informative. The new message is:

Unable to resolve security_alias based on the inbound identifier(s) provided. Security_alias must be resolved when uploading multi byte information

This issue was tracked as Item #128577.


Support for Special Characters in SMF Inbound Interfaces

The SMF inbound interfaces now support XML special characters, including:

<

>

&

"

'

Note: If you are not using IWS, you must ensure that these special characters are properly encoded.

This issue was tracked as Item #128631.


Support for Special Characters in Entity Inbound Interfaces

The Entity inbound interfaces now support XML special characters, including:

<

>

&

"

'

Support of these XML special characters has been specifically tested in these Entity inbound interfaces:

  • GenericEntity
  • BenchmarkAssignment
  • EntityAccountingBasis
  • EntityAccountingPeriods
  • EntityBankRelationship
  • EntityComposite
  • EntityList
  • EntityManager
  • EntityManagerRelationship
  • EntityToComposite
  • EntityToList

Note: If you are not using IWS, you must ensure that these special characters are properly encoded.

This issue was tracked as Item #128632.


Issue with First-Match Mode Updating SMFs Based on Xrefs

The EagleML inbound interface could incorrectly return the error ''Duplicate Security Found' when in match first cross-reference identifier mode. The resolution logic inappropriately considered more than just the first matching identifier and created an error if all the identifiers did not match. The eagle_default/in/xml/xml-smf_generic.xml rule was updated to allow the security to be found using the match first cross-reference identifier mode and also update the other identifiers appropriately.

This issue was tracked as Item #129266.


Added Edit Checks for All Generic EagleML Streams

The inbound rule for the EagleML reference objects needed to include an edit check for the following objects:

  • AnalyticEquity
  • AnalyticFI
  • Calendar
  • CalendarHoliday
  • Client
  • ClientCommunication
  • CodeValue
  • CodeCategory
  • CodeTranslation
  • ErrorDefinition
  • ExchangePrice
  • Factor
  • GenericIssueAnalytic
  • GIPSDisclosures
  • GIPSComposite
  • IssueAnalytic
  • IssueFxRate
  • IssueFxPcRate
  • IssuePrice
  • IssuerRelationship
  • IssueVariableRate
  • SMFIdentifier
  • TimeSeries
  • TradeQuotes
  • YieldCurve
  • Generic CA
  • Accounting CA
  • Voluntary CA Elections
  • Mandatory CA Exclusions
  • Security Notes
  • Issuer

These edit checks have now been added. The edit check allows exceptions created by the XSL transformations to be handled properly.

This issue was tracked as Item #129874.


Removed Extra Mapping for TRADE.COST_BASE and TRADE.COST_LOCAL in EagleML Outbound

There was an inconsistency in the mappings of TRADESDBO.TRADE.COST_BASE and TRADESDBO.TRADE.COST_LOCAL in EagleML inbound and EagleML outbound. Inbound, TRADESDBO.TRADE.COST_BASE was mapped to openCostBase and TRADESDBO.TRADE.COST_LOCAL was mapped to openCostLocal. Outbound, these fields were mapped as they were in the inbound but were additionally mapped so that TRADESDBO.TRADE.COST_BASE also mapped to costBase and TRADESDBO.TRADE.COST_LOCAL also mapped to costLocal. The outbound rule was updated to remove the additional mapping to the other fields. Both inbound and outbound now only map to openCostBase and openCostLocal respectively.

This issue was tracked as Item #130127.


Warehouse Trade, CloseLot and OpenLot Inbound Interfaces Could Create Duplicate Records

When the master ticket number field was null, the warehouse trade, warehouse closelot and warehouse openlot inbound interfaces would create a duplicate record instead of returning an error indicating the master ticket number should not be null. An edit check was added to ensure an error is now raised if the master ticket number is null and duplicate entries will not be created. Entries that have a matching master ticket number, entity Id, source name and security alias to a security that already existing in the TRADESDBO.TRADE table will be treated as updates instead of being stored as a new entry.

This issue was tracked as Items #130135 (trade), #130141 (closelot) and #130166 (openlot).


Warehouse CashActivity Inbound Interface Could Create Duplicate Records

When the original transaction number field was null, the warehouse cash activity inbound interface would create a duplicate record instead of returning an error indicating the original transaction number should not be null. An edit check was added to ensure an error is now raised if the original transaction ticket number is null and duplicate entries will not be created. Entries that have a matching identification fields will be treated as updates instead of being stored as a new entry.

This issue was tracked as Item #130167.


Generic Entity Failed for Versions Prior to v13.0

The Generic Entity failed for versions prior to v13.0 due to an issue within the rule. The rule contained a parameter mismatch with stored procedure INSERT_UPDATE_ENTITY_INFO. The code was updated and the Generic Entity now works properly for all supported versions. This issue was tracked as Item #130354.


Issue Reading EagleML Version

The logic that determined which EagleML version from the w_config.inc file was flawed and could result in incorrect information returned. The code was updated to resolve this issue.

This issue was tracked as Item #130413.


Issues with JAVA Generated Control Messages

In the XSD revision 200, for the eagleml-msg-2-0.xsd, the group PartiesAndAccounts.model was deleted from the RunTaskRequest complex type. This deletion was required as it was added in error and it caused users to not be able to use JAVA generated control messages.

This issue was tracked as Item #130425.


WSDL for EagleMLWebServices Updated

The WSDL for EagleML webservice has been updated. A new SoapAction ReferenceTransactionMessage was added. This method represents EagleML objects direct synchronous load.

Note: Only the GenericSMF object load is supported currently.
This issue was tracked as Item #130426.

EJM

Incorrect Success Status and Accounting Entity Period Setup Issues with Generic Interface

There were a few issues with the Generic Entity interface that were resolved. The control messages for Generic Entity could return a success status despite the occurrence of errors. The code was updated so that the status will now show as success only when no errors occurred. In addition, there were errors around the accounting entity periods step within the Generic Entity. These errors have also been corrected.

This issue was tracked as Item #127696.


TSR Incorrectly Reported Success When File Not Delivered via FTP

A Task Status Response (TSR) incorrectly returned a success in the case of lack of an extracted file. It was determined the extracted file was not delivered via FTP due to a connection time out as a result of incomplete retry logic. The retry logic was updated and now if an extracted file is not delivered, it will be reported as a failure in the TSR.

This issue was tracked as Item #130093.