People and organizations are kept in Ventoo Case Management as parties and linked to cases and engagements in a role via relationships. Visibility and billing also flow through them.
Parties
A party is a stable reference to a BC master record. The party type determines which master record is referenced:
|
Party type |
BC master record |
|---|---|
|
Customer |
Customer |
|
Contact |
Contact |
|
Employee |
Employee |
|
Vendor |
Vendor |
|
Resource |
Resource |
Key fields: display name, first/last name, email, phone, Shortcut (short code), and Blocked. Display name and contact data are cached from the master record and refreshed on create/modify. Manage via the Party List with views such as Active, All, Blocked, Service Providers, Customers, Contacts.
-
Add Customer/Contact – actions on the party list create parties directly from customers or contacts.
-
Block/Unblock – a blocked customer cascades to block its contact and vice versa; blocked parties are filtered out of planning, factboxes, and lookups.
-
Business relation sync – contacts with the configured business relation (
CASEMGT) are kept in sync with the party list.
Relationships
A relationship links a party in a role to a case or engagement. At least a case or engagement number must be set.
|
Field |
Description |
|---|---|
|
Party Id / Party Display Name |
The party. |
|
Role Id / Role Code / Role Description |
The role in this link. |
|
Engagement No. / Case No. / Scope No. |
Assigned context. |
|
Billable |
Marks the relationship as billable. |
|
Bill-to Customer No. / Name |
Billing recipient (resolved from the party). |
|
Billing Percentage |
Share billed to this customer. |
Billability and primary customer
-
When you set Billable, the bill-to customer is resolved automatically from the party (customer directly, contact via the business relation).
-
The billing percentage can be set only on billable relationships and must be > 0. The sum per case must not exceed 100% (checkable via Validate Billing).
-
The primary customer on case, engagement, and scope is derived automatically from the first billable relationship and is read-only.
Hierarchical inheritance
Relationships inherit their context: on create/modify, scope and engagement numbers are taken from the parent entities. So it is often enough to record a party at the engagement level.
Party summaries
Cases, engagements, and scopes carry calculated summary texts and counters: Service Providers, Customers, and Contacts, plus their counts. They appear on list pages and factboxes and support quick filtering. Role shortcuts and the Hide on Planning Lists flag control which roles appear in these columns. After changes, the setup action Rebuild Party Summaries refreshes all texts.