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: Check Changes, Warnings and Errors
  • Step 2: Put Live and test

Was this helpful?

  1. Guides
  2. Getting Started

6. Put Live

Up to now, Atfinity has carefully kept track of every configuration change we have done so far. Now it's time to put them live which means that Atfinity will implement all our changes. After that, we will be able to start our account opening process.

Step 1: Check Changes, Warnings and Errors

Atfinity provides a list of changes done to the configuration. There we can find everything we have done, from creating the ontologies 'Contract' and 'Person', to creating the document as well as writing the rule's condition.

It could have happened that we forgot something during configuring, like adding a newly created rule to a process. This does not cause any error, but it might not be what we have intended. Therefore, Atfinity will warn about it. If we wish, we can ignore the warnings and still put live.

However, if we have done a mistake that would lead to a fatal error, Atfinity lets us know with an error message. As long as the error is not taken care of, we won't be able to put live. If we have followed this guide painstakingly, there shouldn't be any errors or warnings and we can continue to the next step.

Step 2: Put Live and test

When everything is in order and all possible errors are taken care of, we can put the configuration live.

It is good practise to ensure that changes made to the configuration behave the way they were intended to. Let's go to the Dashboard where we can start a new case.

This is how our process should behave:

  • When we open the new case, what we should see is an instance of a 'Contract' as well as the 'Account Type' information that needs to be provided. Clicking on it should open a dropdown from which we can select 'Individual Account'.

  • As soon as 'Individual Account' is selected, a lot of things happen at once. First, the rule we created becomes active and ensures that there is a person who's account holder. That's because the information about the account type is now 'individual' which was the rule's condition in order to evaluate to true. Second, the document condition evaluates to true as well because now both a contract and a person are part of the case. This leads to all the remaining information we created being asked.

  • We then should be able to enter a first and last name as text and select a date of birth.

  • Approving or declining a case should also be possible. Doing either one should close the case.

If you have done the exercises throughout the guide and have, e.g. created an additional rule that warns when the account holder is underage, you should test its behaviour too. When you enter yesterdays date as a date of birth, there should be a warning. Similarly important, if you then change the date of birth to a date from the last century, the warning should disappear again.

Previous5. Create a ProcessNextSummary and Next Steps

Last updated 2 years ago

Was this helpful?