Release Note: Recipe and Menu Engineering: November 2020

What’s Changing?

• Menu course GUID added
• New DELETE API: Allow deletion of alternate ingredients
• Full Ingredient List (FIR) fields and report to support Food Information (Amendment) (England) Regulations 2019
• FIR Ingredient Intolerance Update Template to support 'may' values
• Performance improvement for recipe recalculation

Release date: 17th and 18th November 2020

Reason for the Change

General system enhancements.

Customers Affected

Menu Course GUID and new DELETE API: Non-breaking changes.  Impacts all RME customers using the related API functionality.
Full Ingredient List (FIR) fields and report:  Will be disabled by default. Can be enabled by submitting a request via the Customer Community
FIR Ingredient Intolerance Update Template to support 'may' values: All RME customers using the related functionality
Recipe calculation performance improvements:  All RME customers.

Release Notes

Menu Course GUID

• • A menu course GUID has been created and will be returned in two API responses
  • This GUID is a unique, unchanging identifier
  • The Menu Course GUID property will be available in the responses from these endpoints:
    • GET /menus/{guid}
    • GET /menus

Fig.1 – Menu Course GUID in GET /menus API

DELETE API: Allow delete of alternate ingredients

A new endpoint for 'delete' of alternate ingredients has been created

• • Ingredient identifier: StarChef key or Supplier Name and Supplier Code combination
  • Validation: An alternate ingredient cannot be deleted if used in recipes
  • After deletion, impacted alternate ingredients will be reordered to close the gap between existing alternates and gaps left due to deletion
  • Parent ingredients cannot be deleted via this method
  • Please note: Details regarding the delete request URL will be provided when development has been completed in mid-November

Full Ingredient List (FIR) Fields and Report to support compliance with Food Information (Amendment) (England) Regulations 2019 (aka, Natasha’s Law)

New ingredient and recipe fields have been created to store ‘Full Ingredient List (FIR)’ information to support customer compliance with Food Information (Amendment) (England) Regulations 2019 (aka, Natasha’s Law).

• The ingredient field, once enabled, can be located in the ingredient’s Nutrition tab, on a new tab called Ingredients List

Fig.2 - New Ingredients List within an ingredient's Nutrition tab

• The recipe field, once enabled, can be located in a Recipe’s Nutrition tab, on a new tab also called Ingredient List

Fig.3 - Recipe field with 'Manual’ Field designated for use in Recipe Report

• Permission to view and edit these fields will be controlled by separate user group permissions
• Recipe ‘Full Ingredient List (FIR)’ information will be auto-compiled in the new recipe field from the recipe ingredient information. A manually populated field is also available - see Fig.3
• In the auto-compiled version of the recipe ‘Full Ingredient List (FIR)’ text, recipe ingredients will be ordered by ‘recipe ingredient weight within the recipe’, from highest to lowest
• Due to the above, ingredient weight values will be required for the recipe information to be auto-compiled
• If all recipe ingredients do not have a weight UoM/conversion, the auto-compiled field will not display the recipe’s ‘Full Ingredient List (FIR)’ information. Instead, a message will display:  Unable to compile list: missing ingredient weight(s)
• A new recipe report called Food Information (Amendment) (England) Regulations 2019 has been created. This report will source information from either the auto-compiled or the manually populated new recipe field. Users can select the source field by selecting the radio button under the field as shown in Fig.3
• The report is formatted to suit an A4 sheet of 4 x 4 labels with one recipe’s ‘Full Ingredient List (FIR)’ information printed per label
• This functionality will be disabled by default. It can be enabled by submitting a request via the Fourth Customer Community. See Fourth Processes - Raising and Managing Support Tickets for guidance. When disabled, neither the new fields nor the new permissions will be visible and the background task that auto-compiles the recipe information will not run.

Fig.4 - FIR user group permissions

Please note: There is additional functionality planned to support the new requirements for future releases such as audit history for the new fields and new import and export APIs. Please see upcoming release notes.

FIR Ingredient Intolerance Update Template to support 'May' values

• 'May' can be uploaded successfully using the template
• Valid 'may' values for the upload template are: may, M
• 'May' values will be accurately displayed on the template when it is generated as a report from Reports > FIR Ingredient Intolerance Upload Template