Jump to content

Recommended Posts

Posted

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.

image.thumb.png.f710ddb3aedf8d71895b473dfae7eef5.png 

Can this be looked at as ' priority' thanks. ;)

Cheers

Martyn

Posted

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

Posted

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.

image.thumb.png.39f539b38033f0549103a9317fa6cc83.png

Cheers

Martyn

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...