require void reason workflow

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that you are looking to create a workflow that requires a reason when a transaction is voided or rejected. Here's a possible solution: 1. Create a custom record (let's call it "Rejections") with fields: Reason, Transaction (is Parent), Created By & Rejected By. 2. Create a workflow (WF#1) that triggers on the rejection state of a transaction. The action on this state should be to redirect the user to the "Rejections" record. 3. The approver enters the rejection reason in a Long Text box and saves the record. 4. Create a second workflow (WF#2) that triggers on the creation of a "Rejection" record. This workflow sets the field values for Created By & Rejected By, redirects the approver back to the original transaction, and sends an email notification to the Created By user, from the Rejected By user, with the rejection reason in the body. For the voiding of a transaction, it seems there isn't a direct way to trigger a workflow on this event. However, you could create a saved search of voided transactions and use this to trigger a scheduled workflow or send an email. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******