Include data objects and data stores in your process maps to show how information is used, produced, or stored during a process. This adds more context and clarity to your diagrams by highlighting key documents, data inputs, and storage locations.
Data Objects: Represent the data being used or processed. It is typically temporary, moving data (e.g., an invoice, an order form). Can be an input or an output.
Data Stores: Represent where data is saved or stored. Where data is kept for reuse or archiving (e.g., a database, a filing cabinet). Can be an input or an output.
But apart from these, BPMN can also imply other kinds of inputs/outputs through physical items, messages and signals. In ProcessPro we specify the use of data inputs and outputs only. All other inputs and outputs are categorised as default.
Display Data Objects and Data Stores on Map
Data objects and data stores are displayed on the map as smaller nodes leading into/out of nodes in the process. A data object node looks like a page with a corner turned over. A data store node looks like a round cylinder.
To display data objects and data stores on your map, set your preferences.
To demonstrate how to use data object and data store inputs and outputs, the below example illustrates a customer submitting a car accident claim:
Data Objects:
The Accident Report, Photos of Damage, and Repair Estimate are modeled as Data Objects — they are used and updated during some of the process activities.
They flow between tasks but don’t persist once the process is done.
Data Store:
The Claims Database is modeled as a Data Store.
It stores all processed claim records for long-term retention, auditing, and future reference — before, during, and after the workflow.
This combination helps stakeholders see what data is needed, where it comes from, how it moves, and where it is stored for compliance and reporting.
Learn more about how to add/edit/delete these inputs and outputs and how to turn the display of data objects and data stores on the map on/off.