August 7th, 2024, Release Note: RME | Recipe Yield Auto-calculation, Nutrition Tab Hidden, POST /ingredients New 'Variable Weighted' Property

Summary

Release date for all features: August 7th 2024*

*Feature 3 delayed until September 4th

Recipe Yield, Raw and Cooked Weight, to Auto-Calculate Before 'Save'

• Enabled by default? - Yes
• Set up by customer admin? - No
• Enable via support ticket? - No
• Affects configuration or data? - No

What's Changing?

For an existing recipe, when Recipe Yield, Raw Weight value 'calculation method' is set to Auto-calculate and Cooked Weight is set to calculate from manual, if any of the recipe ingredient quantities are changed, then the Raw Weight and Cooked Weight values will recalculate automatically before Save is selected.  Before this change, the auto-calculation occurred after Save was selected.

Reason for the Change

To increase ease of use by reducing the need to manually recalculate recipe yield, and auto-calculated values, before selecting Save. Reduction in the frequency of the user warning message 'Cooked Weight mandatory for batch recipes' when recipe ingredients all have sufficient data for Raw Weight and Cooked Weight auto-calculation.

Customers Affected

All customers using the recipe yield, Raw Weight and Cooked Weight 'auto-calculation' settings.

Release Note Info/Steps

• To see the recalculated values, select the Yield tab

There will be a brief screen refresh and the newly calculated values will display.

For new recipes, the recalculate button should be manually selected to populate the Raw Weight and Cooked Weight values before selecting Save.  

For existing recipes, Raw Weight and Cooked Weight will auto-calculate automatically when recipe ingredient quantities change.

Fig.1 - For new recipes, the 'recalculate' link must be selected to populate Raw Weight and Cooked Weight before the recipe is saved.  

The error message below will be displayed if the global setting Cooked weight mandatory for batch recipes is enabled and neither Raw Weight nor Cooked Weight have been populated

Fig.2 - Error message

Additional Resources

Inventory Restaurants: Creating Batches in Master Data

Nutrition Tab to be Fully Hidden

• Enabled by default? - Yes
• Set up by customer admin? - No
• Enable via support ticket? - No
• Affects configuration or data? - No

What's Changing?

When the user group permission View Nutrition and Intolerance information is not enabled, the entire Nutrition tab will be hidden. Before this refinement, the Nutrition tab within recipes remained partially visible when that user group permission was not enabled.

Reason for the Change

To more effectively remove access to nutrition information when the View Nutrition and Intolerance information permission has been disabled.

Customers Affected

All RME customers.

Release Note Info/Steps

When the user group permission View Nutrition and Intolerance information is enabled, the Nutrition tab is visible for Ingredients and Recipes.

Fig.3 - 'View Nutrition and Intolerance information' user group permission

Fig.4 - When permission to 'View Nutrition and Intolerance information' is enabled, the Nutrition tab is displayed

Fig.5 - When permission to 'View Nutrition and Intolerance information' is disabled, the Nutrition tab is hidden

Additional Resources

RME | Nutrition 1 - Overview

POST /ingredients, 'Variable Weighted' Can Be Populated as True 

• Enabled by default? - Yes
• Set up by customer admin? - No
• Enable via support ticket? - No
• Affects configuration or data? - Yes

What's Changing?

POST /ingredients, 'Variable Weighted' can now be populated as 'true'. When an ingredient is created via the import API, the 'Variable Weighted' value will still default to 'false' but with this change, it could also be populated as 'true' if needed.

Reason for the Change

To extend the import API so that 'catch weight' products, also called 'variable weighted' can be created via this method.

Customers Affected

All customers using the request POST /ingredients

Release Note Info/Steps

New property in POST /ingredients payload to allow the creation of 'variable weight' (aka 'catch weight') ingredients.  

Valid values are 'true' or 'false'.

 If 'variable weight' is not included in the payload, it will default to 'false'. This is existing behaviour and will not change.

Global Database (GDB) Settings

• If the GDB setting Apply UoM restriction when Variable Weighted Equals True is enabled, when an ingredient's value of 'variable weighted = 'true', the 'unit size UoM' is no longer dependent upon the base supply quantity UoM. Instead, the 'unit size UoM' is dependent on the 'invoice UoM'
• If the GDB setting Variable weighted read-only for live ings is enabled, the 'variable weighted' value cannot be changed once an ingredient is created and saved in a live ingredient set

[
  {
    "supplierName": "Dairy",
    "supplierCode": "B365",
    "starChefKey": "0030702",
    "ingredientName": "Orange",
    "internalCode": "1007",
    "supplyQuantityNumber": "150",
    "supplyQuantity": "12",
    "supplyQuantityUnit": "milliliter",
    "costPrice": "20.16",
    "distributorName": "Dairy",
    "distributorCode": "B3652",
    "externalCode": "ANB2321",
    "supplyQuantityDescriptor": "Case",
    "zeroStockCount": "True",
    "firstDelivery": "2019-10-18",
    "maxOrderQuantity": "1232",
    "minOrderQuantity": "222",
    "invoiceUom": "KGM",
    "invoicePrice": "12.5",
    "consignmentLocation": "Any Text",
    "routeToMarket": "Any Text",
    "ingredientDepots": {
      "depots": [
        "Depot1",
        "Depot2",
        "Depot3"
      ]
    },
    "isConsignment": "true",
    "supplierOrderUom": "KGM",
    "transferRequisitionStatus": "True",
    "itemVatable": "Yes",
    "ingredientGuid": "5FD5ED46-C254-4002-9EF4-6513C623CD0D",
    "ingredientSets": {
      "set": [
        "drink",
        "food",
        "Cafe Metros",
        "menu development"
      ]
    },
    "ingredientType": "Food",
    "unitSizeNumber": "2.5",
    "unitSizeUom": "Litre",
    "unitSizeUomDescriptor": "Bottle",
    "costModel": "Highest",
    "isAdjustmentItem": "False",
    "preventUsageInRecipes": "False",
    "parentIngredientProductName": "Fresh Orange",
    "excludeFromGP": "False",
    "binNumber": "1234AABC23",
    "alternativeUnit1Quantity": "12",
    "alternativeUnit1Uom": "LITRE",
    "alternativeUnit1Descriptor": "Case",
    "alternativeUnit2Quantity": "2222",
    "alternativeUnit2Uom": "KILOGRAM",
    "alternativeUnit2Descriptor": "Case",
    "wastage": "22.56",
    "orderType": "SOA",
    "flagType": "3",
    "flagExpiryDate": "2019-10-20",
    "ingredientShortName": "Orange",
    "variableWeighted": true

Fig.6 - New property 'variableWeighted' is available for POST /ingredients

New Terms/Acronyms 

Reminder: 'Variable Weighted' and 'Catch Weight' both refer to products that are purchased and invoiced in different 'units of measure'.  For example, a 'leg of lamb' might be purchased as '1 each' but be invoiced by the 'kilogram'.

Additional Resources

Inventory Restaurants: Setting Up Catch Weight Products in Recipe and Menu Engineering