Release Notes
- We adapted our helm chart to support Ingress-Nginx Controller to prepare for Kubernetes 1.28
- Bugfixes
- We made the order of roles, documents and instances in RuLa always predictable. Unpredictable orders could have caused infinite rule engine loops for some configurations.
- Internal taxonomies of information could sometimes end up having keys that are too long. The system was changed to have a random key that never exceeds the maximum length.
- Added
CASE.states_history
. The states history outputs some statistics on how long a case was in a certain state, how often it entered it and which user moved it last to a certain state. - Improved case loading performance
- Environment Constants that will not be exported or imported and stay with the environment itself
- Instance sorting in a case can now be configured per process.
- Autocompletion for Constants, so when typing
CONSTANTS.
you get a list of all constants you have defined before - Add
USER_ROLES
andUSER_GROUPS
objects to access the permission model directly in RuLa - Uploaded case documents can now also be deleted directly in the documents view
- Users can be prohibited from changing the name of a case
- When uploading a booklet, documents with missing pages can also be forced to be still attached
- Add
CASE.all_states
, which returns all the states the workflow of a case can be in - More infos about the case are displayed in an info bubble:The new case info bubble
- 👪 Child and parent relationships: This makes Atfinity even more powerful. Configure multi-level structures by declaring a company a child of a person, or make people employees by assigning them to a company
- 👾 Variables in RuLa: Write simpler rules by using variables and giving names to individual parts of your rules. If you want to check if a person is allowed to rent a car you can now do:
1
old_enough := p.age > 2
2
has_license := "driver_license" in p.licenses
3
old_enough and has_license
- 🪐 Meta Documents. Meta Documents contain information about other documents. Using these, you can e.g.
- Create a document per needed proof and contain extra information per proof
- Store when each uploaded document has been reviewed and by whom
- Have a document with review defects (e.g. missing last name) and manual corrections
- 🏷️ Case Tags: Add tags like #important to cases to further organise your teams work. Overviews can be filtered and sorted to just have tags
- 🔔 In-App Notifications: In addition to getting notifications via email they will now also be displayed in the Atfinity app directly
- 📄 More Document upload options. If outdated documents are uploaded, users can overwrite this and still accept the document.
- Custom 好 Text Assets: Allows to create text assets with a key and translations to all configured languages. These assets can then be used in RuLa and ADX
- 💬 Comment Improvements:
- Mention and notify other users in comments with e.g. @Thorben
- Images in comments
- Rich text formatting with a GUI editor
- Edit comments after they have been written
- Proof Previews: Most proof types can be previewed in the application directly without downloading them
- Assignee rules: Assign people to work on cases based on rules
- Splitting Booklet by ontologies. Booklets can already be split by different documents, however, the same document can be required to be filled out by multiple people. This creates a single booklet by instance, so, for example, for each person in a case
- Case Manager Overview improvements, highlights:
- Filtering for information columns
- Sorting for information columns
- Improved speed
- Much better full-text search
- Configuration Export Robustness: We changed the matching of items like document and information from the configures key to a created UUID. This means changing the key will no longer result in a deletion and creation of a document or information
- ADX templates: Now you can create even more powerful ADX systems by creating ADX templates and reusing them in ADX document
- Process Designer improvements:
- Moving information up and down affects the layout a lot less now
- Information can be "locked" in place. They will then not move left or right to fill space
- Move a whole category to a different tab
- Move a whole category up or down
- Add line breaks inside categories
- Information on the tabs have links to the information detail view
- Set default values for information
- Case Manager Overview Configuration Improvements, highlights:
- Configurable Access Rights
- New Tag Filter
- New State Filter
- Configurable Sorting
- Configurable Icon
- Different titles for the navigation element of a parent overview
- External Data Source Queries can now also contain case information. You can configure this directly next to the data source
- In addition to sending a whole booklet, you can now also just send single documents with the rule action "Send Email"
- Adapt the content of the notification email templates of your tenant
- More login policies:
- Enforce regular password changes
- More password policy options, e.g. no duplicated characters
- Configurable session duration
- Rules and scheduled rules can now be sorted
- The ID-Prefix of cases can be configures, so instead of CSE-45 it can also be BUG-45 or LOAN-45
- Configure whether you want a sidecar file for Hyperarchive export or not
- New Notification for case owners when an explanation comment has been provided
- New Notification when users get a reply to a comment
- Show labels in addition to keys for Sub-taxonomies
- Make
CASE.last_transition_by
andCASE.last_transition_by_name
available in RuLa - Translations for texts can be edited directly in context, e.g. you can edit the translations for all languages of the display name directly in the information detail view
- As always the release also contains various security fixes, so for onsite clients we recommend updating as soon as possible.
- Administrators can clear all caches directly in the user interface
- Taxonomy keys have been changed to be SCREAMING_SNAKE_CASE for consistency
- Retrieve Case, Create Case, Create Case With Predefined Objects, Change Field (instance and information_key), Change Field (case_field_key), Change multiple fields, Change Case Owner and Transition Case
- in
data.booklets[i].documents
the itemid
instead of thedocument_id
are used data.booklets[i].documents[i]
have additional fields:instance_id
andparent_booklet_id
data.documents[i]
have additional fieldis_meta
,preview
data.fields[i]
have additional fieldneeded_document_id
data.instances[i]
have additional fields:children
,parents
,has_potential_children
andhas_potential_parents
data.proofs[i]
have additional fieldpreview
data.ontologies[i]
have the additional fieldkey
data.outcome_ontology
has the additional fieldkey
data.roles[i]
have the additional fieldkey
data
has additional fieldstags
andissue_comments
- List Cases, List Instances of a Specific Ontology and List Some Cases
- Will no longer return the
meta.columns
andmeta.quick_filters
fields data[i]
have additional fieldsprocess
andtags
- Retrieve Instance, Change Instance Owner, Lock / Unlock Instance and Force Update Instance Values
data.fields[i]
have the additional fieldneeded_document_id
data.cases[i]
have the additional fieldassignee