AI and Rules - Recent Threads

RE: AI Doc Center

ericc087568 — Thu, 09 Apr 2026 15:22:53 GMT

You would want to publish, and download the AIA deployment file, locate the key of the model(s) to be used within that file and reference them in your calls to the AIA run model processes.

AI Doc Center

shivakanthreddyp0001 — Tue, 07 Apr 2026 00:05:48 GMT

Hi All,

We were previously using AI Document Center 2.9, and whenever we created a classification model, the system would automatically create the corresponding classification AI skills in the Generated Objects application.

Recently, we upgraded to Document Center 3.1. After the upgrade, when we create a classification model, the AI skill is no longer created automatically.

Upon reviewing the Create Classification process model, I noticed that it was updated as part of the upgrade and no longer calls the “create objects” process model, which the earlier version did.

Is this the expected behavior in Doc Center 3.1?
Or is there any additional configuration or post‑upgrade step that we might have missed to enable automatic AI skill creation?

Thanks in advance

RE: AI Doc Center

lalithyak07 — Wed, 08 Apr 2026 06:16:01 GMT

yes i have also face the same issue with Doc center 3.1, and i get to know that it is expected behaviour and bit different from 2.9

RE: AI Doc Center

shivakanthreddyp0001 — Tue, 07 Apr 2026 00:47:16 GMT

Hi All,

Yes, it is expected behaviour and calling AI skill is bit different from 2.9.

Thank you.

RE: AI Skill Doc Extraction

Shubham Aware — Mon, 30 Mar 2026 05:06:05 GMT

Yes, we can do that easily. Can you describe your actual requirement, or clarify what confusion you have, so we can help you better?

AI Skill Doc Extraction

leelaraok0002 — Fri, 27 Mar 2026 16:24:58 GMT

can we configure human task where api kicks appian process which ahs doc extraction ai skill in case doc extraction fails

RE: AI Skill Doc Extraction

Stefan Helzle — Fri, 27 Mar 2026 16:35:33 GMT

I think so. But can you describe your specific use case in more detail?

RE: What is a best practice for checking extraction instance result in AI Doc Center for further routing to custom reconcile?

Shubham Aware — Fri, 27 Mar 2026 05:56:51 GMT

Check AIA Extraction Instance status = 2 (Needs Review) - AIA already computed confidence, accuracy, and validation failures internally before setting that status.

What is a best practice for checking extraction instance result in AI Doc Center for further routing to custom reconcile?

ericc087568 — Thu, 26 Mar 2026 22:06:39 GMT

First of all, AI Doc Center is fantastic (3.1.3 installed). Love the way it is easy to set up and version classification and extraction, so much right out of the box.

I think I'm missing something in the documentation though on AIA Extraction Instance's status in a 'real' extraction. I see some constants in the AIA app and can infer in a different app that a status of 2 or 4 means a particular thing that might send me to my custom interface for reconciliation of the instance, which in turn would trigger a model to save to data fabric if reconciled and not abandoned / canceled by an end user. But, I'm getting off track...

I guess I'm asking what is the best practice to see the AIA Extraction Instance's notion that accuracy / precision / validation rule fail on an extraction would drive the decision to send a custom user reconcile task. At the moment, I would be cobbling together a big 'Or' to see if any reconciliation should be routed.

Regards, and see anyone at Appian World 2026?

documents Chat Field

rajeshp7374 — Wed, 18 Feb 2026 09:50:33 GMT

Hi Team,

I am working with the documentsChatField in Appian. After uploading a document, I want to pass it to the chat field for verification. If the verification is successful, I need to save the document details in the database.

Could you please guide me on how to achieve this? Is it possible to trigger document verification immediately after upload and then conditionally persist the document metadata based on the verification result?

RE: documents Chat Field

leelaraok0002 — Thu, 26 Mar 2026 19:39:12 GMT

You can follow below architecture for this

[ Interface ]

└─ Upload document

└─ Show documentsChatField

└─ “Verify” button

↓

[ Process Model ]

└─ AI Skill / GenAI verification

└─ Decision (success / failure)

└─ Save metadata (if successful)

RE: Can't see AI Agent Studio

leelaraok0002 — Thu, 26 Mar 2026 19:32:34 GMT

GenAI Skills are part of Advanced or Premium AI capability tiers

Check for below settings if you have Advanced or Premium tier licence

Admin Console → AI → Generative AI settings

Can't see AI Agent Studio

Harsha Sharma — Fri, 05 Dec 2025 09:09:59 GMT

We recently upgraded to version 25.4 yet we can't find the Agent Studio or option to build new AI Agents in Appian Designer. Is there any additional permission /configuration needed to enable this object type?

Comparing two documents and return the matching Score(Signature Matching)

keerthirak779572 — Wed, 25 Mar 2026 10:25:42 GMT

I am having two Signature Documents. i want to compare both the documents and i have to return the matching score percentage of how similar two of the signatures.

RE: Comparing two documents and return the matching Score(Signature Matching)

Harsha Sharma — Wed, 25 Mar 2026 12:18:28 GMT

Two options for you to try,

1. Use the Apryse WebViewer Component Plug-in. It features document comparison in semantic categories. The score percentage is something you will have to work out depending on outputs I think.

2. Appian RPA has Image Recognition capabilities. Explore and build a bot to do the comparison and return score.

I would suggest to explore Apryse first as that seems more promising to fulfill your usecase and easier to implement too. Hope it helps!

RE: Comparing two documents and return the matching Score(Signature Matching)

Stefan Helzle — Wed, 25 Mar 2026 11:48:32 GMT

What have you tried so far?

RE: AI Document Center Classification Model - "Unsupported file type" when uploading .eml file

Shubham Aware — Tue, 17 Mar 2026 17:15:42 GMT

If you are confident that your file format is correct but it’s still not working, I would recommend raising a support ticket with Appian.

AI Document Center Classification Model - "Unsupported file type" when uploading .eml file

Georgios Pavlidis — Tue, 17 Mar 2026 09:57:26 GMT

Hi everyone,

I am working with AI Document Center in Appian and I am trying to use a classification model with an .eml file.

According to the documentation, .eml should be a supported file type, but when I run the model I get this error:

Generative AI
Classification: Unsupported file type. Try again using a supported type or contact your admin if the problem persists.

The issue happens specifically when I upload an .eml file

Has anyone successfully used .eml files with AI Document Center classification?

RE: AI Document Center Classification Model - "Unsupported file type" when uploading .eml file

Georgios Pavlidis — Tue, 17 Mar 2026 11:50:48 GMT

this plug-in it's already in the system !

RE: AI Document Center Classification Model - "Unsupported file type" when uploading .eml file

Shubham Aware — Tue, 17 Mar 2026 11:38:24 GMT

Make sure this plugin is deployed in environment.
https://community.appian.com/b/appmarket/posts/eml-utility

You could try deploying this and then check.

RE: Smart Search, Documents and RAG

jamesm4933 — Thu, 12 Mar 2026 19:28:14 GMT

Thanks Derek, so what I understand you to be saying, is that there are multiple siloed embedding locations

Documents chat (already knew about that)
Smart Search (NOT available except to anything but the smart search?)
The "Agent Index" (I have never heard about this one)
Document Extraction (I think I know what you are referring to here)

Would you mind clarifying number 3.

The "Agent Index" how does that work, what records and documents are accessible to it, and what features can utilize it?
Are you saying, that the embedding content is *only* available by the use of an Agent?
Are you saying that the Agent Index, and the smart search embeddings will be merged in the future, or are already approximately synonyms?

Appreciate the the help!

K/R

Smart Search, Documents and RAG

jamesm4933 — Thu, 12 Mar 2026 15:16:52 GMT

My client is concerned about reducing token usage, and we are investigating how to prevent repeated tokenization and embedding.

We understand that Document Management Record Types embed the document representations for use in the smart search. Are these embeddings used system wide when document content is provided to an AI Agent or Skill?

Are they only available if the document is referenced using the special system document type?

Help us understand.

Thanks!

RE: Smart Search, Documents and RAG

Derek Knoderer — Thu, 12 Mar 2026 19:09:40 GMT

jamesm4933

Smart search itself tracks and checks for actual data changes from each data sync (which triggers indexing), and will only re/index new or changed rows of data when creating or updating embeddings.

Additionally, Agentic usage of smart search is reusing the same embeddings for records search, and document search will in the future as well. (There are some notable exceptions here, for example: If you are using Agent Studio and doc extraction -- passing in a document as an input or a tool uses the Agent Index, leveraging a doc extraction tool called by an agent will use the doc extraction index.)

For AI Skills, there's no underlying connection between AI Skills and Smart Search/Embeddings. When you load a record document into AI Skills, tokens are consumed for the entire documents i.e. no embedding info is used. Now if you're querying using smart search and sending chunks of the document to AI Skills as text, only those tokens are consumed. Overall, new tokens are used every time a document is used with AI Skills.

RE: AI Agent returns empty result for Excel file

Harsha Sharma — Thu, 12 Mar 2026 06:09:16 GMT

Hi Rishu Kumar Gupta It looks more of a security issue in your case. Check the users's group assignment and ensure the group is configured for AI Agent's security (atleast as Viewer) as well as any AI Tools you might have in the Agent - check their permission as well.

AI Agent returns empty result for Excel file

adamb9906 — Tue, 27 Jan 2026 00:24:28 GMT

I’m testing an Appian AI Agent that needs to read data from an XLSX document. I have two copies of the exact same XLSX file stored in two different folders in Appian.

When I point the AI Agent to the file in Folder A, it works as expected and can read/extract the data.
When I point it to the identical file in Folder B, it does not work (the agent appears to find nothing in the file / doesn’t extract data).

Both documents are valid Appian documents of type .xlsx, AI Agent uses Semantic Search to read the data, and the file contents are identical. The only difference is the folder they’re stored in.

Has anyone seen this behavior before or can suggest what to check? Any guidance on why the same file would work in one folder but not another would be appreciated.

I created new folders, checked the folder security, but I can't find the issue.