Voters 1
Stop duplicate checking modifying old MRE records
- Open
- Subscribe
 |
Scott Bussinger |
Currently, if you receive a new MRE from a previous client and assign it to the same mentor they've seen in the past, Engage marks the new MRE as a duplicate and changes the old MRE request to the new question.
This is TERRIBLE! If the previous request was 5 years ago, the entire session history no longer makes any sense because the question on the case is now different. It's also confusing for the mentor because it doesn't show up as a new request in the normal way.
Catching and blocking duplicates when a client posts 5 identical requests in one day to different mentors is great and makes sense. But don't modify existing valid case records!