-
Bug
-
Resolution: Done
-
Critical
-
fuse-7.x-GA
-
%
-
+
-
Automated
-
Fuse 7.5 Sprint 52 - Bug fix
The channel dropdown in Slack connection is as input type. After click on them, the datalist is shown with the available channel. Hence, the user is able to fill in the name of the channel which doesn't exist (or just make a TYPO error). The Slack connection wizard doesn't verify whether the channel exists or not. In that case, when the slack connection is:
- as a start step (Reading from channel operation), the integration is never triggered. Which make sense when the channel doesn't exist.
- as a middle or final step (Send a message to a channel), no errors are shown. It can be confusing for a user who e.g. makes a TYPO in the channel name because the integration is running without any errors but they doesn't see any messages in the channel.
In my POV, the channel element in the Slack connection (Send a message and read a message action) should be only dropdown with all available channel without possibility to add something else. Or is any use case when the user wants to add the name of the channel which doesn't exist?
- is related to
-
ENTESB-11787 Reconfiguration of SQL query step changes text to dropdown
- Closed
-
ENTESB-11282 Google calendars select calendar dropdown changed to text input
- Done
-
ENTESB-11719 Choosing Resource Collection in OData allows inserting unexisting resource collection name
- Done
-
ENTESB-11758 Restore behavior of dynamic action metadata lookup form field rendering
- Done
-
ENTESB-11843 Text field instead of dropdown in the Salesforce connection
- Done