March 19th, 2025 Release Note: RME: Ingredient Audit History Extended, Recipe CO2 Ranking in API, Copy Ingredient Without Nutrition, Data Caching, Ingredient Costs in 'Menus 3' Report

Summary

Select the release feature from the table below to be taken directly to that section of the release note. 

 Great Idea! One of these features was originally raised as an Idea in our Customer Community. The suggestion helped our teams to design and release an enhancement which is now available to everyone.

Look for the  symbol to see which feature started life as an Idea!
Why not share your inspirational ideas (or vote on someone else’s) today!

Release date for all features:  March 19th 2025

Ingredient Audit History Extended

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

What's Changing?

When an ingredient's pending cost price becomes the current cost price, the ingredient audit history will now show an entry. Previously, this cost price change was captured only in the 'price history' audit.

Reason for the Change

Increases ease of use by including this audit value in the general audit, reducing the need to check the 'price history' audit separately.

Customers Affected

All customers.

Release Note Info/Steps

The example ingredient audit history pop-up below shows 'Cost Price' as the 'Modified' field, with the automated-system administrator indicated as the user who implemented the change.

Fig. 1 - Ingredient audit history - 'Cost Price' modified by 'OA ADMIN'

Manually Populated CO2 Ranking in API Response

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

What's Changing?

A recipe's manually populated 'CO2 Ranking' value (located on the Recipe Details tab) will be returned in the API response for the GET /recipes request. Previously the manually populated value from this field was not available in the API response.  

Reason for the Change

Increases ease of access for recipe CO2 data via the APIs.

Customers Affected

All customers using the manually populated field 'CO2 Ranking' on the Recipe Details tab and using the GET /recipes request.

Release Note Info/Steps

The manually populated recipe value CO2 Ranking will be returned in the API response for the GET /recipes request.  

Fig. 2 - CO2 Ranking value as represented in the API response to GET /recipes

Fig. 3 - Recipe CO2 Ranking Field on the Recipe Details tab

Copy Ingredient Without Nutrition

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

What's Changing?

Functionality has been added to copy a parent ingredient without nutrition, intolerance and ingredient list values.

Reason for the Change

Allows more users to copy ingredients without copying values that should be added by nutrition specialists.

Customers Affected

Available to all customers.

Release Note Info/Steps

This functionality is controlled by a new ingredient permission - Allow Copy Without Nutrition.

• Please contact Fourth's Support team to request that this new permission be made available for your organisation
• Once the permission is enabled for your organisation, a system administrator can enable it for user groups

Fig. 4 - Copy Without Nutrition permission displays in the list of ingredient permissions

Once the permission has been enabled, a new Copy Without Nutrition button will be visible on the ingredient toolbar.

Fig. 5 - Copy Without Nutrition button displays on the ingredient toolbar

Fig. 6 - Example - The original ingredient has populated values for Nutritional Values

Fig. 7 - The copied ingredient will have blank fields for Nutritional Values, Intolerance Data and Ingredient List

Alternate ingredients will not be copied when Copy Without Nutrition is used to copy a parent ingredient.

Data Caching to Improve Performance: User-Defined Units Could be Delayed in Appearing in UI

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

What's Changing?

Data caching has been implemented for some lists that are changed infrequently. The impact of this caching could be a slight delay between the creation of 'user defined units' and their availability in the ingredient and recipe screens.

Reason for the Change

To improve the page loading time of the RME screens.

Customers Affected

All customers creating new 'user defined units'.

Release Note Info/Steps

When 'user defined units' are created (Admin > User Defined Units), there could be a delay of several minutes before the new units are available in the ingredient and recipe screens.

Sample 'user defined unit' of type 'volume'

Unit Name: Green ladle, 3.5 fl ounces
Unit Abbreviation: GRN LDL
Unit Type: Volume
Equates to: 3.5 Fluid Ounces (UK)

Fig.8 - User Defined Units in the RME 'Admin' tab

Reminder: User defined units are units of measure that are created according to the specific needs of a particular RME organisation. Access to user defined units is often restricted for Inventory customers because any new units of measure must be mapped to Inventory units of measure before use.

Recipe Usage in Menus 3 - Report - Refinement to Sub-Recipe Ingredient Costs

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

What's Changing?

The 'sub-recipe ingredient costs' (column N) in the 'Recipe Usage in Menus 3' report are now scaled to represent the cost of the sub-recipe ingredient quantity that is in the main recipe.  

Reason for the Change

Before this change, the sub-recipe ingredient costs in the report were not scaled and were, instead, representative of the total amount required for the sub-recipe's total yield.  

Customers Affected

All customers.

Release Note Info/Steps

See the previous release note (link below) for details of this report. There are no steps required to implement the refinement to sub-recipe ingredient costs.

January 21st 2025, Release Note (1 of 2): RME: Recipe Videos, 'Recipe Usage in Menus 3' Report Refinement – Fourth & HotSchedules Customer Success Portal