June 22nd 2021, Release Note: RME: Change of Ingredient Field Name, Improved Ingredient List Report, API Changes

Summary

Release date for all features: 22nd June 2021 for USA, 23rd June for EMEA/APAC

Change of Ingredient Field Name

• Enabled by Default? - Yes for Inventory customers. For non-Inventory customers, the field might not be enabled
• Set up by customer Admin? - Yes. Can be made visible/invisible per user group by customer Admin users
• Enable via Support ticket? - Possibly, if the field has not already been enabled for an organisation
• Affects configuration or data? - No
• Roles Affected: - Anyone using the field. Most likely will be the Purchasing Department

What's Changing?

An ingredient field name has been changed.
'Date 1st delivery to warehouse' has been changed to 'Date First Available for Order'.

For parent ingredients, this field is located on the Ingredient > Internal Spec tab.
For Alternate Ingredients, see the Alternates > Details tab.

Reason for the Change?

More easily understood field name.

Customers Affected

All customers using this field.  Likely to impact all Inventory customers.

Release Note Info/Steps

Fig.1 - Parent ingredient, renamed field

Fig.2 - Alternate ingredient with renamed field, located above 'Supply Quantity' field

Ingredient List Report (for Ingredients)

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

What's Changing?

The blank row that sometimes appears between ingredients in the 'Food Information (Amendment) (England) Regulations 2019 Ingredient Data' report should no longer occur.

Reason for the Change?

Easier filtering of this report in Excel format.

Customers Affected

All customers using this report.

Release Note Info/Steps

Once the report has been enabled for an organisation, it can be accessed via the RME reports tab.

Fig 3 - RME Reports Tab

Additional Resources

RME Release Note: April 2021: Natasha's Law

API Changes

• Enabled by Default? - No
• Set up by customer Admin? - No
• Enable via Support ticket? - Yes
• Affects configuration or data? - Yes
• Roles Affected: - Integration partner who manages data via API

What's Changing?

1. GET /ingredientlist

Supplier Name and Supplier Code properties have been added to the response for this endpoint.

2. Recipe Import API > POST /recipeprepsteps
Validation has been added so an error is generated if recipe types 'Choice Recipe' or 'Option Recipe' are in the payload. This is because Choice and Option recipes do not have preparation steps.
Error message: Choice or Option recipe is not a valid recipe type for this endpoint.

Reason for the Change?

Reduced friction/increased ease of use.

Customers Affected

All customers using the particular endpoints.

Recipe Nutrition Recalculation - advance notification

Following the recent deployment and in line with our new policy of automatic post-deployment recalculation, recipe nutrition will be recalculated during the week of 28 June.