This release uses XSD Revision 220.

Enhancements

EagleML

New Corporate Actions Flag
The flag corpActIDLikeMatchFlag was added to the corporate action interface. This new flag can be set to 'Y' to make the option of finding CorpAction and VolCAElection records available. This flag can be used in an RTR for either insert, update or delete modes. With this enhancement, a new message mapping was added to the rule_xmlref_voluntarycaelections.xml inbound rule.
This issue was tracked as Item #135073.

New Fields in Accounting Trades Interface
The accounting trades interface received two new fields:

• CASH_ACCOUNT_NAME
• CASHACCOUNT NUMBER

These tags can be used to store cash account data in the accounting trade tables within the database. The tags are included on the run task request (RTR) messages. Valid entries must be present in the RTR for the fields in the database to be updated.
This issue was tracked as Item #133469.

Improved Issuer Role Logic 
Issuer role logic was modified for performance improvements. Loads and updates for the issuer role objects are now more efficient. The

• eagle_default/in/xml/xml-ref_issuerrole.xml
• eagle_default/in/xml/include/xmlref_issuerrole_common.inc
• eagle_default/in/xml/xslt/eagleml_smf_issuer_role.xsl

rules were all updated, with the major change being the replacement of look up logic with a direct message mapping. Additionally, the xreference resolution logic was added to allow for lookups using these identifiers.
This issue was tracked as Item #135600.

Tags Added to the Accounting Interface
The fields Manual Call (tag 7020) and Schedule/Unschedule Payment (tag 16008) were added to theAccounting interface. The two tags show up on the RTR EagleML messages. The tags must be appropriated with the available values in order to be processed correctly.
This issue was tracked as Item #133468.

Asset Identifiers Model Group Updates
There were several fields by which you could query the database but were not included in the asset identifiers model group. Therefore, there was inconsistency. Fields that can be used to run a basic SQL query with the goal of returning an asset should also be included in the model group that embodies this purpose. To resolve this issue, the following fields were added to the asset identifiers model group:

• <investmentType>
• <processingSecurityType>
• <securityType>
• <releaseStatus>
• <issueCountryCode>

This issue was tracked as Item #135985.

Added New Rating Objects Filter
A new filter was created for extracting rating objects. This feature can be used by including the necessary task parameter in a control message sent to the eagle_ml-2-0_default_cm_control_message stream. This greatest effective date filter will grab one record with the most recent effective date that does not surpass the date passed in the parameter. This was all controlled by adding the task parameter called maxeffectivedate.
This issue was tracked as Item #136118.

Added New Fields in Generic Corp Actions Interface
A new element <originalTransType> was added to the generic Corporate Action interface. In some cases using CANCEL as the Trans type would not be enough for the system to recognize which record should be cancel. To safeguard against this issue, the <originalTransType> element was added and is populated with the original Trans type.
This issue was tracked as Item #136608.

EJM

Multiple File Masks in One Workflow
EJM was enhanced to allow multiple file masks in one workflow. Instead of having to create multiple workflows that parallel each other in order to process different types of files, one workflow can now be used to process all them. This item is pertinent to the Integrated Workflow Studio (IWS). The code was updated to allow for such multiple masking.
This issue was tracked as Item #137750.

New eagle_wrf_default_purge Workflow
A purge workflow that had been used internally by Eagle's QA team has been converted to a default workflow named eagle_wrf_default_purge workflow. This workflow now confirms to the standards of all other eagle_wrf_default* workflows. It is now included in the EagleML package.
This issue was tracked as Item #135394.

Software Fixes

EagleML

Mapping Issue in Corporate Actions Interface - Oracle Only
The corporate actions interface had a missed mapping for one of its tags. VOL_CORP_ACTION_ELECTION.LONG_SHORT_INDICATOR was not properly functional and therefore would not allow for manipulation of data in the database tables. This was an Oracle environment specific issue. It occurred when sending a corporate action object for load through the eagle_ml-2-0_default_in_xml_reference stream. To resolve this issue, the mapping was added to allow the proper execution of the corporate action load.
This issue was tracked as Item #134954.

Fixed Message Mappings in Add Issuer Rating and Delete Issuer Ratings Rules 
Message mappings were edited in the Add Issuer Relationship and Delete Issuer Relationship panels. These panels need proper message mappings to operate correctly and to be able to execute lookups, as well as carry out the addition or delete action. The issue occurred specifically in the xml-ref_issuerrelationship.xml rule. The code was updated with the correct mappings.
This issue was tracked as Item #135652.

Fixed Issuer Organization Logic
The issuer organization rule contained incorrect logic that could result in certain fields not be returned as expected. This problem occurred during load of issuer organization objects through the eagle_ml-2-0_default_in_xml_reference stream. The root of the problem lay within the potential of a field not getting populated with any value in the case when a lookup panel returned no matches. The code was updated to resolve this issue and now also now includes a safeguard that will render the field with a default value in the case of no matches.
This issue was tracked as Item #135728.

Increased Performance for Secnotes Rules
The secnotes rule was performing at a lower speed than desired. The reason for this rule's under performance was hinged on the fact that it relied on a panel call to find the required information. The code was updated to avoided making a direct call to the engine instead by including some new message mappings.
This issue was tracked as Item #135830.

Issue with Generic Deletion for Entity Interface
The Entity generic delete was not functioning. The workflow would not execute properly. The problem was due to links that were not functional and has been corrected. Additionally, some minor changes were made to increase performance. These changes included warehouse deletion were moved to the front of the solution, cm parameters were added to the main workflow and conditions were added to allow for execution of GENERICS and ISSUER deletion workflows.
This issue was tracked as Item #135947.

Issuer Organization Rule Generates Duplicates 
The issuer organization interface had a problem with the creation of duplicate records in the database. For this particular object, it is sometimes necessary to have duplicate records with the only difference being the source name. This issue was only relevant in the case of loading issuer organization objects through the eagle_ml-2-0_default_in_xml_reference stream. There was logic that did not allow duplicate records to be added with different source names. The logic was rewritten to make the source name the primary key for these objects and allow other fields to have the same value as records that already exist in the DB as long as the source names or these records were different.
This issue was tracked as Item #136338.

Missing Field in Entity Extracts 
The limit loss indicator was missing from entity extracts. During extracts through the EJM this field would not show up. The reason for the field not getting pulled up was due to a missing code that added the field to the final extract file. The q entity rule had the code necessary to extract the element but the t_entity.xml rule was incomplete and therefore was unable to deliver the properly formatted extracts. The code was updated to resolve this issue.
This issue was tracked as Item #136730.

Issue with Corporate Action Cancels
Corporate Action Cancels were not working. The code was updated to resolve this issue. Corporate Action Cancels now work as expected.
This issue was tracked as Item #136939.

Errors with Forward Leg of Multi Leg Contracts
The forward leg on multileg contracts was not processed correctly. This issue mostly occurred when records with no begin date were generated and sent for load. The problem lay within the logic that would attach the current date for any record with no begin date. When sending records for updating within the database, the begin date would often be left off. In this case a record with the same data except for the begin date was created instead of the desired update. The code was updated to resolve this issue.
This issue was tracked as Item #136952.

New Flag for CSV to EagleML Version of Warehouse Open Lot Rule 
Warehouse position tables were getting rolled up during warehouse lot load. It is a regular procedure to typically roll up the position tables during lot loads, but sometimes there is a need to keep the processes separate as there is more specific information in a separate positions file. This issue only happens on the CSV to EagleML version of the lot load rule. EagleML had a similar item which was resolved with a flag that controlled the roll up. This flag was leveraged for the CSV version of the rule and as long as the RTR is sent with the value of the flag set to "Y" the records do not get rolled up.
This issue was tracked as Item #137368.

Issue with CSV to EagleML Warehouse Objects 
There were issues with CSV to EagleML for warehouse objects. Specifically, the problem occurs on the CSV to EagleML version of the inbound warehouse rule. The logic would previously only use certain tags to go through the security resolution process. These tags were not as direct as tags 14, 1432, 1233, and 1234. Since the core CSV version can support these tags, the resolution process was edited to include them as the primary keys.
This issue was tracked as Item #137369.

Issue with Non Multi Leg Swaps
Non-multileg swap securities were not being updated due to a flaw in the resolution logic. This created processing problems and data issues since necessary fields were not updated. When sending a record of a non-multileg swap for updating, the logic would fail and create a new duplicate record rather than updating the existing one. The resolution logic was corrected to recognize existing credit default swaps and update them accordingly.
This issue was tracked as Item #137631.

Issue with SMF Extracts When Extensions Table Called
The SMF extract was not working due to the extensions table being included in the SQL request within the rule. This issue only occurred in the case of extracts involving the SMF extension tables. The SQL contained two different syntax for joins which could not be used in the same statement. The code was updated to resolve this issue.
This issue was tracked as Item #137919.

Cancel Issue with Accounting Trades Interface  
There were issues with the cancellation of accounting trades. This issue applied to any cancellation of an accounting trade object. The <accounting Trade/undercounting> field had an incorrect mapping that would cause problems when the cancellation feature was used. The mapping was edited so that the cancel feature now works as expected.
This issue was tracked as Item #138018.

Issue with Compression of Extracts
Large extracts were not getting compressed into zip files. The impact of this issue is that large uncompressed files could result in time out errors. This scenario only occurred during extracts of very large files. The issue stemmed from the compress_extract.inc include file which controlled the task parameter that would be used to compress the files. The include was corrected and compression now works as expected on large files.
This issue was tracked as Item #138048.

EJM

Subprocesses Showed Success Despite Having Errors When Diskspace Issue
EJM could show false positives for the sub processes of a workflow's execution. During execution any given sub process could encounter an error and still show up as a successful execution in the case of when of lack of disk space was encountered. This issue occurred in the EJM framework when a control message would be sent to the eagle_ml-2-0_default_cm_control_message stream. The underlying cause of the issue was a lack of disk space which would cause the preprocessor to fail without sending a TSR with an error status. The code was updated to resolve this issue. A failed TSR will now be sent in the event of the preprocessor not working properly even when disk space issue is encountered.
This issue was tracked as Item #135827.

Unprocessed TSR Not Received
In some instances EJM was unable to pick up on completed sub processes and would show the workflow as still in progress. This issue can cause performance concerns since the workflow technically never finishes if any of the sub tasks are not reported. This issue only occurred if a workflow had multiple sub processes finish at the same time. A catch mechanism was created to handle situations in which more than one sub process would terminate at once.
This issue was tracked as Item #136784.

Incorrect TSR When Lack of Virtual Memory and Message Center Restart
While TSR reported a success status, some data was actually not loaded into the database. This scenario occurred in cases where there was a lack of virtual memory and Message Center restarted. To mediate this problem, the TSR logic was changed to send a failure response in the case of lacking virtual memory.
This issue was tracked as Item #137471.

Interfaces without Extract Functionality - Windows Only
Some interfaces did not have the functionality of extracts. This issue affected Windows platforms only. The outbound warehouse rules were updated with new blocks of code that would execute the SQL necessary to trigger the extracts.
This issue was tracked as Item #136840.

Extract Issue with Warehouse Activities - Windows Platform Only
WH Close Lot, WH Performance and WH NAV activities did not extract as expected. This issue affected Windows platforms only. The code was updated to generate SQL request in following extracts:

• WH Close Lot
• WHPerformance
• WH NAV
• Pending Trade
• Cash Flow Projection

This issue was tracked as Item #138142.

Data Files with Transformation Results Missing from the TSR - Linux Only
Data files with transformation results, produced by the transformer streams on the workflow steps, were missing from the consolidated TSR of the whole workflow. This issue only occurred in Linux environments. The issue occurred because those data files were not properly added to the PACE_MASTERDBO.ORCH_REQUEST_PARAMS table due to the wrong file mask of the corresponding trigger file. The code was updated to resolve this issue. The data files are now listed in the consolidated TSR as expected.
This issue was tracked as Item #138166.