Process Modeler symbols and shapes
There are many different kinds of symbols and shapes. Click on a link below to see a legend of the shapes and their purposes:
Gallery symbols - used for system diagrams
Process flow diagram symbols
Gallery symbols - used for system diagrams
Note: These symbols apply to Process Modeler version 4.1.3.
To get all of these icons listed below, you must import the QM gallery files. See Eureka! document 15336 — PeopleSoft QPM gallery icons.
| Object | Definition/Purpose |
|
Feedback
|
This object represents feedback into a process. For example, this symbol would be used to represent responses from customer satisfaction surveys, etc. |
Input or Output
|
This object represents an input or output of a process. For example, information for inputs can come from various entities, such as; customer requests, organizations, industry trends, etc. Outputs are the expected results from the process. |
Metric
![]() |
This object represents a metric to a process. The actual metric can be attached. For example, metrics can be measured by using service level agreements, help desk statistics, and cost measurement (ROI), etc. |
|
CobiT control objective or
High level process/function |
This type of model is used to establish the scope of a distinct process or an entire functional area. This symbol is used to represent process flows within a system diagram. |
System Diagram Task
|
This object represents the high level task at the system level. |
Click here to go back to the beginning of this document.
Note: These symbols apply to Process Modeler version 4.1.3.
Most of these symbols do not appear until you import the QM gallery files. See Eureka! document 15336 — PeopleSoft QPM gallery icons.
| Object | Definition/Purpose |
Task
|
This object represents a piece of work that is part of an overall activity. Tasks should always start with an action verb such as "gather requirements" or "contact the vendor". |
|
Task with an Internal Control
|
Internal Control Points provide reasonable assurance that business objectives will be achieved and that undesired events will be prevented. Begin the naming of every control task with a "C-" (i.e. C-XXX). For example, a control would exist for purchase authorizations. |
Decision Point
|
This object represents a decision point. (Yes/No). It is on your Object Creation bar. |
Data Store
![]() |
This object represents the storage of data for processing by a subsequent task or activity. An example use of this type of object is to store EDI records created by the Invoice Generation task. |
Transfer point
|
This object is a task that represents transfer point into another process. Begin the naming of every transfer point with a "T-" (i.e. T-XXX). For example, the process for ordering a laptop will include a transfer point into the overall Purchasing process. |
|
Source / Sink
|
This object represents the beginning (the source) and end (the sink) of a process. A source icon is gray, and sink icon is orange. |
Organization
|
This icon is used in the swim lane to identify the flow of an organization. A process model may include multiple swim lanes, depicting various organizations responsible for completing a process. |
|
Role
|
A role is used in the "swim lane" to identify a specific role within an organization. A process model may include multiple swim lanes, depicting various roles within an organization responsible for completing a process. |
Click here to go back to the beginning of this document.
Created by the PeopleSoft Knowledge Management Team.
Copyright © 2003
All rights reserved.
Created: kcw 11/17/2003
Reviewed: 10/04/2004