Welcome to the HCL Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events, please visit our HCL Connections page.
Certain types of API generated activity stream events are rendered ugly when they appear in the daily digest
Problem Scenario When API generated @mention events show up in the notification email, the format is ugly.
Troubleshooting Customer is following steps from API documentation here: https://ibm.biz/BdYCnq
In the daily digest mail, the API generated events are rendered with ugly links:
Steps To Reproduce 1. Users have "Daily Newsletter" option selected for "Mentions" in Notifications Settings screen.
2. Register an extension for the Activity Steam service in the appregistry for the org. That extension is then specified as the generator in the payload of the API request. (For example, the customer is using one called "SelfServiceApp".)
3. Using a REST client, customer is using the following JSON payload.
POST to URL: https://apps.ce.collabserv.com/connections/opensocial/basic/rest/activitystreams/@me/@all/@all:
4. Once the above event is posted via API, the next day, the user will see the "ugly" links in their daily digest newsletter mail.
Cause: This feedback provided by Connections Dev team: "These particular emails in Cloud have a link stripping process run on them - it is a security requirement - basically it is taking any anchor tag within content and if the host does not match a predefined one (which by default is global and set to the current Connections domain) it will be split out title:[url] for safety.
While this was a security requirement it could be reviewed and at a minimum offer admins the opportunity to set the whitelist of hosts - potentially also in this case auto whitelist the host if its the same as the Activitystream.generator.url"