12 posts tagged with "Commerce Extensions"

MINOR Added support for the is_null search operator when searching for custom api entries.

MINOR We have enabled Custom API Role and Permissions management in Commerce Manager.

For each Custom API, you can assign specific access permissions to each built-in store role.

See Manage Custom API role permissions.

MINOR We have introduced a mechanism that will allow you to influence the layout of Custom Fields within a Custom API in a User Interface. It does not order or affect the JSON response, and has no semantics on the backend. For more information, see Creating Custom Fields.

MINOR We have introduced the ability to configure a Custom API to allow a Custom API Entry to be created if it didn't exist when attempting to update it. This simplifies business processes such as data import and synchronization. For more information, see Upsert Custom API Entries.

Additionally, we have also added a checkbox in Commerce Manager to enable the upsert functionality. See Creating Custom APIs.

MINOR A cart.updated event is now emitted whenever any tax-related operation occurs on the cart, such as adding, updating, deleting, or performing bulk actions on tax items. For more information, see Observable Events.

MINOR We have now introduced a new optional field, order_number, which serves as an alternative to the existing order_id. For Authorize.net transactions, order_number will be sent instead of the order_id, and will appear as the invoice number. For more information, see Update an Order.

MINOR We have added the ability to configure string Custom Fields for use_as_url_slug, allowing you to use the value of that Custom Field to access your Custom API Entry in a way that is well-known to you and your processes rather than an auto-generated identifier. For more information, see Update Custom API Entries.

Additionally, we have also added a checkbox in Commerce Manager to enable a Custom Field for use as the URL of entry record. See Creating Custom Fields.

MINOR We have introduced the ability to configure a Custom Field as immutable, allowing you to better align your Custom API with your business needs. When set to true, the value of this field can be specified only during POST requests and cannot be modified during PUT requests. For more information, see Custom Fields.

MINOR Previously, we had introduced the ability to model data with uniqueness constraints for string fields in Commerce Extensions. This feature is now further enhanced to be case-insensitive, that is, to take different cases into account for conflicts. For more information, see Custom Fields.

MINOR We have introduced the ability to model data with uniqueness constraints for string fields in Commerce Extensions. For more information, see Custom Fields.

MINOR When using Custom APIs, we have introduced support for HTTP Conditional Requests, using the If-Match header. Clients can use these requests to implement safe concurrent updates to the same resource by multiple writers. For example, this is useful in inventory tracking, as it prevents lost updates and other data consistency issues with the inventory amounts. For more information, see Update Custom API Entries.

MINOR We have added the capability to configure the storage of null values in Custom API Entries. For more information, see Null Values.

MINOR On October 18, 2022, we notified customers that the bundle_configuration object was misspelled as bundle_configuation in the cart, cart items, and order items, and has been deprecated. We recommend using bundle_configuration to create bundle configurations.

MINOR We have introduced support for float field types in Commerce Extensions to support your business needs. For more information, see Custom Fields.

MINOR We have added events for Custom API entries. You can integrate Commerce Extensions with your external systems by observing the appropriate events. For more information, see Custom API Entries.

MINOR Shoppers can now select a bundle that has a default list of products. Shoppers can choose to have all the default products, keep some of the default products or change the default products completely. This is useful, for example, if you want a new addition fragrance in a fragrance bundle to appear as the default option. For more information, see Dynamic Bundles.

MAJOR We have now introduced a new feature, called Commerce Extensions that supports the creation of Custom APIs according to your business needs. These Custom APIs support a variety of field types, including:

• String with customizable length limits and regex validation
• Integer with minimum and maximum value constraints
• Boolean

Moreover, Commerce Extensions offers the ability to apply filters to all fields, enabling multidimensional data retrieval. Additionally, we've enhanced sorting and filtering capabilities based on creation and last update dates. For more information, see Commerce Extensions.

You can also create new Custom APIs within Commerce Manager. For more information, see Commerce Extensions in Commerce Manager.