Skip to main content
gd008227
gd008227
November 20, 2025
Question

Enable activity-chaining into all initial nodes in the subprocess

  • November 20, 2025
  • 4 replies
  • 0 views

Hey!

I'm going through the Appian docs for activity chaining https://docs.appian.com/suite/help/25.3/Sub-Process_Activity.html#activity-chaining-into-a-subprocess-activity

I see that there is a checkbox to Enable activity-chaining into all initial nodes in the subprocess and Appian recommends(for the sake of design consistency) enabling activity chaining in the subprocess despite selecting this checkbox. 

My question is with respect to the following statements as highlighted in image below

1. I agree with the first statement and I have tried it out myself

2. The second statement says keep Enable activity-chaining into all initial nodes in the subprocess checkbox cleared if I have a start form in subprocess.

Now, my question is - does it matter if I have checked/unchecked this checkbox as I already know the start form will be skipped. Like what am I achieving by clearing the checkbox if I know it's going to skip the start form present in subprocess. As per my tests indeed the start form was skipped. Is 2nd highlighted statement is incomplete? Have you got something to add that I might be missing out?

Here are the process models I tried out the tests with
1. Parent process

4 replies

mikes0011
mikes0011
Brainy
November 20, 2025

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?

gd008227
gd008227Author
November 20, 2025
  • 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?
mikes0011
mikes0011
Brainy
November 20, 2025

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.

shubhama926776
shubhama926776
November 21, 2025

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.

Terms & ConditionsAccessibility statement