SDP-14563 : Pricing Center - Parent event showing completed prior to child event completing
When a Pricing Center Event consists of one rule, the sub-event that is executed for this rule runs independently. Pricing Center event does not wait for its completion and reports that the whole event is finished. When Pricing Center event is executed via EJM, the process is marked as complete even if sub-event is still running.
EJM was enhanced to check statuses of Pricing Center sub-events and wait for their completion.
Files changed:
exec_pace_event.xml
exec_pace_event_pricing_check.inc
SDP-15206 : In the Generic Loader process change the processing so that the SMF Composite is only executed when loading SMF data
Generic Load workflow has a sub-process “eagle_generic_load_smf_composite” which can be used to call Pace Event or RDC or SRM events.
When one of the following parameters (PACEEventName, W_ExecuteSRM or W_ExecuteRDC) is set (for example in w_config_custom.inc) this sub process was launched.
The problem was regardless of whether or not SMF files were present in the incoming files, this sub-process was triggered.
Condition to trigger this step was updated to check if SMF file is part of the incoming files.
Files changed:
eagle_wrf_generic_load.ejmwf
eagle_wrf_generic_load.wrf
SDP-14278 : Add handling any issues in TSR from reason node processed by i2i_parse_errors_from_hub.xsl/taskstatusresponse.xml
In the Instance2Instance process two environments exchange RTR\TSR with each other. In case if error happens on the remote server, when it sends back failed TSR, the local environment should be able to process this TSR and show correct error description message on the local environment.
XSL Transformation file has been adjusted to process all error descriptions present in the incoming TSR file.
Files changed:
- /msgcenter/eagle_ml-2-0_cm/in/xml/taskstatusresponse.xml
- /msgcenter/eagle_ml-2-0_cm/in/xml/xslt/i2i_parse_errors_from_hub.xsl
SDP-10920 : Issue with query panel/tag55 logic in the xml-ref_issueprice.xml
issuePrice has been adjusted that in case of invalid effectiveDate or sourceName fields in the incoming message, the logic goes to insert mode, instead of update mode as it was before. (Different stored procedure)
Files changed:
- msgcenter\eagle_default\in\xml\xml-ref_issueprice.xml
SDP-14566 : Enhance EagleML in the AccountingAssetCash coverage to support mapping of the Cash Event Type - CS0136160 - Inbound MISC Entry negative EML message
The AccountingAssetCash Interface was enhanced to support cashEventType element for MISC Income and Expense Asset Cash message types (Asset Cash Type = AMISCINC or AMISCEXP).
Possible values of Cash Event Type: DISB, RECPT.
Files changed:
\dynamic\msgcenter\eagle_default\in\xml\ xml-acct_cash_asset.xml
\dynamic\msgcenter\eagle_default\in\include\csv-cash_misc_inc_exp.inc
\dynamic\eagleml\schema\eagleml-acc-2-0.xsd
SDP-17003 CIBC : Loading EntityAnalytic issue
EntityAnalytic interface failed during load, the problem was in auto-generated stored procedure which in some cases had incorrect convert logic for dates.
Include, which generates stored procedure, has been fixed to handle such cases correctly.
Changed file:
eagle_ml-2-0_cm\generate_sp_on_fly.inc
SDP-15851 : Entitytocomposite object fails the record when the same record is loaded in
entitytocomposite object fails the record when the same record is reloaded instead of being ignored or updated.
There is a problem with parallel loading of several entities to one composite. This happens due to the logic of stored procedure that updates the entire composite even if the effective date for one entity was updated.
A condition in the split rule was updated to process entities added to one composite with the same effective date to be processed sequentially.
Files Changed:
eagle_default\in\xml\xml-ent_objects.rsf
eagle_default\in\xml\ xml-ent_entitygeneric.spl
SDP-14038 : Issue with incorrect TSR (missed identifiers) in case of enabled auto-reprocess streams
There were no error details in final TSR for messages that were processed by auto-reprocess stream. These messages have specific status value in MSGCENTER_DBO.MSG_DETAIL.STATUS like 10 or 11. To collect error details for messages with such statuses for TSR, the requests were updated in eagle_ml-2-0_default_cm_task_reporter stream.
Files changed:
task_reporter_generate_task_unit.inc
task_reporter_gen_task_unit_realtime.inc
SDP-17249 : ISSUERRATINGEXTRACT data source filter and grouping issues
Issuer Rating Extracts were enhanced to support source filter and grouping was updated to include source field in group key.
Correct grouping statement is Issuer Alias + Alpha Rating + Source Instance.
Changed files:
- extract_issuer_rating.inc
- t_issuer_rating_streaming.inc
SDP-15083 : Inbound EML Forward Alt Asset ID Unique on Both Currency Legs
Forward model of GenericSMF Interface was enhanced to support unique Asset Identifiers in legAsset node and lookThroughIndicator, lookThroughValue fields for second leg (buy or sell) in one message.
Changed files:
eagle_default\in\xml\xml-smf_generic.xml
eagle_default\in\xml\include\smf_forwrd.inc
eagle_default\in\xml\include\security_resolution_generic.inc
eagle_default\in\xml\include\get_xrefs_list.inc
eagle_default\in\xml\include\smf_aliases.inc
eagle_default\in\xml\include\forwardsmf_model.inc
eagle_default\in\xml\xslt\get_smf_all_xrefs_list.xsl
eagle_default\in\xml\xslt\eagleml_smf_gen_fields.xsl
New files:
eagle_default\in\xml\include\forward_identifiers_remap.inc
eagle_default\in\xml\include\smf_identifiers_map.inc
SDP-14318 : Duplicate identifier in DB after SMF update
The problem was that Duplicated Xref Identifiers were added to the same security when Accounting Validation Flag is set to Y.