What changed, and when

Rules answer the question of who gets a record. Until now there was no place to answer the question before it: whether the record should go into distribution at all.

The pre-filter sits in the distribution's settings, between the strategy and the price, because that is the order a record travels in. It uses the same condition builder a rule uses, so there is nothing new to learn.

It is also named where people look for it. The rules tab shows it under the strategy with a link to change it, the dry run counts what it held back, and the log gives it as a reason. A filter that silently removes records from a list of rules turns every rule into half an answer.

A rule used to carry a switch called "own price" next to the amount. Which price applied was decided by the switch, not by whether an amount was actually there, so a rule could claim a price it did not have. Distribution then ended with no price and the record went nowhere.

The switch is gone. If the rule states a complete price, that price applies. If it does not, the distribution's price applies. Zero is a price like any other and is treated as one.

The client secret of a webhook login sat in an empty field with the note "Saved. Leave empty to keep it, enter a value to replace it." The note appeared whether or not a secret was stored, so it answered everything except the only question anyone has at that point.

It now follows the pattern the mail login already used: a stored secret shows as set with a button to replace it, and an empty one shows the field. A field that looks like it holds something is the dangerous version, because saving the form overwrites the real secret with nothing.

The switch that stops records going to a partner was labelled as though it stopped the partner. A partner is not active or inactive, it is simply there. What you actually pause is the delivery to that partner inside one distribution.

Everything now says what it does: "Delivery to this partner" on the switch, "Delivery paused" on the card, and a sentence in the routing decision that names the distribution it applies to.

The switch also moved. It used to sit in the rule tab directly under "Rule active" and look identical to it, which put two switches side by side where one affected a single rule and the other every rule for that partner. It now sits in the delivery tab beside the delivery route and the time window, which belong to the same thing.

Fifteen help topics on distribution promised instructions and carried none. They now have them: four to five steps each, in English and German, following the path through the screen rather than the structure of the article.

The help text beside a screen is loaded from the same source the public help center reads, so the two cannot drift apart.

If a field's type changed after records had already been stored under the old one, intake refused every submission that carried the old shape. It refused the entire record, not the one field, so a single mismatched value cost the whole lead.

A type change can now carry a conversion: you say how the old value becomes the new one, and intake applies it. Where no conversion is written down, the field is reported and the rest of the record still arrives.

Anonymising a record used to clear every field and leave only the proof of consent. That is more than the purpose asks for and less safe than it looks.

Fields that do not name anybody are what every report about closed records is built on. Clearing them removes the analysis and keeps the risk. Worse, a record that looks completely empty stops anyone from asking whether what remains is actually anonymous.

Anonymising now works field by field: identifying values go, values that describe the case are coarsened or kept, and each decision is recorded. What was removed stays on file after the data is gone.

The list could be sorted by any column since the beginning. The board could not, and always showed the same default order, which made it useless the moment a column held more than a screenful of cards.

The board now takes the same sort the list takes: created, last changed, or any field you defined, in either direction. Paging inside a column follows the sort rather than fighting it, so scrolling to the bottom of a long column returns what you expect.