Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

eagle_ml-2-0_cm/out/tagvalue/extract_acct_settled_cash_activity.inc
eagle_ml-2-0_cm/out/tagvalue/extract_acct_traded_cash_activity.inc

SDP-

...

68023 Security Resolution for EDS load for Oracle was improved

EDS Security Resolution

...

was improved for Oracle and Snowflake. The following Security resolution logic now support MATCH_ALL mode in which all identifiers mentioned in battingOrder are used and only when ALL identifiers belong to the same security it is marked as successful.

EDS Security resolution logic was enhanced to support the MATCH_ALL mode in which all identifiers specified in the battingOrder node are used for resolution. A security is resolved only when ALL the identifiers belong to the same security.

SDP-68498 Expression support for DbCall T-Item in data rules interfaces

Expression support was added for the dbcall T-Item in the Data Rules interfaces to use dynamic SQL queries.

The new parameter should be added after the condition for execution to process the SQL query as expression.

Usage example:

{noformat}[dbcall, get_event_id,

              [EVENT_ID, :EVT_ID:],
              [EVT_ID, EVT_ID],
              [SQL, 'SELECT EVT_ID FROM 'is in place on data upload:

  • Resolution mashup logic will be applied for all xrefIdentifiers instead of just the first xId1 pair as it was before.

  • If the resolution via the mashup fails, then the stored procedure will be called. A new Stored Procedure similar to the Oracle procedure was created for Snowflake.

By default, the USE_FIRST_AS_MAIN will be used. Additional security resolution options and Batting Order are also supported.

SDP-68518 EDS Security Resolution - MATCH_ALL Option

EDS Security resolution logic was enhanced to support MATCH_ALL mode in which all identifiers specified in the battingOrder node are used for resolution, so a security is resolved only when ALL identifiers belong to the same security.

Files changed:

src/eagleinvsys/etl/core_etl/resolution_service.py
ontology/resolution/defaultassetresolutionservice.json
ontology/templates/includes/defaultassetresolutionservice.jso

SDP-68498 Expression support for DbCall T-Item in data rules interfaces

Expression support was added for the dbcall T-Item in the Data Rules interfaces to use dynamic SQL queries.

The new parameter should be added after the condition for execution to process the SQL query as expression.

Usage example:

{noformat}[dbcall, get_event_id,

              [EVENT_ID, :EVT_ID:],
              [EVT_ID, EVT_ID],
              [SQL, 'SELECT EVT_ID FROM '+:ESTAR_PARTITION_NAME:+'.ESTAR_FINANCIAL_EVENT WHERE 1=1 and EVT_ID = :EVENT_ID'],
              [:is_sell_subtype: = 'Y' and :sell_lot_selection_method: = 'IDLOT'],
              [Y]
]{noformat}

The new expression parameter can be set only to Y and does n0t not expect any expressions.

Files changed:
eagleinvsys/etl/core_etl/genetl_dbcall.py
eagleinvsys/etl/core_etl/genetl_items_enum.py
tests/ebstests/test_ebs_with_mock.py

...

EagleML/WarehouseTransaction/warehouseTrade/openCostLocal

[https://eagledocs.atlassian.net/wiki/spaces/EAGLEML/pages/251920822|[https://eagledocs.atlassian.net/wiki/spaces/EAGLEML/pages/251920822|smart-link ]

Signage logic for the Open Cost Local is enabled through an opt-in element with the EnableSignageLogic set to Y.

Signage is enabled when the following parameters are included:
<taskParameter>
<name>EnableSignageLogic</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>

Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_wrhs_trade_signage_logic.inc
eagle_ml-2-0_cm/out/tagvalue/extract_warehouse_trade.inc
eagle_ml-2-0_cm/out/xml/t_warehouse_trade_streaming.inc

SDP-68023 Security Resolution for EDS load for Oracle was improved

EDS Security Resolution was improved for Oracle and Snowflake. The following Security resolution logic is in place on data upload:

  • Resolution mashup logic will be applied for all xrefIdentifiers instead of just the first xId1 pair as it was before.

  • If the resolution via the mashup fails, then the stored procedure will be called. A new Stored Procedure similar to the Oracle procedure was created for Snowflake.

By default, the USE_FIRST_AS_MAIN will be used. Additional security resolution options and Batting Order are also supported.

Files changed:

????/EAGLEML/pages/251920822|https://eagledocs.atlassian.net/wiki/spaces/EAGLEML/pages/251920822|smart-link ]

Signage logic for the Open Cost Local is enabled through an opt-in element with the EnableSignageLogic set to Y.

Signage is enabled when the following parameters are included:
<taskParameter>
<name>EnableSignageLogic</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>

Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_wrhs_trade_signage_logic.inc
eagle_ml-2-0_cm/out/tagvalue/extract_warehouse_trade.inc
eagle_ml-2-0_cm/out/xml/t_warehouse_trade_streaming.inc

SDP-67839 Exchange Rate Inbound and Outbound interfaces were enhanced to support new fields

...

SECURITYDBO.SCHEDULE.BASE_CURR_SCH (tag - Tag 3676)
SECURITYDBO.SCHEDULE.PUT_NOTIFICATION_MAX_DAYS (tag - Tag 1657)
SECURITYDBO.SCHEDULE.PUT_NOTIFICATION_MIN_DAYS (tag Tag 1658)
SECURITYDBO.SCHEDULE.EXERCISE_PRICE (tag -Tag 3661)

Xpath:

Load within GenericSMF:
EagleML/referenceTransaction/genericSMF/schedule/baseCurrSch
EagleML/referenceTransaction/genericSMF/schedule/putNotificationMaxDays
EagleML/referenceTransaction/genericSMF/schedule/putNotificationMinDays
EagleML/referenceTransaction/genericSMF/schedule/exercisePrice

...