Approve/Deny
One of the basic actions is a need to approve/deny a request. Using the Adaptive Card Designer, I copied out the basics of the approve/deny JSON and edited to how it is below. You'll note that the "data" key under the "Action.Submit" is highly customizable. This action is placed in the "body" section of the card update.
In this example, you'll see the information that I determined was necessary to be able to handle the approval/denial of a submission from our service desk to our software subject matter experts who review if the submission meets the threshold to submit to our developers. This workflow is triggered on a ConnectWise PSA ticket record saved that matches the right board and status.
I added the following fields for the response handler workflow:
"Type" - I use this to condition the initial noop on the response handler workflow to determine which sub-workflow is required
"ServiceTicketId"
"ApprovedTicketNote" - This is the ticket note ID used to generate the approval. In the video for the 4/5 ROC Open Mic, you'll see that this is the note that I used to format all of the information for the SME (we have since moved this away from our QA team) to review. On approval, I use this to obtain the note/time entry and send the same information off to our Azure DevOps to create the work item.
"CardID"/"CardActivityId" - The information returned from the original message needed to update this message again once the response is recorded.
Last updated