Understanding Navigator Map Design

The mechanics of creating Navigator maps are the same as those for creating all other workflow maps. Of course, you omit workflow-specific elements, such as events and routings, if PeopleSoft Workflow does not also use the map.

However, because Navigator maps serve a different purpose than maps designed for workflow purposes, there are additional design considerations:

• Navigator is organized hierarchically.

  Users drill down from business processes to activities (or other business processes), then down to steps. A well-designed hierarchy of business processes and activities is important for usability.

• You need a business process that can serve as the Navigator homepage, the first map that users see.

  Users can drill down only to maps that are hierarchically related to this homepage. Therefore, the homepage hierarchy is also important for security.

• Because the maps are visible to end users, good graphic design is important.

  For example, icon position within maps and aesthetic elements on maps, while irrelevant to workflow, can help users understand the maps and the processes that they represent.