Today, we are pleased to announce a significant enhancement to our Rules Engine, namely the introduction of a new type of Rule known as a "Branch Rule."

There is now a custom Variable format available to support converting regular fractions to their Unicode equivalent. For example, 1/2 becomes ½.

Calling all search engine gurus or marketers 📣 This is a small improvement: The API will now always return an opengraph property even if you omit the advice property when using Sparse Fieldsets.

Happy Halloween 🎃 We are excited to share the newest feature available in our API: multiple Variables per Input Request!

We added an all-new Advice API response format earlier this year, which enables a host of new development and integration options. As we expanded the testing of the API's new response body, we discovered the examples property could be much better.

We added the isToggleable Variable property in the API last month, and now have added the data-variable-is-toggleable HTML attribute on the Taffrail Var in the API's generated HTML responses.

Our clients often want to associate Advice API requests with a specific user. We've designed Taffrail's infrastructure with privacy at its center. None of the rules used in our Rules Engine need specific user information and, indeed, no Personally Identifiable Information (PII).

It's been a long time coming, but the Taffrail API is out of beta with this version 🎉 Since v0.12.0 we've added dozens of features and major changes, and it is now time.

To support more thorough testing as well as AI model training, we've added an all-new Advice Set decision tree branch generator. This replaces our previous capability, and does not introduce any API changes.

For Boolean Variable types only, we've added a toggleable state indicating the Variable can be connected to a toggle style interface switching between true and false values.