Elastic Path 8.0.x Release Notes

`8.0.0`

Released: February 27, 2020

Release Highlights

Payments

With the new Payments framework, Elastic Path provides the capability to easily create payment plug-ins for different payment providers and methods to support the changing needs of today’s shoppers and buyers.

The Payments framework provides a capability-based plug-in model that is designed to support traditional and non-traditional payment types. Plug-in developers only implement what is relevant for their use case, simplifying and reducing development efforts.

Available out-of-the-box is a CyberSource plug-in for Visa CyberSource customers, and a Purchase Order plug-in, available as source. Use the Purchase Order Plug-in to capture Purchase Order numbers in the checkout flow or customize it for your specific use case. For more information about the Payments framework and plug-ins, see Payments and Payments Plug-ins.

Announcements and Notices

Removed Features

Feature	Notes
The deprecated Cortex system tests in the `extensions/cortex/deprecated-system-tests` module were removed.	Cortex system tests are still available in the `extensions/cortex/system-tests` module.

System Requirements and Compatibility

Elastic Path Commerce 8.0.0 is compatible with the following Elastic Path releases:

Elastic Path Component	Versions	Locations	git branch or file name
Elastic Path CloudOps for AWS (Amazon Web Services)	CloudOps for AWS compatibility matrix	code.elasticpath.com	release/3.N.x where N is the minor version number
Elastic Path CloudOps for Kubernetes	CloudOps for Kubernetes compatibility matrix	code.elasticpath.com	release/2.N.x where N is the minor version number

New in This Release

In addition to the Release Highlights, this release contains the following updates.

Core Commerce updates

Added the Payments framework which provides a capability-based plug-in model that is designed to support traditional and non-traditional payment types. Plug-in developers only implement what is relevant for their use case, simplifying and reducing development efforts. For more information, see the Payments documentation.

Added the CyberSource plug-in: CyberSource customers can connect the plug-in to the Elastic Path Payments framework, configure in Commerce Manager and start accepting payments immediately. Customers can handle credit card payment processing and tokenization out-of-the-box,using either the Direct Post or Hosted Page methods provided by CyberSource. For more information, see the CyberSource Plug-in documentation.

Cortex API updates

Support for payments resources in Cortex.
Added the paymentmethods order-payment-method resource to show all the available payments methods.
Added the paymentinstructions order-request-instructions-form resource to retrieve the instructions from the payment plug-in.
Added the paymentinstruments order-payment-instrument-form resource to generate the payment instrument.
Added the paymentinstruments order-payment-instrument-selector resource to choose an available payment instrument and attach it to the order.
Added the paymentinstruments payment-instruments to get all the profile payment instruments.
Added the paymentinstruments profile-default-payment-instrument-selector selector to choose a default profile payment instrument.
Added the paymentmethods profile-payment-method resource to show all the available saveable payments methods.
Added the paymentinstruments purchase-payment-instruments resource to show all the payment instruments used to pay for an order.
Added the paymentinstruments purchase-payment-instrument resource to view the payment instrument used in the order.

Reference Storefront updates

Added a dynamic style guide to Storybook from Invision
Bug fixes
B2B branding theme
Quick order and Bulk order with Multi-cart
Initial Payments 8.0.0 compatibility for Happy Path plug-in (a test credit card plug-in) if available.
Payments with Purchase Order plug-in

CloudOps updates

CloudOps for Kubernetes replaces CloudOps for Azure. CloudOps for Kubernetes is a re-engineering of CloudOps for Azure to add support for both Azure and AWS (Amazon Web Services) deployments using cloud agnostic tooling.

Upgrade Notes

The upgrading Elastic Path guide provides general instructions on upgrading Elastic Path projects.

Core Commerce

With the introduction of the new Payments framework, significant changes have been made to how Elastic Path stores payment transactions and how these transactions relate to orders. There is no out-of-the-box data migration that exists to move data from the old schema to the new schema. As a result, upgrading to 8.0.x without taking specific steps to migrate the data, can result in Commerce Manager users unable to execute the following behavior:

Complete shipments from pre-existing orders. This is any order that pre-dates the upgrade.
Modify an order total, by either increasing or decreasing on existing orders. This is any order that pre-dates the upgrade.
Create a refund on pre-existing orders.
Create and exchange on pre-existing orders.

The following behavior can also be present:

Saved payment tokens on customer profiles are no longer be visible.
Payment history on existing orders is not be visible in Cortex or through Commerce Manager.

If any of these behaviors impact you, contact your implementation partner and consider upgrading to a future release.

note

Existing data is not deleted. The issues mentioned relate to the pre-existing data format being incompatible with the new payments capabilities. New order and payment transactions are stored in the new schema and are unaffected.

Database Changes

Ensure that the database is updated as required when you upgrade Elastic Path Commerce to the current version. The following database tables are updated:

Updated TSHOPPINGCART table to replace the individual indexes on SHOPPER_UID and STATUS with a new composite index on SHOPPER_UID plus STATUS.

The following database tables are added for payments:

TPaymentInstrument: Represents the Payment Instrument
TPaymentInstrumentData: Represents additional data associated with the payment instrument as key value pairs
TPaymentProviderConfig: Represents an association to payment provider configuration by GUID and name
TPaymentProviderConfigData: Represents additional data associated with the payment provider configuration
TCustomerPaymentInstrument: Represents the payment instrument saved in profile for a customer
TCustomerDefaultPaymentInstrument: Represents the default profile payment instrument for a customer
TCartOrderPaymentInstrument: Represents the relationship between the chosen payment instrument and the cart order
TOrderPaymentInstrument: Represents a payment instrument used in an order
TOrderPayments: Represents a payment transaction on a payment instrument
TPaymentLocalizedProperties: Represents a localized name for a payment provider configuration
TStorePaymentProviderConfig: Represents the relationship between the store and the payment provider configuration

For more information about database tables, see Payments.

Fixed Issues

Core Commerce

Fixed an issue with the availability rule setting for a product in Commerce Manager. Previously, if the availability rule for a product is set to always available, you can’t change the rule to any other option. Also, if the rule is set to any other option than always available, you can’t change it to always available. Now, you can change the availability rule for a product as required.
Fixed issue with retrieval of SKU Options and SKU Option Values when reading products, which resulted in unnecessary database queries, increased memory consumption and potential system instability. For more information, see Optimizing Performance.
Fixed issue where many duplicate copies of queries with an IN clause are cached, which resulted in increased memory consumption and potential system instability.
Fixed performance degradation when shoppers have a large number of carts.
Fixed product search indexing performance issues with a large number of stores and virtual catalogs.