¶¶Òõ

Create New Product - Add a new Entitlement Product.

¶¶ÒõPortal → Data Management → Order Settings → ¶¶Òõ → Product List

To add an entitlement:

Named Calculations - Add Entitlements as a condition to a Named Calculation.

¶¶ÒõPortal → Data Management → Reporting → Named Calculations → New or Existing Calculation → Conditions

To add an Entitlement to a Named Calculation:

activateEntitlements - Activate Entitlements.

deactivateEntitlements - Deactivate Entitlements.

Roles - Added new subcategory under ¶¶ÒõPoint of Sale (POS) group, Ordering.

¶¶ÒõPortal → User Management → Roles → Selected Role → POS → Ordering → Entitlement

Admin Roles - Available for the following Roles:

Added Entitlements as a product option to associate them with loyalty to use in an order for redemption.

Added the ability to deactivate Entitlement products sold, deleted, or when an order is void, suspended, or refunded.

Toggle Yes to allow bypass of the Close Drawer popup.

Toggle No to NOT allow bypass of the Close Drawer popup.

Added Allergens tab to Product List editor. Allergens Information is used to set the possible allergens for products/modifiers at a site. The options include: Contains, May Contain, and Does Not Contain.

For more details, see Product List - Allergens.

Added ability to add and change a icon when creating and editing an allergen.

¶¶ÒõCloud Porta → 4-Dot Menu → Data Management → Ordering Settings → ¶¶Òõ → Allergens → Allergen Configuration

To configure an allergen icon:

To set a allergen icon:

product.View

products.View

standard-product.View

retail-item.View

modifier.View

Improved the logic when duplicating an order to update the duplicated order when the menu has also been updated.

Order List columns can now be fixed.

Increased the maximum order item quantity limit 99 to 999.

Questions are NOT fetched for the orders that can not be edited.

Improved logic to subtract change from the payment total for orders that have change.

Improved SS change cart API to reduce the query and return of information and provide a more stable return response data structure.

Improved the MenuEngine logic to include requests with the parameter include_item to reduce duplicated requests.

Improved the reporting data logic.

Enhanced SCP configuration to replicate the SS configuration in order to enhance user experience.

Improved the logic for ¶¶ÒõCloud Portal notifications when receiving event orders.

The Audit Trail now tracks ¶¶ÒõSuite Catering (XCAT).

Rolled back card on file deletion in order to investigate and product a better solution.

Enhanced the Suite Order Summary Report with the following:

Migrated historical data to accommodate ETL process improvements.

A new Injected Order Options section—located below the General area

Moved the Combine Like Items for Injected Order option to the Injected Order Options section

Added a new option to Enforce Order Check-in on Commit—when enabled injected orders are automatically checked-in upon the commit of the order

Added the filters to Orders and Archived tabs on the Order History page:

Added Welcome splash screen when opening the app.

Selecting Manage My Account navigates to My Account instead of Contact Details.

Selecting Review on the Review Order page shows the Product popup.

Expanded Order Details in order and invoice lists are always in view.

Added the following permissions:

• Export.Roles.View - Allows the user to view and download the list of .csv files that contain roles and permissions.

• Export.Roles.Manage - Allows the user to view, download, and edit the list of .csv files that contain roles and permissions.

Users can set any permissions to a newly created role and successfully save a role.

Added setting Display Ordered Quantity on Menu Buttons to the Company and Site preferences.

¶¶ÒõCloud Portal → 4-Dot Menu → Data Management → Ordering Settings → Settings → Preferences → Company/Site Preferences → Ordering Application → Ordering

Added override setting Display Ordered Quantity on Menu Buttons to the Terminal Scheme preferences.

¶¶ÒõCloud Portal → 4-Dot Menu → Data Management → Ordering Settings → Hardware → Terminal Scheme → Order Entry → Terminal Scheme Configuration

Enables Biometric Authentication for ¶¶ÒõPoint of Sale (XPOS)

Edit the Consent Prompt

Set the number of stored fingers

Enhanced and updated Access Control List.

Improved API logic to prevent logs of incoming access_tokens and passwords.

Modifier Builds

Tags

Subtract Price on Modifier Replacement - When this setting is enabled, the price of the modifier is subtracted from the modifier build price when it is replaced with a variant.

Add to Parent When Assigned to a Modifier Build - When this setting is enabled for a tag, and the tag is added to a modifier build, then the tag is automatically added to the parent item (modifier) for child-item pricing rule evaluation when the modifier build is applied to a product.

Calculate the price of an item based on the applied product tags from the Order Object. This allows for tag-based, child-item pricing rules that are defined for modifiers and their variants to be applied to the parent item.

Optionally update the modifier build price when a build modifier is replaced with one of its variants.

Added Validation Format to ¶¶ÒõData Management. Use this feature to view, add, edit, and delete formats.

To add a Validation Format:

1. From the upper-right of the Validation Formats homepage, select New Validation Format to add a validation format.

2. From the Description page of the Validation Formats editor, define the following:

   Setting	Description
   Format Name	Type a name for the validation format.
   Entity	From the dropdown, select the entity to assign to the validation format.
   Priority	Type the numeric priority to assign to the validation format in relation to other validation formats.
   Active	Toggle the Active status of the validation format for each site.

3. From the Scan Format page of the Validation Formats editor:

   • Define the format of the scanned entity, including the character type, and character count.

   • Define the conditions that the entity string must meet.

4. From the Scan Format section, define the format of the scanned entity:

   Setting	Description
   Character Types	From the dropdown, select the type of characters to include in the string.
   Minimum Character Count	Type the minimum number of characters that are required.
   Maximum Character Count	Type the minimum number of characters that are allowed.

5. From the Contains section, define the conditions that the entity string must meet:

   • From the upper-right of the Contains section, select Add Condition.

   • From the Create Condition window, define the following:

     Setting	Description
     String Position	From the dropdown, select the position where the string is located in the scanned entity. For example, select Starts With if the string is located at the beginning of the scanned entity.
     String Value	Type the string value. The eligible characters are dependent on the Character Type selected in the section above.

6. From the Parsing Rules page of the Validation Formats editor, add rules that determine how the scanned entity is parsed. A parsing rule instructs the application how to read and interpret the values in the scanned entity.

   To add a parsing rule:

   • From the upper-right of the Parsing Rules page, select Add Parsing Rule.

   • In the Rule Name field, type the name of the parsing rule.

   • From the Parameters section, select Add Parameter.

   • From the Add Parameter window, use the provided fields to define the function, position, value, and/or length of the string included in the scanned entity.

     The provided fields are determined by the selected string position. Some fields described below may not be available.

     Field	Description
     Use As	From the dropdown, select the function of the string.
     String Position	From the dropdown, select the location in the scanned entity where the string is located.
     Value	Type the specific string value.
     Length	Type the number of characters that make up the string.
     Start Character	Type the first character in the string.
     Start Character Position	Type the position value of the first character in the string. For example, if the first character in the string occupies the third position in the scanned entity, then type 3.
     End Character	Type the last character in the string.
     End Character Position	Type the position value of the last character in the string. For example, if the last character in the string occupies the ninth position in the scanned entity, then type 9.

   • From the lower-right of the Add Parameter window, select Save.

7. From the Actions page of the Validation Formats editor:

   • Identify the screen(s) where the user at the POS is allowed to scan the barcode.

   • Identify the action to execute at the POS when the barcode is scanned.

8. To add a POS action and associated screen:

   • From the upper-right of the Actions page, select Add Action.

   • From the Add Action window, define the following:

     Setting	Description
     Action Name	Type a name for the action.
     Screen	From the dropdown, select the screen where the user at the POS is allowed to scan the barcode.
     Action	From the dropdown, select the action to execute at the POS when the barcode is scanned.

9. From the lower-right of the Add Action window, select Save.

10. From the upper-right of the New Validation FormatÌý´Ú´Ç°ù³¾.

To delete a Validation Format:

To edit a Validation Format:

Added the following permissions to allow a user to view, add, edit, and delete validation formats: