SDP-18770: Enhance object type User to allow similar usernames to be added
There was a problem with loading the User and User Group if the Username is a part of another Username that is already loaded. The panel that checks for the existence of an User uses a wildcard clause instead of an EXACT match resulting in an error indicating an unsuccessful attempt to update an existing User.
For example, if a User with the Username 'EAGLEUSER123' already existed on the environment there was the potential to load a User 2 with the Username 'EAGLEUSER12'.
The User check was updated for resolving the User by an exact match in the User and User Group inbound interfaces. The same problem was fixed for the Center Role existence check.
This option to lookup users and center roles by an exact match is supported in panels starting with the 2017R2.11 version only.
Files changed:
eagle_default\in\xml\include\user_common.inc
eagle_default\in\xml\include\user_group_common.inc
SDP-10367: Enhance the Date format option naming convention
Added a new expression @DateTimeStampISO as part of the custom extract name pattern parameter ExtractNamePatternEx to specify the datetime value in the output file name as YYYYMMDDTHHMMSS format (with the ‘T’ separator between the date and time values).
Files changed:
parse_tp_pattern.inc
SDP-18516: Incorrect final WrfStatus
The task reporter rule was modified to make the final workflow status to be consistent with the TaskStatusResponse Status when the CreateConsolidatedTSR was set.
File changed:
task_reporter.xml
SDP-18616: Missing mapping for the long_short_ind in SPD DELTA LOG request
The rule for the SPD DELTA LOG file did not delete the Position records as mapping for the longShortIndicator was missing. The mapping for the longShortIndicator was updated.
Files changed:
xml-dbdirect_wrhs_delete_statement.inc
SDP-19773: Realtime: support for acct trade and acct cash single messages within in-memory processing
Added support to load the following EagleML interfaces as single messages within in-memory processing:
AccountingTrade, AccountingCash, AccountingAssetCash, AccountingReclaimCash, BankCashSettlement, ExpectedCreditLoss
Files changed:
eagle/estar/eagle_ml-2-0_default_in_xml_acct_cash_no_split.pkg
bank_cash_settlement_aliases.inc
cash_aliases.inc
cash_reclaim_aliases.inc
trade_aliases.inc
accounting_common_header_aliases.inc
multiplelegtrade_aliases.inc
xml-acct_cash.rsf
xml-acct_cash_asset.xml
xml-acct_cash_cancel.xml
xml-acct_expectedcreditloss.xml
xml-bank_cash_settlement.xml
realtime_rtr.xml
task_reporter.xml
resolve_inbound_stream_name.inc
w_config.inc
SDP-14261: Performance improvement in the Warehouse Position query
The logic for the parameter ExcludeCurrentDay has been updated to be more specific eliminating the OR clause in the subquery improving throughput.
ExcludeCurrentDay is common logic used within the WRHSPOSITIONEXTRACT, WRHSCASHACTIVITYEXTRACT, WRHSTRADEEXTRACT.
File changed:
eagle_ml-2-0_cm/extract_where_section.inc
SDP-19775: EagleML: Added missing links to the installer packages
The installer package had missing links resulting in some files not being included in the Installer package, which could cause a problem with a fresh installation.
This issue was fixed.
Files changed:
eagle_mc_installer.pkg
eagle_ml-2-0_default_cm_control_message.pkg
eagle_ml-2-0_default_cm_task_reporter.pkg
SDP-15824: IssuerXref object load does not support xsd-conforming objects
Previously xsd valid IssuerXref objects cannot be loaded through the eagle_ml-2-0_default_in_xml_reference.
A new rule has been added in the stream eagle_ml-2-0_default_in_xml_reference to handle the IssuerXref interface.
File changed:
xml-ref_objects.rsf
xml-ref_issuer_xref_mi.xml
xml-ref_issuer_xref.xml
SDP-16569: Missing Xref ID creation in Entity Xreference table
Adding additional Accounting Xreferences to an already existing entity resulted in erroneously changing the existing xrefAccountIdType to the xrefAccountIdType from the incoming file.
The logic for inserting the Accounting Xreferences is fixed.
File changed:
entity_xref_ins_upd.inc
SDP-19204: Omit date rule in file mask if daterule was added to transform_pairs.inc
Now date rule token that gets to transform_pairs.inc is omitted.
Date rule token is part of transform pair (file mask and translator that is supposed to translate this file) configuration If user creates profiled generic load through EJM MT and incoming file mask contains date rule token date rule.
Evaluation of date rule on translation distribution is excessive because only files that match date rule will get to translation step because of ndfa_exec logic.
Files changed:
eagle_ml-2-0_cm/unpacker/custom_routing.inc
SDP-18449: EagleML - IssuerEntityRelationship - Update load logic to include changes made in primary key on issuer_entity_relation table
The following changes were added to accommodate changes made in primary key on securitydbo. issuer_entity_relation table which now has fields relationship_type and start_date in addition to issuer_alias and entity_id in the primary key.
- Rebuilt stored procedure for insert/update issuerEntityRelationship to use the same primary key as in database.
- Fixed grouping according to new primary key. Added start_date and relationship_type for grouping to transformation to EagleML.
- Added missed elements startComments, endComments to inbound and outbound interfaces.
- Added ability to delete issuerEntityRelationship records.
Files changed:
eagleml_ref_issuerentityrelationship.xml
extract_issuer_entity_relationship.xml
generate_sp_on_fly.inc
ref_issuerrole_delete_aliases.inc
t_issuer_entity_relationship_streaming.xml
xml-ref_delete.xml
xml-ref_issuerentityrelationship.xml
Files Added:
ref_issuerentityrelationship_delete.inc
ref_issuerentityrelationship_delete_aliases.inc
extract_issuer_entity_relationship.inc
t_issuer_entity_relationship_streaming.inc
SDP-13632: EJM - In-memory Price Loading should return Business Task ID in TSR
Previously in-memory processing for any interface didn't handle business task id from incoming RTR or PayLoad file.
Rule for in memory processing was improved to handle incoming value and output it in the final TSR.
Files changed:
eagle_ml-2-0_cm/in/xml/realtime_rtr.xml
eagle_ml-2-0_cm/out/tagvalue/realtime_ejm_stat.xml
SDP-14813: Update User interface to insert records about delete in Journal table
Records were not getting added to Journal table on user role delete event.
Changed deleting method of user role. Records are added to Journal table on user role delete event.
Files changed:
eagleml_user_group.xml
user_common.inc
SDP-20038: Date Rules doesn't work when environment use HTTPS connection instead of HTTP
Date Rule logic always used http protocol by default. It caused an issue when environment used https protocol.
Include for date rule logic was updated with additional check for the calculation of the appropriate protocol to be used for the SOAP call.
File changed:
eagle_ml-2-0_cm\calc_date_from_rule.inc
SDP-19387: JMS stream delivery does not work for extracts
Extracts were not working when Delivery Method = JMS and logic to check JMS delivery stream execution status is turned on. This logic was not called in T Streaming outbound stream due to incorrect condition.
The variable that was used in condition to run check logic was updated to get correct value.
Files changed:
eagle_ml-2-0_cm\reporter_dist_methods.inc
SDP-15915: In-Memory Process - display execution time of streams correctly in file statistic
Issue was that for realtime processes the start and end processing times were equal and did not show real time.
Query on reporting step has been improved to get summary and detail information with correct start and end processing time and display this information on the file statistic tab.
File changed:
realtime_ejm_stat.xml
SDP-14597: EJM workflow remains in progress when data load task request is sent with empty Workflowdata
In case when workflow was launched by RTR with empty WorkflowData task parameter, the workflow stayed in progress and waited for a file.
Added support to handle case when WorkflowData defined in RTR have empty value and stop workflow execution with ‘WorkflowData Parameter cannot be empty’ error
File changed:
runtaskrequest.xml
SDP-20196: Error Executing eml_update_issuer_organization
Rule for the loading issuer organization interface in XMLDBAPI format produced an error due to incorrect SUB_MSG_TYPE.
Logic for loading was improved to support prefix for auto generated binds.
File changed:
xml-dbdirect_issuer_common.inc
SDP-9609: Warehouse Nav Multi cannot be loaded into non-default partition
Warehouse Nav Multi inbound interface didn't support load data to the non-default partition due to issue in the bind.
The logic for the bind generation was updated to support non-default partition.
Files changed:
eagle_ml-2-0_cm/extract_sql_schema_name.inc
eagle_ml-2-0_cm/generate_and_save_bind.inc
SDP-20049: Pricing Center - Underlying Price Demand for security is still in progress
When Pricing Center Event processes data, where securities have underlying security, the additional Underlying Price Demand events can be executed. They are launched after Pricing Center rules finished and they are not always catched by the logic, which checks Pricing Center event and its rules execution status. In this case EJM process is finished with "Underlying Price Demand for security… is still in progress" error.
The logic with checking Pricing Center sub-events statuses was enhanced firstly to check if all sub-events were started and then to wait their completion.
Files changed:
exec_pace_event.xml
exec_pace_event_pricing_check.inc
SDP-16418: realtime_rtr.rsf to support unzipped messages for all reference data files - Variable Rates.
SDP-16419: realtime_rtr.rsf to support unzipped messages for all reference data files – Factors.
SDP-16420: realtime_rtr.rsf to support unzipped messages for all reference data files -Schedules
Added support to load following EagleML interfaces as single messages within in-memory processing:
Generic SMF, IssueVariableRate, Schedule, GenericCA
Files changed:
realtime_rtr.xml
SDP-19849: XSD for Liquidity data model additions
The new elements for mapping to DB table HOLDINGDBO.POSITION_DETAIL_LIQUIDITY were added to the XSD type WarehousePosition (complex element <liquidity>).
The new elements for mapping to DB table PERFORMDBO.PSR_LIQUIDITY were added to the XSD type WarehousePosition (complex element <liquidity>).
The new elements for mapping to DB table RULESDBO.ENTITY_LIQUIDITY were added to the XSD type GenericEntity (new complex element <entityLiquidity>).
Please note: the new elements were not added to inbound or outbound interfaces. It is an XSD change only.
Files changed:
eagleml-entity-2-0.xsd
eagleml-entity-shared-2-0.xsd
eagleml-wh-shared-2-0.xsd
SDP-10090: Improve XREFEXTRACT to use bind variables
Filters xrefidtype, securitysubtype were updated in order to use bind variables. Filter securitysubtype was added to common security filters.
Files changed:
eagle_ml-2-0_cm/extract_filter_smf.inc
eagle_ml-2-0_cm/out/tagvalue/extract_smf.inc
eagle_ml-2-0_cm/out/tagvalue/extract_xref.inc
SDP-9970: Correct error messages in the security_resolution_generic
Error message for security resolution was fixed for case when security was not resolved by incoming identifiers. Updated message contains a list of identifiers that were a part of the resolution and a list of options.
Example of reported error message in GenericCA:
Security for the identifier(s) does not exist in Eagle:
99769N108_1/CUSIP, 99769N109_2/SEDOL. Resolution options: Currency: USD.
Also the following changes were done: - added information status that displays the actual list of identifiers that were a part of the resolution and a list of options.
Example:
Resolution Based On:99769N108_1/CUSIP, 99769N109_2/SEDOL. Resolution options: Currency: USD.
Tag No Change Case: 1952,1955,1958,1961,1964,1967,1970,1973,1976,1979
Added condition to include into resolution in First Match mode the 10th pair of identifiers, which contains Primary Asset Identifier, only in case the value is not empty
SDP–17647: Support outbound interface for VENDORCASHFLOW
An outbound interface for VendorCashFlow object was created.
Feed type: VENDORCASHFLOWEXTRACT
Supported EagleML filters:
Date Filter
Sources Filter
Security Master File (SMF) Filter
Held Only Filter
The extract was added to the eagle_wrf_generic_extract workflow.
Files added:
eagle_ml-2-0_cm/out/tagvalue/extract_ref_vendor_cash_flow.inc
eagle_ml-2-0_cm/out/tagvalue/extract_ref_vendor_cash_flow.xml
eagle_ml-2-0_cm/out/xml/t_ref_vendor_cash_flow_streaming.inc
eagle_ml-2-0_cm/out/xml/t_ref_vendor_cash_flow_streaming.xml
Files changed:
changes in the eagle_wrf_generic_extract workflow
eagle_ml-2-0_cm\ w_config.inc
eagle/estar/EAGLE_ML_2_0.pkg
eagle/estar/eagle_ml-2-0_default_out_q.pkg
eagle/estar/eagle_ml-2-0_default_out_streaming_t.pkg
/eagle_ml-2-0_cm/out/tagvalue/extracts.rsf
/eagle_ml-2-0_cm/out/xml/t_eagleml-2-0_streaming.rsf
SDP-19071: The Security Resolution is not using assetCurrency when PC Price is loaded.
An issue was detected with assetCurrency missing for Issue PC Price security resolution.
In order to avoid this issue, mapping for assetCurrency (tag85) was added for Issue PC Price inbound interface.
Files changed:
/eagle_default/in/xml/include/ xml-ref_security_pricing_common.inc
SDP-10341: Entity Extract to have Additional Filter to allow extracting Active Entities only
There was added a new filter 'activeStatus' for Generic Entity Extract to leverage filtering records by the RULESDBO.ENTITY.ACTIVE_STATUS field.
Example:
<taskParameter>
<name>activeStatus</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>
Files changed:
extract_entity.inc
extract_filter_sql.inc
SDP-14769: Update logic for tag 2301 in secmastersynthetic.inc for Options
Synthetic Securities logic adjustment. Now Synthetic Security type depends on Processing Security type.
Files changed:
eagle_default\in\xml\include\secmastersynthetic.inc