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: uploading a file or a proof, changing the owner or the assignee, and creating or deleting a case. File, structure and relationship fields are read but not written. 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. Only the file types whose text Atfinity Intelligence can read are accepted: PDF, PNG, JPEG, TIFF, HEIC and GIF, and of those only the ones your tenant allows for documents. When your tenant does not restrict the file types for documents, all six are accepted. When it 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 can be up to 20 MB and a PDF or TIFF up to 30 pages, and a larger one is refused when you attach it. Whoever runs your installation can change both limits, as described under Language Models.
For a passport or an identity card it also receives the machine readable zone, even when the rest of the text could not be read, and is told to prefer it for names, numbers and dates wherever its check digits pass. Before it answers, it waits for the text of the files you just attached, for up to three minutes. A file it could not read by then, or could not read at all, is left out of that answer.
Every answer sees the text of the files attached earlier in the conversation, not only the latest ones. It receives the first 60,000 characters of each file, newest file first, and only the names of the older files once their text no longer fits. With tools, it reads the rest of a long file, or an older file, when your question needs it. A conversation without tools cannot read beyond what it received, and says so when your question needs more. It is told to treat what a file says as information to check, never as instructions to follow.
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.