Release notes

V 5.6.107

• Voyado contact will get created/updated on the transaction thread.
• Breaking changes and some code in Accelerator removed.
• See Upgrade instructions.

V 5.6.106

• Optimize product feed generation. Now the product feed is generated by fetching the variants in batches, which makes a graceful memory footprint and execution with other tasks.
• See Upgrade instructions.

V 5.6.105

• Fixed: In Product feed generation, if an error occurs for some reason, the sync lock may not be properly released.
• See Upgrade instructions.

V 5.6.104

• When feeds are generated, any errors were logged with xml serialization of some entities. However xml serializer does not work always, this is now changed to json serialization so that log files contain correct and all data.

v 5.6.103

• Support multiple stores for the same tenant

v 5.6.102

• Allow to configure the feed scheduler as a task in web.config instead of the Voyado addon .config. This allows all the feeds to execute as determined by the project and can configure in which server feeds will run. This also improves performance.
• If user exists in Voyado for a given email, fetch the contact using email.
• Send mobile phone and customer number to voyado
• Send country code (Market) to voyado
• Breaking change in business logic: End-customer contact is not automatically updated when a order is placed anymore. Call the MarketingAutomationService.RegisterUserCreated and MarketingAutomationService.RegisterUserUpdated events from accelerator code where user is created or updated. For performance reasons, it is prefered not to listen to user created/updated events.