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
  • Example: CASE.number_of_issues
  • Example: CASE.state

Was this helpful?

  1. Rule Language (RuLA)

Information about the case

From RuLa, you can access certain information about the case itself. For this, within applicable rules, you have access to the constant CASE like to any other instance. On this instance, the following information is available:

Property

Description

CASE.case_number

The case number in the user readable format, e.g. CSE-1991.

CASE.process_key

CASE.process_name

CASE.outcome_instance

CASE.state

The key of the current state the case is in, e.g. draft.

CASE.all_states

All possible states the case could be in according to the workflow of the process.

CASE.states_history

Returns a dictionary with some statistical information about each state. This includes:

  • initiator (the last one)

  • entered (when was this state entered last)

  • days (Total days in state, so the time in days the case was in this state every time it entered)

  • times_entered (how many times the case entered this state)

  • previous_state (the last one)

CASE.last_transition

The key of the last transition (if any) that was done to arrive at the current state, e.g. back_to_draft.

CASE.last_transition_at

The time when the last transition (if any) happened, e.g. 2022-11-17 11:05:30.322951

CASE.last_transition_by

The username of the user that performed the last transition

CASE.last_transition_by_name

The name of the user that performed the last transition

CASE.number_of_missing_information

How many information still should be provided (the sum of all the grey bubbles on information tabs).

CASE.number_of_tasks

Current number of tasks within the case.

CASE.number_of_issues

Current number of issues within the case.

CASE.created_at

The time when the case was created, e.g. 2021-11-30 16:40:12.923654

CASE.last_update

The last time the case was updates, e.g. 2021-03-12 11:58:08.644664.

CASE.owner

The owner of the case (the email in rules and the full name and email when printed)

CASE.owner_name

The full name of the case owner

CASE.owner_groups

A list of the names of the groups the current case owner has.

CASE.owner_roles

A list of the names of the roles the current case owner has.

CASE.initiator

The initiator of the case (the email in rules and the full name and email when printed)

CASE.initiator_name

The full name of the case initiator

CASE.assignee

The assignee to the case (the email in rules and the full name and email when printed)

CASE.assignee_name

The full name of the case owner

Case.approver

The user (if any) who approved the case (the email in rules and the full name and email when printed)

CASE.approver_name

The full name of the case approver

CASE.documents

A list with the names of all documents that are used in a case. This can be used to e.g. create a customised table of contents.

CASE.proofs

A list with the names of all proofs that are used in a case. This can be used to e.g. create a customised table of contents.

Example: CASE.number_of_issues

CASE.number_of_issues = 0 and CASE.number_of_tasks = 0

This rule will only be fulfilled when there are no issues or tasks within a case.

Example: CASE.state

CASE.state = 'draft'

This rule would only be fulfilled while the case is in the state with the key '"draft".

Please note that if you are using this to create an issue or comment, it would be, as any other issue, comment or warning, removed when the case leaves that state (unless a user replied to it or was assigned to it).

PreviousCommentsNextAccessing the outcome instance

Last updated 1 year ago

Was this helpful?

The key of the process the is based on, e.g. end_to_end_onboarding.

The translated name of the the case is based on, e.g. End to End Onboarding. Note: This will be translated on documents and in the case manager. Within rules, it's just a placeholder, so e.g. `CASE.process_name = 'Onboarding'` will not work. Use process_key for such comparisons.

The outcome this case operates on. For a case creating a new contract this is often ContractualRelationship.

case
process
instance