Quickstart

Administrators can configure custom Lifecycles to govern the allowed statuses and transitions for different types of records, such as engagements or quotes.

In-Depth

By default, Servantium provides a standard set of active and inactive statuses. However, you can map custom Lifecycles to one or more collections (like engagements and quotes) to enforce exact workflows and terminology for your organization.

How Lifecycles Work

A Lifecycle consists of:

• Applied Collections: The record types (e.g., engagements, quotes) governed by this lifecycle. A single lifecycle can be mapped to multiple collections simultaneously.
• Statuses: The allowed states for a record (e.g., “Draft”, “In Review”, “Active”, “Completed”). Exactly one status must be marked as the default. The backend automatically manages this uniqueness—if you mark a new status as the default, any previously default status is automatically unmarked. If a status is deleted, the backend automatically removes any associated transition paths to maintain workflow integrity.
• Transitions: The allowed paths between statuses (e.g., you can transition from “Draft” to “In Review”, but not directly to “Completed”).

When you create a new record in a mapped collection, the backend automatically assigns it the default status defined in its Lifecycle.

Enforcing Workflows

To ensure data integrity, users cannot manually edit the status field on a record. Instead, the backend enforces status changes through Lifecycle actions.

• With Transitions: If a Lifecycle has transitions defined, users must select a valid transition action to move the record from its current status to the next logical step.
• Without Transitions: If no transitions are defined, users can move the record to any other valid status within the Lifecycle.

Related

• Engagements
• Roles & Permissions