Sprint 7 - June 02, 2021
- Feature
Course and Person leaders who are able to send out emails, now are getting the ability to send out an email copy to themselfs. The feature is available for the following functionality:
- Sending out invitation emails for a course (My Page for Course leaders)
- Sending out a manual email to a chosen participants in a list of participants (My Page for Course leaders)
- Sending out a manual email to a chosen persons in a list of persons (My Page for Person leaders)
How to use:
- Go to My Page as e.g, a course leader
- Open a course card, and navigate to the list of participants
- Choose few people from the list, and click “Send email” button at the top
- In a lightbox, define the email body text, and click a new checkbox “Send a copy to my email”
- Feature
A new feature is released for course leaders who are able to manage course participants details. Now it becomes possible to set up a separate admin discount for a participant. The discount is applicable for all course products the participants will get via the course invoice.
How to use:
- Go to My Page as a course leader with the rights no lower than Course Editor
- Open a course card, and navigate to the list of participants
- Open details of one participant
- Navigate to the “Admin discount” block
- You can turn on the admin discount, and apply a value of discount in percents (should be more then 0, and less or equal 100)
- In case you aplly 100% admin discount, the system will not generate the course invoice for this participant
- Bug fix
Previously CiS system didn’t allow to send more than 100 reminders for Multikanal delivery. This limitation was caused by the peculiarities of processing requests that the system sent to the Multikanal. This approach has been updated and uploaded to a live server.
- Bug fix
Changes in the project setup have to lead to the turning off of e-mail functionality. The project settings were reviewed and the team has developed an updated approach. The fix was uploaded to the live server.
- Bug fix
There was an issue caused by the difference in the production environment after moving to the new server. Previously we have changed the variable in the project setup, however, there was one unobvious place in the database where this data was used, thus the fix developed earlier was not enough for resolving this case.