March 22nd 2023, Release Notes | RME | Single-Ingredient Recipes, New Report. GET Nutrition, More Precision in API Responses

Summary

“Great Idea! Two of these features were originally raised as Ideas in our Customer Community. The suggestions helped our teams to design and release enhancements which are 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!

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

Release date for all features: March 22nd 2023

Single Ingredient Recipe Creation

• Enabled by Default? - No
• Set up by customer Admin? - Yes
• Enable via Support ticket? - No
• Affects configuration or data? - No
• Roles Affected: - Recipe creators of drinks and retail products

What's Changing?

It is now possible to create a 'single ingredient recipe' without leaving the main Ingredient screen. The new recipe is a 'standard' recipe with all the related functionality available to standard recipes.

Reason for the Change

Increase ease of use, particularly for recipe creators of 'Drinks' and 'Retail Product' recipes.

Customers Affected

Optional.  Available to all customers.

Release Note Info/Steps

There are four permissions that control the single-ingredient recipe functionality.

1. Enable the new button

• Access to the new functionality is controlled by a new user group permission - Create single-ingredient recipe - located in the 'Recipe Permissions' section
• The existing Create public permission must also be enabled

The new permission will be available but 'disabled' by default in existing user groups.

Fig.1 - New 'Create single-ingredient recipe' permission

  Once enabled, a new Create Recipe button will appear in the ingredient 'action button' row.

fig.2 - New 'Create Recipe' button in ingredient action button row

2. Ensure visibility of recipe pricing information

• To see the recipe selling price fields in the new 'create recipe' window, the recipe permission View pricing information must be enabled

Fig.3 - Recipe permission 'View pricing information' is required to see recipe selling price fields

3. Control which recipe selling price field is displayed in the new 'create recipe' window (two possible permissions/two possible selling price fields)

• To display 'Target Sell Price (inc.)' which corresponds to 'Target Sell Price calculator, Sell Price (inc)' on the recipe record, enable the recipe permission Allow save target sell price.

Fig.4 - Recipe permission 'Allow save target sell price' is required to see recipe selling price field Target Sell price (inc.)

Fig.5 -Target Sell Price (inc.) field in 'Create Single Ingredient Recipe' window (left image) corresponds to 'Target Sell Price Calculator, Sell Price ('inc.) in main recipe record (right image)

• To display 'Sell Price (inc.)' which corresponds to 'Default FnB Site Sell Price, Sell Price (inc.), enable the recipe permission Allow suggested sell price

Fig.6 - Recipe permission 'Allow suggested sell price' is required to see recipe selling price field Sell price (inc.)

Fig.7 -Sell Price (inc.) field in 'Create Single Ingredient Recipe' window (left image) corresponds to 'Default FnB Site Sell Price, Sell Price ('inc.) in main recipe record (right image)

To display both fields, enable both permissions.

Create the Recipe

• From within the desired ingredient, select Create Recipe
• In the new window that opens, add recipe values as required - mandatory values are marked with an asterisk *
  
  • Name *
  • Description
  • Menu Description
  • Short Name - possibly mandatory, depends on global settings
  • UoM * - this is the recipe ingredient UoM for the new recipe, e.g. ML (millilitres)
  • Quantity * - this is the recipe ingredient quantity for the new recipe, e.g. 175
  • Target Sell price (inc.) - corresponds to 'Target Sell Price Calculator, Sell price (inc.)
  • Sell price (inc.) - corresponds to 'Default FnB Site Sell Price, Sell price (inc.)

Permissions, described above, will determine which 'Sell Price' value will be displayed and populated when the recipe is saved.  

• • Suggested PLU - if the global setting has been enabled, validation will be applied to the PLU to prevent duplication
  • Category Type - the categories available here in the drop-down list are existing recipe categories.  If the global setting has been enabled, a 'SMART' category will be mandatory
  • Category - the values available in this drop-down list are main and sub categories that are associated to the selected Category Type

Other global settings that, if enabled, will impact the 'single-ingredient' recipe's values

• Set Standard Recipe Portion Size to 1 each
• Recipe ingredient wastage set by default

Fig.9 - New recipe creation window has only three mandatory fields for recipe creation

New Recipe Report: Recipe Menu Description and Kcal per Serving

• Enabled by Default? - No
• Set up by customer Admin? - No
• Enable via Support ticket? - Yes
• Affects configuration or data? - No
• Roles Affected: - TBC

What's Changing?

A new recipe report is available. Values on the report include recipe 'menu description', kilocalories 'per serving', recipe portion size and 'suitable for' values (vegan, vegetarian, coeliac).

Reason for the Change

From an 'Idea' raised on the Fourth Community. To increase ease of use for users responsible for point of sale setup that uses limited recipe values.  

Customers Affected

Available to all customers.  Optional.

Release Note Info/Steps

To have access to this report, please raise a request with Fourth's Support team.

This tabular report includes the following recipe values:

Product Key, Name, Menu Description, Kcal Value Per Serving, Portion Size (Cooked Weight / # Servings).

Also included are these 'Suitable for' values:  Vegans, Vegetarians, Coeliacs.

API Changes

Precision extended in two 'nutrition-related' API responses to more places after the decimal point

• Enabled by Default? - Yes
• Set up by customer Admin? - No
• Enable via Support ticket? - No
• Affects configuration or data? - Yes
• Roles Affected: - if applicable

What's Changing?

GET /ingredients/{guid}/nutrition

GET /Recipes/{guid}/nutrition

In API responses for the above requests, the precision of the response for all nutrient values has been extended from three digits after the decimal point to six digits. If there are meaningful digits (i.e., values greater than zero) after the decimal point, these values will be included in the response. For example. 0.50000 will still be displayed as 0.5 but 0.000200 will be displayed as 0.0002.

Reason for the Change

Nutrient values in RME API responses are always specified in 'grams'.  Before this change to extend the API response beyond the usual three decimal places, it was not possible to report on the presence of nutrients that were present in tiny amounts.  This change will mainly impact sodium which is often displayed in milligrams on the RME Recipe and Ingredient Nutrition screens but returned in the API as a 'gram' value.

Customers Affected

All customers using the requests mentioned above

Release Note Info/Steps

There are no steps required by users to implement this change.

Additional Resources

See developer.fourth.com for detailed integration guidance.