This page describes the daily work with the core hierarchy: a scope schema yields a scope, under which engagements and cases live, where activities are recorded.
Create a scope
A scope is the customer-specific instance of a scope schema.
-
Open the Scopes (Scope List) and create a new one.
-
Choose the underlying scope schema – items, process, and attributes are inherited.
-
Adjust items, quantities, and prices via the Items part (field Unit Price overrides, 0 = BC price finding; Duration (Hours) sets a default duration; Auto Create Activity creates an activity on the case automatically).
-
The primary customer is derived automatically from the first billable relationship.
Key fields: description, scope schema no., process no. + current step, active flag, billing profile and invoice texts, plus calculated counters and totals (number of engagements/cases, Total Amount).
Create an engagement
An engagement groups related cases under a contract. It is optional – cases can also exist without an engagement.
-
Open the Engagements (Engagement List) and create a new one.
-
Link it to a scope (Scope No. field) – description and primary customer are derived.
-
Set start/end date and, if needed, process and billing profile.
-
Add the responsible parties via relationships (e.g. key account manager, client).
Create and run a case
A case is the actual unit that is managed and billed.
-
Create a case – within an engagement or standalone.
-
The case inherits scope, process, dimensions, and billing settings from its context.
-
Add parties (see Parties and relationships).
-
Record activities (see Activities and time tracking).
-
The case starts at the initial process step.
The case card at a glance
The case card bundles: header and context (engagement, scope, primary customer), process and current step, attributes, activities (subpage), relationships, tasks, and statistics/billing factboxes. A guided tour (teaching tips) points to process, attributes, activities, and relationships when needed.
Advance a process step
Users with the Proceed in Process capability advance the case to the next step via an action. Before the change, the app checks:
-
Mandatory attributes – empty required attributes block the change.
-
Approval gate – if "Require All Activities Approved" is set on the step, all activities must be approved.
Each step change raises integration events to which tenant-specific automation can attach.
Change context (reassignment)
Via the Case Context page, a case can be moved to a different engagement or scope – if the Manage Context capability is present. Already posted case ledger entries can be reassigned to the new context (reversal + repost) so that totals stay correct. See Billing and case ledger.
Cancel
A case or engagement carries a Cancelled flag. Cancelling requires the Cancel Case capability. Cancelled cases are excluded from billing.
Change log
If Enable Case Change Log is on, the app logs changes to cases, activities, relationships, and attribute values. View via the Change Log action on the case card or centrally from the setup page.