If a customer has the following Mapping Rules defined in their API Integration Settings:
And distinct Metrics associated to each one.
It will result in both metrics being incremented, since it's currently not possible to isolate the String 'search' from a call which could be considered a valid id (e.g. 12345).
On that scenario, it would be useful a flag which, once toggled or checked, would stop processing the remaining Mapping Rules and incrementing their metrics after the first one is met.
In summary, it would be a "stop processing other Mapping Rules" configurable policy through the UI.
|Add ability to order mapping rules in the UI||Closed||Unassigned|
|Add option to indicate if the matched mapping rule is the last one to be processed||Closed||Unassigned|