Release Notes 8.8.25:

1. Enhancing to prevent "Error deleting (spfitems/spbev/smenus/spbitems) record | Errorlog | EventFoodItem Update ex:

The app should allow the user to delete in batch items in the order details grid. 

1. On the left side panel, go to Sales & Marketing

2. Click on Event & Order Management

3. Choose Event Management - All Status Types Included

4. Open an existing event, add multiple items to the event

5. Delete 5 or 10 items by putting a check mark on the desired items and then click on Delete Selected

2. Wanting to add or edit content using the in-cell in the Order Details grid, so that I can work faster:

An authenticated user wants to edit options within an event order detail item.

Editable Fields:

  • Sequence (may cause brief loading time)
  • Production Event Notes
  • Contract or Proposal Notes
  • Recipe Equipment (only for recipe items)
  • Equipment Quantity (only for recipe items)
  • Menu Page

Editing Actions:

  • Save Changes:

    • Press Tab or Shift + Tab to confirm and move to the next/previous cell.
    • Press Enter to confirm and move to the cell below.
    • Click another cell to confirm and begin editing it.
    • Click outside the grid to confirm and exit edit mode.
  • Cancel Changes:

    • Press ESC to cancel and exit edit mode.
    • Perform another grid operation (e.g., paging or sorting) to cancel the current edit.

Performance Consideration:

  • Loading time may affect the row or grid but should not exceed 1 second.

1. On the left side panel, go to Sales & Marketing

2. Click on Event & Order Management

3. Choose Event Management - All Status Types Included

4. Open an existing event by clicking on the pen icon

5. Go to Order Details

6. Add items to the event and then try to edit the items information using the in-cell feature

3. Retrieving package numbers instantly so that I avoid performance delays during data lookup [Research Item Result 12] | [Order]:

  • Stored Procedure Implementation
    • Create a stored procedure callable from the generic scalar endpoint to retrieve values from the appropriate table.
  • Guard Clause Addition

    • Add a guard clause to prevent API calls for Staff and Miscellaneous departments.
  • Parameter Update

    • Include the department name along with the Event ID in the parameters.
  • Endpoint Review

    • Evaluate existing endpoints to determine if they can be marked as obsolete or removed to streamline future backend development.
  • Cleanup of Method Definitions

    • Remove GetNextPackageNumberAsync and department-specific variants from the EventCrudEditor class.
    • Replace with a simplified backend call to retrieve the package number.

image.png

4. Accessing the Delivery Tab instantly with pre-validated event data so that I avoid waiting for processing delays:

  • Reduce Complexity:

    • Break InitializeDeliveryDataAsync into smaller, focused private methods.
    • Group common validations into reusable methods for clarity and maintainability.
  • Validation & User Guidance:

    • Before loading the Delivery Tab, check if the Event Date, Time, and Location are set.
    • If missing, redirect to the Event Info Tab and show the message:

      “Please select the Event Date, Time, and Location before setting up your Delivery times”

  • Performance Optimization:

    • Once the Event Info Tab is completed, automatically trigger InitializeDeliveryTab.
    • This preloads delivery data to reduce loading time when the user navigates to the Delivery Tab.

1. On the left side panel, go to Sales & Marketing

2. Click on Event & Order Management

3. You can either select Create New Event Order or Event Management - All Status Types Included (New Entry

5. Working on the Sync of Beverages groups between Core and Shopping Cart:

Add Beverage Group
  • Method: POST
  • Endpoint: https://shop-sync.dev.elecate.net/sync/to_pg/bevgrps//
  • Criteria: A new beverage group is successfully created and synchronized.
Update Beverage Group
  • Method: PUT
  • Endpoint: https://shop-sync.dev.elecate.net/sync/to_pg/bevgrps//
  • Criteria: An existing beverage group is successfully updated and synchronized.
Add Beverage
  • Method: POST
  • Endpoint: https://shop-sync.dev.elecate.net/sync/to_pg/beverages//
  • Criteria: A new beverage is successfully created and synchronized.
Update Beverage
  • Method: PUT
  • Endpoint: https://shop-sync.dev.elecate.net/sync/to_pg/beverages//
  • Criteria: An existing beverage is successfully updated and synchronized.

1. On the left side panel, go to Data Items

2. Click on Beverage Management

3.  Select Beverage Group Management (Batch Assignment)

6. Configuring the merchant settings with live variant support so that I use the correct processor configurations across sandbox and production environments:

Update the following keys from Sandbox to Live:

  • ElavonV2.0 → ElavonV2.0Live
  • Authorize → AuthorizeLive
  • OpenEdgeV2 → OpenEdgeV2Live

For the Authorize section, hide the following fields:

  • Account Number
  • Solution ID
  • Global Payments
  • Account ID
  • App Name

1. At the top of the screen, on the right side go to the Gear Icon

2. Click on Business Units

3. Select Create and Edit Merchants

4. Choose New Entry and fill in the required information