Our Roadmap
Follow the development progress of our platform.
Backlog
66Under consideration
Moving Workflow Blocks
When creating a workflow sometimes its necessary to add a case, if you decide this part way through a build you cannot move a section of blocks already configured under this new case. It would be great to have either a drag-and-drop facility (preferred) to move blocks or copy and paste function.
API to User Management
Could we add an API to update the user data, as part of the Offboarding processes in clients ITSM tools. It would be great to be able to revoke the licence of a OneBot User. This would be best served as an API call to allow it to work with any tooling/platform available.
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.
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.
Rename 'Delete step' in case action to 'delete case'
The button in a clause config of a case action says ‘delete step’. It should really say ‘delete case’ as the step (the action) is not deleted.
Change Label of "Analyse" on workflow setup tab when using AI as NLP intent
This currently says "analyse" which could be a bit misleading to customers, would be better if this said "Analysis".
Add a "log ticket" button for the technician in a handoff
The technician should have the ability to escalate a handoff to a ticket themselves so adding a button or an option at the end of the handoff on the technician's side would encompass this
Show Required Fields for Integration Commands
Would be good when field mapping for a command in an integration to know which fields are required and which are optional.
Issue with rendering of Autogenerated Cards in teams
When creating an Auto Generated Request Offering card in teams it is not able to convert the HTML elements and renders it as text. I ran the outputted card definition through AI and asked it to make it compatible with Teams and it updated it into a useable format, are we able to do something similar in tool when auto generating the card / or another option to strip and replace the HTML.
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
Up Next
3Committed and queued
Card Designer
Rather than having to go to adaptivecards.io to create Teams cards, it would be nice to have our own card designer.
Global Variables
There might be scenarios where a globally stored/managed variable could be useful. For instance, we might want to have Company Name in a variable so that all workflows can use it. Another instance could be common websites such as Self Service Portals, Wiki Sites or Resources.
REST Patch action has no backend logic
Trying to use the REST Patch action causes error: Command 632c33c4-b92a-11ed-9621-5f04f6163792 could not be found After some investigation, it appears there is no backend logic for the action. The following repro makes a request to a free API test resource. I’ve included it for simplicity. Steps to repro Set up a workflow and add the action: REST API > REST Patch. Set up the header. In the Header field enter Content-type and in the Value field enter application/json; charset=UTF-8 Click ok. In the URL enter https://jsonplaceholder.typicode.com/posts/1 In the Body enter { "title": "My new title" } Save the action and run the workflow. Expected outcome: The status code should be 200 The text response should be (something like) { "userId": 1, "id": 1, "title": "My new title", "body": "quia et suscipit\nsuscipit recusandae consequuntur expedita et cum\nreprehenderit molestiae ut ut quas totam\nnostrum rerum est autem sunt rem eveniet architecto" } Actual outcome: Error with Command 632c33c4-b92a-11ed-9621-5f04f6163792 could not be found
In Progress
10Actively being built
Run workflow command passing data.
The "Run workflow" command should have the option to pass data into the workflow its running like the POST API request to run a workflow has.
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
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.”
Change name of Saved Search Parameter on "Saved Search" action
Currently when filling in a Saved Search action we have 2 “Search” fields to be filled in, 1 is the saved search from Ivanti and the other is the filtering section, see below. Proposal is changed the Neurons Search field rename to “Saved Search” to help be clearer what each field does
Bot Training
Currently, every interaction with an End User must be via a Workflow. While our workflow engine is incredibly versatile, we must create many workflows to accommodate knowledge searches. To make OneBot more ‘intelligent’ and versatile from the start, we will implement Bot Training. This new feature will allow Admins to link or import data to OneBot to train it on the organisation's use cases for OneBot. The idea is that you could consume a website or a knowledge base that would be searchable by the bot to answer questions in conjunction with running a workflow. Where the bot can answer an end user query based on its training, it will reply, not with a card, but in a natural language response. This approach will drastically improve the TTV and ROI of an implementation, as the bot could be up and running within minutes of training. It will also create a better end-user experience as the current setup of answering queries with full-knowledge articles is subjected to third-party system designs.
New Interface
We’re developing a clean new interface for OneBot ahead of some significant new features. The new interface should simplify using OneBot and allow us to expand the platform without further interface changes.
Cannot Disable "Catch-All" and "Similarity" workflows
If a workflow is set as the catch-all or the similarity workflow, enabling or disabling the workflow won’t make a difference if you do hit the catch-all.
Ending handoff when there are more users in queue card
Currently, if you end a handoff and there are more users in the queue waiting for the handoff, the technician should receive another queue card so they don't have to scroll up the chat to start the next handoff.
Date difference expression
A very useful feature would be a new date expression to allow you to input two dates, to then return the difference between the two dates. This is already somewhat possible if the date is in epoch format but adaptive cards does not use this format, so creating an expression for this format or maybe for any format of date would be extremely helpful
Salesforce Integration
It would be great to have an integration with Salesforce. We would use it to query opportunities, quote and invoice updates as well as search for client information
Done
89Recently shipped
HaloITSM
We need to expand our ITSM roadmap, and HaloITSM has a clean API, so should make the integration relatively straightforward.
Draft available
Clicking ‘Draft available’ should switch user to the draft workflow
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.
Variables Naming
We need a process to review where variable names are being used, especially now that we have blocks, if we rename a variable it will not update the name across the system.
System Freezes on return to App Store
When looking at the workflow screen click the OneBot logo in the top left corner and the screen will freeze trying to load the homepage, a quick refresh will get me where I need to go so not critical.
"You have unsaved changes" when editing workflow
It would be good to have a warning come up on the page when you have made changes to a workflow and then try and leave the page without saving it, otherwise accidentally leaving the page can cause a lot of lost progress.
Larger Icon size limit for the Webchat logo.
Would be nice to be able to have bigger images for the webchat logo so having a configurable size for this would allow for that. Also being able to change the shape of the icon to something other than a circle to allow for differently shaped images.
Update of description and title on Integration
The Ivanti Neurons integration needs to be renamed to Ivanti Neurons for ISM they are different products.
Regeneration of Endpoint
The end point changes on initial save of the record, so the first one that was generated and used is not valid. Please can we hide the endpoint until after first save.
Base64 Encode Function
Could we get a new function in the list to encode a string to Base64 please. This will be useful for future integrations. Jira for example takes Username:APIKey and needs it to be encoded as part of the request.