Enhancements:
SDP-35591: Global parameter was added to cancel orphaned workflow executions
When the existing supported parameter,EnableTimeoutCancel, is set to Y, it only allows the ability to cancel a workflow for a specific schedule event.
Introduced a new global and optional parameter W_SCHD_EJM_WORKFLOW_CANCEL that may be set to Y in the w_config_custom.inc which will enable the ability to cancel all workflows based on workflow_restart rule when the timeout occurs. It enables the ability to end all orphaned workflow executions when the timeout limit is met.
Files changed:
eagle_ml-2-0_cm/out/tagvalue/workflow_restart.xml
SDP-35483: Added Option to control ACK and Reply File names distributed via FTP/SFTP
The RTR parameters TSRStrictPattern and ACKStrictPattern capabilities were expanded to control the names for the ACK/REPLY files. When included the auto-generated Timestamp & Correlation Id will be removed from the final file name to maintain the original file name.
This functionality is configured within the w_config_custom.inc as the optional parameter :W_REPLYCM_MODE with a value of Y
<CODE>
:W_REPLYCM_MODE: :='Y';
</CODE>
RTR Example:
<taskParameter>
<name>TSRStrictPattern</name>
<dataType>S</dataType>
<value>SPTEST_LOCAL_DEV_TRADE_BUY_TSR_timestamp_</value>
</taskParameter>
<taskParameter>
<name>ACKStrictPattern</name>
<dataType>S</dataType>
<value>SPTEST_LOCAL_DEV_TRADE_BUY_ACK</value>
</taskParameter>
Files changed:
reporter_dist_path.inc
SDP-35344: Accounting Trade Inbound Interface was enhanced to support new elements
The Accounting Trade Interface was enhanced to support new elements on the Receive event: methodOfLTDAmortization, LTDAmortizationCostLocal, LTDAmortizationLocal, LTDOIDLocal.
These elements are mapped to the Trade panels.
The accountingValidationFlag should be set to Y. THe Accounting Trade for Deliver was also enhanced to include the targetTradeTicketNumber to support IDLOT.
Files changed:
eagle_default/in/include/csv-deliver.inc
eagle_default/in/include/csv-receive.inc
eagle_default/in/include/trade_aliases.inc
SDP-35293: Enhanced the Position Analytics Model in the Warehouse Position Inbound Interface
Added support of the additional element daysToMaturityScore as part of Position Analytics Model within the Warehouse Position Inbound Interface.
Files changed:
eagle_default\in\xml\xslt\wrh_egl_gen_interface3.xsl
SDP-35218: Accounting Trade Extract was redesigned in order to improve throughput
The Accounting Trade Extract was modified and enhanced to improve throughput. The issue occurred only when a large amount of data was extracted. The result file had only the EagleML wrapper without any extracted records when more than 10,000 records where returned by SQL query. It happened as a result of different methods of processing small and large files.
The ACCOUNTINGTRADEEXTRACT was redesigned to use temporary file for all cases.
As well, the following improvements were made:
added support of streaming transformation
added inclusion of additional elements: otherFee and longShortIndicator
Files Added:
eagle_ml-2-0_cm/out/tagvalue/extract_acct_trade.xml
eagle_ml-2-0_cm/out/xml/t_accounting_trade_streaming.xml
Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_financial_event.inc
eagle_ml-2-0_cm/out/xml/t_accounting_trade_streaming.inc
eagle_ml-2-0_cm/out/xml/t_eagleml-2-0_streaming.rsf
eagle_ml-2-0_cm/w_config.inc
SDP-35098: Introduced an option to load Issuer Role in batch mode via SMF MI Interface
A new processing option, DIRECT_ISSUER_ROLE_OPTIONS was introduced for the SMF MI object. It should be used in conjunction with the ISSUER_ROLE_GROUPING which enables the load of the ISSUER ROLE in batch mode. DIRECT_ISSUER_ROLE_OPTIONS may be used to override or manipulate the actions like ISSUE_ROLE_UPSERT_MODE and USE_LATEST_START_DATE triggered by ISSUER_ROLE_GROUPING.
However, these options may be individually passed in the processing option to take effect.
For example, using the ISSUER_ROLE_GROUPING,DIRECT_ISSUER_ROLE_OPTIONS, or ISSUE_ROLE_UPSERT_MODE in the processing option will trigger only the UPSERT MODE while processing but will not use latest start date .
Files changed:
eagle_default/in/xml/xml-ref_issuerrole_batch.xml
eagle_default/in/xml/xslt/eagleml_smf_issuer_role.xsl
SDP-34566: IncludeExtendedDetails filter includes additional entity.base_currency field for Warehouse extract
Added the possibility to extract the rulesdbo.entity.base_currency field for the WRHSPOSITIONEXTRACT, WRHSOPENLOTEXTRACT, WRHSTRADEEXTRACT and WRHSGLDETAILPOSTINGEXTRACT. The field will be included when the IncludeExtendedDetails filter is part of the RTR with a value of Y or ALL.
Files changed:
extract_entity_fields.inc
SDP-34561: New Inbound Interface BrokerRate
Added support to load, update and delete Broker Rate data. The new object type BrokerRate is supported via the default generic load workflow.
Files added:
eagle_default/in/xml/xml-ref_brokerrates.xml
Files changed:
eagle_default/in/xml/xml-ref_objects.rsf
SDP-34337: Update logic for Issue Rating was adjusted
New Logic was introduced for the Issue Rating to insert a new record only when both the effective date and the Rating are different than the existing values in the database. This new logic may be triggered by using the processingOptions SKIP_UNCHANGED_RATING in the incoming file. The new logic checks if the latest rating record (highest effective date) for the same key (Security + Issue + Source) has a different alpha rating or the same rating. If the new record matches the existing alpha rating, the record will be skipped, otherwise the a new record will be created. The new logic does not affect the default behavior and is only available when the processing option SKIP_UNCHANGED_RATING is set in the incoming file.
Files changed:
eagle_default/in/xml/xml-ref_issuerating_all.xml
SDP-34049: Asset Resolution Option for Maturity Date was adjusted as part of Security Resolution Logic
The Asset Resolution Option for MATURITY_DATE did not work in the First Match mode as part of the Security Resolution logic. The issue was fixed for all inbound interfaces using Security Resolution.
Files changed:
eagle_default/in/xml/include/security_resolution_generic.inc
SDP-33599: EntityXrefs Update Logic supports EntityID less than 8 characters
The Entity Xrefs were getting inserted instead of updated causing multiple xrefs with the same type to be created. This was only happening when the Entity ID was less than 8 characters because the query was not padding values when necessary. The update of xrefAccountId for existing xrefAccountIdType logic was corrected.
Files changed:
eagle_default/in/xml/xml-ent_entityxref.xml
eagle_default/in/xml/include/entity_xref_ins_upd.inc
SDP-32452: Added ability to load ExchangeCode via GenericSMF into the SECURITYDBO.XREFERENCE.EXCHANGE
The GenericSMF Inbound Interface was enhanced to load the ExchangeCode as part of the XREF Identifiers.
An Xref with the following structure will load the xExchangeCode into the SECURITYDBO.XREFERENCE.Exchange
<xId1>
<xId>TEST1</xId>
<xIdType>BBID</xIdType>
<xExchangeCode>XBER</xExchangeCode>
</xId1>
When the xExchangeCode is not set, the XREF will be loaded with the primaryExchangeCode.
Files changed:
eagle_default/in/xml/include/ins_upd_xrefs.inc
eagle_default/in/xml/xslt/get_smf_all_xrefs_list.xsl
SDP-10606: Corrected an issue extracting the UnderlyingType value for the Warehouse Extracts with the IncludeExtendedDetails flag set to Y
When the Warehouse Extract based on Security with several Underlying Securities, the field UnderlyingType was extracted as concatenated string of several underlying types, for example: 'PRIMARY,PRIMARY'.
The issue was fixed. Now only one value from corresponding Underlying Security with empty EndDate is extracted as UnderlyingType.
Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_asset_properties_fields.inc
Production Bugs:
SDP-36117: Ability to disable pre-extract cache validation step at the profile level
The logic for the eagle_wrf_generic_extract workflow execution was adjusted to allow a user to disable the cache validation step at the profile level using the parameter EnableValidateCache when the global flag W_ENABLE_VALIDATE_CACHE is enabled and date rule is used in the EJM profile.
Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_calculate_date.inc
eagle_ml-2-0_workflows/eagle_wrf_generic_extract.wrf
eis/ejmwf/eagle_wrf_generic_extract.ejmwf
SDP-36101: Corrected inconsistency with In Progress Status in Automation Center for files that do not match any mask
The externalData Scheduled event remained In Progress in Automation Center after the file was sent for processing to the eagle_ml-2-0_default_in_ndfa stream. It failed within the EJM process with the corresponding error message: Files do not match any mask. The Issue was fixed.
Files changed:
eagle_ml-2-0_cm/ins_upd_file_stat.inc
SDP-35999: Corrected Wrong Status for files failed on translation step
Fixed status from Pending to Failed for files failed on the translation step executed via profiled generic load.
Files changed:
eagle_ml-2-0_workflows/eagle_wrf_generic_load_profile_executor.wrf
eis/ejmwf/eagle_wrf_generic_load_profile_executor.ejmwf
SDP-35655: Corporate Action Rebook logic was corrected
Corporate Action Rebook functionality was updating records while they should be ignored due to incorrect variable names.
A few tags did not contain database value: tag65 (Ex Date), tag3962 (Cp Cash Currency), tag1734 (Cp Term Flag), tag1705 (Cp New Px).
Correct variables for these tags that contain value from DB are: tagdb65, tagdb3962, tagdb1734, tagdb1705.
Rebook logic was adjusted to use the proper variable names and the issue was fixed.
Files changed:
eagle_default/in/xml/include/ca_true_rebook.inc
SDP-35264: MC2 UNSETTELEDTRANSACTIONEXTRACT was corrected in regards of repeated Entity nodes
The Unsettled Transactions Extract via MC2 was returning repeated entity nodes if executed in accounting mode, accountingValidationFlag set to Y. The logic was corrected to fix this issue.
Files changed:
t_acct_unsettled_transactions_streaming.inc
SDP-35019: Generic Entity Inbound Interface was updated to correct the Inner logic on how fwdPriceSource field is calculated
The logic for populating the fwdPriceSource field was corrected for the Entity Update when the accountingValidationFlag is set to Y to process against the front-end panel.
The new logic uses the incoming value for tag 86 correctly in order to calculate tag 2920 - fwdPriceSource.
Files changed:
eagle_default\in\include\csv-entity_columns.inc
SDP-34809: User Inbound Interface was updated in regards of Date format conversion
The User Inbound Interface was updated to correct a database error: date format picture ends before converting entire input string
A date format conversion was corrected for the lastOperationTime, lastFailedTime and unlockDateTime elements.
Dates are accepted in the datetime format: YYYY-MM-DDThh:mm:ss.
File changed:
eagle_default/in/xml/include/user_common.inc
SDP-34678: Entity Composite Inbound Interface was updated
Editcheck logic was added to properly assign the Failed status to the messages if an error was raised during data load.
Files changed:
eagle_default\in\xml\xml-ent_entitycomposite.xml
SDP-33577: Added support of the EmailDistributionList task parameters by default workflows
The default workflows sub-processes did not support EmailDistributionList task parameters.
Added support of task parameters by default workflows:
ACKEmailDistributionList
ExtractEmailDistributionList
ResponseEmailDistributionList
AlertEmailDistributionList
Example:
<taskParameter><name>ACKEmailDistributionList</name><dataType>S</dataType><value>x@y.com</value></taskParameter>
<taskParameter><name>ExtractEmailDistributionList</name><dataType>S</dataType><value>x@y.com</value></taskParameter>
<taskParameter><name>ResponseEmailDistributionList</name><dataType>S</dataType><value>x@y.com</value></taskParameter>
<taskParameter><name>AlertEmailDistributionList</name><dataType>S</dataType><value>x@y.com</value></taskParameter>
Files changed:
get_w_state.inc
execute_wrkfl_event.xml
reporter_dist_methods.inc
SDP-32491: Entity Statistics Extract was corrected
ENTITYSTATISTICEXTRACT was corrected to properly support the updateSource field.
File changed:
eagle_ml-2-0_cm/out/xml/t_rule_start_trx_header_streaming.inc
SDP-26945: Corrected logic for system generated EntityId
The system has the ability to generate an entityId. When the Entity load file was missing the entityId and entityXrefs, an error was returned that the EntityId generated must not exceed 8 characters when a system generated id was expected.
The logic was corrected, to assure that system generated EntityId will not exceed 8 characters.
Files changed:
eagle_default/in/include/entity_acct.inc
eagle_default/in/xml/include/entity_xref_resolution.inc
eagle_default/in/xml/xml-ent_entitygeneric.xml