August 2024 New Digest

Welcome to the August edition of our News Digest, featuring the latest updates and enhancements in Virto Commerce solutions.

Highlights

  • New storefrontless architecture
  • xAPI decoupling
  • Marketplace enhancements

Frontend Application 2.0.0

:fire: As of July 2024, Virto Commerce Storefront and Theme have been replaced with the Frontend Application. The simplified and accelerated Frontend Application architecture is as follows:

It was designed to minimize custom development, leverage standard network products, and deliver faster speeds at a lower cost. This revamped architecture simplifies the development process, making it more accessible for developers.

:fire: Key highlights:

  • The new architecture significantly reduces the need for custom code, allowing you to deploy solutions faster. We replaced custom .NET application with load balancer.
  • By utilizing industry-standard network products, we ensure compatibility, reliability, and ease of integration.
  • This update ensures enhanced speed and lower costs.
  • The architecture enables developers to work more efficiently and focus on innovation. From this moment we have two dev points: Virto Commerce Frontend and Virto Commerce. Virto Commerce Frontend can be connected by Platform URL and that all.

:fire: Out-of-the-Box features:

  • Virto Cloud Support.
  • Ready-to-use Azure ARM templates streamlining your deployment process.
  • CDN integration, Firewall, DDoS protection, and optional Server-Side Rendering (SSR) for improved SEO and initial load times.

:warning: Current Storefront and Theme users can migrate to the new storefrontless architecture with our assistance, or continue using the Storefront with the 1.62 version, which will receive updates until the end of 2024. After that, while it will still be possible to use the Storefront, no further updates will be provided.

Read more about Storefrontless architecture

Frontend Application 1.62.0

For corporate accounts in the Frontend Application, you can assign multiple organizations to any contact or employee:

The contact can switch between the assigned organizations in the Frontend Application:

Frontend Application 2.1.0

Frontend Application homepage can now be customized via the builder.io application:

Content can now be configured:

Platform

:fire: In July 2024, we migrated to a new xAPI architecture to better support the evolving needs of our business API with GraphQL. The xAPI module has been replaced with a suite of new more specialized modules. This change is part of our effort to simplify business API development and streamline our release cycle.

:warning: The xApi module is archived and will be supported in Stable 8 and Stable 9 releases.​ Future developments will focus on the new VirtoCommerce.Xapi and related modules.​ The latest Edge release has adopted the new modules.​and namespaces.

Read more about update path

xAPI 3.802.0

Anonymous uploads are now allowed to specified scopes within the file upload options. Developers can now configure anonymous uploads for a particular scope, enabling users to upload files without needing to sign up:

{
  "FileUpload": {
    "RootPath": "attachments",
    "Scopes": [
      {
        "Scope": "<your scope>",
        "MaxFileSize": 123,
        "AllowedExtensions": [ ".jpg", ".pdf", ".png", ".txt" ],
        "AllowAnonymousUpload": true
      }
    ]
  }
}

Skyflow 3.804.0

The Skyflow implementation has been reworked, allowing users to optimize the Credit Card UX.

Order 3.823.0

  • In the Customer orders blade, you can copy order Id and number and apply quick filters using the dropdown menu:

  • Now you can copy the current order URL and paste it into a new window to open the desired order immediately:

    order-url

The same feature has been added for products and categories (Catalog 3.813.0).

3.805.0 Store

Public store settings can now be read with the Rest API:

Marketplace

  • If a vendor is initially assigned a specific category to manage and the operator later upgrades their access to a higher-level category, the child-parent category hierarchy will be automatically adjusted. This means that child categories will be re-assigned to their appropriate parent categories.

  • End-to-end tests for the product creation process have been added. This new feature ensures that every step of creating a product, from initial input to final listing, is thoroughly tested and verified for functionality and reliability.

  • In the Vendor portal, you can now add or edit shipments:

    shipment

  • You can add, edit, and delete vendor logo in the Operator portal:
    adding-logo (1)

    and Vendor portal:

    adding-logo-vendor-portal

  • Rating and Reviews is now a separate module that can be installed at the user’s discretion.

For more information, request a demo

VC Shell

  • Application Insights support has been added to the VC Shell. Now, the instrumentationKey can be easily configured during VC Shell initialization, enabling the logger to function in two key areas:

    • Error monitoring:

      • Automatically detects and logs application errors.
      • Helps developers quickly identify and address issues.
    • PageView tracking:

      • Monitors user interactions and page views.
      • Provides insights into user behavior and application performance.

      image

  • The VC Shell now includes a combined API client generator and build script, streamlining the process into a single command. This feature simplifies generating and building API clients by consolidating multiple steps into one efficient workflow:

    "generate-api-client": "cross-env api-client-generator --
    APP_PLATFORM_MODULES=' [VirtoCommerce.MarketplaceVendor, VirtoCommerce.Orders, VirtoCommerce.Catalog]' --APP_API_CLIENT_DIRECTORY=./src/api_client/ --APP_OUT_DIR=dist --APP_PACKAGE_NAME=@vcmp-vendor-portal/api --APP_PACKAGE_VERSION=$npm_package_version",
    

    Key parameters:

    • –APP_OUT_DIR: Specifies the output directory for the final JavaScript (JS) and TypeScript (TS) declarations.
    • –APP_PACKAGE_NAME: Sets the package name for the package.json file.
    • –APP_PACKAGE_VERSION: Uses the version specified in the top-level package.json file.

Explore new VC Shell features and capabilities

Documentation

2 Likes