Flow form
Process Modeler — Editing FlowEnd tasks
|
|
Define an end of the flow by dragging the End shape (
) update icon to the diagram and dropping it. A flow
may contain none, one, or multiple End shapes. is this still true? COLLAPSE CANDIDATE
When processing reaches this shape, no further processing by this flow rule occurs. If this flow was called as a subflow by another flow, processing continues in the calling flow.
The work object may remain open when it advances to an End shape. Processing in a separate flow may advance the work object farther toward eventual resolution.
Flow processing automatically saves the work object (using the Obj-Save method) when an End shape is reached, unless the work object is temporary. CLINIC MARIK 11/29/05
1. Right-click on a blank area of the canvas.
2. Click the End shape to add it to the flow. will the properties panel display by default? Not yet -- too complicated if you add multiple at once, per Joan.If the properties panel displays by default, it would have to close one before you add a new assignment
3. Optionally, true?complete the End Properties panel. Right-click the shape and select Properties to display the properties panel.
4. When the Assignment Properties panel appears, 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.)
3. Click OK when done.
4. Click and drag the shape as needed to position it in the flow.
5. Connect at least one other shape to the FlowEnd shape.
Select shape from plus-sign style icon and drop-down menu on toolbar (eventually)
Field |
Description |
| Name |
Enter descriptive text for this End shape. Choose a name meaningful to application users who see this on the work object history display and the Where-Am-I? diagram. B-16966. For example, Application Completed. Bug-2983Will name display at all, and if so, under? The shape name is only descriptive; it does not affect runtime execution of the flow. This name also appears inside the End shape on the Diagram tab. |
| Status |
C-1375 Optional. Enter a literal constant that indicates the outcome of the flow when this End shape is reached. When the current flow is a subflow, the system returns this value to the calling flow, which can accessed the value in a connector. If a process flow rule contains two or more End shapes, they may return the same or distinct status values. true? For example, a subprocess can include two End shapes with status values Success and PartyNotFound. The calling flow can contain two outgoing connectors from the Start shape, one to match each of these two outcomes. |
XXXXXAdd 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 Process Commander application can set or raise this ticket by executing the Obj-Set-Tickets method with this ticket name as a parameter.
A raised ticket causes the system to search for any executing flow (on the same or a different work object) that contains this ticket. If found, processing stops on that flow promptly, and resumes at the ticket point.
The system adds a Ticket modifier to End shape to indicate one or more tickets are associated with this shape. get an icon when they are done.
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:
|
Although using the FlowEnd shape is recommended
for clarity, a flow rule may contain no FlowEnd shapes. true? will mxgraph require an end?Technically, a
flow execution ends when processing reaches a shape that has no outgoing
connectors. This may be any shape except an assignment shape. MARIK
3/17/06
As a best practice, include at
least one End shape in every process flow, and connect each ending shape to
it. Avoid creating flows that have execution end at other shapes, as this
can be a source of (human reader) confusion. C-1375 pyTaskInfo propertyDELETED WAS No Properties are
required.R-3771 11/6/02
Optional. Select one
or more tickets that are to be available at
runtime from this End shape. Add a row for each ticket. Use SmartPrompt to display all
tickets available to flows in this work type.
Creating ticket rules is recommended but not required.
You can enter here a name that does not correspond to a ticket
rule