There are two nodes used to define a final state in an Activity, both defined in UML 2.4.1 as of type Final Node. The Flow Final element depicts an exit from the system, as opposed to the Activity Final, which represents the completion of the Activity. Only the flow entering the Flow Final node exits the Activity; other flows continue undisturbed.
The following example Activity Diagram illustrates the development of an application. The process comes to a Flow Final node when there are no more components to be built; note that the Fork element indicates a concurrent process with the building of new components and installation of completed components. The Flow Final terminates only the sub-process building components. Similarly, only those tokens entering the decision branch for the installation of further components terminate with the connecting Flow Final (that is, stop installing this component, but keep on installing other components). It is only after the Deliver Application activity is completed, after the control flow reaches the Final node, that all flows stop.
See UML Superstructure Specification, v2.1.1, figure 12.91, p. 374.
|•||Moving a diagram generally does not affect the location of elements in packages: if you move a diagram out of one package into another, all the elements in the diagram remain in the original package|
However, Flow Final elements are used only within one diagram, have no meaning outside that diagram, and are never re-used in any other diagram; therefore, if you move a diagram containing these elements, they are moved to the new parent package with the diagram
OMG UML Specification:
The OMG UML specification (UML Superstructure Specification, v2.1.1, p. 375) states:
A flow final destroys all tokens that arrive at it. It has no effect on other flows in the activity.