October 2024

We updated the pre-selected option of 'Display the edition in shopping cart and orderflow' to Yes.

We added company name field to 'Product Quotation' form type of a dynamic form.

We created Shop notification endpoints for API v2.

• /api/v2/shopnotifications (get) - This endpoint retrieves a list of shop notifications.
• /api/v2/shopnotifications/{id} (get) - This endpoint retrieves details of a specific shop notification by specifying a shop notification ID.
• /api/v2/shopnotifications (post) - This endpoint create a new shop notification.
• /api/v2/shopnotifications/{id} (put) - This endpoint updates every fields of shop notification by specifying a shop notification ID.
• /api/v2/shopnotifications/{id} (patch) - This endpoint updates only particular fields of shop notification by specifying a shop notification ID.

To check the api endpoint, please visit this url your shop/api-swagger

We built a support to check the status of server-side render that generates 3D screenshot.

We implemented a support on admin interface to enable users to request multiple screenshots from a server-side render. The multiple screenshots can be integrated further in various way as desired. In this task, we created an interface for users to enter the names of screenshot events. An update on the screenshot service will be shipped afterwards.

Note: The events must be implemented with the 3D products first. Please contact your account manager for the implementation on products.

We added a new setting 'Display the edition in shopping cart and orderflow' in edition to Default feature. With this setting, users can set up the default option either to Yes or No for every newly created edition. The default option from the system is 'No'.

We created endpoints for products as follows:

• /api/v2/products (get) - This endpoint retrieves a list of products.
• /api/v2/products (post) - This endpoint created a new product.
• /api/v2/products/{id} (put) - This endpoint updated every field of product by specifying a product ID.
• /api/v2/products/{id} (patch) - This endpoint updates only particular fields of product by specifying a product ID.
• /api/v2/products/{id} (delete) - This endpoint deleted the product(s).

Also, we updated a get product endpoint by removing value field under OriginalPrices, ServiceFees and DownPaymentPrices and chnage the output format of price related fields.

To check the api endpoint, please visit this url your shop/api-swagger

We created the endpoints of API v2 for shop user achievements as follows:

• /api/v2/shopuser/{Id}/achievements (get) - This endpoint reteives a list of achievements that a specific user have.
• /api/v2/shopuser/{Id}/achievements (post) - This endpoint adds a new achievement to a specific shop user.
• /api/v2/shopuser/{Id}/achievements (put) - This endpoint updates the achievements of a specific user.
• /api/v2/shopuser/{Id}/achievements (delete) - This endpoint removes the achievement(s) from a specific user.

To check the api endpoint, please visit this url your shop/api-swagger

Regarding an enhancement of multilingual Url feature that allows users to set the product, category, page URL active or inactive. We updated the Url field of the product endpoints of API v2 (get, put, patch, post) to use a new format that supports active/inactive status.

We created an order endpoint of API v2 to get details of specific order.

We added the function to activate and deactivate the specific language of Product, Page, and Category. The inactive URL will be hidden from all locations. Please navigate to the page or product or category you would like to manage and click to manage multilingual URL. Turn on or off the boolean to activate and deactivate the URL.

We implemented the feature 'Product Variants' to name the query string of the products. To access this feature, users are required to have 'ProductVariants' permission. The feature can be accessed with the button on top of the product detail page. The variants will be automatically recorded when that product is selected as a 3D look alike product in an other product or when that configuration is selected on a website. The variants will appear after search.

This feature can be further integrated with the shopping cart to display more concise configurable product or meta tags or data tracking tool for various usages.

We resolved an issue with the master edition metadata that cannot save when it was empty.

We resolved an issue that a shop user type filter on shop user dashboard filtered the invalid users not having that type. This issue occurs when a user used to have that shop user type, but it was removed.

We resolved an issue that the metadata of Account page disappeared and cannot be saved.

We resolved an issue that 'All' extension/image type didn't work.

We resolved an issue that sync all editions function didn't work.

We resolved an issue with taxonomy tags structure that the child tags changed their parent tag without any action.

We upgarded the project framework to .NET 8.0.10.

We optimized the data export function to generate the export file more efficiently.

We upgrade the 3D configurator to version 4.7 and update to work with both old and new version. Also, we updated the upload function of 3D objects to be able to select the configurator version and users is required to specify the version before uploading the 3D objects.

Note: After an upload, if the system detect an unsuitable version, it will automatically change the version to the suitable one.

Note: Changing the configuration version is allowed only when there is no file uploaded.

We enhanced the image loading to process more efficiently.

We upgrade a front-end project package.

We removed the unused campaign columns.

Regarding an action plan to update product name field to be a single language field, we haved updated the input field of product name to allow only one language and migrated the name to title in case the title was not filled. Now, we removed the product name column from product translation to completely remove the multilingual product name.

Also, some locations in the admin side which integrated with multilangauge product name were updated to use single language product name instead.

We updated the following locations in admin interface to use product name instead of product title.

• Order summary page
• Order detail page
• Shop user detail page