samwoo Posted July 25, 2024 Posted July 25, 2024 Good morning, We don't usually update Resolution Text via the Workflow using variables, but in a recently created Workflow, we are. However, the variables in the Workflow are not being replaced with the actual text when using that Node: This is the configuration of the Update Resolution Text node: Despite careful consideration of the business case you presented as reason for unblocking the website - &[global["flowcoderefs"]["getReqInformation"]["customFieldP"], we regret to inform you that it has been rejected for the following reason(s): '''[Reason(s) for Rejection:]''' &[functions.getTaskAnswers("task-926b921e").rejection_reason] And I've double-checked and triple checked (using the Variable Picker) that the variables are indeed correct and are present prior to the Update Resolution Text node. I can also confirm that there is data in these fields, here is an example of a ticket: h_custom_p and the task itself had the rejection reason populated, shown in the timeline of the ticket. So, I wonder if there is a defect with the Update Resolution Text node? Thanks, Samuel
ArmandoDM Posted July 25, 2024 Posted July 25, 2024 Good morning @samwoo we can investigate this. From the screenshot I can see that the Resolution Text is set to 'Manual'. Does setting it as 'Variable' would solve the issue ? Regards Armando
samwoo Posted July 25, 2024 Author Posted July 25, 2024 Hi @ArmandoDM, Thanks for responding quickly - I think might have been a glitch because it now appears to be working. I'll keep an eye on this and update this thread accordingly if it happens again. 2
Berto2002 Posted August 1, 2024 Posted August 1, 2024 Phew thank goodness that is workin, we use it all the time!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now