Issue with Unified Messaging Channel - Post Deployment
We recently migrated code to staging environment and noticed that we could see connection details of Dev in staging.
Steps followed as below:
1. Added Manager ID and Manager Key in application rule > Integration and Security tab. (we maintain separate credentials for different environments)
2. prepared a unified messaging channel in development environment.
3. added connections using "manage connections" button (added facebook, twitter, twilio etc)
4. locked application rulesets and included in product rule
5. included class instance for BotAgent class
6. included channel instance from "Data-Channel-Configuration-BotAgent" class. without which i don't see channel in STG environment
7. added manager key and ID in STG environment
8. opened channel in STG environment and went ahead to add connections
9. clicked on "manage connections" and we notice that connections are available same as Dev.
10. tried to delete them from STG, but these are getting deleted from Dev.
please suggest if there is a way to fix this? Let me know if you need any further details.
Thanks in advance..!!
Updated: 30 Apr 2021 8:33 EDT
Pegasystems Inc.
CA
Hi @AbdulAhad, we are investigating your case and will report back. Thank you for providing the config steps and details.
Thanks and regards
Cognizant
IN
@AbdulAhad This can be avoided by following below steps.
1. In the application in Dev Studio, go to Configure > System > Settings > URLs and set the Publicurl 2. In the Digital Messaging Manager, delete your connected accounts before deployment. 3. Edit your manager ID if needed, for example if you're starting on a new environment. 4. Create the channel if needed, or save on the current one. 5. Add your accounts in the Digital Messaging Manager.
6. Save the channel rule