...
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 the 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.
<cashEventType>DISB</cashEventType> or <cashEventType>RECPT</cashEventType>
...
Changed files:
t_entity_share_class_streaming.inc
t_entity_rating_streaming.inc
t_entity_statistics_streaming.inc
SDP-15920 15920: Workflow_restart stream not failing if the underlying workflow is failed
The Logic was enhanced to ensure that the corresponding event and schedule for the schedule-based workflow did not get the correct status when the underlying workflow fails.
The issue has been fixed by setting the overall status of the workflow as FAILED when the CreateConsolidatedTSR is defined as Y and the underlying steps have errors.
Changed files:
task_reporter.xml
workflow_restart.xml
...
Modified file:
sequencer_orch.xml
SDP-15048: EagleML: Source interface has an issue with long sourceName
...
Files changed:
xml-ref_source.xml
SDP-12457 12457: Incorrect error message for WarehousePosition
...
There were a number of fields that were missing in the Generic Issue Analytic extract.
The Generic Issue Analytic interface has been updated to extract these fields.
Following The following models were changed:
analyticsUserModel (SECURITY_USER_ANALYTICS table) - userSaChar16 - userSaChar30 were not loaded on MSSQL environments version 2017
Meta information has been updated for this model, to load these fields on MSSQL environments.
ePSEquityModel (SECURITY_EPS_EQUITY table) - only epsEst1X and epsEst2X elements were supported on Oracle environments. The model wasn't was not supported on MSSQL environments.Added processing of ePSEquityModel for MSSQL. Added all fields for the model described in XSD for Oracle and MSSQL to load and extract.
priceEarnEquityModel (SECURITY_PRICE_EARN_EQUITY) - The model wasn't was not supported on MSSQL environments.
Added processing of priceEarnEquityModel for MSSQL.
Changed files:
call_eagleml_dbml_request.inc
eagleml_ref_genericissueanalytic.xml
generate_sp_on_fly.inc
t_generic_issue_analytic.xml
t_generic_issue_analytic_streaming.inc
xml-ref_genericissueanalytic.xml
SDP-12935: provide Provide a possibility to exclude files from WAITEVENTS.DAT queue
Previously user wasn't User were not able to remove records about files waiting to be processed.
Information about waiting workflows and files waiting for the launched workflows stored in WAITEVENTS.DAT file or
in the data base database (if parameter W_WAITEVENTS_DATABASE_MODE = Y in the w_config_custom.inc) are now available.
Functionality to cancel wait event based on the file name (FileName) or WaitEventCorrelationId has been added.
When a user sent sends a RTR with WaitEventCorrelationId or CancelRemoteFileName and , this value match with will wait for the event state record,
then and the waiting file for the workflow will be canceled.
Ability Added the ability to update the file statistic information for the canceled files when the file statistic is available
(W_ENABLE_EXTENDED_FILE_STATISTICS = Y is set in w_config_custom.inc) was added.
if W_WAITEVENTS_DATABASE_MODE = Y then canceled files will be transferred from {workflow_name} _wait_queue (queue for waiting events) to {workflow_name} _error_queue (queue for canceled events)
...
Fixed the error of executing of Warehouse Position and OpenLot extracts with parameter 'IncludePortfolioValuation' = Y or ALL and Source filter = 'MSTARDIRECT'.
Changed rules:
- extract_holding_ext_port_valuation_fields.inc
SDP-15207: EagleML: Warehouse Rollback functionality should not use the CorrId from the file name(XMLDBAPI)
SDP-15191: EagleML: Warehouse Rollback functionality should not use the CorrId from the file name(EagleML)
Roll Up rule handled correlationId value in the incoming file name for the Rollback functionality.
This value was used in the query The usage of the correlation id from the file name for checking which sub batches had failed on the load and run a roll back for the whole batch was proven reliable because the correlationId should be in exact place in the file name.
Only the correlationId in the file name can link key and data files related to the one process instance.
This method was not reliable because correlationId should be in exact place in the file name.
This approach was replaced by adding correlationId value on the Python transformation step in the files itself.
Now key and data files have an additional value CORRELATION_ID(XMLDBAPI) and taskIdentifier/correlationId (EagleML).
It helps to link key and data files related to the one process more reliable, because each process has a unique correlationId.
Changed files:
include/xml-warehouse_common.inc
xml-dbdirect_invar.xml
xml-dbdirect_invar_rollup.xml
xml-warehouse_v2.xml
...
There was a problem with extension processing when fieldCompareFlag = Y, because the insert\update to into the extension table happens in a separate DB call and as a result database call resulting in the extension and core tables could not be being in sync.
The new implementation allows to extend the core stored procedure to support loading extension fields and which will keep the extension and core tables in sync.
Please note: To activate this logic and switch to the new processing some manual steps are required .
They have to be done only once, please visit confluence page about to be setup as a one time activity. Request additional information located on the confluence page defining extensions.
Changed files:
...
The Expense Activity Extract did not report an error in case when the required filters reportStartDate and reportEndDate were not specified.
...
There was an issue identified in grouping for the Warehouse Position and OpenLot extracts when using the ‘IncludePortfolioValuation’ with a value set to Y or ALL. The data appear as an outlier, but to handle this inconsistency, the PortfolioValuation logic has been enhanced and a new repeated node pvAssetPrice was added in the extendedPortValuationModel to address when more than one price / source combination exists for the specific position.
...