Provide access to relevant resources, such as properties or Rules, that are outside your current Case Type by changing the scope of a Subprocess in the Case Type. As a result, you ensure that users can access information that is necessary to successfully resolve their business processes even if the resolution requires data from another Case.
For example, a customer service representative (CSR) can resolve a complaint about hotel service by using information that a customer provided while booking a hotel room.
Before you begin:
- In the navigation pane of Dev Studio, click Cases, and then click the Case Type that you want to open.
- In the Case Lifecycle section, in the header of a Process that contains a Subprocess, click Configure Process.
- On the toolbar, click Open Process.
- On the Diagram tab of the Flow form, open the property dialog box by double-clicking the Subprocess shape.
-
In the Subprocess details section, in the Define
flow field, select a working context for the Subprocess:
Choices Actions The Subprocess works on a current Case Select On current page. The Subprocess works on a specific Case - Select On specific work item.
- In the Work property field, enter a property reference in the current work item that identifies the key of the Subprocess work item.
- In the class field, enter the class of the Subprocess work item.
- Optional:
To specify a Clipboard page that holds the Subprocess work item, in the
Page name, enter the Clipboard page name.
Note:
If the Case is open as a page on the Clipboard, you can leave the Work property field blank.
If the Case does not already have a page and you do not provide a page name, your application creates a page named
pyNextObj
,pyNextObj_1
, and so on.
The Subprocess works on an embedded page - Select On embedded page.
- In the Page property field, enter a reference to the property of the Page, Page list property, or Page group property type that holds the embedded page.
- In the class field, enter the class of the embedded page.
-
In the Flow name field, enter a name of the Process that
includes the Subprocess for which you provide additional configurations.
By default, the system autopopulates this field with the name of the current Process.
- Optional: To display a message in the audit trail of the Subprocess, in the Audit note field, enter a Rule that stores the audit note that you want to include.
- Optional:
To allow the parent Process to continue processing without waiting for this Subprocess
to return, select the Spinoff flow checkbox.
When a Case reaches the Subprocess that runs as a spin-off, the Subprocess runs asynchronously and independently from the main Process. The main Process can continue without waiting for the results from the Subprocess. The main Process and the Subprocess might operate on the same work item or different work items.
Result:
- Optional:
To provide a link to the Subprocess in the breadcrumb trail navigation, select the
Enable navigation link checkbox, and then configure additional
navigation options:
- To enable users to get back to the Subprocess after the Case moves forward, select the Only allow navigating back to this Step checkbox.
- To enable post-processing or validation when users navigate back from the Subprocess in the breadcrumb trail, select the Perform post-processing when navigating away from Step checkbox.
- To allow users to return to the last Step in the Subprocess, select the Subprocess has navigation links checkbox.
Note: If you select neither the Only allow navigating back to this Step nor Subprocess has navigation links, the users can go back only to the first Step in the Subprocess. - Click Submit.
-
In the upper-right corner of the Case Type, save your changes by clicking
Save or Save and run.
Note: In Constellation applications, the Save and run option opens the previewed Case without showing the Create form of the Create Stage in the dialog box first. Instead, the Create Stage will be visible in the Case’s action area when the Case opens.