-
Recently active
Have questions or feedback on the Appian Dev MCP? This is a great place to ask them. Appian’s Dev MCP plugin can be found on the Appian App Market here (https://appmarket.appian.com/listings/appian-dev-mcp), as well as a read-only version intended for production use or other environments where it’s important to avoid any design object changes (https://appmarket.appian.com/listings/appian-dev-mcp-read-only). Documentation and installation guidance can be found here: https://docs.appian.com/suite/help/latest/devmcp.htmlAnd finally, our public repo of skills to install alongside the MCP can be found here. We welcome contributions if you’ve developed a skill or skill update you think would benefit other users. https://github.com/appian/dev-mcp-skills
I have worked across various applications. In my first application, we had 2,3 query rules for same record type but each serving a different purpose depending upon the field being queried or the amount of data being passed. In another project, we have a generic rule for each record type which is being used whenever we want to query the data. In one more project, I have seen only one generic rule being used for all record types which in turn means even the record type is being passed dynamically. I want to understand which approach makes more sense, pros and cons and do we really need to modularize everything this much.
Hi,Here is the scenario I am facing:I open an Expression Rule and implement my logic. I add several test cases to validate the expected behavior. I save the Expression Rule, which creates version 18. Later, I modify the Expression Rule code and save it again, which creates version 19. When version 19 is created, I can see that the test cases from version 18 are available in the new version.Could you please explain why, when I delete version 18 and refresh the latest version, all my test cases are lost?I would expect the test cases to be kept in version 19 since they were automatically carried over when the new version was created.I tried this on many ERs and observed the same behavior.Regards
Hi everyone, I’m experiencing this odd behaviour with this specific dataset. The other start processes within the platform are running just fine! The log does not provide me any useful info also. This is my input example. The start process will run in MNI for each set of input. Sometimes parent process stopped because of this error: Failed to start process. Process Model ID: ButI open the sub-process it run till the end.The parent process will run sub-process for each pv!relationshipToUpdate. Process parameters are provided like below: Below is my pv!relationshipToUpdate example. {a!map(fileId: "FILE_GUID_001",relationshipToRemove: null,relationshipsToAdd: a!map(entityId: "ENTITY_001",entityType: "REFERENCE"),approvalNeeded: false,addRemovalNote: false,documentDescription: "Sample Document 1.pdf",updatedRelationships: {a!map(entityId: "CLIENT_001", entityType: "CLIENT"),a!map(entityId: "EVENT_001", entityType: "EVENT"),a!map(entityId: "CASE_001", entityType: "CASE")}),a!map(fileId: "F
I created a grid plus UI where I want to add color for status column like if active -green and if reject -red color and I also want to add some icon for one column, is it possible with Appian Grid Plus functionality?
I'm planning to create some reusable components in Appian. I've already built several, including reusable forms, page headers, message banners, empty state (no data) screens, date and currency formatting utilities, and a few others. Can anyone suggest additional reusable components, patterns, or expression rules that would be useful across most Appian applications?
Hi Appian Community, wanted to see if anyone has this setup of being an Appian Cloud customer and has email server setup with Microsoft 365 cloud SMTP relay, specifically for outbound emails from Appian → External Recipients?I am able to receive outbound emails from the Appian platform with my organization’s internal email addresses. The problem is when testing by sending to external email addresses (both business email addresses, tested by sending to @microsoft.com and personal email addresses, tested by sending to @gmail.com and @hotmail.com). They failed with 2 different error messages from the STDout log: Error 1 (Attempt to send to external business emails): 451 4.4.62 Mail sent to the wrong Office 365 region. ATTR35. For more information please go to https://go.microsoft.com/fwlink/?linkid=865268 [Full certificate chain to a Microsoft-trusted Root CA was not found in TLS handshake. See https://aka.ms/UntrustedRootNdr for more] [YT2PEPF000001C9.CANPRD01.PROD.OUTLOOK.COM 2026-08-04
Hey all! I'm sharing the Appian interface I recently built to give better visibility into the system's recent internal Login Audit files (instead of constantly downloading and opening CSV files) - particularly helpful if you're an O&M user and/or diagnosing login issues for any other reason. This interface relies on the Log Reader plug-in (and also uses the Date and Time Utilites plug-in for a certain transform on timestamps). That said, I can't say how it'll perform on multi-server environments, since I don't have one to try it on. The entire interface is self-contained, with the sole exception of a custom rule I wrote that utilizes the internal "User" record to take an entered username and get the system's properly-cased username (since there is some inconsistent case sensitivity around usernames and there's no other way I could come up with to tell what the 'real' version is). I'll include that expression rule co
We're experiencing an issue in the Appian Mobile App on iOS.When viewing a PDF document and tapping the Print icon, the app prints a screenshot of the current screen instead of the actual PDF document.Has anyone else experienced this?Is this a known issue with the Appian Mobile App on iOS? Is this expected behavior or a product defect? Are there any known workarounds or configuration changes to ensure the actual PDF is printed?@stefanhelzle0001
We're experiencing an issue with text rendering in the Appian Mobile app.EnvironmentAppian Mobile Android and iPhone Observed across multiple screensIssueAll text is displayed in bold, regardless of the font styling configured in the interface. This occurs on both Android and iPhone devices.For example:Labels, paragraph text, and other text components all appear bold. Read and unread messages in the Inbox look identical because both are rendered in bold, making it difficult for users to distinguish between them.QuestionsIs this a known limitation or issue with Appian Mobile? Has anyone experienced the same behavior on Android or iPhone? Are there any recommended workarounds or configuration changes to ensure normal font weight is displayed correctly?Any guidance would be greatly appreciated. Thank you!@stefanhelzle0001
Hi everyone,We're experiencing an issue with the pull-to-refresh gesture in the Appian Mobile app (IPhone & Android) and would like to know whether this is expected behavior or if there's a recommended solution.When performing the standard pull-to-refresh gesture (swiping down from the top of the screen):A refresh indicator appears. However, the screen content does not refresh or reload. The displayed data remains unchanged. @stefanhelzle0001
Hello,When users download a document from our application in Appian Mobile, the downloaded filename does not match the original document name.Android: The downloaded file is saved with a gibberish/system-generated filename.Is this a known limitation or issue with Appian Mobile? Is there a supported way to control the filename used when downloading documents on Android ? Are there any recommended workarounds to ensure the original document name is preserved? @stefanhelzle0001
sites have urls like this one:https://<subdomain>.<domain>/suite/sites/<SiteName> subdomains:https://<subdomain>.<domain>/<PortalName> We want them to be resolve them with the SiteName as the subdomainhttps://<SiteporPortalName>.<domain> Is it possible somehow to create a redirect url on your side (appian cloud) so that specific sites/portal can be resolved with unique urls. I am aware that we would have to create a dns delegation for that but the problem is that we cannot create delegations with url paths (i.e. /suite/sites/<SiteName>) and we do not seem to have a make that redirection.
Hi everyone, I encountered an issue regarding saving process variable using a!startProcess -> onSuccess on version 25.4, the fv!processInfo.pv.subCategory was not saved back into local variable ri!checkStatusofChangingCategory. Here is the code: a!startProcess( processModel: cons!NFL_CONS_PROCESS_CHANGE_CASE_TYPE_CATEGORY, processParameters: { subCategory: ri!subCategory, newCategoryId: local!selectedNewCategory }, onSuccess: { ri!saveInto, a!save( ri!checkStatusofChangingCategory, append( ri!checkStatusofChangingCategory,fv!processInfo.pv.subCategory ) ), a!save( local!currentCategory, local!selectedNewCategory ), a!save(ri!subCategory, null), a!save(local!selectedNewCategory, null), } ) The initial value of ri!checkStatusofChangingCategory was null after onSucess, it became [null]. This code worked with version a!startProcess_24r3 ( it successfully saved pv.subCategory into ri!checkStatusofChangingCategory), i want to know the reason why, what am i missing? I'm look
Hi All, We are using 24.2 Appian version and trying to update to 25.3 version. What are the perquisites to be checked to update Appian version and can we backup version if we required. Thanks Saidivya Minna
Hi Appian Folks, After community version got upgraded to 26.6, I see process models are not opening at all. Is anyone facing the same issue? 504 Gateway Time-out
Hi Everyone, I have a requirement where a user clicks a notification, and before opening the Summary page, I need to mark the notification as Read. To achieve this, I created a Process Model Start Form that updates the notification status and then displays the same Summary UI. The issue is that the Summary UI contains an email section with a File Upload field. When the user clicks Send Email, I call: a!submitUploadedFiles( documents: local!attachments ) This works correctly when the Summary UI is opened from the Record Summary page, but when it is opened through the Process Start Form, I get the following error: a!submitUploadedFiles() cannot be evaluated in this environment I understand that a!submitUploadedFiles() is not supported in a Process Start Form. Has anyone implemented a similar requirement? What is the recommended approach complete it Would creating a separate interface or dialog just for file uploads be the recommended approach, or is there a better Appian design patte
I have a question regarding the subprocess status shown in the attached screenshot. The subprocesses are displaying the status as "Unattended" instead of "Completed". I have configured the subprocess node to "Run as whoever designed the process model" in the assignment settings. Could you please help me understand why the subprocesses are still showing as Unattended rather than Completed? I've attached the screenshot for reference.
I'm looking for a way to generate an Excel file from a template in Appian while ensuring that all existing formulas in the template are preserved. Has anyone implemented this or knows of an approach? Thanks in advance.
currently I have a subprocess that uses pp!initiator to get the user data to check few validation, and one sometimes the pp!initiator seems to not pick the user from the parent process and i think instead it picks the masteruser (i.e. ABC) which was used to publish the process model. It happens on random instances. Am i missing something.
Is pursuing a career as an Appian developer a wise choice?
I have process model which run subprocess.Both main and sub process already set alert to specific user. However, when error occur on sub process, alert email was sent to all admin in environment (admin@xxx.appiancloud.com) Are there any workaround for this issue? ----- Following is main and sub process configuration. Main Process Sub Process
Hi everyone, We're planning to upgrade our production environment to Appian 26.6 and currently we are on 25.3 version, wanted to check with the community before proceeding. For those who have already upgraded to 26.6, have you encountered any significant issues, regressions, or unexpected behavior after the upgrade? Our application is a fairly large enterprise solution with extensive use of Record Types, Process Models, Connected Systems, integrations, and custom plug-ins, so we're keen to understand if there are any unexpected issues faced due to upgrade. Any feedback or recommendations would be greatly appreciated. Thanks in advance!
Hi, I have a button on my application's homepage/landing page designed to execute a specific task in the database. When clicked, it should trigger the appearance of a dynamic interface. This interface should smoothly transition into view, causing the landing page interface to fade away. For visualization consider below screenshot, imagine the "Create Interface" dialog overlaying the landing page interface, which fades into the background during the task interaction.
Hello team, I have a parent process model from which I am triggering child process instances asynchronously using MNI. The child process instances have been successfully triggered and have reached the end node. However, the parent process instance is still showing as Active in the Monitor tab since yesterday. Additionally, when I view the process instance and hover over each node, the Start Process node appears disabled, whereas the End Event node appears enabled. Could you please help me understand why the parent process instance is still in an active state despite the process reaching the end node? As I am triggering child instances through MNI, my understanding is that if I use a Terminate End Event in the parent process, it will also terminate the child process instances. Therefore, I do not think that approach will work for my scenario. Please correct me if my understanding is incorrect.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.