How to Create a BPMN Diagram

This BPMN diagram sample shows the recruitment (hiring) process workflow.
"Recruitment refers to the process of attracting, screening, selecting, and onboarding a qualified person for a job. At the strategic level it may involve the development of an employer brand which includes an "employee offering".
The stages of the recruitment process include: job analysis and developing some person specification; the sourcing of candidates by networking, advertising, and other search methods; matching candidates to job requirements and screening individuals using testing (skills or personality assessment); assessment of candidates' motivations and their fit with organizational requirements by interviewing and other assessment techniques. The recruitment process also includes the making and finalizing of job offers and the induction and onboarding of new employees.
Depending on the size and culture of the organization, recruitment may be undertaken in-house by managers, human resource generalists and/ or recruitment specialists. Alternatively, parts of the process may be undertaken by either public-sector employment agencies, commercial recruitment agencies, or specialist search consultancies." [Recruitment. Wikipedia]
The BPMN (Business Process Model and Notation) diagram example "Hiring process BPMN 1.2 diagram" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Business Process Diagram solution from the Business Processes area of ConceptDraw Solution Park.

This BPMN (Business Process Model and Notation) diagram sample illustrates the issue tracking system workflow.
"An issue tracking system (also ITS, trouble ticket system, support ticket, request management or incident ticket system) is a computer software package that manages and maintains lists of issues, as needed by an organization. Issue tracking systems are commonly used in an organization's customer support call center to create, update, and resolve reported customer issues, or even issues reported by that organization's other employees. An issue tracking system often also contains a knowledge base containing information on each customer, resolutions to common problems, and other such data. An issue tracking system is similar to a "bugtracker", and often, a software company will sell both, and some bugtrackers are capable of being used as an issue tracking system, and vice versa. Consistent use of an issue or bug tracking system is considered one of the "hallmarks of a good software team".
A ticket element, within an issue tracking system, is a running report on a particular problem, its status, and other relevant data. They are commonly created in a help desk or call center environment and almost always have a unique reference number, also known as a case, issue or call log number which is used to allow the user or help staff to quickly locate, add to or communicate the status of the user's issue or request.
These tickets are so called because of their origin as small cards within a traditional wall mounted work planning system when this kind of support started. Operators or staff receiving a call or query from a user would fill out a small card with the user's details and a brief summary of the request and place it into a position (usually the last) in a column of pending slots for an appropriate engineer, so determining the staff member who would deal with the query and the priority of the request." [Issue tracking system. Wikipedia]
The business process modeling diagram example "Trouble ticket system - BPMN 2.0 diagram" was designed using the ConceptDraw PRO diagramming and vector drawing software extended with the Business Process Diagram solution from the Business Processes area of ConceptDraw Solution Park.

This BPMN (Business Process Model and Notation) collaboration diagram sample depicts interactions between customer, travel agent and cab driver, which are defined as a sequence of activities, and represent the message exchange during a cab booking process.
"Business process modeling is used to communicate a wide variety of information to a wide variety of audiences. BPMN is designed to cover this wide range of usage and allows modeling of end-to-end business processes to allow the viewer of the Diagram to be able to easily differentiate between sections of a BPMN Diagram. There are three basic types of sub-models within an end-to-end BPMN model: Private (internal) business processes, Abstract (public) processes, and Collaboration (global) processes...
Collaboration (global) processes.
A collaboration process depicts the interactions between two or more business entities. These interactions are defined as a sequence of activities that represent the message exchange patterns between the entities involved. Collaboration processes may be contained within a Pool and the different participant business interactions are shown as Lanes within the Pool. In this situation, each Lane would represent two participants and a direction of travel between them. They may also be shown as two or more Abstract Processes interacting through Message Flow. These processes can be modeled separately or within a larger BPMN Diagram to show the Associations between the collaboration process activities and other entities. If the collaboration process is in the same Diagram as one of its corresponding private business process, then the activities that are common to both processes can be associated." [Business Process Model and Notation. Wikipedia]
The business process modeling diagram example "Cab booking public process - Collaboration BPMN 2.0 diagram" was designed using the ConceptDraw PRO diagramming and vector drawing software extended with the Business Process Diagram solution from the Business Processes area of ConceptDraw Solution Park.