-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slack Plugin Config should be stored in Custom Settings #593
Comments
Hi @Damecek! I've been having similar ideas over the last few months, and I think I'm going to...
I've started a prototype of using custom objects, and it'll give me a lot more control & flexibility over how Slack notifications can be setup (including sandboxes with cloned data). I'm hoping to make more progress on this over the next few months. |
What limitations are you talking about? The benefit of custom settings is the hierarchy where different users or profiles can send messages to a different Slack channels. Also, using custom settings will be easier to integrate the slack setup to the current custom setup component. |
There are a couple of issues with using custom settings
By decoupling notification configuration from logging configuration, it'll provide a lot more flexibility. |
Thanks for explaining, it looks like you have everything though through. Definitely looking forward to this upgrade. 🚀 |
Package Edition of Nebula Logger
Unlocked Package
Package Version of Nebula Logger
1.5.2
New Bug Summary
Hi,
currently the Configuration of the Slack Plugin is stored in the Custom Metadata Type called Logger Parameter. This brings complications in following cases:
My suggested solution is to store those information in Custom Settings, which are not deployable. Another benefit of this would be that we could publish messages to multiple Slack Channels from single Salesforce environment. Could be useful for example to log System Admin Profile to different channel than the rest of profiles.
The text was updated successfully, but these errors were encountered: