This is where you control how records move through your workflow.
Accessing Pipeline Configuration
Prerequisites: Admin or Superadmin role required. Custom Objects with pipelines require the relevant plan tier — if you don't see Custom Objects in your list, check your subscription under Settings → Billing.
Go to Settings → Pipeline Configuration. Only admins and superadmins can access this page.
You'll see a list of all objects grouped into two sections:
System Objects — Jobs, Visits, Clients, Requests, Estimates, Invoices, Products/Services
Custom Objects — Any custom objects you've created with pipelines enabled
Each row shows the object name, description, and the number of stages and transitions configured. Click any object to open its pipeline settings.
Table View and Graph View
At the top of the page, you can switch between two views:
Table View (default) — Lists all objects with their stage and transition counts
Graph View — A visual data model diagram showing all objects and their relationships as a network. You can toggle between horizontal and vertical layout, zoom in/out, and click any node to jump to that object's pipeline settings. A legend at the bottom shows relationship types: One-to-Many (cyan), Many-to-One (green), Many-to-Many (amber), and Action (orange dashed line).
Managing Stages
When you open an object's pipeline settings, the Stages tab is the first thing you see. Each stage has the following properties:
Field | Description |
Label | The display name users see (click to edit inline) |
Value | The internal slug identifier |
Color | A color picker to assign a visual color to the stage |
Category | One of three categories: To Do, Doing, or Done |
To add a stage: Click Add Stage at the bottom of the list, enter a label, pick a color and category.
To reorder stages: Use the up/down arrow buttons next to each stage.
To delete a stage: Click the trash icon. System stages (marked with a badge) cannot be deleted. Custom stages can only be deleted if no records are currently in that stage.
Tip: System stages cannot be deleted. Custom stages can only be removed when no records are currently in that stage — move or reassign records to a different stage first before deleting.
Managing Transitions
The Transitions tab controls which stage changes are allowed. Each transition specifies:
Field | Description |
From Stage | The starting stage (or "Any" to allow from all stages) |
To Stage | The target stage |
Button Label (optional) | Custom text for the transition button |
Required Capabilities | Which user capabilities are needed to perform this transition. Capabilities are tied to user roles — see Team Roles & Permissions for the full list of capabilities per role. |
Conditions | Optional rules for when the transition is available |
Click Add Transition to create a new one. Select the from and to stages, optionally set a button label and capabilities, then save.
Computed Rules
The Rules tab is where you set up automation. FieldCamp supports seven types of computed rules:
Rule Type | What It Does | Example |
Status Propagation | Moves a parent to a stage when children reach a stage | All Visits complete → Job moves to "Completed" |
Child Creation | Creates child records when a parent reaches a stage | Job scheduled → Visit records auto-created |
Action | Triggers actions on other objects during transitions | Stage change → Update fields on a target object |
Cascade Delete | Controls what happens to related records on deletion | Delete Job → Cascade to Visits → Cascade to checklists |
Validation | Enforces constraints before create/update | Required fields, min/max values, format rules |
Side Effect | Triggers background actions at a stage | Emit workflow events, sync integrations, recalculate data |
Auto-Calculation | Sets parent field values from child data | Job total = sum of line item amounts |
1. Status Propagation
Automatically moves a parent record to a specific stage when its child records reach a certain stage. For example: when all Visits for a Job are marked "Complete," move the Job to "Completed."
2. Child Creation
Automatically creates child records when a parent reaches a stage. Supports three generator types:
Single — Creates one child record
Date Range — Creates one child per day in a date range
Recurrence — Creates children on a schedule (daily, weekly, etc.)
3. Action
Triggers an action on another object when a stage transition occurs. Can update fields on a target object or create records.
4. Cascade Delete
Defines what happens to related records when a record is deleted. Two strategies:
Hard delete — Permanently removes related records. They cannot be recovered.
Soft delete — Marks related records as deleted but preserves them in the database, allowing recovery.
Supports nested cascades (e.g., deleting a Job cascades to Visits, which cascades to Visit checklists).
5. Validation
Runs before a record is created or updated. Enforces constraints like required fields, min/max values, format patterns, and custom rules. If validation fails, the save is blocked with an error message.
6. Side Effect
Triggers background actions when a record reaches a stage. Types include updating child records, emitting workflow events, recalculating related data, and syncing with integrations.
7. Auto-Calculation
Automatically sets a parent field value based on child record data. For example: calculate a Job's total from its line item amounts, or set a completion percentage based on finished tasks.
Other Tabs
Each object's pipeline detail page also includes:
Relationships — Shows how this object is linked to other objects (read-only view)
Fields — Lists available fields for use in rule configurations and field mappings
Saving Changes
When you make changes, an unsaved changes indicator appears in the header. Click Save to apply all changes at once. All stage, transition, and rule changes are validated on save — if something is invalid, you'll see an error notification.
FAQ's
What is the difference between hard delete and soft delete in cascade rules?
What is the difference between hard delete and soft delete in cascade rules?
Hard delete permanently removes related records when a parent record is deleted — they cannot be recovered. Soft delete marks related records as deleted but preserves them in the database, allowing recovery if needed. You configure the strategy per cascade rule in Settings → Pipeline Configuration → [Object] → Rules → Cascade Delete. For example, if you delete a Job with a hard delete cascade, all linked Visits and Visit Checklists are permanently removed. With soft delete, they're hidden from the UI but can be restored.
Can I delete a system stage in FieldCamp?
Can I delete a system stage in FieldCamp?
No. System stages (marked with a badge in the Stages tab) are built into FieldCamp and cannot be deleted. You can only delete custom stages that you've added, and only if no records are currently in that stage. If you need to remove a custom stage that has records in it, first move or reassign those records to a different stage, then delete the empty stage.
How do I automatically complete a Job when all its Visits are done?
How do I automatically complete a Job when all its Visits are done?
Use a Status Propagation rule. Go to Settings → Pipeline Configuration → Jobs → Rules tab → Add Rule → Status Propagation. Configure it so that when all child Visits reach the "Complete" stage, the parent Job automatically moves to "Completed." This eliminates the need for admins or dispatchers to manually update Job status after the last Visit is finished.
Who can access Pipeline Configuration in FieldCamp?
Who can access Pipeline Configuration in FieldCamp?
Only users with Admin or Superadmin roles can access Settings → Pipeline Configuration. Dispatchers, Field Technicians, and other roles cannot view or modify pipeline settings. If you need to grant someone access, an admin must upgrade their role first.