This release helps you set up connections more precisely and understand faster what happened.
You get more control over which data is included. You also see more clearly whether a process succeeded, partly succeeded, or really stopped because of an error.
Do you use the BrynQ API to read or change filters for templates or connections? The structure has changed.
Filters are now stored separately for Source and Target. Update API connections that still expect one shared filter list.
In BrynQ itself, this prevents filters for the source app and target app from overwriting each other.
The data filters tab gives you more choice and a clearer view.
You can now filter Source and Target separately. Each tab shows the related app and the number of rules set. This helps you see faster where a filter is active.
With Date Window, you decide which period is included. Current is selected by default. You can also choose Past or Future and enter the number of months. Past is available for Premium and Enterprise. If you see a lock, BrynQ explains why the option is not available.
You can now also choose configuration questions and free fields in filters. These work in the same way as regular app fields. Existing filters keep working.
The logs page now makes a clearer distinction between warnings and real failures.
A process that finishes with non-critical errors or warnings is now called Partial Success and is orange. A process that really stopped because of a critical error is called Failed and is red.
You can now find warnings separately in log levels, filters, and counts for the last 24 hours. This helps you see faster whether action is needed.
We also prevented the logs page from reaching the request limit too quickly when you click through several processes. This makes logs more reliable to view during testing or demos.
On the page where you set permission for Source or Target, a green dot shows which environment is really active. The dot stays visible, even when you open another tab.
If Test uses the Live login details, that setting is now in the Live tab. In the Test tab, buttons to add, change, or re-authorize Test login details are then disabled. Existing Test login details are kept, but they are not used while this setting is on.
BrynQ now handles languages more consistently.
Template administrators can now manage configuration questions in Dutch, English, French, and German. If text is not available in the user’s profile language, BrynQ shows English first and then Dutch.
New users can start in their company’s default language. That default language can be English, Dutch, French, or German. A user’s personal profile language remains leading once it is set.
Messages in BrynQ have a new look. They are calmer, show more clearly whether something succeeded or needs attention, and can include links in the text. Error messages stay visible a little longer. When you hover over a message, automatic closing pauses.
We also tightened a few areas.