This release makes it easier to start a new interface, work together on scenarios, and understand what happened when something gets stuck.

You get safer fixed choices in places where an accidental change could cause problems. You also see more context in logs and error messages, so you and support have less to search for.

Featured

Creating a new interface with more guidance

When you create a new interface, BrynQ now guides you step by step while you choose source and target apps. You see which templates match your choice. You can view details before continuing, such as the description, scenarios, and a preview of the target fields.

You can also continue more easily when an app is not active yet. In the app picker, you see active and inactive apps. You can select an active app right away. For an inactive app, BrynQ asks for confirmation first, because activation may affect your monthly licence.

Search in the app picker now works again in the template flow. You can type an app name and the list is filtered immediately.

Comments on scenario rows

You can now use comments per scenario row. This helps when you review a template or interface together.

With edit rights and the right plan, you can open a side panel for a scenario row. There you can add comments, reply, mention someone with @, and mark a conversation as resolved.

BrynQ shows whether there are unread comments. If someone mentions you in a new or edited comment, you receive an email with the latest text and a direct link.

Fixed app versions for stable fields

Templates and custom interfaces now store which published app version they use. This means existing fields and choices do not change silently when a new app version is published later.

For templates and custom interfaces, you can choose the version in a dropdown. If a newer version exists, you see a subtle exclamation mark. For interfaces created from a template, the linked template determines the version. You can see this in BrynQ, but you cannot change it there.

BrynQ now uses the same published app version for fields and categories in the library, scenarios, filters, templates, and API responses. This keeps choices consistent across different places.

More protection for templates

Admins can now make a scenario required in a template. When that scenario is used in an interface, a user cannot turn it off. This keeps necessary parts active.

For interfaces created from a template, the target scheme stays locked. This is the choice that determines which target fields belong to the scenario. This prevents you from accidentally clearing fields that you cannot restore yourself.

In partner templates, value conversion is only available where it fits. For configuration questions without multiple fixed choices, you can no longer enter value conversion that incorrectly makes the scenario invalid.

Clearer administration and support

We have clarified several places where you need to find out what happened.

• You now see in the audit log when an interface was disabled or enabled again, by whom, and at what time.
• The Customer and Created by filters in Audit logs now show real customers and users again instead of only Undefined.
• When assigning interfaces to users and roles, you now also see the ID under the name. This helps when several interfaces have almost the same name.
• Log lines from a processing event with the same second are now shown in the correct order. The newest message is at the top.
• General error messages now show an error reference when one is available. You can copy the request ID and share it with support.
• Errors in the authorization history now show a readable message instead of technical JSON. Technical details remain available for support.