Connections
There are several issues to me with connections. Coming from 20 years experience using an alternative product that has great enterprise features, there are a few things that make life difficult using ActivePieces connections.
We build solutions for products that then get deployed as canned solutions for multiple customers, e.g. invoice overdue notifications from multiple ERP systems.
When we migrate what we hope will now be ActivePieces solutions, the connections should be exported with the solution or at least have the ability to export separately the connections.
Additionally we will configure say email,ftp or db connections and uses them in some cases in maybe 50 plus flows. Without being able to edit connections, if a password changes, and they do, you would have to add a new connection, and remap all the flows to now use this connection, rather than just edit the old one.
It would be useful to be able to dupliacet connections as manytimes the settings for dbs, email and ftp are virtually identical. That would require renaming of connections which is missing, but a good thing to have for organisational reasons. The abilty to make things self documenting through correct naming is super useful when you come back in a years time.
When you save a connection, the one I’m playing with at the momennt is postgress, it won’t save unless oit tests successfully. In many instances I won’t have all the details yet, but will still want to add the connection and update it later. This obvioulsy relates back to not being able to edit a connection, so I understand why it behaves this way.
