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
  • Summary
  • Next steps

Was this helpful?

  1. Guides
  2. Getting Started

Summary and Next Steps

Previous6. Put LiveNextAdvanced Topics

Last updated 2 years ago

Was this helpful?

We have reached the end of the getting started guide. Well done! Together we have created a simple process that allows us to start a new case of an account opening where we collect the personal information of a person. Let's briefly repeat and summarise the essential steps we have done and which steps could be done in further, more advanced steps.

Summary

We have looked at the concepts of what ontologies and roles are. The necessary ontologies for our process were 'Contract', which has an 'Account Holder' role, and 'Person', which can take the 'Account Holder' role on a contract.

The next thing we did was creating the required information for each ontology. That included the 'Account Type' information for the 'Contract' as well as 'First Name', 'Last Name' and 'Date of birth' for 'Person'. During that step we have also got to know that information can be of different types.

After creating a document we put our information on it and defined in a condition that this document should only become part of a case if there is a person who's supposed to be on the contract.

We also made a rule that ensures a person whenever a contract will be about opening an 'Individual Account'.

Finally we needed to bring everything together in one place. For that reason we created a process and added the rule and the document containing all the information to it.

After putting the changes live we were able to start a new cases where we can select and fill in information. That way we could test that the case behaves in a way we want it to.

Next steps

Although the process we made is fully functional, it is also very minimal. With a couple of additional steps the process can be improved a lot, both visually as well as functionally.

  • Structure the appearance of a process with additional and . Every category concerning the account belongs in the 'Account' tab, information about persons involved goes in the 'Parties' tab.

  • Add document to further structure information on a document. This way it can be controlled under what condition a specific (group of) information should be asked for.

  • Add to the process.

  • Create a more advanced workflow with additional and rules.

  • Display a in the 'Parties' tab to have an overview of people involved in the case and their roles.

  • Create for answer options from an information of list. That way the answer options can be used by another information of type list if suitable.

  • Create additional roles on the contract if required, e.g. 'Beneficial Owner' or 'Power of Attorney'.

  • Create more rules to help guiding processes. E.g. if an account holder is underage, a rule should ensure a person who takes the role 'Power of Attorney'.

  • Add more documents to a process if required, e.g. a form for opening a joint account.

  • Give every ontology an to show in the navigation bar.

tabs
Categories
sections
proofs
taxonomy
type
icon
states
transition
role matrix