We love to hear your feedback. Your suggestions and ideas are important to us. Our feedback forum is a great place to post your ideas and vote on others. Please share your detailed use case and how the proposed enhancements can increase value to your business. We do read all of your posts, but may not be able to respond to all comments.
More information on the status of submitted ideas can be found here
Our end users are getting very confused with the excessive amounts of expiration emails for activities that they have multiple records for ( ex. one expiring, one current). Ideally the system would recognize that there are current records for a course with the same code and not send out expiration emails, despite the multiple records.
|
What is the business process you are trying to achieve?
To verify if current on a learning activity that is expiring before sending out an expiry email. Employees are getting expiration emails for activities that they have a current record in, because the expiration system works on a per-record basis, rather than an activity completion basis. |
Communications should check for "current" and not expired courses before being sent out with the same course code.