Follow the development progress of our platform.

Backlog

Up Next

In Progress

Done

Our Roadmap

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.

Logged

Moving Workflow Blocks

Alasdair

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.

API to User Management

Pete Mawle

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:<ul><li>actions that have configuration fields that appear due to their association with an Adaptive Card.</li><li>fields that appear in the Run Workflow action, derived from its connection to a workflow that has workflow inputs.</li></ul>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. <img data-width="100%" data-align="left" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/post/6852dd6104198d5d437588ec/019783aa-c5af-7ac2-9199-97527c114834/b64u-U2NyZWVuc2hvdCAyMDI1LTA2LTE4IGF0IDE2LjA2LjUxLnBuZw.png" data-featurebase-content-filename="Screenshot 2025-06-18 at 16.06.51.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/post/6852dd6104198d5d437588ec/019783aa-c5af-7ac2-9199-97527c114834/b64u-U2NyZWVuc2hvdCAyMDI1LTA2LTE4IGF0IDE2LjA2LjUxLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=03342547d9e473d9a2410737c9b76559958e2cb2b324a6e3c6b6047efbf9f1c5">

Es ist für den Benutzer hilfreich, wenn die Benutzeroberfläche eine semantische Unterscheidung zwischen Feldern trifft, die zu einer Aktion gehören, und solchen, die aufgrund einer Verbindung zu einem separaten Objekt vorhanden sind. Beispiele hierfür sind:<ul><li>Aktionen mit Konfigurationsfeldern, die aufgrund ihrer Verbindung mit einer adaptiven Karte erscheinen.</li><li>Felder, die in der Aktion Workflow ausführen erscheinen, abgeleitet von der Verbindung zu einem Workflow mit Workflow-Eingaben.</li></ul>Das Aktionskonfigurationspanel könnte sinnvollerweise einen Abschnitt enthalten, der einen Bereich bezeichnet, in dem Felder aufgrund einer Beziehung erscheinen werden/können. Damit können Sie dem Benutzer auch sagen: "Hey, Sie sollten diesen Bereich im Auge behalten - es könnten weitere Felder erscheinen" oder "Die Input-Workflows, die Sie verbinden, werden hier erscheinen".Dadurch wird der Benutzer auf das Konzept eingestimmt und orientiert, was zu einer verbesserten UX führt. <img data-width="100%" data-align="left" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/post/6852dd6104198d5d437588ec/019783aa-c5af-7ac2-9199-97527c114834/b64u-U2NyZWVuc2hvdCAyMDI1LTA2LTE4IGF0IDE2LjA2LjUxLnBuZw.png" data-featurebase-content-filename="Screenshot 2025-06-18 at 16.06.51.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/post/6852dd6104198d5d437588ec/019783aa-c5af-7ac2-9199-97527c114834/b64u-U2NyZWVuc2hvdCAyMDI1LTA2LTE4IGF0IDE2LjA2LjUxLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=03342547d9e473d9a2410737c9b76559958e2cb2b324a6e3c6b6047efbf9f1c5">

Hinzufügen von UI-Semantiken zu Feldern, die durch Assoziation zu separaten Objekten angezeigt werden

Det hjälper användaren om användargränssnittet gör en semantisk skillnad mellan fält som är inneboende i en åtgärd och de som finns på grund av att en anslutning till ett separat objekt har upprättats. Exempel på detta är:<ul><li>åtgärder som har konfigurationsfält som visas på grund av att de är kopplade till ett Adaptive Card.</li><li>fält som visas i åtgärden Kör arbetsflöde, som härrör från dess anslutning till ett arbetsflöde som har arbetsflödesingångar.</li></ul>Panelen för åtgärdskonfiguration kan med fördel ha ett avsnitt som anger ett område där fält kommer/kan visas på grund av en relation. Det gör det också möjligt att säga till användaren "Du bör hålla utkik här - fler fält kan dyka upp" eller "De ingående arbetsflöden som du ansluter kommer att finnas här".På så sätt orienteras användaren i konceptet, vilket leder till en förbättrad UX. <img data-width="100%" data-align="left" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/post/6852dd6104198d5d437588ec/019783aa-c5af-7ac2-9199-97527c114834/b64u-U2NyZWVuc2hvdCAyMDI1LTA2LTE4IGF0IDE2LjA2LjUxLnBuZw.png" data-featurebase-content-filename="Screenshot 2025-06-18 at 16.06.51.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/post/6852dd6104198d5d437588ec/019783aa-c5af-7ac2-9199-97527c114834/b64u-U2NyZWVuc2hvdCAyMDI1LTA2LTE4IGF0IDE2LjA2LjUxLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=03342547d9e473d9a2410737c9b76559958e2cb2b324a6e3c6b6047efbf9f1c5">

Lägg till UI-semantik för fält som visas genom koppling till separata objekt

Add UI semantics to fields displayed by association to separate objects

Ben Lehmann

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.

Knappen i en klausulkonfiguration för en ärendeåtgärd säger "delete step". Det borde egentligen stå "delete case" eftersom steget (åtgärden) inte raderas.

Byt namn på "Ta bort steg" i ärendeåtgärd till "Ta bort ärende

Rename 'Delete step' in case action to 'delete case'

This currently says "analyse" which could be a bit misleading to customers, would be better if this said "Analysis".<img src="https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/1712217402653..png">

Change Label of "Analyse" on workflow setup tab when using AI as NLP intent

Gabe Bryant

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

Add a "log ticket" button for the technician in a handoff

Would be good when field mapping for a command in an integration to know which fields are required and which are optional.

Show Required Fields for Integration Commands

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

Allow the OneBot to add values to an array after Create Array Step

Anthony Dew

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.

Show key workflow config info in the workflow editor

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…’ <img data-width="100%" data-align="left" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/post/68bace3570c8b2a0124d40df/019919b5-247f-7864-b7fa-148bbc693a30/b64u-U2NyZWVuc2hvdCAyMDI1LTA5LTA1IGF0IDEyLjM5LjExLnBuZw.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/post/68bace3570c8b2a0124d40df/019919b5-247f-7864-b7fa-148bbc693a30/b64u-U2NyZWVuc2hvdCAyMDI1LTA5LTA1IGF0IDEyLjM5LjExLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=ede0b37ba61ff3a9341f1744f1593c8cbdb8935ea16d87e0492238db2c39770e" data-featurebase-content-filename="Screenshot 2025-09-05 at 12.39.11.png">

Die Benutzeroberfläche für die Neuronen "Geschäftsobjekt erstellen" bietet dem Benutzer keine kohärente Möglichkeit, vorhandene Werte zu bearbeiten. Stattdessen muss der Benutzer auf "Felder hinzufügen..." klicken, um die Bearbeitungsansicht für die Werte der vorhandenen Felder zu erhalten. Ändern Sie den Wortlaut der Schaltfläche in "Felder hinzufügen/bearbeiten...". <img data-width="100%" data-align="left" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/post/68bace3570c8b2a0124d40df/019919b5-247f-7864-b7fa-148bbc693a30/b64u-U2NyZWVuc2hvdCAyMDI1LTA5LTA1IGF0IDEyLjM5LjExLnBuZw.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/post/68bace3570c8b2a0124d40df/019919b5-247f-7864-b7fa-148bbc693a30/b64u-U2NyZWVuc2hvdCAyMDI1LTA5LTA1IGF0IDEyLjM5LjExLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=ede0b37ba61ff3a9341f1744f1593c8cbdb8935ea16d87e0492238db2c39770e" data-featurebase-content-filename="Screenshot 2025-09-05 at 12.39.11.png">

Unklar in Neurons 'Create Business Object' UI, wie Feldwerte bearbeitet werden können

Användargränssnittet för neuronerna "Create Business Object" visar inte användaren ett sammanhängande sätt att redigera befintliga värden. Istället måste användaren klicka på "Add Fields..." för att få redigeringsvy för värden i befintliga fält. Ändra ordalydelsen på knappen till "Add/Edit Fields... <img data-width="100%" data-align="left" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/post/68bace3570c8b2a0124d40df/019919b5-247f-7864-b7fa-148bbc693a30/b64u-U2NyZWVuc2hvdCAyMDI1LTA5LTA1IGF0IDEyLjM5LjExLnBuZw.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/post/68bace3570c8b2a0124d40df/019919b5-247f-7864-b7fa-148bbc693a30/b64u-U2NyZWVuc2hvdCAyMDI1LTA5LTA1IGF0IDEyLjM5LjExLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=ede0b37ba61ff3a9341f1744f1593c8cbdb8935ea16d87e0492238db2c39770e" data-featurebase-content-filename="Screenshot 2025-09-05 at 12.39.11.png">

Oklart i Neurons "Create Business Object" UI hur man redigerar fältvärden

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

Can we have an option to add a welcome card to the Webchat similar to what we have in the teams integration.

Kan vi ha ett alternativ att lägga till ett välkomstkort till webbchatten liknande det vi har i teams integration.

WebChat välkomstkort

Released

WebChat Welcome Card

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.

System Freezes on return to App Store

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.

"You have unsaved changes" when editing workflow

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.

Larger Icon size limit for the Webchat logo.

The Ivanti Neurons integration needs to be renamed to Ivanti Neurons for ISM they are different products.

Update of description and title on Integration

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.

Regeneration of Endpoint

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.

Base64 Encode Function

API keys for Ivanti Neurons and other integrations are stored as plain text and not masked in the user interface. these should not be visible once entered for security.

High Priority

API Keys in Plain Text

ISM has the ability to include Query strings within the API calls for example changing the number of records returned. An example would be:?$top=100This would get around the default limit of 25 records on a Related Business Object Search.

Query String for Neurons Intergation

Currently set to 25 which is too small.

Increase default pagination to 50 per page

Kevin Baker

We need to expand our ITSM roadmap, and HaloITSM has a clean API, so should make the integration relatively straightforward.

HaloITSM

<img data-width="100%" data-align="left" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/static/01975981-54ed-77ae-9d80-8ec228aed079/ss-01975981-54ed-77ae-9d80-8ec228aed079.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/static/01975981-54ed-77ae-9d80-8ec228aed079/ss-01975981-54ed-77ae-9d80-8ec228aed079.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=72b917a07bbc19efbf3bea6fb291df7077404e2b4340e83045d9353c2c1f4cc2" data-featurebase-content-filename="ss-01975981-54ed-77ae-9d80-8ec228aed079.png">Clicking ‘Draft available’ should switch user to the draft workflow

<img data-width="100%" data-align="left" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/static/01975981-54ed-77ae-9d80-8ec228aed079/ss-01975981-54ed-77ae-9d80-8ec228aed079.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/static/01975981-54ed-77ae-9d80-8ec228aed079/ss-01975981-54ed-77ae-9d80-8ec228aed079.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=72b917a07bbc19efbf3bea6fb291df7077404e2b4340e83045d9353c2c1f4cc2" data-featurebase-content-filename="ss-01975981-54ed-77ae-9d80-8ec228aed079.png">Durch Anklicken von "Entwurf verfügbar" sollte der Benutzer zum Entwurfsworkflow wechseln.

Entwurf verfügbar

<img data-width="100%" data-align="left" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/static/01975981-54ed-77ae-9d80-8ec228aed079/ss-01975981-54ed-77ae-9d80-8ec228aed079.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/static/01975981-54ed-77ae-9d80-8ec228aed079/ss-01975981-54ed-77ae-9d80-8ec228aed079.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=72b917a07bbc19efbf3bea6fb291df7077404e2b4340e83045d9353c2c1f4cc2" data-featurebase-content-filename="ss-01975981-54ed-77ae-9d80-8ec228aed079.png">Klicka på "Draft available" för att växla användaren till det preliminära arbetsflödet

Utkast tillgängligt

Draft available

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.

Vi behöver en process för att granska var variabelnamn används, särskilt nu när vi har block, om vi byter namn på en variabel kommer det inte att uppdatera namnet i hela systemet.

Benämning av variabler

Variables Naming

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.

Run workflow command passing data.

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.

Focus the first input field (with active cursor) when opening modal in workflow editor

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. <video data-width="100%" data-align="left" alt="" data-featurebase-content-filename="Screen Recording 2025-12-16 at 10.11.46.mov" data-featurebase-content-key="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJvYmplY3RLZXkiOiIwMTliMjZhOS0wYTcwLTdiMmMtYTY5NS0zZjNiMDliNjZmMjYiLCJ0eXBlIjoidmlkZW8tdXJsIiwicmVzb3VyY2VJZCI6IjY5NDEzMWFmODZmOWNlZmM5YmM1MjEyZCIsInJlc291cmNlVHlwZSI6InBvc3QiLCJvcmdJZCI6IjY0ZDNkMzA2MmY4ZjZlOGEzZTU4Zjc5YiIsImlhdCI6MTc2NTg4MDIzOX0._zl-fsCkvAPx8f5lON8QLEBC9NhtMn3_3EFF3MJOq1U" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/videos/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJvYmplY3RLZXkiOiIwMTliMjZhOS0wYTcwLTdiMmMtYTY5NS0zZjNiMDliNjZmMjYiLCJleHAiOjE3NzAwNzY4MDAsInR5cGUiOiJ2aWRlby11cmwiLCJvcmdJZCI6IjY0ZDNkMzA2MmY4ZjZlOGEzZTU4Zjc5YiIsInJlc291cmNlSWQiOiI2OTQxMzFhZjg2ZjljZWZjOWJjNTIxMmQiLCJyZXNvdXJjZVR5cGUiOiJwb3N0In0.ASexTXOVZEtnhKMZ2a5bJ7Uee2tNz3L0xyq3r_MsGvg/manifest.mpd"></video>

Prevent the workflow scroll in background when scrolling a modal

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.

Add time to error report table view

The tag control renders tags so they appear to overlap the boarder of the tag control. Look rough, see attached picture.<img data-width="100%" data-align="left" alt="" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/post/693bf5dce91e92c9033a9799/019b1238-3649-74ee-a61d-f71ba794268e/b64u-aW1hZ2UucG5n.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/post/693bf5dce91e92c9033a9799/019b1238-3649-74ee-a61d-f71ba794268e/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=3e73446c86f810e0d064bdd410766484ff97341f0e1021981150c4b65bf7b83d" data-featurebase-content-filename="image.png">

Tag control renders tags overlapping control boundary

The highlight that appears on hover for and editable expression in a tag control has spacing/overlapping/z-layer issues. See attached picture.<img data-width="100%" data-align="left" alt="" data-featurebase-content-key="64d3d3062f8f6e8a3e58f79b/post/693bdda1fefee0b5f00e772d/019b11d9-b3c9-7a31-9f0d-1649a66adcac/b64u-U2NyZWVuc2hvdCAyMDI1LTEyLTEyIGF0IDA5LjE1LjE0LnBuZw.png" data-featurebase-content-filename="Screenshot 2025-12-12 at 09.15.14.png" src="https://64d3d3062f8f6e8a3e58f79b.featurebase-attachments.com/c/post/693bdda1fefee0b5f00e772d/019b11d9-b3c9-7a31-9f0d-1649a66adcac/b64u-U2NyZWVuc2hvdCAyMDI1LTEyLTEyIGF0IDA5LjE1LjE0LnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260202T230000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260202%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=31a4f16285ad7dccdd7ca91ce05e4b9abd1ed50e06787365831c1f1c1a100bb0">

Tag control highlight overlaps/collides with other content

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:<ol><li>Open a workflow</li><li>Enter edit mode</li><li>Add an array step</li><li>Add an element to the array.</li><li>Publish the workflow</li><li>Click on the array step to reveal the config panel</li><li>Click the red cross to delete the element</li><li>Click ‘Confirm’ on the popup that appears asking for confirmation to edit workflow.</li><li>Note that the element appears to have been removed from the array.</li></ol>Desired behaviour:Array elements should remain visible if red cross is clicked while not is draft mode Actual behaviourArray elements disappear when red cross is clicked when in draft mode

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

Rather than having to go to <a target="_blank" rel="noopener noreferrer nofollow" class="text-indigo-500 dark:text-indigo-300 cursor-pointer" href="http://adaptivecards.io">adaptivecards.io</a> to create Teams cards, it would be nice to have our own card designer.

Card Designer

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.

Global Variables

Help Center

Improved

Fixed

onebot

Rejected

Low Priority

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