Related terms
A swimlane organizes and graphically identifies a related group of shapes that are performed within a specific work context (typically a work group). A router activity defined in the lane shape is associated with Assignment shapes inside the lane. During processing work items are to the appropriate user worklist or workbasket defined by the router. If a lane contains an assignment, you must specify a router in the lane property panel; the Router fields in the assignment property panels are locked.
On the diagram, a swimlane must be contained in a Router Pool shape (not available from the palette). You cannot delete the only lane in a pool — you must delete the router pool. By default, when you drop a new swimlane, it is framed inside a Router Pool shape. You can then add swimlanes to the pool.
In releases prior to V5.5, pools and swimlanes defined and separated processing performed by distinct organization units within one division, or that depended upon the value of a work item property. Pool and swimlane shapes in such versions will function as originally configured in V5.5 and later. You cannot add more lanes for organization units or property values.
As a best practice, upgrade them to router pools, which use swimlanes that employ router activities. This enables you to more precisely direct assignments to user worklists and workbaskets and illustrate router behavior.