This illustration shows a portion of the Travel Request Process player instance page. 

In the top left is the Travel Request Process tab. 

On the tab, to the right of the name is an X icon. 

Below the tab are the Employee and Manager swimlanes; although the swimlane roles have been cutoff. Each swimlane contains flow elements (left to right) and sequence flows.

The process starts at the left end of the Employee swimlane with the Submit Travel Request start event. 

There is a sequence flow from Submit Travel Request to the Amount > 5000 exclusive gateway in the Manager swimlane. 

From Amount > 5000 there one sequence flows pointing to the Approve Travel Request approve human task in the Manager swimlane. 

The Approve Travel Request task has a sequence flow pointing to the Approved? exclusive gateway in the Manager swimlane. 

The Approved? gateway has two sequence flows. The No sequence flow points to the Redo Travel Request task. 

The Redo Travel Request task has a sequence flow pointing to the Approve Travel Request task. The Yes sequence flow points to the Fulfill Travel Request submit human task. 

The Fulfill Travel Request task has a sequence flow that points to the Completed end event which signifies the end of the process. 

The Submit Travel Request start event, the Amount > 5000 gateway, the Approve Travel Request task, Approved? gateway, the Fulfill Travel Request task, the Completed end event and the sequence flows between the flow elements are highlighted. 

The highlight signifies the path the Player took through the process.

The following items are bordered in red, to call attention to them:
X icon
Completed end event