Which record types, documents and tools can a mismatch task pack include?
Answers common questions about record pairs, linked documents, policy text, interactive tools, cases with no fix, domain mix and the generated status of the content.
**Which record types can a release cover?** Any pair of records that should agree in a business process: payments and ledgers, claims and payouts, orders and shipments, rosters and timesheets, stock and sales. Agree the pairs you need during scoping.
**Can cases come with linked documents?** Yes. A release can include supporting items such as emails, case notes, remittance advice or exception reports, generated to match the records they refer to.
**Can policies be included?** A release can include policy text and structured rules, such as tolerance bands and approval limits, so each case has a defined correct action.
**Can we get an interactive environment?** A simulated environment can expose actions such as search records, view history, post reversal, raise adjustment and escalate. The environment resets to a known state so runs can be repeated.
**Do all cases have a fix?** Not necessarily. A task pack can include cases where the right outcome is to escalate or to leave records unchanged, and these should be labelled as such.
**Is the content real?** No. It is generated. Customers should inspect grounding and disclosure risk, and you should not present it as real business records.
**Can we request a domain mix?** A buyer can ask for a mix across finance, insurance, utilities, logistics, healthcare administration or retail. Scope this in a pilot.
Scope record pairs, documents, policies and tools separately, so each part of the release matches what your customers will actually test.
- Audience:
- Licensed resellers
- Content type:
- FAQ
- Buyer question:
- What can be generated
Content release: r-a220eb6e099b243b
Related questions
- What would a generated freight invoice versus proof-of-delivery task contain?
- What file layout and schema would a generated case set use?
- Can a pack include policies, tolerances and escalation rules, not just records?
- Which record elements should a dataset for this workflow include?
- What records and relationships can MirrorFirm generate for this workflow?
- What fields and file formats can a generated mismatch pack use?