Skip to content
MirrorFirm

Which elements should we request in a generated set-up sample?

A checklist of the record types, links and rules worth asking for so a sample can support both training and evaluation, from approvals through to the event log.

Before requesting a sample, confirm which of these elements your customers need the generated set-up material to contain.

- **Approval records:** decisions with conditions, validity dates and the policy reference behind them, so every set-up step can be traced to its source decision. - **Party records with match outcomes:** new, matched, merged and rejected parties, including near-duplicates that call for judgement rather than a simple rule. - **Account or agreement records:** product, terms, status and the link back to the approval, with some cases that change after the account is opened. - **Service or entitlement state:** what is switched on, what is pending and what is blocked, with a stated reason for each block. - **Open tasks by role:** follow-up work assigned to billing, field, documents or compliance roles, each with an owner and a status. - **Policy text and structured rules:** readable guidance plus fields a script can use to score outputs against the same rules. - **Event log:** timestamped state changes with the acting role, so a sequence can be replayed, audited or turned into a training trace.

Asking for these elements up front produces a sample you can test thoroughly, rather than a set of finished accounts with no trail.

Audience:
Licensed resellers
Content type:
Checklist
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Account setup