Extensibility

Hi everyone, We’re working on enabling document preview functionality in our Appian application. We created a Web API that can successfully preview and download documents from the UI. However, we’re facing an issue specifically with Microsoft Office files (Word, Excel, PowerPoint). Instead of previewing in the browser, these files automatically download. Current behavior: PDF files preview correctly in the browser MS Office files (.docx, .xlsx, .pptx) always trigger a download, regardless of browser settings We are returning the document via a Web API using proper headers, but preview still doesn’t work What we need help with: Is it possible to preview MS Office documents directly in the browser using Appian? Does Appian support inline preview of these formats, or do we need an external viewer (Office Online Viewer, Google Docs Viewer, etc.)? Any recommended approach, best practices, or sample configurations to achieve inline preview?

I am using Export DSE to Excel node so currently, the data in each tab of the Export uses the default horizontal (normal) formatting.  The user would like to have the columns transposed to Vertical formatting when the Excel is created. Excel tab show the data in vertical rather than horizontal.  So, column A would have all of the column headers, Column B  & Column C should hold the related data and so forth. Kindly give your suggestions From this to  To this

Hi everyone, I am developing a Custom UI SDK component (JavaScript/Web Component) to create a custom image gallery. My goal is to have this component working seamlessly in both Appian Sites and Appian Portals in version 25.4. The Problem: I have tried using existing plugins and my own custom code, but images are not rendering. When passing the Document IDs to the SDK, the component fails to display the images. I suspect this is due to session/authentication restrictions or how the source URL is being handled, especially considering the architectural differences between Portals and Sites. Technical Details: Version: Appian 25.4. Component type: UI SDK (JavaScript). Current approach: Passing a list of Document IDs and trying to resolve them within the component. Issue: The <img> tags remain empty or return 401/403 errors when the component is loaded. What I need help with: What is the best practice for passing Appian Documents to a Custom UI SDK so they are accessible i

Hi Everyone, I have few questions regarding the two AWS S3 related plugins available in Appian. Currently there are two plugins that appear to provide similar functionality for uploading and downloading documents to Amazon S3: Amazon S3 Utilities (Smart Services) AWS S3 Bucket Management (Connected System / Integration based) Both plugins seem to support operations such as uploading documents to S3 and downloading objects from S3. However, they follow different approaches in terms of configuration and usage. My questions are: 1. What is the main architectural difference between these two plugins? 2. Are they intended for different use cases (e.g., process-based vs integration-based)? 3. Is the AWS S3 Utilities plugin considered a legacy approach compared to the Connected System based plugin? 4. For new implementations, which plugin is generally recommended by Appian? I would appreciate any insights on when to use each approach in the real time. Thanks in advance! Ananda

Hi Team  we have requirement of generaing pdf file.we have designed a flow for that first we are generating the docx file from that will bys using PDF from DOCX service trying to convert pdf file. In this process we could see docx file generating successfully we are giving docx file as input to PDF from DOCX smart service.Docx file is generating successfully but pdf file is not generating.I can see PDF from DOCX is not running sucessfully with error message of "Exception exporting package".Can someone help me what could be the reason . Thanks for the response in advance.

I am using the Import Excel to Database plugin along with a Connected System to download Excel files from a client’s Google Drive. Here is the behavior I am observing: When the Excel file is created using Microsoft Excel, the file is downloaded successfully via the Connected System, and the plugin works as expected. All the data present in the Excel file is imported correctly. However, when the Excel file is created in Google Sheets, or when an existing Excel file is opened/edited and saved using Google Sheets, the file is still downloaded successfully, and I can see the complete data in the file. But in this case, the Import Excel to Database plugin treats the file as null and does not return any data. In both cases, the file extension is .xlsx. Is this a known limitation of the Import Excel to Database plugin when handling .xlsx files generated or modified by Google Sheets? If so, is there any workaround or recommended approach to handle Excel files comi

Hi Team  I am trying to convert word to pdf  i have used this plugin Convert DocX to PDF Aspos. i am getting  this error ErrorCode=99, ErrorMessage=Cannot invoke "com.appiancorp.suiteapi.content.ContentUploadOutputStream.close()" because "cos" is null] .I have configured necessary inputs. Thanks for the response in advance.

Hello, We are experiencing an issue with the PDF From HTML plug-in, as it generates the entire output on a single page. I would like to understand whether there is a way to render the content across multiple pages, preferably using a standard A4 page size. The problem becomes more pronounced when the generated content is very large and exceeds approximately 200 inches in page length. In such cases, Adobe has limitations when opening the file and truncates content at the top of the page. As a workaround, Adobe is only able to display the full content when opening the file in a web browser. I would appreciate any guidance or recommended solutions to address this limitation. Thank you.

We recently migrated our Appian environment from a legacy EC2-based infrastructure to Kubernetes. Following the migration, the below plugins have started failing. Affected Plugins: Rich Text Editor (Vuram): https://community.appian.com/b/appmarket/posts/rich-text-editor-vuram Timeline Chart Component: https://community.appian.com/b/appmarket/posts/timeline-chart-component Both plugins were working as expected prior to the infrastructure migration. Issue After moving to Kubernetes: The components are failing to load in the UI. Questions Has anyone experienced plugin compatibility issues after migrating to Kubernetes-based Appian environments? Are there any additional configuration steps required for custom plugins in Kubernetes deployments? Is there any known compatibility issue with these specific plugins in Kubernetes environments? Any suggestions or guidance would be greatly appreciated.

Hi Everyone,I am trying to create a SharePoint Connected System using Client Credentials-Entra ID authentication. We have created an Azure AD App and given the app read and write access to a specific SharePoint site. While configuring the connected system, can I use the link to the specific SharePoint Site in place of the instance URL? 

1. Responsiveness / iframe height (main priority)I have a custom component plugin  that loads in an Appian interface. The plugin’s UI is responsive (e.g. adapts to mobile and different breakpoints), but the iframe and field layout do not adapt to the content height. In the interface designer I set the component Height to Auto. The parent div gets the class CertifiedSAILExtension---height_auto, but the iframe still has an inline style like height: 270px !important; overflow: hidden;. So the plugin content grows vertically (and is responsive), but the iframe stays at a fixed height and does not grow with it. Content is cut off or overflows below the visible area. The JavaScript API reference (e.g. 25.3) only documents how to receive the height parameter via Appian.Component.onNewValue(); I don’t see any documented way for the compon

Requirement is to display single color for first bar in each row and for 2nd bar in each row it show change dynamically as per status of the field. We are trying implementing timeline chart for one of the use case in which it should display 2 Bars in each row. One bar's color is fixed and another should be changing based on status. But when we try to implement logic then color is not coming properly using colors{} inside timeline chart. Output is not coming properly. Using two different loops for two bars in each row but it's not reflecting in the chart : googleTimelineChartField(chartColumnData: {{type: "string",id: "Name",rowDataKey: "name"},{type: "string",id: "Title",rowDataKey: "title"},{type: "date",id: "Start Time",rowDataKey: "start"},{type: "date",id: "End Time",rowDataKey: "end"} },chartRowData:{a!forEach(items:index(local!ccatAssesment,"data&q

Has anyone experience with Connecting on premise Dynamics CRM system with Appian Cloud instance ? Can it be readily done ? If not what are the pre-requisites to be completed . The On-prem system moreover is on local ADFS authentication.

Hi everyone, When I exported data using "Export Data Store Entity to Excel" from a proprietary Excel workbook that contains formulas, the Excel formulas get corrupted. Is there any limitation on the Excel workbook version that can be used with "Export Data Store Entity to Excel"? I am using Excel 365. Symptoms: (1) Formulas are shown as text and no longer calculated, for example:_xlfn.VSTACK({""}, _xlfn._xlws.FILTER(category!J2:J1001, TRUE, ""))IF(A9=0,,SUM(A9:B9))(2) Japanese phonetic (furigana) information appears in the same cell.

I have found information regarding a 5MB limit when my Appian application uses an Integration Object to call another API hosted on an external system. However, if my Appian application is exposing a WebAPI, so that an external system can make a GET request to my Appian application, is there a size limit on the JSON payload that my Appian WebAPI can return to that external system?

I have a webAPI which will receive the document from external system in binary format, but for file size around 25 MB, the API is taking more than 25 seconds.Is there any way we can increase the API performance by reducing the time taken by it?Thanks in advance.

In http response I am getting IDs and codes. Each id will have multiple codes. now i need to store the code with respective Id in table. How to do it?

i am trying to create a data store , i have already created teh data type and i can see teh field from database , The data source schema does not match the type mappings: Schema-validation: missing table [`xxxx_LIST`] (APNX-x-xxx)

what is the maximum limit of data that an integration call can retrive/query/ get  in vice versa .., How much (what is the maximum limit) of data we can expose to the external systems (when using WEB API's), where we can configure/ set these data limits

Hello Appian Community, I'm experiencing a URL encoding challenge with query parameters in an integration and would like to know if there's a solution or workaround. The Problem: I need to pass query parameter values that contain spaces (e.g., "North America") to an external API via a GET request. When I use Appian's standard Query Parameters in my integration object, the spaces are encoded as + signs, resulting in ?searchText=North+America. However, the external API we're integrating with does not recognize + as a space character and requires spaces to be encoded as %20 (i.e., ?searchText=North%20America). What I've Tried: Pre-encoding the parameter with substitute() - Replacing spaces with %20 before passing to the integration causes double encoding, resulting in %2520 because Appian encodes the % character itself Using urlwithparameters() function - Still produces + encoding for spaces, which follows the application/x-www-form-urlencoded standard Stand

Hi Team, I’m encountering an issue while uploading a file as part of the integration. The upload works fine for PDF files, but when I try with a .rtf.gz file, I receive a 403 Forbidden error. Interestingly, when I upload the same file to the same URL using Postman, it works without any problem. Could someone please look into this integration issue and help me resolve it? Thanks in advance.

Hi everyone, To avoid ambiguity: my input is an excel document. The relevant sheet is the first sheet (index 0). In that sheet, the first row is completely empty, and the header starts on row 2 (e.g., A2, B2, …). When I try to read the data with readExcelSheetPaging(), Appian seems to interpret the sheet as empty and I get: List of Variant - 0 items Example Code: a!localVariables( local!excelData: readexcelsheetpaging( excelDocument: ri!excelInputFile, sheetNumber: 0, pagingInfo: a!pagingInfo( startIndex: 2, batchSize: 10 ), stopReadingAtFirstBlankRow: 0 ), local!excelData.data) What I have tried so far: Using the remove() function to remove the first row does not help. The empty row is removed but Appian still returns 0 row, interpretating the sheet as empty. If I modify the respective excel Input file sheet and put any dummy value in "A1", then the exact expression works as expected and returns data from row 2 onwards. In that case, removing/skipping the

Hi Appian folks, I am getting this error on Export SQL to Excel smart service - "The following error was raised by the Export SQL to Excel function:  Name is insufficiently unique". I have configured "Document_name_to_create" on this node by appending now() after the document name i.e. "Document Name " & now(). I understand that this error comes up when document name is not unique, although I have appended now() in the end, the error doesn't seem to resolve. How do I fix this issue?

I am raising an issue with the Plug-in called Advanced Rich Text Editor (component: richTextEditorField) which is not loading or displaying to some users in some browsers from last few days, I am using it from last few months, but this issue is occurring from last few days!In appian environment the plug-in version is 1.7.3

We are looking for connect our appian with on prem oracle via jdbc. We are trying to understand the error, but the suite/logs result in 403. There's another way for read it? We cannot have a troubleshooting without this kind of information.