Flow rules
Process Modeler basics
 

xxxxxxxxxxx

xxxxxxxxxxxxxxxx

xxxxxxxxx

Consider these tips as you complete the flow rule:

• Every flow must include one StartFlow symbol, and at least one FlowEnd symbol identifying an end.
• Limit each flow to about 15 shapes (not counting connectors) to avoid difficult-to-follow flows. If your diagram includes too many shapes, simplify the diagram by moving a portion of the processing to a subflow. Consult the PDN for more information about creating flows.
• You can work and test proj-201 in draft mode first, and then print the diagram as a requirements specification.
• Start out simply by creating and testing the main path of the flow. Don't forget to add flexibility and robustness with supporting error flows, tickets for exceptional conditions, and so on.
• Choose likelihood values that are initial guesses. After the flow is in use, click the  Flow Analysis   button on the Design tab to obtain statistics for comparison. If you estimated that a connector flow action will be used 1 percent of the time, but it is in practice used 15 percent of the time, this large difference is worth researching. Productivity, costs, and timeliness are directly related to the path that a work object takes through the flow diagram.
• Include tickets and utility tasks to accommodate cancellations, rollbacks (sometimes called compensating transactions), errors, and similar exceptions.