|
|
Flow form — Editing with Process ModelerA Subprocess shape 
may represent any of the following:
- A branch to another flow without returning (one or more incoming connectors, no outgoing connectors)
- A call to another flow with return (one or more incoming connectors, one or more outgoing connectors)
- Part of a Split Join or Split For Each shape (at least one incoming and one outgoing connector)
The 
helps to identify the Subprocess shape.
A
on the shape indicates that one or more tickets are defined on the Subprocess. Assigned ticket names appear beside this icon on the flow.
Check the Spinoff Flow box to cause this shape to start an asynchronous flow execution at runtime, in which the current flow execution continues while the subprocess executes. When this box is checked, 
appears on the Subprocess shape.
Add A Subprocess to the process flow
On the flow Diagram tab, you can add a shape in one of three ways. Validation of the added shapes occurs when you save the flow.
Use the canvas context menu:
- Right-click a blank area of the canvas near the location where you would like the Subprocess shape to appear.
- Hover over Add on the submenu to display a list of shapes you can add to the flow.
- Click the Subprocess shape. After the shape has been added to the canvas, click and drag to reposition.
Use the toolbar Flow Shape palette:
- Click the Flow Shape palette
on the toolbar to display a drop-down shapes menu that will remain open until you close it, facilitating the process of rapidly adding multiple shapes. Click the window title bar and drag the submenu to another area of the screen, as needed. - Click and drag the Subprocess shape to the canvas.
- Close the Flow Shape palette at any time.
Use the Flow Shape palette drop-down menu:
- Click the down arrow
on the toolbar Flow Shape palette to display a drop-down shapes menu. - Click and drag the Subprocess shape from the drop-down menu to the desired position on the canvas.
1. On the flow Diagram tab, open the properties panel using one of the following:
- Double-click the shape.
- Right-click the shape and select Properties from the drop-down menu.
- Click the shape, then click the toolbar View Properties icon
.
2. When the Subprocess Properties panel appears, enter a text name for this shape. The shape name defaults to Subprocess. Choose a name meaningful to application users who see this on the work item history display, the breadcrumbs control (for entry points), and the Where-Am-I? diagram. For example: Customer Limit Check.
The shape name is only descriptive; it does not affect runtime execution of the flow. This name also appears inside the Subprocess shape on the Diagram tab.
To change the name after you have exited from the properties panel, click the name, and type over the highlighted text.
3. Complete the fields as described in the tables below. (To edit the shape properties after you save the Flow form, open the Diagram tab, right-click the shape, and select Properties.)
4. Click OK or click anywhere off the shape to save edits and close the panel.
5. Click and drag the shape as needed to position it in the flow.
6. Connect at least one incoming connector to the Subprocess shape.
7. Connect at least one outgoing connector from the Subprocess shape to another shape.
Deleting a Subprocess shape from the flow
A subprocess shape may be deleted from the process flow. Right-click the subprocess shape, and select Delete from the drop-down menu.
You can also select the subprocess and do one of the following:
- Click Delete
on the toolbar. - Press the Delete key on your keyboard.
When a shape is deleted, the connectors to and from the shape are also deleted.
Complete the following fields on the Subprocess tab.
The Subprocess tab — for flow defined "on Current Work Item"
Use the following table to complete the fields if your flow is being defined on the current work item:
Field |
Description |
| Name |
Enter a name for the subprocess. Choose a name meaningful to application users who see this on the work item history display, the breadcrumbs control (for entry points), and the Where-Am-I? diagram. It does not affect flow execution.
|
| Define Flow |
Identify the objects the flow is to update. Select:
|
| Filter Flow Rule By |
Select |
Flow Rule
|
|
| Parameters |
Some flows have input parameters. Enter parameters for the selected flow. |
| Application |
|
| Work Type |
|
| Specification |
|
| Audit Note |
|
| Spinoff Flow |
Select to indicate that this Subprocess is a Spinoff Flow. When a work item advancing through a flow reaches a Subprocess with Spinoff Flow selected, PRPC starts execution of a different flow, using the current or a different work item. Processing in the current flow continues in parallel, without waiting for the other flow to complete. When this box is checked, |
| Entry Point |
Select to indicate that this Subprocess shape is an entry point, which a user can return to using the breadcrumbs control or the standard flow action Previous. The default is cleared. This checkbox works with Perform harnesses that include a breadcrumbs display and with assignments that offer the Work-.Previous flow action. In other cases, the checkbox has no effect. |
| Only Going Back |
This checkbox appears only when you select the Entry Point checkbox. Select to restrict users at runtime from jumping ahead to this step without having completed the preceding steps. After having completed this step, users may jump back to it from steps that follow it.
|
| Post Action on Click Away |
This checkbox appears only when you select the Entry Point checkbox. Select to run flow action post-processing when you click away from this entry point. |
| Subprocess has Entry Points |
In a regular flow, select to allow users to return to the entry points within the subprocesses using the breadcrumbs control, or clicking a tree-harness node from a completed subprocess or the standard flow action Work-.Previous. For example, assume that a Subprocess shape calls a flow containing two assignments ("Review" and "Approve) and the pg1 -Review - Approve - pg2 - Review - Approve — pg3 - Review - Approve.
By default, the box is cleared. |
When first building, it is simplest to make this name the same as the name of the called flow. Later when your flow is complete, you can change the name to be more descriptive.
Select the Flow Name, the second key part of the flow to be started for the other work item.
25196 How to control history instances written to the audit trail.
For maximum user flexibility, leave this checkbox unselected if your flow accepts inputs in any order.The Subprocess tab — for flow defined "on Another Work Item"
Use the following table to complete the fields if your flow is being defined on another work item:
Field |
Description |
| Name |
Enter a name for the subprocess. Choose a name meaningful to application users who see this on the work item history display, the breadcrumbs control (for entry points), and the Where-Am-I? diagram. It does not affect flow execution.
|
| Define Flow |
Identify the objects the flow is to update. Select:
|
| Work Property |
|
| Class |
|
| Page Name |
Optional. If (when this shape is reached) the other work item is present on the clipboard, enter the page name that holds it. If the other work item is not present, enter the page name to be created that holds it. When you leave this field blank but complete the Work Property field, the system opens the work item on a page named
|
| Filter Flow Rule By |
Select |
| Flow Rule
|
|
| Parameters |
Some flows have input parameters. Enter parameters for the selected flow. |
| Application |
|
| Work Type |
|
| Specification |
|
| Audit Note |
|
| Spinoff Flow |
Select to indicate that this Subprocess is a Spinoff Flow. When a work item advancing through a flow reaches a Subprocess with Spinoff Flow selected, PRPC starts execution of a different flow, using the current or a different work item. Processing in the current flow continues in parallel, without waiting for the other flow to complete. When this box is checked, |
| Entry Point |
Select to indicate that this Subprocess shape is an entry point, which a user can return to using the breadcrumbs control or the standard flow action Previous. The default is cleared. This checkbox works with Perform harnesses that include a breadcrumbs display and with assignments that offer the Work-.Previous flow action. In other cases, the checkbox has no effect. |
| Only Going Back |
This checkbox appears only when you select the Entry Point checkbox. Select to restrict users at runtime from jumping ahead to this step without having completed the preceding steps. After having completed this step, users may jump back to it from steps that follow it.
|
| Post Action on Click Away |
This checkbox appears only when you select the Entry Point checkbox. Select to run flow action post-processing when you click away from this entry point. |
| Subprocess has Entry Points |
In a regular flow, select to allow users to return to the entry points within the subprocesses using the breadcrumbs control, or clicking a tree-harness node from a completed subprocess or the standard flow action Work-.Previous. For example, assume that a Split Join shape calls a flow containing two assignments ("Review" and "Approve) and the pg1 -Review - Approve - pg2 - Review - Approve — pg3 - Review - Approve.
By default, the box is cleared. |
The Subprocess tab — for flow defined "on Embedded Page"
Use the following table to complete the fields if your flow is being defined on an embedded page:
Field |
Description |
| Name |
Enter a name for the subprocess. Choose a name meaningful to application users who see this on the work item history display, the breadcrumbs control (for entry points), and the Where-Am-I? diagram. It does not affect flow execution.
|
| Define Flow |
Identify the objects the flow is to update. Select:
|
| Page Property |
|
| Class |
|
| Filter Flow Rule By |
Select |
| Flow Rule
|
|
| Parameters |
Some flows have input parameters. Enter parameters for the selected flow. |
| Application |
|
| Work Type |
|
| Specification |
|
| Audit Note |
|
| Spinoff Flow |
Select to indicate that this Subprocess is a Spinoff Flow. When a work item advancing through a flow reaches a Subprocess with Spinoff Flow selected, PRPC starts execution of a different flow, using the current or a different work item. Processing in the current flow continues in parallel, without waiting for the other flow to complete. |
| Entry Point |
Select to indicate that this Subprocess shape is an entry point, which a user can return to using the breadcrumbs control or the standard flow action Previous. The default is cleared. This checkbox works with Perform harnesses that include a breadcrumbs display and with assignments that offer the Work-.Previous flow action. In other cases, the checkbox has no effect. |
| Only Going Back |
This checkbox appears only when you select the Entry Point checkbox. Select to restrict users at runtime from jumping ahead to this step without having completed the preceding steps. After having completed this step, users may jump back to it from steps that follow it.
|
| Post Action on Click Away |
This checkbox appears only when you select the Entry Point checkbox. Select to run flow action post-processing when you click away from this entry point. |
| Subprocess has Entry Points |
In a regular flow, select to allow users to return to the entry points within the subprocesses using the breadcrumbs control, or clicking a tree-harness node from a completed subprocess or the standard flow action Work-.Previous. For example, assume that a Split Join shape calls a flow containing two assignments ("Review" and "Approve) and the pg1 -Review - Approve - pg2 - Review - Approve — pg3 - Review - Approve.
By default, the box is cleared. |
Complete the Work Status field under the Status tab to set the status for the work item. This allows you to easily change the status at multiple points in the life cycle of a work item without adding a Utility shape to the flow for each status change. Similar to setting work item status using a Utility shape, setting the status on this tab invokes the UpdateStatus activity. Any defined tickets dependent on the status are raised, as appropriate.
Field |
Description |
| Work Status |
A status indicator appears on connectors to shapes that change a work item status. For example, if the shape status is set to Pending-External, the connector to that shape will display a small red flag. All transitions connecting to the shape will display the status indicator. Following are the status indicators for the four status prefixes.
|
New
Open
Pending
ResolvedAdd a Ticket Name field under the Tickets tab to indicate the ticket(s) available at runtime. Use the Ticket to mark the starting point for exceptions that may arise at any point in the flow, such as a cancellation. The ticket is a label for a point in a flow, much like a programming "GOTO" destination.
An activity executing anywhere in your entire PRPC application can set or raise this ticket by executing the Obj-Set-Tickets method with this ticket name as a parameter. See Ticket help for other ways to raise a ticket.
The scope of a raised ticket includes all flows on the current work item that contain this ticket. If found, processing stops on that flow promptly, and resumes at the ticket point.
The system adds to the subprocess shape to indicate one or more tickets are associated with this subprocess. Assigned ticket names appear beside this icon on the flow.
Field |
Description |
| Ticket Name |
ExampleProcessing is connected to a ticket to respond to an exception, error flow or event. For example, if a mortgage application is withdrawn after some, but not all, of the application processing is completed, a mortgage processing flow can:
|
| Display Name | Optional. The Ticket Name appears by default. Enter a name to display other than the ticket name. |
Optional. Select one or more tickets that are to be available at runtime from this subprocess. Add a row for each ticket. Use SmartPrompt to display all tickets available to flows in this work type.