Foundamentaly connectors help eramba to connect to other systems (and other systems to eramba, if they have that capability) to do “things”.
The table below is a list of current connectors:
Issues:
- Their configuration is spread all around the tool, not in a unified location
- They “do” things in different parts of the software
- They all have pretty custom configuration settings, UI, etc
Immediate Fixes:
- We need a unified place where they are configured, Settings/* is the logical place
- That unified configuration place needs to show clearly where they are used (and where they can be used, for example Mails can not be used in account reviews)
Slack & Teams:
- We want to expand to these connectors
- They will be used for “Notifications”, the goal is that when they are configured the user can use them to deliver notification messages (comments, warnings, awareness and reports)
We have in mind a “Triggers” functionality (Feature - triggers), if very likely that they could trigger (yes..) connectors, for example a configured REST Call connector.
Int ref: https://docs.google.com/spreadsheets/d/1Q-gSyJtuIl0f7gzqr4XuJ6nRGVQV2XgTWXWS-B1jS9k/edit