Tell us how we could make the product more useful to you and be kept informed of future updates.
Got some feedback or found a bug?
AI API Key Selection
As we are increasing the areas that use AI, are we able to create a central management area for the API keys then select from a list when adding it to a feature rather than having to type it into each integration: As it is today, if the key was to change we would need to update in multiple different areas rather than a single location.
Allow the OneBot to add values to an array after Create Array Step
Currently when you use the Create Array step you can only use this then in other steps. However sometimes the data you receive from an integration endpoint is not in the correct format to be used in your flow, for example on dropdown lists for Adaptive cards requires the keys âtitleâ and âvalueâ but you currently have âRecIdâ and âSummaryâ there is no way to meet that format standard. If you can add a âAdd Array Itemâ step which allows you to add a json object to the array would allow us to fix the issue above by using a For
Released
Focus the first input field (with active cursor) when opening modal in workflow editor
Modals opened by adding an expression to a tag-control will open without their first field focused and without the text entry cursor present in the text field. This is annoying if you are entering multiple entries into the tag-control. For example, trying to access multiple fields from an object requires the user to have to repeatedly move from the keyboard to the mouse and back again, disrupting their progress. The tab/enter combo provided for the tag-control (which is great, by the way) is made much less helpful as using it is immediately followed by the need to take your hand off the keyboard to âclick intoâ the text field of the modal window. The ideal UX would be for users to be able to keep their hands on the keyboard throughout working within a tag-control. There would need to be the occasional exception to this, of course. However, where modals use dropdowns or text fields etc., focusing the first field of a modal with the input cursor ready to accept text would be a beneficial experience for users.
Released
Prevent the workflow scroll in background when scrolling a modal
Scrolling a table inside a modal in the workflow editor causes the blurred out workflow in the background to also scroll. This is disorientating for users when working with larger workflows, and fixing it would improve UX. See attached video.
Show key workflow config info in the workflow editor
Show the user key information on workflow while using the editor. Ideally, the current language would be displayed. In addition, if there is no linked assistant this would be evident also.
Released
Add time to error report table view
When hunting a bug, it would help to have a time stamp on the error. Currently, all the records visible in the table view show errors on the same day using the same date, but donât show time. This makes it hard to differentiate when troubleshooting â you get lots of indistinguishable records for the same bug and have to click all of them to find the error you were looking for.
Old bug report UX was better
Can we have the old methodology for reporting bugs? It was easier to use, more intuitive, took less clicking, and critically, it made it super simple for users to take screen-captures. I love the new Featurebase widget and its integration into the tool, but the old workflow for reporting bugs was easier and really a great user experience. It was almost fun to report bugs using the old method. Hard work for the Dev team to have users enthused and slapping down bug reports all the time, but probably a win for the product in the long run? :D
New Adaptive Card Features
Adaptive Cards have added some new features, these work in tool, but the preview in Card Designer does not display the new parts of the card. This is not a major issue as the cards still work as expected in teams.
Add UI semantics to fields displayed by association to separate objects
It will help the user if the UI makes a semantic distinction between fields that are intrinsic to an action, and those that are present due to establishing a connection to a separate object. Examples include: actions that have configuration fields that appear due to their association with an Adaptive Card. fields that appear in the Run Workflow action, derived from its connection to a workflow that has workflow inputs. The action configuration panel could usefully have a section that denotes an area where fields will/may appear due to a relationship. It also allows you to say to the user âhey, you should watch this space â more fields may appearâ or âThe inputs workflows you connect will be hereâ. This will orientate and prime the user to the concept, leading to an improved UX.
Released
Include CC and BCC in Send Email
Currently in the Send Email action you can only populate the To field, there is no way currently to include any emails in the CC or BCC field.
Ability to make inputs multi line text instead of just 1 line
Currently when you add inputs, you can only set 1 line of text. However some times you will need to send multi line text to other workflows for examples a description. It would be great to be able to toggle inputs to make multi line or not.
Parameterisation available as part of user blocks
The ability to define a parameter as part of a user defined block would make user defined blocks more generic, more flexible, and more capable, and should make it easier for partners to create generic solutions for clients.
User defined blocks in custom menu
User defined blocks - would be great if they could: Appear in action menu under âUser defined blocksâ on the left-side action menu panel, joining the core actions and plug-in actions as options; this would allow user defined blocks to be âsearched forâ and added to workflows just like regular blocks. Would âbuildâ userâs sense of ownership of the experience, with the tool filled with the userâs own content. Allow custom icon upload The ability to import/export blocks as JSON would also be great.
Released
Information from Webchat
Can we get any additional information from the webchat component such as IP Address, we are unable to access where the request came from due to the anonymous access so when a user is asking questions we have no way to identify the location or user.
Remove requirement for prefix for trusted domains in Web Chat Client config
Remove the requirement for trusted domains to include a protocol prefix when included as a trusted domain for a web chat client configuration. Examples of current requirement for trusted domains https://obie.onebot.co.uk https://*.trysaasiteu.com Examples of preferred requirement for trusted domains obie.onebot.co.uk *.trysaasiteu.com
Released
Message Notification
Could we have sound notification when someone replies on the handoff in the browser.
Released
Email Support for Modern Auth
Can we have support for Modern Auth on email configuration, most email accounts have moved away from a simple username and password.
Released
WebChat Welcome Card
Can we have an option to add a welcome card to the Webchat similar to what we have in the teams integration.
Business Object Variable
Could we make the Business Object Name in the Neurons integration accept a variable. We could then convert multiple steps from a block into a single flow reducing complexity and making the process more flexible.