Roadmap
Changelog
Help Centre

Got some feedback or found a bug?

Tell us how we could make the product more useful to you and be kept informed of future updates.

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.

Pete Mawle About 1 month ago

💡 Feature Request

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

Anthony Dew 2 months ago

1

💡 Feature Request

In Progress

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.

Ben Lehmann 3 months ago

💡 Feature Request

In Progress

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.

Ben Lehmann 3 months ago

💡 Feature Request

In Progress

Array elements 'disappear' from array step after confirming desired to edit workflow

Element appear to disappear from arrays if you click the red cross button on the element before entering the workflow edit mode. Steps to repro: Open a workflow Enter edit mode Add an array step Add an element to the array. Publish the workflow Click on the array step to reveal the config panel Click the red cross to delete the element Click ‘Confirm’ on the popup that appears asking for confirmation to edit workflow. Note that the element appears to have been removed from the array. Desired behaviour: Array elements should remain visible if red cross is clicked while not is draft mode Actual behaviour Array elements disappear when red cross is clicked when in draft mode

Ben Lehmann 3 months ago

🐛 Bug Reports

Unclear in Neurons 'Create Business Object' UI how to edit field values

The UI for the Neurons 'Create Business Object' does not show to the user a coherent way to edit existing values. Instead, the user has to ‘Add Fields
’ to get editing view for values of existing fields. Change the wording on the button to ‘Add/Edit Fields
’

Ben Lehmann 6 months ago

đŸ“„ Feedback

Close button on Featurebase widget hides user profile button

The Featurebase widget has a User Profile button in the top right of the slide out panel. This profile button is hidden, however, behind the ‘Close Panel’ button. Makes the product look shabby and makes it difficult for the user to access their user profile. Expected behaviour No UI functionality should overlap. Actual behaviour Two UI functions are overlapping in the UI Steps to reproduce Open the Featurebase widget and look in the top-right corner :D

Ben Lehmann 6 months ago

🐛 Bug Reports

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

Ben Lehmann 6 months ago

💡 Feature Request

New users fail to appear in user's view

Problem Accepting an invitation as a new admin user causes the user record to be removed. When the invitation is sent, user is visible in both the Administrators view and the list of users in the Users view, with the ‘invitation’ badge showing on their record. Once the invitation is accepted, the record is removed from the Users view, instead of updated to show the new badge. Note that the actual User record remains intact in the backend: and the user can still log in with their accepted credentials. Desired outcome Accepting an admin invitation updates badge on user record seen in the Users view. Actual outcome Accepting an admin invitation removes the User record from Users view. Steps to recreate Invite a new admin user. Note the user’s record the Administrators view. Note the user’s record the Users view. Accept the invitation. User’s record disappears from User’s view, but remains in Administrators view.

Ben Lehmann 6 months ago

🐛 Bug Reports

In Progress

Include the term 'presence' in the description of available information.

The term used in Azure is ‘presence’. Can we improve the wording of this description to say something like: “In order to check the user's availability, you will need to authorize the bot so that it can view that information. Authorization for this is provided by configuring 'presence' permissions for your app in your Azure tenant.”

Ben Lehmann 8 months ago

đŸ“„ Feedback

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.

Ben Lehmann 9 months ago

💡 Feature Request