A scope schema is a reusable product template: it defines which items (services), which process, and which attributes apply to scopes created from it. A schema is the abstract template; a scope is the customer-specific instance.
Scope schema
|
Field |
Description |
|---|---|
|
No. |
Unique number from the number series. |
|
Description |
Template name, e.g. "Assessment Standard", "Coaching Package". |
|
Process No. |
Default process applied to cases under this schema. |
|
Active |
Whether the schema is available for new scopes. |
Scope schema items
Via the Items part you record the included services:
|
Field |
Description |
|---|---|
|
Item No. |
BC item representing the service. |
|
Item Description |
Item description. |
|
Quantity |
Default quantity. |
|
Duration (Hours) |
Default duration in hours. |
|
Auto Create Activity |
When on, an activity is created automatically from this item when a fresh case/scope is created. |
|
Sort Order |
Display order. |
Link to the BC item
Through the item extension, every BC item carries a Scope Schema No. VTO field that can link it to a scope schema, so items can be assigned to their matching templates.
Attributes on the schema
Via the Assign Attributes action on the schema card, you bind attributes to the schema. These flow through the resolution chain to the scopes and cases created from it (see Attributes in Ventoo Case Management).
From schema to scope
A scope is created from a schema and inherits its items, process, and attributes. It can be overridden per customer (quantities, prices, attribute values). Creating and running scopes, engagements, and cases is described in Scopes, engagements, and cases in Ventoo Case Management.
Tip: Set up scope schemas once as templates. Recurring offerings are then created quickly and consistently as scopes from the matching schema.