Loading demo data

The Demo data screen (menu Administration › Instance and operations › Demo data) fills the instance with a consistent sample set for the enabled modules: published, orderable catalog, knowledge base, objects, tickets… It is meant for presentations, training and trials. It is reserved for Administrators.

Availability

Demo data is only available on a non-production instance: an instance declared non-production in the licensing screen, an instance in evaluation, or an instance that has not yet received any license. On a production instance, the menu entry does not appear and the screen explains why.

Loading the set

1. Choose the Demo language: item, room and supplier names… are created in this language.
2. Choose the Demo account address: a pattern in which {local} is replaced by each person's local part, for example {local}@example.com (test mail server) or test+{local}@example.com (everything lands in a single mailbox). Account passwords are random and never displayed.
3. Run all runs every step, or Run a single step of the list.

The table gives the Result of each Step: Done, Failed (with details) or Skipped, with a message (for example the number of items created).

Loading can be replayed: nothing is duplicated and customizations are not overwritten. Replaying it in another language keeps what already exists.

CRM step: it relies on the sales team created by the Users and groups step; run before it, it is Skipped and completes on the next run. If a record cannot be created, it keeps none (Failed, with details). The person who runs it receives the "CRM administrator" role to see the data created. Demo orders are never sent to billing.

Monitoring step: it creates two monitoring sources and twelve alerts in every state, linked to the equipment of the CMDB step, and an upcoming maintenance window. It also creates a "Create an incident" processing rule for critical alerts; two critical alerts from the application server, received after this rule, open a single incident (the second joins the first one's; without the CMDB step, each opens its own). The incident appears in the Service Desk, assigned to the demo Infrastructure team, and on the page of both alerts. Alerts received before the rule have no incident. Without the Service Desk module, the rule is not created and both alerts stay open, without an incident. The step creates nothing more once its sources exist: to get the rule and the incident on an instance that is already loaded, use Run everything again (see below).

Purging business content

The Danger zone — purge business content deletes all business content of the instance (tickets, requests, CMDB objects, changes, projects, stock, purchasing, CRM accounts, opportunities and orders, demo accounts…), not only what the demo created. Kept: configuration (groups, permissions, menus, translations, templates, settings), your account and every account not created by the demo.

1. Type the instance name shown next to the field (the host name of its address).
2. Purge all business content deletes the content; Run everything again deletes it and then reloads every step, in the language and with the address pattern chosen above.

A Purge report states, for each step, N item(s) deleted. If the name typed does not match, nothing is purged.

Purging is irreversible: back up the database first.