Release 4.13.1

🐛 Bugfixing

• Fixed SQL problem when calculating deltas of extraction jobs that caused to fail all extraction jobs automatically triggered by cron expressions.

Release 4.13.0

This release contains a serious bug in delta calculation for extract jobs. Please skip it and use release 4.13.1 instead

⚙️ Improvements

This release provides the following improvements:

• Take into account previous job executions when calculating deltas for extraction. Now jobs automatically set the initial time for searching changed entities in Mirakl to the time of the last execution of the job that returned Mirakl entities.

New properties

The following properties have been added:

• PAYPAL_HYPERWALLET_JOB_EXTRACTION_MAXDAYS : this is the maximum number of days to look in the past when retrieving changed data from Mirakl during the extraction jobs.
  Default Value: 30
  Possible Values: any integer

Release 4.12.0

⚙️ Improvements

This release provides the following improvements:

• Avoiding exhausting API limits for endpoints such as S20 of Mirakl, for doing so the connector is now keeping a track of relationships between Mirakl and Hyperwallet entities.
• Implementing the retry job item logic for stakeholders.
• Establishing a max number of retries for items that failed on previous executions.

Release 4.11.0

⚙️ Improvements

This release is focused on adding support for automatically retrying items that have failed during the execution of a batch job.

• Added a cache for failed job items so they can later be retried without making again requests to Mirakl APIs.
• Added retry jobs for the following items:
  • Individual sellers.
  • Professional sellers.
  • Business stakeholders.
  • Bank accounts.
  • Invoices.

Note: All retry jobs, except business stakeholders one, recover the failed item information from the cache, and if the item is not found in the cache it is requested to Mirakl API. Business Stakeholders retry job only recovers information from the cache in this release.

🐛 Bugfixing

• Fixed invoice extraction job that failed when there were invoices from more than 100 different shops. Now requests to Mirakl are split into batches of 100 shops and if some batch fails, the connector will try to process the invoices belonging to shops whose request hasn't failed.

New properties

The following properties have been added:

• PAYPAL_HYPERWALLET_SEARCH_INVOICES_MAX_DAYS : this is the size in days of the search window when searching invoices by id. It is only used for the failed invoices retry job. This is needed since Mirakl API doesn't allow for searching invoices by id, but only by date range.
  Default Value: 15
  Possible Values: any integer
• PAYPAL_HYPERWALLET_RETRY_SELLERS_CRON_EXPRESSION : The cron expression to trigger periodically the Individual Sellers Retry Job.
  Default Value: 0 0/15 * ? * * *
  Possible Values: any valid cron expression
• PAYPAL_HYPERWALLET_RETRY_PROFESSIONAL_SELLERS_CRON_EXPRESSION : The cron expression to trigger periodically the Professional Sellers Retry Job.
  Default Value: 0 0/15 * ? * * *
  Possible Values: any valid cron expression
• PAYPAL_HYPERWALLET_RETRY_BUSINESS_STAKEHOLDERS_CRON_EXPRESSION : The cron expression to trigger periodically the Business Stakeholders Retry Job.
  Default Value: 0 0/15 * ? * * *
  Possible Values: any valid cron expression
• PAYPAL_HYPERWALLET_BANK_ACCOUNT_RETRY_CRON_EXPRESSION : The cron expression to trigger periodically the Bank Account Retry Job.
  Default Value: 0 0/15 * ? * * *
  Possible Values: any valid cron expression
• PAYPAL_HYPERWALLET_RETRY_INVOICES_CRON_EXPRESSION : The cron expression to trigger periodically the Invoices Retry Job.
  Default Value: 0 0/15 * ? * * *
  Possible Values: any valid cron expression
• PAYPAL_HYPERWALLET_RETRY_CREDITNOTES_CRON_EXPRESSION : The cron expression to trigger periodically the Credit Notes Retry Job.
  Default Value: 0 0/15 * ? * * *
  Possible Values: any valid cron expression

Release 4.10.0

⚙️ Improvements

• Added support for retrying items that have failed during the execution of individual sellers extract jobs.
• Improved reliability of professional sellers extract job by ensuring that the business stakeholder extraction operation can be retried without errors or side effects.

New properties

The following properties has been added:

• PAYPAL_HYPERWALLET_STK_MANDATORY_EMAIL: controls whether or not the email is mandatory for the business stakeholders of a professional seller. If it's mandatory and the email it's not filled, the business stakeholder will not be processed and an email will be sent reporting the business stakeholder creation failure.
  Default Value: false
  Possible Values: true or false

Release 4.9.0

⚙️ Improvements

• Improved error handling and logging on documents extract job by processing each document individually.
• Improved reliability of individual and professional sellers extract job by ensuring that the extraction operation can be retried without errors or side effects.
• Improved reliability of bank accounts extract job by ensuring that the extraction can be retried without errors or side effects.
• Improved reliability of invoices extract job by ensuring that the extraction can be retried without errors or side effects.

🐛 Bugfixing

• Fixed an error that caused the bank account extract job to only extract bank accounts from individual sellers but not from professional ones.

Release 4.8.0

⚙️ Improvements

• Upgrade Spring Boot version to 2.6.6 to fix security problems (including cve-2022-22965)
• Refactored Invoices Extract Job to improve the reliability and logging of the job.
• Refactored Bank Account Extract Job to improve the reliability and logging of the job.

Release 4.7.3

⚙️ Improvements

• Logging improved for Individual sellers extract job and Professional sellers extract job by extracting items individually.

4.7.2

⚙️ Improvements

• Support for storing and querying webhook notifications
• Support for housekeeping stored notifications within an interval of time via endpoint

🐛 Bugfixing

• Avoiding processing duplicated notifications
• Avoiding processing obsolete notifications

New properties

All new properties are located in file notifications/src/main/resources/notifications_db.properties

• notifications.db.datasource.url: Connection url/path for the notifications datasource
• notifications.db.datasource.driverClassName: Driver for connecting with notifications datasource
• notifications.db.datasource.username: Datasource password
• notifications.db.datasource.password: Datasource username

4.7.1

🐛 Fixes

• Fixed compilation issue in 4.7.0 due to incorrect case of files KycUserEventListener and KycUserEventListenerTest

⚙️ Improvements

• Added support for new Hyperwallet document types in notifications (BUSINESS_REGISTRATION, OPERATING_AGREEMENT)

Changed properties

• PAYPAL_HYPERWALLET_RETRY_FAILED_NOTIFICATIONS_CRON_EXPRESSION: The cron expression to trigger periodically the Failed Notifications Retry Job.
  • Default value changed from * 0/15 * * * ? * to 0 0/15 * * * ? * to avoid an excessive number of job executions.