New Development
      Back to home
      1. Home
      2. Software Updates Timeline
      3. New Development

      Release Notes 58

      1. Needing the development team add re-export functionality and conditional UI changes for QBO integration:

      • When QBO integration is enabled via appsettings, the following controls are hidden:

        • "Select New Status..." dropdown
        • "Update Selected" button

      •  A new "Re-export" button is added to the grid section under "Exported Records" and is available for:

        • Customer
        • Sales

      • The "Re-export" button triggers the appropriate logic to re-export the selected records to QBO.

      • The UI updates dynamically based on the QBO setting without requiring a page reload.

      • All changes are tested and verified in both QBO-enabled and non-QBO scenarios.

      2. Syncronizing Jamix Stock Cards into Recipe Items, so that I can Manage Jamix POs:

      • Stock Card sync in the Recipe Management Items Window**
            * Read  `EnableJamixSync`, if 'Yes', then read `JamixInstanceId`
            * Display the import Stock Cards button
            * Add a loading screen while processing, show spinner wheel screen, with the message 'Please, wait while we load your Jamix Locations'
            * Response handling:
               * Success: show pop-up with a successful message, refresh 
               * Error: Show a pop-up message
      • Endpoint Consume**
           * Send a KeyCloak token

      3. Creating Purchase Orders in Empower and Jamix, so that Kitchen department is aware of the correct requests:

      • Food PO's Management by Event Date Window:
            * Read  `EnableJamixSync`, if 'Yes', then read `JamixInstanceId`
            * Display the Generate Jamix PO button
            * Add a loading screen while processing, show spinner wheel screen, with the message 'Please, wait while we load your Jamix Locations'
            * Response handling:
               * Success: show pop-up with a successful message, refresh 
               * Error: Show a pop-up message
      • Endpoint Consume:
           * Send a KeyCloak token


      4. Updating Purchase Orders already placed in Jamix:

      TBD business Logic

      5. Having an option to nest the packages within the order review:

      • A “Nest Packages” option (toggle or button) is available in the Order Review screen.
      • When enabled, all items belonging to the same package are grouped under the package name.
      • Each package group can be expanded (unfolded) or collapsed (folded) using a visual control (plus/minus button).
      • Collapsing a package hides all its items, while expanding reveals them again.
      • The nested view updates dynamically when the Nest package button is clicked — no page refresh required.
      • When packages are nested the button will change the text to un-nest pkgs
      • The grouping respects existing data relationships (items only appear under their correct package).
      • The nested or flat view preference persists while the user remains on the Order Review page.
      • The feature does not affect the accuracy of item quantities, prices, or totals.
      • Styling clearly differentiates package headers from individual items (bold font).

      Shift - 2:

      • If the use clicks on the "Nest" or "Un Nest" button, then the app must not fire a full save for the event.
      • Once items are nested on a package, then the "Group" column must be disabled. 
      • If a user does a change on the "Production Notes, Contract Notes, Sequence or Eqp Quantity" then those changes must be saved only if the user clicks on the "Save" button for the event.
        • Remove the need for the "Edit" button on the items that are on a nested package
        • Allow the user to click on to click on those fields without pressing on the edit button
        • This must also applied to items that are outside of a package. 

      6. Having a drop-down field for Jurisdictions:

      • In the Delivery Postal Code Information window, we need to have a dropdown that will pull the information from the "Jurisdiction" table.

      7. Adding Captain from the Staff Scheduling Window:

      • On the Staff Production Scheduling by Event window, when clicking on the "Action" button dropdown, we need the ability to assign a Captain
        • This will be display as two options:
          • Add Captain
          • Delete Captain
          • Unassign Captain
        • The add action must be enable only if you are selecting a record that has not been assigned as a captain.
        • Delete captain must delete the whole staff and skill type and must be visible if you are selecting a record who is already a captain
        • The Unassign Captain action must be enable only if you are selecting a record from the grid that is a captain

       Additional AC: 

       
      **AC 1**
      Given an Operations Manager,
      when they want to assign captains,
      then they can go to the Staff Production Scheduling Window by event, select assigned staff from the grid, and by pressing the batch update, they will mark a new Captain toggle that they can enable, so the selected staff is a new Captain in `dbo.StaffCaptain`
       
      **AC 2**
      Given an assigned captain,
      when they authenticate and select the Event Cards,
      then they can view event attachments assigned as public, and marked for Event Staff and Captain
       
      AC 3
      • A column will be added to identify who is the captain on the staff members added to the grid. 
      AC 4:
      • Remove the "Delete Captain" option
      • The "Add Captain" action must only be enable if you are selecting a skill type with a staff member available and the event does not have a captain assigned to it. Otherwise the button must be disable
      • "Unassign Captain" button must be enable if you are selecting the captain for the event, otherwise that must be disable. 

      8. Allowing EventType.EventTypeDivision to be nullable and handle null values during invoice export:

      • Database/Model Update:

        • Modify the EventType.EventTypeDivision property to allow NULL values.

      • Validation Logic:

        • In ExportInvoiceCommandHandler (line 142), add a check:
          • If EventTypeDivision is NULL, handle gracefully (e.g., skip logic or apply default behavior).
          • Ensure no exceptions are thrown due to null references.

      9. Wanting to be able to do partial refunds:

      Partial Refund:
      • Allow the user to do a "partial refund" process when doing the "Refund Transaction" process
        • This should allow the user to refund only a portion or the desired quantity for the user, but not the total payment.