Please Share your Product Ideas with us!

All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.

Store the Rejecter in the tables together with the Rejection Reason

Currently, in dspConduct, the Rejection reason is being stored in some tables, but not who is actually rejecting the roles. 

When the customers want to know what happened we cannot extract that information from anywhere. It would be great to store that information somewhere.

  • Sara
  • Sep 20 2018
  • Shipped
  • Sep 21, 2018

    Admin response

    The actual Reject Event occurs at different levels than where the Rejection reason is entered.

    The Reject Event is on the Request Role Level and whoever clicks that button is the User who is considered to reject the role.  The notification also tells the person who is rejecting.

  • Attach files