Skip to content
English
  • There are no suggestions because the search field is empty.

Release Notes 7.28.26 (Release 29.6) - Online Portal

1. Default Salesperson Assignment

Enhanced Shopping Cart order creation to automatically assign the default salesperson configured in App Settings when new orders are submitted to the Core.

What changed:

  • Updated the Shopping Cart synchronization process to include the configured default salesperson when creating new orders.

     

  • The WebAppDefaultSalesperson App Setting is now used to populate the salesperson value during order creation.

     

  • Orders created from the Shopping Cart are automatically assigned to the configured default salesperson in the Core.

     

  • This enhancement applies during the initial order creation without modifying existing order records.

Impact:

  • Ensures new Shopping Cart orders are consistently assigned to the correct salesperson.

     

  • Eliminates the need for manual salesperson assignment after order creation.

     

  • Improves consistency between Shopping Cart configuration and Core order management.

2. Web Group-Based Menu Availability

Enhanced Shopping Cart menu visibility by allowing Data Item Groups to be displayed based on their Web Group configuration, providing centralized control over menu availability.

What changed:

  •  

    Updated the Shopping Cart to respect the Web flag configured at the Data Item Group level.

     

  • When a group's Web flag is enabled, all web-enabled items within that group become available in the Shopping Cart.

     

  • When a group's Web flag is disabled, the group's items are hidden from the Shopping Cart, even if individual items are web-enabled.

     

  • Changes to a group's Web flag are automatically synchronized between the Core application and the Shopping Cart.

Impact:

  • Simplifies menu management by allowing visibility to be controlled at the group level.

     

  • Reduces the need to update individual menu items when enabling or disabling an entire group.

     

  • Ensures consistent menu availability between the Core application and the Shopping Cart.

3. Show Web Validation for Catalog Synchronization

Enhanced the synchronization process to validate the Show Web setting before synchronizing catalog records, ensuring that only web-enabled options are available in the Shopping Cart.

What changed:

  • Updated the synchronization process to validate the Show Web field for the Mail Type, Referred By, and Customer Type catalogs.

     

  • Only records with Show Web enabled are synchronized and made available in the Shopping Cart.

     

  • Records with Show Web disabled are excluded from synchronization and are not displayed as selectable options.

     

  • The same validation logic is consistently applied across all supported catalogs.

Impact:

  • Ensures customers only see options that are intended to be available online.

     

  • Improves consistency between Core configuration and the Shopping Cart.

     

  • Simplifies catalog management by allowing administrators to control web visibility using the Show Web setting.

4. Instruction Title Label Update

Updated the Admin Portal to improve labeling consistency for the Instruction Title field.

What changed:

Renamed the field label from "Title Introduction" to "Instruction Title" in the Admin Portal.
Updated the label to better reflect the purpose of the field and align with the associated instructions section.

5. Event Type Full Payment Enforcement

Enhanced the Shopping Cart to support full payment requirements based on the Event Type configuration in the Core application.

What changed:

  •  

    Added support for the Enforce Full Payment setting configured at the Event Type level in the Core.

     

  • When full payment enforcement is enabled, customers must pay the entire outstanding balance to complete a payment.

     

  • Partial payment attempts are rejected, and a validation message informs customers that full payment is required for the selected Event Type.

     

  • When full payment enforcement is disabled, both partial and full payments continue to be accepted.

Impact:

  • Allows organizations to require full payment for specific Event Types.

     

  • Ensures payment rules configured in the Core are consistently enforced in the Shopping Cart.

     

  • Provides a clear validation message to customers when partial payments are not permitted.

     

  • Helps organizations maintain compliance with event-specific payment policies.