Release Notes 9.1.25:

1. Wanting to have an Update the UPS setup flow including Batch Shipments and Pickups, so that I can track Shipments:

Under the UPS category, there will be the following changes in the AppSettings:

New AppSettings:
  • `UPSShipperAddress`: this is the 'Sent From' address
  • `UPSPackageType`: Package Type, we can provide a list of options (see attached file)
  • `UPSUnitOfMeasure`: Options: KGS | LBS | OZS
  • `UpsShipmentServiceCode`: List of options (see attached file for the Shipment Service Code)
  • `UPSPickupServiceCode`: Service Code, we can provide a list of options (see attached file)
  • `UPSPaymentMethod`: Payment method, we can provide a list of options (see attached file)
  • `UPSContainerCode`: Options 01/02/03 (see attached file)

Remove the following:

  • `UPSLicenseKey`
  • `UPSUserName`
  • `UPSPassword`

Swap:

  •  Change `UPSPickupURL` to `UPSTrackingURL`

UX Changes:

1. From the Shipment Window or Pickup Window:

  • Select an event or set of event
  • Click on the UPS button
  • A popup window appears asking for confirmation of creating a Shipping Label with UPS _(This already happens in our current flow)
  • After user confirms Shipping Label creating, a new popup window appears with a form of two fields:

1. Total of bags included:

Please note: shipments do not required a bag value, UPS considers only one package, however, we do need quantity of items in the API call for pickup

2. Total weight: consider only 150 pounds can be sent in a package

  • User can confirm or cancel
          1. If this is in batch, it will loop through the events' selection

1. On the left side panel, go to Production

2. Click on Dispatching and Shipping

3. Select Shipping

4. Choose Dispatch Pickup Window

5. Select the Event Status drop down, put a check mark on the statuses

6. From and To calendars, select the dates, click on the Refresh button

7. Put a check mark on the desired events, then click on the Batch Process button

8. Press Yes in the pop-up message, next enter the Number of Bags and Weight, click on Process, a successfully pop-up message will be displayed.

2. Being able to Setup an experimental SSRS folder in Empower so that I can show clients early preview versions of their custom reports:

1.  App Settings:

  • SSRSEnableExperimentalReports and SSRSExperimentalReportsFolder are created under Report Server Configuration.
  • When enabled, lookup order is: Experimental → SSRSReportFolder SSRSDefaultReports.
  • When disabled, lookup order remains: SSRSReportFolder SSRSDefaultReports.
  • Error is thrown if report not found in any location.

2.  Folder & Permissions:


  • Experimental folder resides in the production SSRS server and supports subfolders per database.
  • Chris has read/write permissions; others have limited or no write access.

5.  Promotion Workflow:

  • Reports tested in experimental can be promoted to the official repo and pipeline.
  • After promotion, experimental copy is removed, and app setting reverts to No.

7.  Monitoring & Compliance:

  • Scheduled job generates a report listing all experimental reports and their age.
  • Report is distributed periodically to Infosec and Management.
  • Reports older than threshold (e.g., 30 days) are flagged for review.

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

2. Select App setting and look for SSRSEnableExperimentalReports and SSRSExperimentalReportsFolder

3. Set the value to Yes

Next

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

5. Click on Event & Order Management

6. Choose Event Management - All Status Types Included

7. Pick an event, select a report in the drop-down menu (Invoice), choose Preview


3. Validating if Beverages items are web-enabled before adding them to the Shopping Cart during Sync:

1- Web-Enabled Validation:
When syncing Beverages items via the endpoint sync/to_pg/equipments/{DatabaseName}/{equipmentId}, the system must validate whether the item group is web-enabled before allowing it to be added to the Shopping Cart.
2- Shopping Cart Inclusion:
Only Beverages items that are confirmed as web-enabled should appear in the Shopping Cart.
If Beverages item is not web-enabled, it must be excluded from the Shopping Cart and optionally logged for audit or debugging purposes.

1. On the left side panel, go to Data Items
2. Click on Beverage Management
3. Select Beverage Management (Active Items Only)
4. Open an existing item and go to the Web Details Tab

4. Creating the API Keys for the Zaffre Client for Blazor:

API Key Generation:

Generate unique API keys for the Zaffre Client.

Ensure the API keys are securely stored and managed.
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.
Security:
Implement measures to protect the API keys from unauthorized access.
Ensure that the API keys are not exposed in the client-side code.
5. [Infrastructure] Configure Account-Specific URL for Zaffre in production Environment:
Add a pre-production environment URL to point to the Zaffre Client account. 
 URL: zaffre.elecate.net
6. Having the ability to register Credit Cards with Global Payments Payfields:
  • In the Costumer Management Window or the Event Editor Windowm, the credit card payment option using PayFields is visible and selectable in the Billing Tab.
  • Users can securely enter Customers credit card details via the PayFields interface.
  • Transactions are processed successfully through the Global Payments PayFields API (Consuming the Payment API developed by the Shopping Cart Team.
  • Shift - 1 : Shift 27360: Add Credit Card Type to GlobalPayfields form

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 existing event, go to the Billing Tab

5. Click on Add Credit Card

Adding a card in the Open Edge Payfields window at event level:
Card successfully added:

Adding a card in the Open Edge Payfields window at customer level:

Card successfully added: