Using Atfinity Intelligence¶
Info
New in Atfinity 17.
Atfinity Intelligence works in two places, and each is a separate conversation with its own tools. A configuration conversation reaches your configuration, so you can ask why a question is never asked, have it draft a rule, or have it add a category to a tab. A case conversation reaches the case a user has open, so it can answer what the case still needs, fill fields in and move it on.
Neither is on until an administrator turns it on, and each area has its own pair of settings under Integrations in AI. A case conversation never reaches the configuration, whatever the configuration setting says.
Read and read + write¶
Each conversation carries its own access, and it applies to every answer in that conversation from then on. A new conversation starts on Read, apart from the one a case started with AI opens with.
- Read: it can look anything up, but a request to change something is refused and it describes the change for you to make instead.
- Read + write, shown as Read + edit in a case: it can also change what that conversation reaches.
Access never exceeds your own. The conversation runs as the user it belongs to, so it reaches exactly what that user reaches, and the write setting for the area caps every conversation in it whatever access the user picked.
In the configuration¶
On Read + write it creates, edits and deletes information, rules, documents, pages, ADX templates, process layouts, taxonomies and translations, and fills in a draft case to try out what it built. It also creates the ontologies, processes and workflows the rest of that work hangs off, so a new area can start from nothing; changing or deleting one of those three stays with you. A user who may not see the configuration gets no access at all.
Every change lands in the draft configuration, where your own edits go, so nothing reaches a live case until you Put Live. Putting live is not something it can do. After changing anything it checks the draft for errors and reports the ones it could not resolve, but the draft is yours: read the changes before you publish them.
A deletion is a real deletion of the draft object. Use Read while you are still exploring, and switch to Read + write once you know what you want changed.
In a case¶
The conversation belongs to one case and stays pinned to it, so a comment or a document that asks for another case is refused rather than followed. A conversation about a test case works that test case, and one about a live case works that live case.
It reads the case's fields, its documents and the text extracted from uploaded files, so it can answer what a statement says without you opening it. It lists what the case is still missing, and separates the fields that are optional from the ones a rule requires.
On Read + write it fills fields in, moves the case through a transition, and writes comments, including raising one as an issue or assigning it to someone as a task. Your configuration governs all of it: a write needs the workflow action for the case's current state, so the same user is allowed in one state and refused in the next.
Unlike the configuration, a case change takes effect immediately rather than landing in a draft. Turn the case write setting off where only a person should edit a case.
Some things stay with the application: changing the owner or the assignee, and creating or deleting a case.
A file field, a proof or a document takes only a file attached to the conversation, as described under
Keeping an attached file.
Structure and relationship fields are read but not written.
An SVG field is not written, and the case shows Atfinity Intelligence only its
name, such as [drawing: Onboarding Checklist]. When a question depends on what the picture shows, it reads the
template the picture is drawn from, the values the template reads, including those of related instances, structure
occurrences and the case, and the text the picture displays.
Without access to the case it reads only the text the picture shows, such as
[drawing: Onboarding data, 6 / 6, Date of birth, Address].
A rich text field keeps bold, italic and bulleted lists when it is filled in, and loses any other formatting it had,
such as a link or a heading.
The fields of a requested document or proof are written like any other.
So are the fields inside an occurrence of a structure, but adding or removing
an occurrence stays with the application.
Starting a case with AI¶
Info
New in Atfinity 18.
Start case with AI starts a case and opens it on its Assistant tab with a new conversation, so a user can describe the case instead of filling it in. That conversation starts on Read + write, or on Read where the case write setting is off. The button sits next to the buttons that start a new case, on the dashboard, on pages and among the draft cases, and lists the creation processes whose AI features settings tab has Start a case with AI enabled, which every creation process has by default. The button and the setting only show while case conversations are turned on.
The Assistant tab and the side panel share their conversations, so a conversation moved between them keeps its messages and the access chosen for it. Moving it to the side panel returns to the tab that was open before the assistant, or to the first tab when the case opened on the assistant, as a case started with AI does. The case only remembers that tab until it is left or reloaded.
Attaching files¶
Info
New in Atfinity 18.
You can attach files to a message in either kind of conversation.
Atfinity Intelligence accepts the file types whose text it can read: PDF, PNG, JPEG, TIFF, HEIC, GIF, text (.txt)
and Markdown (.md).
Of those it accepts the ones your tenant lists under Allowed document file types, or all of them when that list is
empty.
A list set before Atfinity 18 cannot contain Markdown, so add md to it to accept Markdown files.
When your tenant allows none of them, or your installation does not read the text of uploaded files, the conversation
offers no way to attach a file.
By default a file is refused when you attach it if it is larger than 20 MB, a PDF or TIFF with more than 30 pages, or
a text file with more than 10 million characters.
A text or Markdown file is also refused when it holds binary content, such as a Word file or an archive renamed to
.txt.
Whoever runs your installation can change the size and page limits, as described under
Language Models.
Atfinity Intelligence answers straight away, without waiting for the text of the files you just attached. Every answer receives a list of all files attached in the conversation, oldest first, with each file's type and whether its text has been read, is still being read or could not be read. For a file that has been read, the list also gives its number of pages and characters, but never the text itself.
With tools, it reads the text of a file when your question needs it. One answer reads up to 160,000 characters of attached files, and when your question needs more it tells you what it has not read yet, so you can ask it to continue. A file that is still being read is not ready yet, so it says so and you can ask again a moment later. A file whose text could not be read is reported as such, rather than guessed at. A conversation without tools cannot read attached files, and says so when your question needs one.
For a passport or an identity card the list also holds the machine readable zone, even when the rest of the text could not be read. A case conversation is told to prefer the zone for names, numbers and dates wherever its check digits pass. It is told to treat what a file says as information to check, never as instructions to follow.
With tools it can also search the attached files for words or a phrase, count the pages of a PDF, and read the size of an image as stored and as shown upright. It can read what a PDF says about itself, such as its title, author, creation date and whether it is encrypted, which is what the document claims rather than proof that it is genuine.
Keeping an attached file¶
Info
New in Atfinity 18.
On Read + write a conversation can store a file you attached to one of your messages in the case or the configuration it works on. It stores a copy under the file's own name, checked as an upload in the application is: the same file types, size limits and permissions.
In a case, the file goes into:
- a file field, including one inside a structure occurrence or on a document or proof
- a requested proof or document, or an appendix to one that is already provided
- a custom proof the case did not ask for, under the name you give it or the file's name
A document to be signed takes only a print of the PDF Atfinity generated for it in this case. Its pages are found by their QR codes, so a PDF missing one of them, or printed before the data on it changed, is refused, and you upload it in the application if it belongs there anyway. Any other document, and an appendix to a document, takes any PDF.
In the configuration, the file lands in the draft and goes into:
- the PDF of a PDF document, in one language
- the PDF of a document template, in one language
- an image asset for ADX templates, created when its key is new
- one of the tenant's logos, favicons and background images
A language can be named by its key, its English name or its own name, so de, German and Deutsch all work.
A name that fits several of your languages, such as German with both de and de_CH, needs the key instead.
A PDF in a new language takes the box positions of the first one, and a replacement keeps them except on pages the new
file no longer has.
A smart document prints on the PDF of its document template, so asking for one names the template and the other
documents that print on it, and changes the template only once you confirm.
Where a file is already in place, it asks before replacing it, and replacing a proof or a document detaches its appendices. A field that holds several files gets the file added instead.
Following what it did¶
Every answer lists the tools it called and the arguments it passed, and marks the calls that failed.
Where an answer names a configuration object it writes that object's id, such as ONTO-12 or RLE-34, and the id
becomes a link to the object.
Opening one keeps the conversation open next to it, so you can look at what it found and carry on from there.
A long task can end before it is finished: the answer says what is still open, a note under it marks it as unfinished, and asking it to continue carries on from what it already read.
An answer only ever links inside Atfinity. A web address in an answer is shown as text and cannot be clicked, so a link cannot lead you out of the product.
Example¶
Asked why a question never appears on a case, a configuration conversation searches the information by title, reads the rules that require it, and answers that the rule requiring the field is guarded by a condition the case does not meet, naming both by id. On Read it stops there. On Read + write it can change the condition, check the draft for errors and tell you what is left to review before you put the change live.