What's new in Rossum

We are happy to announce some exciting news for Data Matching! 🎉

Effective on Tuesday, June 21 at 6 pm CEST, we are adding 2 new features that are both adding up to the out-of-the-box line items matching story at no extra cost:

1. Add conditions to matching (API only)
2. Matching based on the previous match

The release to production will happen next week on Tuesday, June 21 between 5 and 6 PM CEST.

🚨 Due to the release, there will be a short maintenance window when Data Matching will not be responsive for about 20 minutes. We apologize for any inconvenience.

Add conditions to matching (API only)

• E.g. the item matches if “description” AND “price” match OR “item code” AND “price” match
• Reason to implement: Enabler for various matching needs without programming
• Documentation: API documentation (endpoint “match/logic”, attribute “matching_flow”)

Matching based on the previous match

• E.g. based on previously matched vendor ID (matching against a list of vendors) find a matching PO number from that vendor (matching against PO table)
• Reason to implement: Enabler for various matching needs without programming

On top of these, there are some additional changes below:

Added:

• Conditional matching (adds optional `id` and `matching_flow` attributes to matching logic)
• Authorization icon to the endpoints where authorization is needed (in API documentation)

Changed:

• Name of new Data Matching hooks now additionally contains [matching_field_id] and [queue_name] for easier identification
• Small description update in the Data Matching UI (we now have a "blue check" instead of "blue +" in adding the rules)
• Deprecated [order] as [/match/logic] parameter in [matching_rules] and also in nested [rules]
• Deprecated [order] in [/helpers/queues] response in [matching_rules] and also in nested [rules]

Note to all the changes:

1. There is no visible change in the UI apart from the fact that you will be able to select any matching field as a Rossum field to be matched against the database
2. There are some changes in the API but if you don’t want to use the new features, you don’t need to change anything and everything will work as before. If you want to make use of the new Conditions in matching (the [matching_flow] attribute), you need to start using [id] instead of [order]. This is described in the API docs.