Body
Frequently Used Terms for ProcessMaker
Case
A case is an instance when a user initiates a process, which may consist of one or more requests. In simple processes, a case will include just one request, but in processes with additional components like sub-processes, a single case may encompass multiple requests.
Collection
A collection is a set of data records (eg. rows in a table) which can be created.
Dashboard
A dashboard displays important information and key metrics about a process and its requests. Processes may have multiple dashboards to display relevant information about the process to different types of users. Dashboards may contain links to the Request Form if there is a Web Entry start option, and other relevant links for the process.
Group
A group is a set of users who can be selected to start and/or cancel requests associated with a specific process, assigned tasks, sent notifications, given access to a dashboard or assigned additional permissions.
Participant
A request participant is a user who interacts with and participates in requests, their tasks, and/or collections within ProcessMaker. The Request Starter is a participant. Any user who is assigned a task or completes a task in the request will also be listed as a participant.
Process
A process is a set of steps and decisions to complete a particular goal, often as efficiently as possible. It may involve users or be completely automated through scripting and can integrate with external third-party systems and legacy applications to extend their functionality.
Process Manager
A process manager is responsible for monitoring a specific process and troubleshooting request routing incidents within a process workflow. This role is necessary when a workflow is interrupted due to inactive user accounts, unconfigured accounts, or when a user's account status affects task assignment. The process manager may also be the first to notice when unexpected user input causes a problem, or an unhandled scenario causes a request to no longer make progress. The process manager manually reassigns tasks to active users or delegated users to ensure the continuation of the workflow when routing is the cause of the issue. The process manager may also submit a Process Maker Incident ticket if an active request is effected that they are unable to resolve or a ProcessMaker Service Request to make updates to a process.
Process Model
A Process Model is a visual representation of how the process works. ProcessMaker uses this model as a blueprint to carry out instances of that process, which are called requests. The Process Model should map out the routes for all possible pathways a request might follow, including the entry points and exit points for the process.
Project
A project is a way to organize assets and collaborate with others to create and manage processes. It typically contains at least one process and all of the screens and other assets involved in the process.
Request
A request is a single instance of a process, containing all the details of that specific instance and routing details based on the process model. A request is linked to a single process. Cases may included multiple requests when a request of a parent process initiates a new request from a sub process.
Requester or Request Starter
The user who initially started the request either from Web Entry or through the ProcessMaker Platform.
Saved Search
A Saved Search in the ProcessMaker Platform enables users to save and share search parameters associated with Requests, Tasks, and Collections. This feature allows users to quickly access and utilize saved searches efficiently. Furthermore, Saved Searches can be leveraged to create charts for analytics reporting and to schedule automated reports for specific processes.
Screen
A screen is like a building block for making interactive interfaces. These interfaces can be for things like forms, displays, dashboards, emails, or conversations. Screens come in different types, like Form-type, Display-type, Email-type, and Conversational-type. Each type does a specific job in a process and needs certain permissions to be created and viewed.
Self Service
Refers to a task that is NOT assigned to a user but is placed into a queue for a specified Group of users. Like a shared to-do list, any available user in the group can claim and complete a task as it comes in.
Task
A task represents an activity or work a request participant must do in ProcessMaker. This activity can be providing information, reviewing, approving, deciding, or other actions taken by a user completing a form. Tasks can also occur offline in the world, such as moving inventory containers or making a phone call.
Web Entry
Web Entry allows users to start requests or complete tasks through a URL link that can be emailed or published on a website. If authentication is required, users will be redirected to log in to ProcessMaker with their Drake credentials after clicking on the link.
Workflow
A workflow is like a carefully designed series of steps and decisions to achieve a specific goal. It can be done by people or completely automated and might connect with other systems. A workflow is shown as a process model, a visual guide to how the process works. ProcessMaker uses this model as a blueprint to carry out instances of that process, which are called requests.