Data Feed 56 Release
Data Feed - 56 Release Notes
Data Feed
-
Transaction Type 16/17 enabled in Data Feed [EXTRACT-2061 / DEV-11375]
Transaction types 16 (Reinstate Charge transaction) and 17 (Reinstate Payment transaction) are now enabled and processed in Data Feed. These transactions are created when reinstating a previously voided transaction, typically using the reinstate_transaction_m API.
Two new fields have been added to the Transaction_type Entity to support these transaction types:
Type No | Label | Charge / Credit |
---|---|---|
16 | Reinstated Charge | charge |
17 | Reinstated Payment | credit |
Two new "type_no" IDs have been added to the Transaction Entity specifically for these Reinstate transaction line types:
Field Name | Datatype | Description |
---|---|---|
reinstated_reason | [Ref](#Ref)<[Reason](#Reason)> | only [Types](#Transaction_Type) 16 and 17 |
reinstated_transaction | [Ref](#Ref)<[Transaction](#Transaction)> | only [Types](#Transaction_Type) 16 and 17 |
- Dead letter retry [EXTRACT-8801]
A parameter, deadletter-retry-limit, has been added to application.conf
This parameter restricts the number of retry attempts that will be made to resolve an error, that occurred when parsing a object, before raising a hold event.Prior to this enhancement, when an error occurred while parsing an object, a dead letter would be created and the system would attempt to reparse the object an unlimited number of times until it was successfully resolved.
The default for the 'retry limit' is 3 attempts but the limit can be overridden in application.conf.# number of deadletter retry attempts before raising as a hold event deadletter-retry-limit = 3
-
bank_account_holder_type in Payment Method LOM [EXTRACT-8743]
A new field <bank_account_holder_type> has been added to the Payment_Method Object. This field represents what type of bank account, Individual or Company, is presented.
Field Name Datatype bank_account_holder_type VARCHAR(4000)
Snowflake
-
Transaction Type 16/17 Snowflake [EXTRACT-8834]
Transaction types 16 (Reinstate Charge Transaction) and 17 (Reinstate Payment Transaction) for reinstate_transaction_m API are now enabled and processed in Data Feed and subsequently, Snowflake. Three fields have been added to support transaction types 16 and 17 within the transaction object in Snowflake.
Field Name Datatype REINSTATED_REASON_NO NUMBER(38,0) REINSTATED_REASON_TYPE_NO NUMBER(38,0) REINSTATED_TRANSACTION_NO NUMBER(38,0)
- bank_account_holder_type in Payment Method LOM [EXTRACT-8743]
A new field <bank_account_holder_type> has been added into the Snowflake Payment_Method Object table. This field represents what type of bank account is presented.Field Name Datatype bank_account_holder_type VARCHAR(4000) -
Coupon Groups in Snowflake [EXTRACT-8601]
Added support to the Coupon_Group Object in Snowflake. Two new views have been added: <vm_coupon_groups> and <vc_coupon_groups>.
- ► vm_coupon_groups
-
Field Name Datatype CLIENT_NO NUMBER(38,0) IS_DELETED BOOLEAN REF_PK VARCHAR(4000) COUPON_GROUP_NO NUMBER(38,0) CLIENT_COUPON_GROUP_ID VARCHAR(4000) NAME VARCHAR(4000) DESCRIPTION VARCHAR(4000) PRECEDENCE NUMBER(38,0)
- ► vm_cg_coupons
-
Field Name Datatype CLIENT_NO NUMBER(38,0) COUPON_GROUP_NO NUMBER(38,0) COUPON_CODE VARCHAR(1000)
- ► vc_coupon_groups
-
Field Name Datatype ACTIONS VARCHAR(100) CREATETIME NUMBER(38,0) EVENT_ID VARCHAR(100) BATCH_ID NUMBER(38,0) CHG_ID NUMBER(38,0) EVENT_TSTAMP TIMESTAMP_NTZ(9) CLIENT_NO NUMBER(38,0) COUPON_GROUP_NO NUMBER(38,0) CLIENT_COUPON_GROUP_ID VARCHAR(4000) NAME VARCHAR(4000) DESCRIPTION VARCHAR(4000) PRECEDENCE NUMBER(38,0) CREATED_TSTAMP TIMESTAMP_NTZ(9)
- ► vc_cg_coupons
-
Field Name Datatype ACTIONS VARCHAR(100) BATCH_ID NUMBER(38,0) CHG_ID NUMBER(38,0) EVENT_TSTAMP TIMESTAMP_NTZ(9) CLIENT_NO NUMBER(38,0) EVENT_ID VARCHAR(100) CREATETIME NUMBER(38,0) COUPON_GROUP_NO NUMBER(38,0) COUPON_CODE VARCHAR(1000)
Universal Connector
-
Transaction Types 16/17 are now supported, see note in Data Feed section above.
-
Payment_Method has had the <bank_account_holder_type> field added, see note in Data Feed section above.