Merge branch 'main' into DB-1029

changelog/2024/2024-10-2-changelog.md

@@ -0,0 +1,12 @@
+---
+title: 'Added First time shopper coupon code, Added duplicate promotion in Promotions Builder'
+date: '2024-10-2'
+tags: ['Commerce Manager', 'Promotions Builder']
+hide_blog_post_date: false
+---
+
+**MAJOR** We have introduced a new feature allowing the creation of promotion codes specifically for first time shoppers, who have not yet completed a purchase with the store. Within Commerce Manager, you can now create a single code and select the option to apply it exclusively for first time shoppers. For more information, see [Creating a Single Code](/docs/commerce-manager/promotions-builder/creating-promotion-codes).
+
+For details on creating a first time shopper promotion code via the API, see [Create First time Shopper's Coupon Code](/docs/promotions-builder/promotions-builder-codes/create-first-time-shopper-code).
+
+**MINOR** Commerce Manager: We have added a new feature allowing you to duplicate an existing promotion in Promotions Builder. For more information, see [Duplicating a Promotion](/docs/commerce-manager/promotions-builder/creating-a-promotion-in-promotions-builder#duplicating-a-promotion).

changelog/2024/2024-10-3-changelog.md

@@ -0,0 +1,8 @@
+---
+title: 'Added Presentation Sort Order for Custom Fields'
+date: '2024-10-03'
+tags: ['Commerce Extensions']
+hide_blog_post_date: false
+---
+
+**MINOR** We have introduced a mechanism to 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](/docs/docs/commerce-manager/commerce-extension/commerce-extension-in-cm#creating-custom-fields).

changelog/Studio-Release-Notes/Release-203-September-26-2024.md

@@ -0,0 +1,27 @@
+---
+title: Studio Release 203 | September 26, 2024
+date: 2024-09-26
+tags:
+  - Studio
+---
+
+#### Overview
+
+Mainly bug fixes in this release.
+
+#### Complete List of Resolved Items
+
+#### Exporting to CSV
+
+* **Bug** - Fixed an issue where exporting to a CSV file was not working.
+
+#### Style Guide
+
+* **Bug** - Fixed an issue where large quote font on a component did not reflect the Style Guide.
+
+#### Cart Drawer
+
+* **Bug** - Fixed an issue where free shipping method was applied improperly after checkout.
+
+
+

docs/commerce-manager/commerce-extension/commerce-extension-in-cm.mdx

@@ -8,29 +8,41 @@ sidebar_position: 4
 
 1. Go to **COMMERCE EXTENSIONS > Custom APIs**.
 1. Select **Create New**.
-1. Fill out the following details in the **Basic Details** section:
-    1. In **Name**, enter the the name of the Custom API. It should be between 1 and 255 characters.
-    1. In **Description**, enter the description for the Custom API.
-1. Fill out the following details in the **Advanced Options** section:
-    1. In **API Type**, enter the type of the Custom API. 
-    1. In **Slug**, enter a unique slug identifier for the Custom API.
-    1. (Optional) Under **Settings**, select the checkbox for **Allow UPSERT** so the system can automatically create a new record if it doesn't exist when updating. For more details, see [Upsert Custom API Entries](/guides/How-To/commerce-extensions/create-a-multilocation-inventories-resource#upsert-custom-api-entries). 
+1. In the **Basic Details** section:
+    1. **Name**: Enter the the name of the Custom API. It must be between 1 and 255 characters.
+    1. **Description**: Provide a description for the Custom API.
+1. In the **Advanced Options** section:
+    1. **API Type**: Specify the type of the Custom API. 
+    1. **Slug**: Enter a unique slug identifier for the Custom API.
+    1. (Optional) In **Settings**, select the checkbox for **Allow UPSERT** so the system can automatically create a new record if it doesn't exist when updating. For more details, see [Upsert Custom API Entries](/guides/How-To/commerce-extensions/create-a-multilocation-inventories-resource#upsert-custom-api-entries). 
 1. Select **Create Custom API**.
 
 ## Creating Custom Fields
 
 To create a Custom Field for a Custom API, follow these steps:
 
 1. Go to **COMMERCE EXTENSIONS > Custom APIs**.
-1. Click on the target Custom API in the list. 
-1. Select **Create Field** and choose one of the following options:
+1. Select **Create Field** and choose one of these field types:
     - **String**
     - **Integer**
     - **Boolean**
-1. Fill out the following details in the **Basic Details** section:
-    1. In **Name**, enter the name of the field for the Custom API. It should be between 1 and 255 characters.
-    1. In **Description**, enter the description for the field.
-    1. In **Slug**, enter a unique slug identifier for the field.
+    - **Float**
+1. In the **Basic Details** section:
+    1. **Name**: Enter the field name. It must be between 1 and 255 characters.
+    1. **Description**: Provide a description for the field.
+    1. **Slug**: Enter a unique slug identifier for the field.
+1. (Optional) In **Settings** section, select the checkbox for **Use as the URL of entry record**. This option is shown only when you select **String** field type. When this option is enabled, the value of this field will be used as the URL slug for entries created in the Custom API. This field must be a String, unique, and cannot allow null value. The Custom API must not have any existing entries.
+1. (Optional) In **Settings** section, set **Sort Order** of your field. This option allows you to prioritize the order in which fields are presented in the user interface. Fields with a higher value will appear first. The value must be between 0 and 1000.
+1. In the **Validation** section:
+    1. Set the value rules from the drop-down lists:
+        - **Can be NULL** or **Cannot be NULL**.  This option is disabled when you select **Use as the URL of entry record**.
+        - **Can be changed** or **Cannot be changed**
+        - For **String** fields, choose among **Is unique and case sensitive**, **Does not need to be unique**, or **Is unique and case insensitive**. 
+            The **Does not need to be unique** option is disabled when you select **Use as the URL of entry record**.
+    1. (For **String** fields) Under **Character Limit**, enter **Minimum Length** and **Maximum Length**.
+    1. (For **Integer** and **Float** fields) Under **Input Range**, enter **Minimum Value** and **Maximum Value**.
+    1. (For **String** fields) In the **Regular Expression** field, enter a less than 1024 character RE2 regular expression to restrict the specific characters that can be stored.
+
 1. Select **Create Field**.
 
 ## Creating Custom API Entries