Martyn Houghton Posted December 3, 2018 Posted December 3, 2018 When using 'Request>Log Request' method 'Log New Incident' the 'Copy Priority' option is not working. In our workflow below we update the Priority (and Service Level) of the parent request to match the value selected in an Outcome Field from a human task. This works and the parent case is correctly updated both for priority and service level, however the subsequent Log New Request ('New Atlas Incident' in the screenshot below') does not create the new request at the updated priority, but used the original one the parent request was created prior to being updated by the workflow. Can this be looked at as ' priority' thanks. Cheers Martyn
Martyn Houghton Posted December 3, 2018 Author Posted December 3, 2018 For background information, we are updating the parent request priority as it is not possible to pass 'Priority' as a variable in the 'Log New Request' method. Cheers Martyn
Martyn Houghton Posted December 3, 2018 Author Posted December 3, 2018 I have inserted 'Get Request' Information node prior to the 'Log New Incident' node to see if this would get it pick up the priority change, but that has not had any impact either. Cheers Martyn
Martyn Houghton Posted December 3, 2018 Author Posted December 3, 2018 This appears to be a Bug, as even hard coding the priority change in front of the 'Log New Request' does not trigger it to use the correct priority, it seems to be stuck on the priority the parent request was originally created on. Cheers Martyn
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