RME Release Note: July 2021: Alternate Ingredient Ranking, Approvals Screen, API Updates

Summary

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

Release date for all features: 27th and 28th July 2021

Alternate Ranking, new ways to Move Alternate to Desired Rank

• Enabled by Default? - No - Alternate Ranking is enabled by User Group permission
• Set up by customer Admin? - Yes
• Enable via Support ticket? - No
• Affects configuration or data? - No
• Roles Affected: - Users with permission to update alternate ingredient rank

What's Changing?

Three new ways of updating an alternate ingredient’s rank have been added.

Reason for the Change?

Increase ease of use.

Customers Affected

All customers using alternate ingredients

Release Note Info/Steps

Three new ways of updating an alternate ingredient’s rank have been added.  See Fig 1. below.

a. Input rank via drop-down list
b. Move to top of list
c. Move to bottom of list

Fig.1 - New controls for changing an alternate ingredient's rank

Additional Resources

Alternate Ingredient Rank in Master Data and its Impact on Inventory

Approvals Screen, Improved Styling

• Enabled by Default? - No, Approval Workflow is set up via User Group settings
• Set up by customer Admin? - Yes
• Enable via Support ticket? - No
• Affects configuration or data? - No
• Roles Affected: - Users that belong to User Groups that 'approve' other user groups' changes to ingredients, recipes and menus

What's Changing?

Styling has been improved in the 'Approvals’ screens so that they have the same appearance as the main screens for ingredients, recipes and menus.

Reason for the Change?

Cosmetic improvement.

Customers Affected

All customers using 'approvals'. 

Release Note Info/Steps

The 'Approvals' screens for ingredients, recipes and menus will be changed to look like the main screens for 'ingredients', 'recipes' and 'menus'.  This is a cosmetic change only.

There is no change to the way 'Approvals' workflow is configured for a User Group.

• If a User Group should belong to an 'approvals workflow', this can be defined on the Approval sub-tab of that User Group

Fig.2 - Approvals sub-tab in User Group settings

New Endpoints (POST/GET) for Alternate Ingredient Creation and Update

• Enabled by Default? - No
• Set up by customer Admin? - No
• Enable via Support ticket? - Yes
• Affects configuration or data? - Yes. Affects data import for users who update alternate ingredient data via the import API
• Roles Affected: - Data manager if import APIs are used for ingredient data maintenance

What's Changing?

New POST and GET endpoints have been created for the creation and update of Alternate Ingredients.

Reason for the Change?

Reduce the complexity of the POST /ingredients request

Customers Affected

All customers using the POST /ingredients request to create or update alternate ingredients.

Important note: As of February 1st, 2022, the Alternate Ingredient properties will no longer be supported by the request POST/ ingredients. Users of the POST /ingredients API should change their integrations so that Alternate Ingredients are maintained via the new endpoint.

Release Note Info/Steps

See our dedicated website for 'how to' information about the RME APIs.  Go to developer.fourth.com.

Access and configuration of these new endpoints can be arranged via a request to support@fourth.com.

POST Endpoints, Validation Added to Prevent Update of Ingredients 'In Approval' 

• Enabled by Default? - Yes
• Set up by customer Admin? - No
• Enable via Support ticket? - No
• Affects configuration or data? - Yes. Affects data import for users who update ingredient data via the import API and who use 'approvals' workflow
• Roles Affected: - Data manager if import APIs are used for ingredient data maintenance

What's Changing?

Validation has been added so that ingredients that are in approval workflow cannot be changed using the POST requests.

Reason for the Change?

Increase predictability:  Align validation on the user interface and the POST requests.

Customers Affected

All customers using the POST requests to update ingredients.

Release Note Info/Steps

If an ingredient is in approval workflow and is included in POST payload, an error will be generated.

Requests impacted by this change:

• post /ingredients
• post /ingredientintolerance
• post /ingredientcategory
• post /ingredientnutrient
• post /ingredientpriceband
• post /ingredientconversion

For details, see our dedicated website for 'how to' information about the RME APIs. Go to developer.fourth.com.

Access and configuration of these POST endpoints can be arranged via a request to support@fourth.com.