Release Notes 3.7.25:

1. Pushing a few USP for all the clients:

It was added for all the clients the new USP:

  • usp_DepositRequestRequiringBillingReminder (updated)
  • usp_billingGetEventsRequiringBillingReminder (updated)
  • usp_GetEventsGuaranteeDateBillingReminder ⁠(new)

2. Saving in Event CRM is using a Full Save vs a Partial Save:

Changes were made and saved on the Last Action or Next Action dropdowns on 
the CRM section and they appeared on the grid in CRM Log section.

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

2. Click on Event & Order Management

3. Select Event Management - All Status Types Included

4. Open an event by clicking the pen icon

5. Go to the CRM tab

3. Making that Salespeople have the new SSO after creation, so they can have access to the business tools:

 [Sales person] As an administrator, I want that salespeople have the new SSO 
after creation, so they can have access to the business tools.

1. On the left side panel, go to General Setup

2. Click on Marketing

3. Select Salesperson

4. Open an existing record or create a new record by clicking on New Entry

4. Converting the attachments on the email threading to be shown as plain text instead of the current format:

The attachments were converted on an email within the email threading from the current format to plain text, in order to look more organized. 

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

2. Click on Event & Order Management

3. Select Event Management - All Status Types Included

4. Open an event by clicking on the pen icon

5. Go to the Email Tab

5. Naming correctly the Event Files column in the Main Staff View Window:

The "Files" column is renamed to "Event File" in the Main Staffing View Window 

1. On the left side panel, go to Production

2. Click on Kitchen Management

3. Select Main Kitchen View

4. Look for the Event Files column

6. Changing the Sender of a Survey:

The survey will be directed to the individual user and not to the event. 

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

2. Click on Event & Order Management

3. Select Event Management - All Status Types Included

4. Open an event by clicking on the pen icon

5. Go to the Customer tab

7. Making some modifications to the Equipment Overbooking Threshold window:

  1. Remove the new button.
  2. Rename fields:
    • "Overbooked From" → "Usage From"
    • "Overbooked To" → "Usage To"
  3. CSS issue: Fix the white border on the left and right.
  4. Grid Persistence: Enable Grid Persistence on this window.
  5. Disable paging.
  6. Popup changes:
    • Adjust the space that appears when clicking the (+) button.
    • Move the Pencil button to the bottom of the popup window.
  7. Quantity column: Ensure it displays quantity instead of currency.
  8. Grid Persistence: Enable Grid Persistence on this grid as well.

8. Adding the functionality to change the "Page" & "Sequence" column for Headers in the Event Sales Menu:

The user will have the ability to change in the header the value for Page & Sequence.

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

2. Click on Event & Order Management

3. Select Main Sales View

4. In Main Sales View, look for Open Event Sales Menu

9. Preventing that the "Tax Percent" field values do not round to the nearest whole number:

The configuration of the “Tax percentage” field in the “Manage tax table” modal 
window has been updated, allowing now up to three decimal places instead of the current two.

1. At the top of the screen, on the right side you will see the Gear Icon

2. Click on the Gear Icon

3. Look for Financial Setup

4. Into Financial Setup, search for Create and Edit Tax Table Entries

5. Click on New Entry

10. Creating the API Keys for the UTAH_FS Client for Blazor:

  1. API Key Generation:

    • Generate unique API keys for the UTAH_FS Client.
    • Ensure the API keys are securely stored and managed.
  2. Integration with Blazor:

    • Integrate the generated API keys into the Blazor application.
    • Ensure the Blazor client uses the API keys to authenticate requests to the backend services.
  3. Security:

    • Implement measures to protect the API keys from unauthorized access.
    • Ensure that the API keys are not exposed in the client-side code.

11. Configuring the Account-Specific URL for UTAH_FS in pre-production Environment:

It was added a pre-production environment URL to point to the account UTAH_FS.