Jump to content

Link requests in BP


Met
 Share

Recommended Posts

Hi,

 

Unless I've missed something, I'm not sure this is currently possible. It would be useful if we could link requests as part of a business process - we're trying to automate as much as possible and this would really help with that.

 

Thanks

Met

Link to comment
Share on other sites

Hey @James Ainsworth

We are bringing part of our procurement process into Hornbill and as part of this users can submit an initial pre-engagement ticket before they are in a position to provide all the details of the procurement activity. This logs a ticket which goes to the procurement team who at a later date can run a task to decide whether we are proceeding with the activity. If we decide to proceed, it will instruct them to ensure a new ticket is logged which contains all the details and for that ticket reference to be entered into the task. The ticket format is verified using regex and the BP then checks that the ticket is a valid procurement ticket - if it is, it will update both tickets to say they are connected and then close the original ticket. We would also like it to link the two tickets as well without the analyst having to do a second step.

The idea is this would stop them linking wrong tickets or tickets logged incorrectly. There is still some manual input required on this particular use case.

Link to comment
Share on other sites

@Met You cannot take a Request Reference and link that to a Request in the BPM, however you can create a Linked Request using the Log Request node (see the Service Manager Business Process Workflow wiki page) which can copy elements of the existing Request and/or specify certain values to automate what you are currently doing manually.

 

Link to comment
Share on other sites

@Steve GillerThanks - yeah I came across that, problem is we need to capture quite a lot of information through the IC on the second request. What we'd probably do is once the second request has been made and the task is run, copy information from the first request to the second request (which already contains information from IC), link them then close the first.

Link to comment
Share on other sites

14 minutes ago, Met said:

problem is we need to capture quite a lot of information through the IC on the second request.

There are ways to do this - for example using your description of the process above you may be able to capture that information in the Procurement Team's Task, log the new Request, then using an Update Custom Fields node and passing the output parameter of the new Request Reference into that update the new Request's Custom Fields with the values from the Task and/or information from the initial Request.
A Task is not as elegant as an Intelligent Capture, but depending on what information you need might well do the job.

Link to comment
Share on other sites

2 minutes ago, Steve Giller said:

There are ways to do this - for example using your description of the process above you may be able to capture that information in the Procurement Team's Task, log the new Request, then using an Update Custom Fields node and passing the output parameter of the new Request Reference into that update the new Request's Custom Fields with the values from the Task and/or information from the initial Request.
A Task is not as elegant as an Intelligent Capture, but depending on what information you need might well do the job.

Sorry should have said - it wouldn't be the procurement team logging the new request, it would be a user. The procurement team would run the task once the user has logged the updated ticket.

Link to comment
Share on other sites

  • 1 month later...

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...