Activity Chaining

brettw over 5 years ago

I've been told that ubiquitous activity chaining is a bad practice, but why is this the case? It seems to me that there are applications where activity chaining is necessary end to end, and indeed I've seen such applications function just fine.

Is it a performance concern, or more a contrast with clean code philosophy?

Thanks

Discussion posts and replies are publicly visible

Top Replies

Mike Schmitt over 5 years ago in reply to omere0001 +5
Certified Lead Developer

It should also never be used after the last User Input task on a process because it is not necessary after that point. For what it's worth, I've experienced multiple use cases where this is outright…
omere0001 over 5 years ago +1
Certified Lead Developer

Using activity chaining in excess uses up system resources and memory. You may not notice this in a dev environment, but you should always try to build your processes to be as efficient as possible. Activity…
harrisont606 over 5 years ago +1

Judicious activity chaining is not a bad practice and virtually every Appian project uses it in some way. Excess activity chaining is a bad practice, as chained nodes will be prioritized needlessly.

Parents

harrisont606 over 5 years ago

Judicious activity chaining is not a bad practice and virtually every Appian project uses it in some way. Excess activity chaining is a bad practice, as chained nodes will be prioritized needlessly.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel

Reply

harrisont606 over 5 years ago

Judicious activity chaining is not a bad practice and virtually every Appian project uses it in some way. Excess activity chaining is a bad practice, as chained nodes will be prioritized needlessly.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel

Children

No Data