Supermind emails #2395

Ticket(s) / Related Merge Requests

#2395 (closed)

Summary of Changes

Send supermind-related emails as per #2395 (closed) description.

Uses action events (pulsar stream) and events delegate.

Remaining/possible issues:

• Possible bug in the 'accepted' template's action button link -- I'm not sure how to get the activity guid of the supermind reply. Currently the "See Reply" action button is pointing to the SupermindRequest->getActivityGuid(), but I believe that is referring to the activity guid of the supermind request.
• The 'expiring in 24 hours' template has been created but is not being activated anywhere
• The 'Learn more' action button link leads to an access-restricted helpdesk page (@markryansallee)

Testing Considerations

Make sure all the emails as listed in #2395 (closed) are sent when specified.

When a new supermind request is created, an email should be sent to both the sender and receiver. Buttons and links clicked. All other emails have just one recipient.

Deployment Considerations

n/a

Regression Scope

I don't think so

Platform Affected (web, mobile, etc)

Web

Developer Testing Completed

All of the templates tested with both cash and tokens, but only using fake data and cli testing tools, as I had continuing issues with the local testing environment.

Screenshots / Screen Recording

In the test scenario, user @Lily made supermind requests to @localhandler.

Does this impact

• Localization
• Dark/light mode
• Guest mode

Definition of Done Checklist

• The Acceptance Criteria has been met
• Code is tested: Testing includes unit/spec, E2E/automated and manual testing
• Merge requests description has been filled out