Read the demonstration context
- 1
Partner Account identifies the commercial organization for the demonstration.
- 2
Branch locates the activity within the responsible operation.
- 3
Sale Executive identifies commercial ownership of the next step.
- 4
Resource assigns the person who will perform or support the demonstration.
- 5
The form covers the demo record; package selection happens on a document line, not here.
The Product Demo record places a demonstration within a company, branch, sales owner and performing resource. Those fields make the activity schedulable and accountable while keeping its result connected to the customer relationship rather than in an external calendar.
Before saving, confirm who owns the commercial next step and who will conduct the demonstration. Afterward, record configuration decisions, objections, outcome and follow-up against the opportunity so the demo becomes evidence for qualification and product fit.
Some products aren't a single line — they are a package whose components the customer chooses: variants, accessories, included services. xMatix models this on the item master and lets you configure the package directly on the document you are working — an opportunity or quote in CRM, and equally an order, invoice, purchase order or requisition elsewhere. Separately, CRM books product demos from the opportunity so the customer can experience the product before deciding.
How packages are defined
An item flagged as a package carries a list of components. Each component names the component item (or specific SKU) and its selection rules:
| Rule | Effect |
|---|---|
| Mandatory | The component must be included — it can't be deselected |
| Pre-selected | Included by default, but removable |
| Quantity, min/max | The default quantity and the editable range |
| Quantity editable | Whether the user may change the quantity at all |
| Feature grouping | Components group under features (e.g. Color, Accessories) for presentation |
| Applicability | A component can apply only to sale, service or purchase documents |
| Partner scoping | A component can be limited to specific partner accounts or account groups |
Because of applicability and partner scoping, the same package can legitimately offer different components on a quote than on a purchase document, or to one dealer than another.
Configuring a package on a document
On an opportunity or quote, configuration works per line:
- Get Configurable Items lists the document's lines whose item is a package — these are the lines that can be configured.
- Get Package Configuration for one line returns that package's applicable components, grouped by feature, with the line's current selections and quantities, priced from the document's price list.
- Apply Package Configuration writes your selection back: selected components become (or update) component lines nested under the package line; deselected components' lines are removed.
The configured components live as real document lines, so totals, taxes and downstream documents (the order generated from the quote) all see exactly what was chosen. Re-opening the configurator shows the current state and can be re-applied any time before the document moves on.
Product demos
On an opportunity, Book Appointment opens the demo booking flow: pick the branch, pick a date and time slot from the branch's available capacity, and confirm. Confirming creates a product demo record booked against the branch's slot capacity — a slot that is full is refused, and moving the demo to another date or slot (or cancelling it) releases the old slot and reserves the new one. Demos can also be booked onsite at the customer's address instead of at a branch.
The demo record carries the appointment (date, time, slot), the customer and partner accounts, the item being demoed and optionally the specific demo asset used, plus confirmation and cancellation state. After the demo, capture the outcome on it — status, rating, the customer's voice and remarks — so the opportunity reflects how it went.
Common questions
Why does the configurator show nothing for my line?
The line's item isn't marked as a package, or none of its components apply in this context — components can be scoped to sale/service/purchase documents and to partner accounts or groups, so a component list that exists on the item may still be empty for this document and partner.
Where do component prices come from?
From the document's price list, the same way ordinary lines price — see pricing, discounts and taxes. The configurator shows prices as of the document's pricing context, so a repriced document reprices its components too.
Is configuration only for CRM documents?
No. The same configure actions exist on sales orders and invoices, and on purchase orders and requisitions — the package definition is on the item, so any document that carries the item can configure it. This page covers the CRM usage; see the Sales and Procurement sections for those documents.