Sipke Schoorstra

Very observant :) It is indeed inspired on WF’s API.

@tomy2105 @jdevillard > However I have one huge fear about this, and it is called backward compatibility. How easy will it be for people who wrote their own activities (god...

@jimitndiaye > Is there a specific reason why you've separated activities from their handlers? Generally I picture activities as self-contained bits of functionality including inputs, variables and an functional implementation....

Check out this sneak-peek of a POC I'm working on for the Elsa 3 designer with embedded activities (as discussed during last community call)! There's still a lot of work...

Yep, that’s the plan.

Here's an updated preview that takes inspiration from WF & ADF: 

I'm on the same page with you there actually. I'm thinking to do it like this: - The current *If* activity is a regular activity that "embeds" the *Then* and...

@tomy2105 > Third, the interesting question here for Join any is what happens with the rest of not executed activities in branches when join is executed. Are they allowed to...

@tomy2105 > True parallel execution What you described here makes perfect sense and is in line with what I'm thinking to go with. Right now, we can implement "jobs" that...

Thanks everyone for the wonderful input provided here! Everything considered, I decided to implement support for both **implicit** as well as **explicit** forks and joins (although I still have an...