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: Select the ontology and choose key and name
  • Step 2: Define the information type
  • Step 3: Add the information to a category

Was this helpful?

  1. Guides
  2. Getting Started

2. Create Information

Previous1. Create Ontologies and RolesNext3. Create and Configure a Document

Last updated 2 years ago

Was this helpful?

is the smallest building block in Atfinity. The probably simplest example of an information is the 'First Name'. In our scenario, we will need to be able to collect the first name, last name and the date of birth from every new client as well as the account type of the opened account.

The next steps will guide through the creation of the first piece of information, the first name. That gives us the general knowledge of information creation. The creation of the other pieces of information will follow a similar procedure with minor differences, which will be pointed out at the end.

Step 1: Select the ontology and choose key and name

We would like to create the information 'First Name'. It is important to understand that information always needs to be connected to an ontology. In our scenario, only the person who opens an account has a first name, the contract does not. So we link the information to the corresponding ontology (in our case a 'Person').

Similar to when we created ontologies and roles we need to give our information a key and a name. We write 'first_name' for the key and 'First Name' for the information name.

Step 2: Define the information type

The defines what form the information has. An information could, for example, be a number or a date. The information 'First Name' is of type 'Text (Single Line). This means that we will be able to type the first name of the client into a text field.

Step 3: Add the information to a category

help to group information that's usually asked together. It makes sense that an information like a first name goes into a 'Personal Details' category, together with the last name and the date of birth. The information 'Account Type' however, should belong to the category 'Account Details'.

Now that we have created the information 'First Name' we are able to create the other pieces of information we require (account type, last name and date of birth):

  • When creating the information for the last name, be sure to give it another information key ('last_name') and information name ('Last Name').

  • For the date of birth information, information type should be 'Date'. That way Atfinity knows that this information is a date and can tread it as such.

  • When it comes to creating the information for the account type, keep in mind that this information concerns the contract. We therefore need to select 'Contract' as an outcome ontology. The information type of this information is 'List (Single Answer). That means that we will be able to select a value from a dropdown list of possible value when filling out the information. Therefore we also need to define the possible values in the dropdown list. For now we need only one value, so we can write individual: Individual Account. The left side of the colon acts as a reference which we can use within Atfinity to refer to this value. The right side of the colon is the translated value of that reference which will be visible in the dropdown list. For more information, see List (Single Answer).

If you feel like it, try to create some additional information as an exercise. Here are some suggestions for information you could create: country of birth, contract number, phone number, email address, gender. For each information, think about the ontology it belongs to and what type it should have.

At this point we have created all the information we need for our process. In the next article we will see how we can .

Information
information type
Categories
Create and Configure a Document