Skip to main content
July 24, 2024
Solved

Rule Event and Activity Chaining

  • July 24, 2024
  • 6 replies
  • 0 views

Hello,

Is the Rule Event node supposed to break activity chaining?

If yes then could someone point me how to achieve something similiar? I've got to wait for all incoming 0 to 4 flows to finish and then start the Statuses PM, all without breaking AC so i thought rule event was perfect for that but its breaking the AC. I know adding XORs and dummies in each route going into AND would solve this but im running low on nodes so maybe theres more efficient way. I'm on Appian 23.4

Thanks!

Best answer by stefanhelzle0001

A rule event is made for a different purpose and will break chaining.

In scenarios in which I need to wait for 1-n parallel flows, I start all of them, but include the skipping and merging logic in each parallel flow. This way I can just wait for all of them in a simple AND.

6 replies

venkatrea696188
July 24, 2024

Activity chaining used when there is a requirement of  successive form-completion by the same user. I don't see any Screens (User input tasks) in your Flow, Do you have any UIT's in Subprocess??. I don't recommend activity chaining if you don't have user screens (It leads to Performance issues).

I've got to wait for all incoming 0 to 4 flows to finish and then start the Statuses PM,

Activity chaining's gonna break when there is wait time of more than 5 seconds. You need to make sure that all paths are completing before 5 secs. I don't know  exactly but try using Complex gateway (Select wait for n of n Paths to arrive before processing).

varuntejg243705
July 24, 2024

Hi [mention:98f9e066def349f386cd6e60367db860:e9ed411860ed4f2ba0265705b8793d05] ,

Activity Chaining is considered to make process complete faster when there are no breaks needed, you had activity chaining all throughtout the process model.

Activity chain breaks when the node waits for 5 or more seconds and the process will be on hold, never goes forward.

your rule event may be taking some time to process, but the only solution is to take off chaining where the node continues to take some time to evaluate.

try to optimize the nodes, and put proper chaining where the node doesn't take much time to proceed further.


stefanhelzle0001
July 24, 2024

A rule event is made for a different purpose and will break chaining.

In scenarios in which I need to wait for 1-n parallel flows, I start all of them, but include the skipping and merging logic in each parallel flow. This way I can just wait for all of them in a simple AND.

July 24, 2024

I was afraid thats gonna be the case. Thanks!