November 23rd 2021, Release Note: RME: API GET/ingredientsalternates: Additional Properties Added, Approval Notes with Audit Information 

Summary

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

API GET/ingredientsalternates: Additional Properties Added

• Enabled by Default? - Yes: New properties available by default / No:  access to the API must be provided by Fourth, per customer request
• Set up by customer Admin? - No
• Enable via Support ticket? - Yes/No (see details above)
• Affects configuration or data? - Yes
• Roles Affected: - API users/integrations that use the response from GET/ingredientsalternates

What's Changing?

Additional properties have been added to the response for the new GET request: GET/ingredientsalternates.

Reason for the Change

Additional information was requested by Fourth Connect to facilitate payload preparation for POST/ingredientsalternates and other POST requests.

Customers Affected

API users/integrations that use the request GET/ingredientsalternates.

Release Note Info/Steps

These properties have been added

• Parent_Ingredient_GUID (to help link to the Export APIs reporting Parent Allergen data)
• Parent_Ingredient_Name (to help the customer relate the alternate ingredient to the Parent Ingredient)
• Ingredient_GUID (to allow linking to data provided in the GET /recipes response)
• Ingredient Sets

Sample response (partial):

[
  {
    "ParentIngredientGUID": "33f996a6-c338-4258-8dec-b1814709d2a6",
    "ParentIngredientProductName": "! a food nonT",
    "IngredientGuid": "e9ad7f40-15a3-461f-8b03-b91950e5eacd",
    "IngredientSets": {
      "Set": [
        "Set 1"
    ]
  },
    "ParentSupplierName": "Alcohol Supplier1",
    "ParentSupplierCode": "qwqw",
    "ParentStarChefKey": "14842",
    "RankOrder": "1",
    "IngredientName": "Copy of ! a food non",
    "InternalCode": "",
    "SupplyQuantityNumber": "1.0000",
    "SupplyQuantity": "1.0000",
    "SupplyQuantityUnit": "bottle",

... 

Please note: Rest of response truncated.  See developer.fourth.com for full response.

Approval Notes with Audit Information

• Enabled by Default? - Yes
• Set up by customer Admin? - No
• Enable via Support ticket? - No
• Affects configuration or data? - No
• Roles Affected: - Users in 'approving' user groups

What's Changing?

Approval Notes will now store and display an audit history. Audit history fields will be:  'Username', 'User group', 'Date', and 'Text' - see FIg.1.

Reason for the Change?

To increase efficiency in the Approvals process. Facilitation of easier communication between an 'approver' if more information is needed to finalise an item's approval.

Customers Affected

All customers using Approvals workflow.

Release Note Info/Steps

Approval Notes are available to all users in an Approvals workflow. When items are created or edited and saved, the Approvals Notes field is displayed in the 'Save' confirmation pop-up. Once saved by a user, an Approval Note cannot be amended by a different user.

Fig.1 - New audit history for Approvals Notes