Updating connections
In Version 3.0, there was an attribute called result that you could select when connecting to an existing connection. In later releases, the result attribute was divided into two separate attributes called normalResult and errorResult. This is helpful because the need to do a check to determine if the result is an error is now not necessary. You can now make a connection from either one or both to something that is appropriate for that case. If you make connections from both attributes, only one will fire depending on whether the result was normal or an error.
If you bring in views from Version 3.0 that had the connection from result, this connection will still work as always. However, we are recommending that as you come across them, you should change the connection to be from the appropriate attribute.
You may notice when migrating from Version 3.0, if you had a connection from result to an action that required a parameter, this connection may now appear dashed. It will still work; however, to cause the line to not be dashed, you will need to open the settings on this connection and change the connection to be from normalResult or errorResult (whichever is appropriate).
 
Last modified date: 07/02/2019