LogoLogo
User DocsAPI Docsatfinity.swiss
  • 🚀Atfinity: No-Code Process Automation
  • Guides
    • Getting Started
      • Introduction
      • 1. Create Ontologies and Roles
      • 2. Create Information
      • 3. Create and Configure a Document
      • 4. Create a Rule
      • 5. Create a Process
      • 6. Put Live
      • Summary and Next Steps
    • Advanced Topics
      • Extending a Workflow
      • Customizing Names of Cases and Instances
      • Automatically Calculating Information Values
      • Using Built in Integrations
    • Troubleshooting
      • Why is a question not asked?
      • Why is a question asked?
      • The value of my calculated field has a strange format
      • Why is my Proof never asked for?
      • Why is my Rule not executed?
      • Why are some options missing in a dropdown?
      • Case Errors
    • Glossary
      • Case
      • Process
      • Workflow
      • Ontology
      • Instance
      • Role
      • Information
      • Document
      • Document Section
      • Document Template
      • Rules
      • Scheduled Rules
      • Information Types
      • Tab
      • Category
      • Taxonomy
      • Proof
      • RuLa Functions
      • Constants
  • Rule Language (RuLA)
    • ℹ️What is RuLa?
    • Declarations
      • is
      • is with where
      • is all
      • is all with min max
      • Role Choices
    • Expressions
    • Operators
      • Boolean Operators
        • =
        • !=
        • >
        • >=
        • <
        • <=
        • and
        • and then
        • not
        • or
        • or else
        • matches (~=)
      • Date Operators
        • NOW
        • IS_DATE
        • TODAY
        • FORMAT_DATE
        • DAYS
        • WEEKDAYS
        • ADD_DAYS
        • ADD_WEEKDAYS
        • ADD_MONTH
        • ADD_YEARS
        • SUBTRACT_YEARS
        • AFTER
        • DATE_EQUAL
        • DATETIME_EQUAL
        • AFTER_EQUAL
        • BEFORE
        • BEFORE_EQUAL
        • DAYS_AGO
        • MONTHS_AGO
        • YEARS_AGO
      • Known Operators
        • unknown
        • known
        • SNEAKY
        • AVG_OF_ANY
        • LIST_OF_ANY
        • MAX_OF_ANY
        • MIN_OF_ANY
        • SUM_OF_ANY
        • CONCAT_OF_ANY
        • UNION_OF_ANY
        • JOIN_OF_ANY
      • List Operators
        • [ , ] (create)
        • [] (access)
        • in
        • not in
        • contains
        • contains any
        • contains only
        • COUNT
        • SORT
        • CUSTOM_MAX
        • REVERSE
        • FIRST_ELEMENT
        • ALL
        • SOME
        • UNION (or |)
        • SET_DIFFERENCE
        • INTERSECTION
        • MAP
        • FILTER
        • FILTER_FALSE
        • FILTER_UNKNOWN
        • SET
      • Dictionary Operators
        • {} (create)
        • [] (access)
        • in
        • keys()
        • FLATTEN
      • Mathematical Operators
        • + - / *
        • %
        • **
        • //
        • AVG
        • CEIL
        • FLOOR
        • MAX
        • MIN
        • ROUND
        • SUM
        • SUM_PRODUCT
        • SQRT
      • String Operators
        • LEN
        • LOWER
        • UPPER
        • TRIM
        • TRIM_LEFT
        • LEFT
        • RIGHT
        • SLICE
        • REPLACE
        • REPLACE_CHARS
        • format
        • calculated_name
        • CONCAT
        • markdown_table
        • make_filename
        • JOIN
        • uuid
      • Special Operators
        • :=
        • ensure
        • get_attr
        • get_translated_attr
        • has_attr
        • get_properties
        • instances
        • instances_exist
        • is
        • ontology
        • Translate (.$)
        • translate_string
        • roles
        • self
        • name_and_log (debug)
    • Conditional Expressions
      • case
      • if-then-else
      • switch
    • Comments
    • Information about the case
    • Accessing the outcome instance
    • Information about documents
    • Recipes
  • Document XML (ADX)
    • ℹ️What is ADX?
    • ADX Elements
      • Body
      • Text
      • Image
      • Columns
      • Field
      • Checkbox
      • Table
      • Rect
      • Line
      • Space
      • KeepTogether
      • Template
      • Style
      • Page Number
      • QR Code
      • HR Code
    • Jinja Templating
      • Instances
      • Case Meta Information
      • Custom Translations
      • Functions
      • Jinja filters
    • Font support
  • API
    • ℹ️What is the Atfinity API?
    • Generate API Keys
    • API Documentation
    • Calling your APIs within Cases
    • External Data Sources (e.g. CRM)
  • Deploying
    • Deploying on-site
      • Kubernetes
      • Docker Compose
    • Management commands
    • Security Logging
    • LDAP User Backend
    • Single Sign On
  • Integrations
    • Avaloq
    • Worldcheck
  • Releases
    • Release Notes
      • Version 11.x
      • Version 10.x
      • Version 9.x and earlier
    • Release Schedule
Powered by GitBook
On this page
  • Step 1: Create a Document
  • Step 2: Select a Document Type and choose a Template
  • Step 3: Write a Document Condition
  • Step 4: Add Boxes to the Document

Was this helpful?

  1. Guides
  2. Getting Started

3. Create and Configure a Document

Previous2. Create InformationNext4. Create a Rule

Last updated 2 years ago

Was this helpful?

In Atfinity, are the place where information can be collected. They are the central part of a process. Every document has a condition. If the condition is true the document will be part of a and with it all the information that is on the document.

For our scenario, we need a document that becomes part of a case as soon as a person would like to open a new account, or in other words, as soon as we deal with a contract and a person. On it we will place all the information necessary to open an account.

Let's start by first creating a new document and then configure it step by step:

Step 1: Create a Document

We know what to do by now: We give the document a key and a name in order to create it. Let's write 'individual_account_opening_form' for the key and 'Form for opening an individual account' for the name.

Step 2: Select a Document Type and choose a Template

In Atfinity, there are three document types. The PDF type uses an actual PDF-Form, which is uploaded, as a template. Information that has been collected in a case will be printed on the PDF-Form at the positions we defined. A Smart Document also prints the collected information. However, it only prints the information which is available and formats itself accordingly. A Group Documents is used to bundle several documents.

For our process, we choose Smart Document as document type.

Next we need to define a template for the smart document. It acts as the background on which the information will be printed.

Step 3: Write a Document Condition

We now have to specify under what condition the document should come into action. For our scenario, we write the following condition:

c is Contract
p is Person

This means that whenever we open an account and create a new contract with a person who is the account holder, the condition is met and all the information placed on the document will be asked.

Step 4: Add Boxes to the Document

So far we have a document which will come into action once we start a new account opening process. Now we need to make sure that we place the information we have created on that document. Only then will we be asked to provide the actual information like first and last name.

When we add a box to the document we choose it to be of type text. Every box we add needs a reference which points to the information we would like to have on the document. For our first information 'First Name', we write p.first_name. The p is an ontology reference and stands for 'Person', the ontology the information belongs to. We have defined it in the document condition. And first_name is the key of the information we are referring to.

Let's do the same for the other information 'Last Name' (p.last_name) and 'Date of birth' (p.date_of_birth).

That's it. Our document is now ready. Every time a person becomes part of a case, this document will become part of the case as well and all the information on it will be asked.

Well done! Configuring a document is often the most laborious part of a configuration. Now, let's go to the next article to .

documents
case
Create a Rule