Frontend for the Admin Portal. This web interface is used by Community Admins (cadmins) to administer community-specific portals and by Super Admins to administer the entire MassEnergize web platform.
4
stars
3
forks
source link
Feat: Refinements to the Bulk Messaging Feature #1248
In this pull request, we introduce several key additions and improvements to the messaging function of our application to improve user experience and performance enhancements. The notable changes in this Pull Request are as follows:
Action-Based Messaging: This feature provides granularity in the messaging function, enabling targeted messaging for users based on the status of the actions they have selected - 'done', 'to-do', or both.
Audience Load Optimization: To enhance the performance on audience load, we now load audience data in chunks. This ensures faster loading times and enhances the application's responsiveness.
Feature Flag for Admin Control: We have added a feature flag to regulate access to the new messaging feature by community admins. This addition is in line with facilitating easier usability and maintaining the stability of our feature releases.
Details (Give details about what this PR accomplishes, include any screenshots etc.)
Summary / Highlights
In this pull request, we introduce several key additions and improvements to the messaging function of our application to improve user experience and performance enhancements. The notable changes in this Pull Request are as follows:
Action-Based Messaging: This feature provides granularity in the messaging function, enabling targeted messaging for users based on the status of the actions they have selected - 'done', 'to-do', or both.
Audience Load Optimization: To enhance the performance on audience load, we now load audience data in chunks. This ensures faster loading times and enhances the application's responsiveness.
Feature Flag for Admin Control: We have added a feature flag to regulate access to the new messaging feature by community admins. This addition is in line with facilitating easier usability and maintaining the stability of our feature releases.
Details (Give details about what this PR accomplishes, include any screenshots etc.)
https://github.com/user-attachments/assets/a47b5602-ec37-4c88-b9a3-e13049d831a9
Testing Steps (Provide details on how your changes can be tested)
Requirements
Transparency (Project board)
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch or to a feature branch, not themainbranchfix #xxx[,#xxx], where "xxx" is the issue number)Other information: Any otherthing we need to know