Processes (Cases)

A process, often called a case, is a unit of work with a beginning and an end: a claim to adjudicate, a vendor to onboard, a lease renewal, an application to review, an order to fulfill. Every process is attached to a parent record (a contact, an organization, an asset, or another process), so the work is always found, secured, and reported on in context.

The process is the hub that ties a piece of work together:

• Workflow. Opening a process can launch its workflow automatically, chosen by a fixed template or by rules based on the process’s data.
• Costs. A process can create its own cost ledger, so fees and expenses are tracked against the work that produced them.
• Documents, tasks, messages, contacts, and scores attach to the process like they attach to any record, so everything about the work sits in one place.
• Responsibility. Each process records who owns it: an assigned person and organization, a vendor, and a client, with a contact person for each side.
• Lifecycle. A process has open and close dates and reasons, a due date, a priority, and a status. Templates can enforce how a process closes and what closes with it.
• Partner security. Assigning a vendor or client to a process grants them access to that process, and only that process, through row-level (extranet) security.

Key concepts

Concept	In QBO	What it does
Process	ProcessObject	One piece of work, bound to its parent through Object and ObjectID.
Process template	ProcessTemplate	Defines a kind of process: what it applies to, which workflow and ledger it starts, who may work it, and how it closes.
Current workflow	CurrentDecisionID	The workflow the process launched when it opened (see Workflow).
Cost ledger	CostLedgerID	The ledger the process created to track its costs (see Ledgers).
Contract	Contract	An agreement between a client and a vendor, with effective and expiry dates, listing the process types the vendor is engaged for.

Choose your view

Use the buttons under the page title. End user covers opening, working, and closing a process; Power user covers process templates and closing rules; Developer covers the API.

Walkthroughs that use this

• Organize a policy’s claims, renewals, and onboarding as processes