Enable activity-chaining into all initial nodes in the subprocess

RE: Enable activity-chaining into all initial nodes in the subprocess

Shubham Aware — Fri, 21 Nov 2025 06:28:24 GMT

The checkbox makes no functional difference when a start form exists in the subprocess, The start form is skipped either way.
Appian recommends unchecking it purely for design clarity, to signal that this subprocess has a start form and isn't designed for activity chaining, making it clearer for future developers maintaining the process.

It's about documentation/intent, not functionality.

RE: Enable activity-chaining into all initial nodes in the subprocess

Mike Schmitt — Thu, 20 Nov 2025 19:15:29 GMT

your screenshot makes it look like your child process does NOT have a start form. What happens when you call a child process that DOES have a start form, with the option un-checked?

EDITED TO ADD: OK, i whipped up a quick test for myself, and like you, i am UNABLE to get the child's process start form to show up when it's launched from a chained parent task. (I originally assumed this just always happens with subprocesses with start forms, and this confirms my original suspicion). I think this is just maybe a case of outdated legacy verbiage in the documentation. That or something got overridden and overlooked in some Appian update, and nobody ever raised it as a bug. If it's important to you, you could try submitting a Support Case with a bug report.

RE: Enable activity-chaining into all initial nodes in the subprocess

gd008227 — Thu, 20 Nov 2025 18:40:16 GMT

As per my testing the start from is not shown to the user. Then why is the documentation pointing to clear it when having a start from?

RE: Enable activity-chaining into all initial nodes in the subprocess

Mike Schmitt — Thu, 20 Nov 2025 15:18:36 GMT

I think (but have almost never tested) that if you uncheck the "enable chaining" option, it means the user who chains into the subprocess will hit the start form and be able to complete it, as opposed to chaining past the start node into the first task in the process. I say I've almost never tested this because I rarely use start forms at all, and would never use one as a user-facing subprocess (or at least, I haven't found any use cases where it would make anything easier).

Also of note: this option goes back to VERY legacy Appian versions, and I'm unclear whether it still behaves the same as it was originally designed to.

What was the result of your testing?