Jump to content

"Log New Incident" Automation in Auto Task is not picking-up a workflow


Berto2002
 Share

Recommended Posts

Hi,

My Service Desk really want a way to "re-log" a Service Request as an Incident when users get it wrong.

I have set-up an Auto Task workflow that should do this and attached it to a Custom Button that appears for all Requests.

image.thumb.png.f321dfc316d427c80bcd8411cd671007.png

In the "Log Incident from Service Request" node I have this where the "Service" variable is gathered from the Get Request Information Service Name.

image.thumb.png.64129b7e77dfa3f07f90ebc27617e184.png

In the case of my test Requests, they are against the "TEST SERVICE" which has the "SYSTEM: Incident" Catalogue Item:

image.thumb.png.7499ee614900313415e651b4c67ff16f.png

Can anyone help please as to why this is not picking-up the workflow I specify?

Thanks in advance

 

Berto2002

Link to comment
Share on other sites

The first thing I would do is to expose the variable you are injecting into the Service parameter so you are certain what is being passed - you can do this by putting it into a timeline update, or adding it to the Notice you post on the next node, for example.
Then double-check that this value is what the Log New Incident node is expecting.

The wiki states:
 

Quote

To add a Service to the new request, set to Manual and select a Service from the pick list. If a Service is specified without a Catalog Item, the BPM workflow set against this request type on the Service Configuration will be used on the new request.

so whether the use of variables is permitted on this node will probably need a comment from a Product Specialist or one of the Service Manager Developers.

Link to comment
Share on other sites

There is also the option to just raise a new linked request.  This will copy over the details from the original request and also allow for a Progressive Capture to be run so that all of the appropriate information for the new request is captures.  Once the new request is raised, the original can be cancelled, but it will still be available for reference if needed through the linked requests section.

image.png

Link to comment
Share on other sites

HI @James Ainsworth. By setting the standard workflow in Service Portfolio for a Request Type, I have managed to ensure the new Requests pick-up a workflow, thank you. This gets around the fact that the Variable for selecting the Cat Item does not seem to work; and it's also a more stable approach.

Can I leave you to query internally whether the Variable should work in Auto Tasks and feed it into the pipeline if not? I do not have a need for it now.

Thank you,

Berto202

Link to comment
Share on other sites

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
 Share

×
×
  • Create New...