Glossary

Every object you configure in Atfinity has an entry here, defining what it is and showing one example. Where the mechanics run longer than a definition, the entry links on to the guide that covers them.

Who and what a case is about

• Ontology: the template for an actor in your contracts, such as a person or a company.
• Instance: one specific occurrence of an ontology.
• Role: the relationship between two ontologies.
• Relationship Information: an information type whose value points at other instances.

Running a process

• Process: the configuration a case is based on.
• Case: what you create every time you start a process.
• Case Errors: what Atfinity records when evaluating a case fails.
• Workflow: the states a case moves through before the process reaches an outcome.
• Wizard: an external step-by-step form for someone with no access to the Case Manager.
• Put Live: publishing your configuration draft so cases start using it.
• Comments: notes users leave on a case.

Asking for information

• Information: the smallest building block, one thing you ask for.
• Information Types: the formats a value can be entered in.
• Structured Information: several sub-fields grouped together and repeated.
• JSON Information: a whole JSON object or array held in one field.
• Taxonomy: a list of options a user chooses from.
• Proof: a document that verifies or supports information given in the case.

Producing documents

• Document: where information is collected and printed.
• Document Section: a collection of information fields on a document.
• Document Template: the PDF a Smart Document prints onto.
• Booklet: a collection of documents handled as one.

Automating decisions

• Rules: the conditions and actions that guide a process.
• Scheduled Rules: rules that run later, or repeatedly.
• RuLa Functions: an expression you name once and reuse.
• Constants: a name with a value assigned to it.
• AI Case Check: a pattern described in plain language instead of as a hard rule.
• Manual Instance Actions: rule logic a user runs on demand on one instance.
• Button Layout Element: a button in a case that runs rule actions.

What users see

• Page: one screen in the Case Manager.
• Tab: one entry in the horizontal navigation near the top of a case.
• Category: the grouping that arranges information fields within a tab.
• Insights Page: a page showing a dashboard instead of a list.
• Instance Tree Page: a page listing the instances of one ontology and what hangs below them.
• Platform Notifications: a message every user acknowledges before carrying on.

Access

• Users and Permissions: access levels, user roles and user groups.