MaxH Honored Contributor.
Honored Contributor.
133 views

Workflow Routing Between Entities

Jump to solution

I am attempting to create a workflow that takes a request, routes it from one customer to another customer, automatically creates a different request which is then is routed to a second customer (which then routes internally at that customer,) then when it completes, sends a closure request for the original request back to the first customer at the same time it is closing the second request.  Is this possible?  How do I relate the two request types so that the routing is correct?  Any help or direction is sincerely appreciated.  Thanks.

 

Max

0 Likes
1 Solution

Accepted Solutions
Jason Nichols K Absent Member.
Absent Member.

Re: Workflow Routing Between Entities

Jump to solution

The Demand Management Configuration Guide would be the place to start.  You are going to want to create an Execution Step that performs a Built-in Workflow Event of Create Request.  When you add this step to your workflow, you will have the option of how to configure the relationship.

3 Replies
Jason Nichols K Absent Member.
Absent Member.

Re: Workflow Routing Between Entities

Jump to solution
One of doing this would be to set the relationship between the first and second request as Successor, meaning that the parent (source) request cannot do any action until the child (spawned) request closes.
0 Likes
MaxH Honored Contributor.
Honored Contributor.

Re: Workflow Routing Between Entities

Jump to solution

Thanks for the quick reply Jason.  Can you please point me to a document that references how to accomplish this?   Thanks.

 

Max

0 Likes
Jason Nichols K Absent Member.
Absent Member.

Re: Workflow Routing Between Entities

Jump to solution

The Demand Management Configuration Guide would be the place to start.  You are going to want to create an Execution Step that performs a Built-in Workflow Event of Create Request.  When you add this step to your workflow, you will have the option of how to configure the relationship.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.