Coffee Talk: What's an agreement management lesson you learned recently?

I just figured out how to use a DATA:DECLINEDREASON within a CLM Workflow to notify the requester that the request was declined and they need to update it so that it can go back to the approver/signer. I created a variable, added an update variable value step after the reject that took the summary.transaction.comments and copied them into the variable, DeclinedReason. Then I used that variable in an email. <%#Variable.DeclinedReason%>.  This workflow doesn’t want to stop if it is denied but goes back to the customer to update the request.

Additionally, I had to update the Signature Audit XML variable to include the comment field, which is why I had not seen the deny reason while running the workflow before.

@mshealy Thank you for sharing! It’s impressive how you figured out a way to keep the process moving even if a request gets declined. The idea of using a special step to grab the comments and put them in the email is smart and changing the settings to see the decline reason is super helpful for transparency. Thanks for contributing this tip!