Process Automation

1. The extracted document contains a table with over 300 rows, but the reconciliation screen displays only 100 fields because the related record type query is limited to retrieving 100 items. Do you have any suggestions on how we can reconcile all the rows? 2. The "Highlight Value in Document" feature on the reconciliation screen is not working properly. I’m using AI Document Center version 3.1. Is there any known reason why this issue occurs? 3. Sometimes, when a document has a large number of rows, the extraction model does not extract all the data. For example, if the document has 600 rows, it only extracts about 350 rows. Are there any limitations on the document extraction model? 4.The extraction process is taking a considerable amount of time. Are there any best practices or configuration changes to improve extraction performance? Environment Details: AI Document Center Version: 3.1 LLM: 4.5 (Reasoning)

Hi Everyone, I'm using Appian Document Extraction and need to process multiple invoice documents uploaded in a claim. What is the recommended approach to: Pass multiple invoices for extraction Extract data from each invoice Store the results in a List of Record Type/CDT Can a list of document IDs be passed directly to Document Extraction, or should each document be processed individually (using a loop/subprocess)?

Hi, I am working on DocCenter Classification and have a few questions around reconciliation and automation. Looking for guidance from anyone who has implemented this. **My Use Case:** I want to classify documents automatically without any human involvement in the reconciliation step. **My Questions:** 1. Is it possible to auto-reconcile a classification instance in DocCenter without human intervention? 2. Does DocCenter Classification expose a confidence score as an output in a process model (similar to the Classify Documents Smart Service)? 3. If DocCenter Classification does not support auto-reconciliation natively, what is the recommended approach to achieve straight-through processing (STP) for classification? Thanks in advance. 

Hi everyone, I’m facing an issue while using Appian AI Skill (GenAI) with an Excel file. When I upload an Excel file with empty data, I get one type of classification output. However, when I upload the same file structure but with data inside, it produces a different classification output. Essentially, the classification result varies depending on whether the file has data, and it seems inconsistent each time. Has anyone experienced this issue before? Any insights on why the classification behavior changes like this?

I am working with a rule in Appian where I expect a consistent structure of List of Map, but I am seeing inconsistent data types in the output.a!localVariables( local!indexval: index( ri!userFilters, "userFilter", null ), local!filters: split(local!indexval, ";"), a!forEach( items: local!filters, expression: a!localVariables( local!valueStart: find("value=[", fv!item), local!valueBlock: if( isnull(local!valueStart), "", mid( fv!item, local!valueStart + 7, len(fv!item) ) ), local!cleanValueBlock: substitute(local!valueBlock, "]", ""), /*Values */ local!AccountName: if( find("name=AccountName", fv!item) > 0, a!forEach( items: split(local!cleanValueBlock, ","), expression: trim(substitute(fv!item, """", "")) ), {} ), local!ProductCategory: if( find("name=Product Category", fv!item) > 0, a!forEach( items: split(local!cleanValueBlock, ","), expression: trim

I am exploring the Appian AI  agend and faced the below Appian error. enable to understand and fix these issue.If anyone has faced similar issue please let know the fixes.

I am facing error in the AI agend while reading the document.LLM execution failed: EVENT_NOT_FOUND - No event exists with name: setVariableValueSteps1:  When I am passing this document as in the TOOL in the AI agend than it is working fine.Steps2:  When passing this document in the input than facing this issue.Please just How can I pass document dynamically in the process model?

Hi Everyone,We have a requirement where we are using AI-based document extraction to extract fields from a predefined form.In the same form, if there are any empty spaces and the user accidentally adds handwritten text or notes outside the expected form fields, we need to detect that additional handwritten content separately.Is it possible in Appian with help of AI extraction to achieve this use case ? Kind Regards, Kavya

I have a Record Type with a Document record field. We have a business requirement to be able to use Smart/Semantic search on this and a text field. The Smart Search Sync consistently fails with the following error message, and a list of failed record ids: "Cannot retrieve the document. Verify the document management record type is configured correctly." Through investigation, we discovered, that the Document field for these records was NULL, which is consistent with the above error message. We would like to have a successful search indexing, for this record type, and so we removed those records from the dataset temporarily.  However, now we get the following error message: "We couldn't check the smart search status. Try resyncing your record type." Attempting to Sync is what produced this error, so it seems a bit unhelpful as an error message.   Why is the indexing failing when the selected smart search field is empty? Is there a workaround? Now that t

Has anyone configured MFA for Appian RPA bots? How is the manual action to accept or decline the request on authenticator bypassed ?

I have many robotic tasks, all of them runs when triggered either from process or by Re-execution or By TEST button, but one of the Robotic tasks which was executing previously has stopped triggering from process model, the process model gets stuck at the robotic tasks node without any errors and fails with timeout after long time. Re-execution of the previous instances is also not triggering any new instance for this robotic tasks alone. 

Sometimes, when I test an agent, it processes for a while, then after a few minutes throws this error: System Error This appears to be a system issue. Try again later or submit a support case if the problem continues. Source: Run Agent - Agent: DG_testAgent - Run ID: 52 Details: LLM execution failed: INVALID_TOOL_RESPONSE - Required schema field not provided in data tree: textValue Any suggestions on what could be going on? Sometimes the agent succeeds, but the frequency of getting this error makes me concerned about using this in production. 26.3 environment hosted on Appian Cloud.

I am using a!currency to show thousand separator but it by default shows $ symbol if used USD ISO.Here I need to remove this  $ symbol while displaying this field. 

I have a subset of .msg files which when read with the read msg smart service, render in a tiny font with the .html output which results in AI being unable to interpret.  Would I probably be better off running several reg ex statements to exclude tags that are confusing it and pasting in some style that would force the font, or just use the extracted (not the generated result document), or move it to PDF, or some different approach? Regards, Eric Casteel

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

Hi All, I have recorded an RPA to Login to Appian  I have configured credentials. Screenshots are below When I start Testing the RPA running and opening the url in the browser, but Username and password are not set After sometime I'm receiving this the below error(attached) and task is terminating. Please suggest some solutions and let me know if you need anything else 

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

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

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?

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? 

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.

I have a question related to "Appian RPA - working with Excel": is the set of activities powerful enough?  I have a project that requires specific activities in a few Excel files: -renaming a sheet -adding/removing a sheet -applying sorting -transferring (copy and paste) data from one sheet to another one in the same Excel documents and between documents -searching in a column for the first file name (the column has files names in it) that has or not an extension (".txt" for example). etc etc etc Can the Appian "working with Excel" set of activities powerful enough? Did somebody have something that couldn't be implemented (lack of functionality maybe)? I have to choose between "Appian RPA" and "MS power automation", I don't want to start with "Appian RPA" and to realize afterwards that it cannot do this and that, etc. Thank you so much.

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 fileHas anyone successfully used .eml files with AI Document Center classification?

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!

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.