<Dd> Has its own self - contained start and end events; sequence flows from the parent process must not cross the boundary . </Dd> <Dd> A form of sub-process in which all contained activities must be treated as a whole; i.e., they must all be completed to meet an objective, and if any one of them fails, they must all be compensated (undone). Transactions are differentiated from expanded sub-processes by being surrounded by a double border . </Dd> <Dd> A point in the process where a global process or a global Task is reused . A call activity is differentiated from other activity types by a bolded border around the activity area . </Dd> <Dl> <Dt> Gateway </Dt> <Dd> A gateway is represented with a diamond shape and determines forking and merging of paths, depending on the conditions expressed . <Dl> <Dt> Exclusive </Dt> <Dd> Used to create alternative flows in a process . Because only one of the paths can be taken, it is called exclusive . </Dd> <Dt> Event Based </Dt> <Dd> The condition determining the path of a process is based on an evaluated event . </Dd> <Dt> Parallel </Dt> <Dd> Used to create parallel paths without evaluating any conditions . </Dd> <Dt> Inclusive </Dt> <Dd> Used to create alternative flows where all paths are evaluated . </Dd> <Dt> Exclusive Event Based </Dt> <Dd> An event is being evaluated to determine which of mutually exclusive paths will be taken . </Dd> <Dt> Complex </Dt> <Dd> Used to model complex synchronization behavior . </Dd> <Dt> Parallel Event Based </Dt> <Dd> Two parallel processes are started based on an event, but there is no evaluation of the event . </Dd> </Dl> </Dd> </Dl>

This is the overall diagram in business process modeling notation (bpmn) terminology