New to Appian - Recent Threads

RE: Request for Appian Interview Questions Based on Current Industry Practices

bk8577 — Thu, 02 Apr 2026 03:02:52 GMT

You can check https://appianverse.com/practice — it’s a good Appian practice resource that covers almost all topics and is really helpful for brainstorming and sharpening your Appian skills.

Request for Appian Interview Questions Based on Current Industry Practices

abramm663344 — Wed, 17 Sep 2025 13:14:59 GMT

Hi Community,

I have prior experience working as an Appian Developer for about 1 year, and after a career break, I have recently revised the Appian tutorials and refreshed my knowledge.

Could you please share some commonly asked Appian interview questions that reflect current industry practices (for example, on record types, queries, process models, activity chaining, and best practices)?

This will help me prepare more effectively for upcoming interviews.

Thank you in advance for your guidance!

Version Control like Git?

darend482717 — Wed, 18 Mar 2026 20:13:56 GMT

Hey all, new Appian developer here! From what I have learned so far, Appian dev teams don't usually follow the branch->merge workflow, but rather work inside the single dev environment. I have no problems with this system and think it is the ideal approach for 99% of cases. However, in a situation like a refactor, where you are changing some of the architecture and breaking a few parts of the system as a side effect, I can see how branching off to make these changes would be safer, cleaner, and not prohibit other developers who need to use the parts that are being changed.

Is there any version control (or hacky workaround) that could solve this in these rare situations? Thanks!

RE: Version Control like Git?

ericc087568 — Thu, 26 Mar 2026 21:53:29 GMT

We're doing a half-way version with Azure Dev Ops pipelines which sticks items in repo. Problems occur though if attempting to get back to point in time because of recordtypes / database and service dependencies / and pull request per user story became a nightmare with some items passing testing but not all, etc.

RE: Version Control like Git?

Stefan Helzle — Thu, 19 Mar 2026 09:55:49 GMT

IMHO the main reason for git is decentralized development in potentially large teams.

Development in Appian in centralized and in small teams, so I do not see any need.

When changing objects, I typically do not just change that one object, but follow the chain of dependencies and adjust them to work with the changes.

RE: Version Control like Git?

Shubham Aware — Thu, 19 Mar 2026 05:21:24 GMT

Appian lacks native Git branching - teams share one dev environment with object versioning.
Workaround - Prefix-clone the objects being refactored (e.g., v2_myProcess), work on clones, swap references when done, delete old ones.
For refactors, use AVM plugin

RE: Character Limits for Data Types

aldousemerson0331 — Thu, 19 Mar 2026 00:15:16 GMT

You will also notice that in the data preview of the Record type, there are no missing characters, persisting bytes beyond the record field limit is also no problem as long as the database field can cater to it.Only when the data is queried that it gets truncated.

Character Limits for Data Types

yongj783799 — Mon, 08 Sep 2025 07:00:23 GMT

Hi all,

I had just been researching on the different character limits for data types. So from my understanding of text data type, these are the following limits.

Text - 255 characters

Long Text - 4000 characters

Extra Long Text - 64000 characters

To my knowledge these are the 3 available options for any VARCHAR in record types, I was just wondering if this information is correct, wanting clarification please.

Couldn't really find a clear answer on the limits.

Note: I believe that for record types, there's a limitation for Extra Long Text, limited to only 3 fields within a record type that's allowed to have the Extra Long Text data type.

Introduction to Process Modeling - Exercise 2: Examine and Configure a Process Model

cnoriego — Sat, 14 Mar 2026 10:43:01 GMT

Hi,

I'm following the exercise in the attached PDF, but I'm getting the following error:

"Reply-To email did not resolve to a valid email address."

I've repeated the steps several times but I can't figure out what might be causing it. Since I'm new to Appian, I'm also not very familiar yet with diagnosing or resolving these kinds of errors.

Could someone please help me understand what might be wrong or what I should check?

Thanks in advance!

[View:/cfs-file/__key/communityserver-discussions-components-files/62/Exercise-2_5F00_-Examine-and-Configure-a-Process-Model.pdf:320:240]

RE: Introduction to Process Modeling - Exercise 2: Examine and Configure a Process Model

Harsha Sharma — Wed, 18 Mar 2026 05:47:27 GMT

The screenshot shared doesnt show any value in Reply To filed yet the error mentions this field. So first clear contents of this field properly (Open expression editor as well and ensure it is blank). Also, worth mentioning, verify the users in the group mentioned in 'To' have valid email addresses to avoid any other errors/issues. Give it a try!

RE: Introduction to Process Modeling - Exercise 2: Examine and Configure a Process Model

amitm9 — Wed, 18 Mar 2026 04:29:40 GMT

Check your email string is valid or not? If valid then clear the set value and re-map with custom value, try to test that way.

RE: Introduction to Process Modeling - Exercise 2: Examine and Configure a Process Model

Shubham Aware — Tue, 17 Mar 2026 05:18:00 GMT

Clear the Reply-To field completely in Send E-Mail > Setup tab. The exercise doesn't require it, and it's causing the error since it's not set to a valid email string. Test with High priority.

RE: Error while using saveInto and recaptchaSaveInto in buttonWidget

Shubham Aware — Fri, 13 Mar 2026 09:38:12 GMT

In Portals only: Remove saveInto completely from the button.
Put all your saves inside recaptchaSaveInto using a!verifyRecaptcha().

This is required because reCAPTCHA reserves the button's save flow.
https://docs.appian.com/suite/help/26.2/fnc_connector_recaptcha_verifyrecaptcha.html

Error while using saveInto and recaptchaSaveInto in buttonWidget

AjinkyaK1 — Thu, 12 Mar 2026 11:54:02 GMT

Hi Everyone,

I am learning Appian and working on a simple interface form. While submitting the form, I am getting the following error:

"A button component must not contain both a 'recaptchaSaveInto' and a 'saveInto' parameter."

I tried removing some parameters but the error still appears.

Can someone explain why we cannot use both saveInto and recaptchaSaveInto in the same button and what is the correct way to handle this?

Any guidance would be helpful.

Thank you.

RE: Error while using saveInto and recaptchaSaveInto in buttonWidget

Harsha Sharma — Thu, 12 Mar 2026 13:47:03 GMT

recaptchaSaveInto is to be used only with Portals. If you are not working with Captcha and portals always use saveInto as that is used to update values in variables.

So removing the recaptchaSaveInto will resolve the error you are facing.

Ref documentation docs.appian.com/.../Button_Component.html

RE: Databricks Integration Help

sushilk061231 — Tue, 10 Mar 2026 18:50:46 GMT

Hello Guy, just checking — have you created the Data Fabric using the Databricks JDBC connection? I’ve already raised a request with Appian Support for the JDBC driver installation.

Please let me know if there’s anything else we need to do from our side.

Thanks.

Databricks Integration Help

nickt765247 — Mon, 16 Jun 2025 22:35:36 GMT

Hi!

Is it possible to use Databricks as a data source with Appian? I know it's not directly supported but maybe there's like a workaround possible? Any help would be great!

Unable to see new data table option

Guna — Fri, 06 Mar 2026 11:24:22 GMT

Hi, I'm new to the Appian. I'm unable to see the 'New Data table' option as mentioned in this documentation: Create-record-data-source.html

So, I Selected Database option and I'm unable to proceed after that. No options provided here to select.

Help me resolve this and provide me the steps to create an database and make connection to the interface. Share any documentation URL or online course for this.

RE: Unable to see new data table option

Guna — Tue, 10 Mar 2026 05:14:38 GMT

Okay, Thanks

RE: Unable to see new data table option

Shubham Aware — Mon, 09 Mar 2026 17:05:50 GMT

Avoid posting links, promotional language.
If flagged, email community@appian.com to appeal for quick moderator review.

RE: Unable to see new data table option

Shubham Aware — Mon, 09 Mar 2026 17:02:02 GMT

The site was most probably under maintenance at that time.

RE: Unable to see new data table option

Guna — Mon, 09 Mar 2026 16:03:56 GMT

And If I create a new post/reply in Appian community. It is flagged as SPAM. What should I do to avoid this?

RE: Unable to see new data table option

Guna — Mon, 09 Mar 2026 14:26:05 GMT

Thanks Shubham Aware , this is working now.

I already tried creating workspace by completing survey multiple times, at that time workspace didn't get create but now it got created. Any specific reason?

RE: Unable to see new data table option

Shubham Aware — Sat, 07 Mar 2026 02:12:46 GMT

After logging into your Community Edition instance and selecting your region, instead of clicking directly on "Appian Designer" from the navigation menu, you'll encounter a survey that prompts you to create your own workspace. Complete this survey to create your workspace, then create a new application within that workspace(Wait for few minutes to create workspace for you then from navigation you can see Cloud Database option with workspace ID). When you try creating a record type in this newly created application, you'll find that the "Create Data from Scratch" option becomes available.
This workspace creation process through the survey flow, rather than directly accessing the designer, appears to unlock additional features including the built-in database capability that's typically restricted in the Community Edition.

You should receive email from Appian community edition for workspace creation.

https://community.appian.com/p/community-edition-guide#about

Login unsuccessful exception on Appian-Locust

manasagarreboina — Tue, 24 Feb 2026 13:02:26 GMT

Hi,

I am new to Appian-Locust, I have installed Appian Locust, executed a login script for Appian URL and I am getting this exception "Login unsuccessful, no multipart cookie found, only found <RequestsCookieJar[<Cookie JSESSIONID....". I checked my credentials and they are working fine when login manually. I have tried executing the same Appian URL via generic Locust and there is no such exception shown.

Can anyone help here.