[FEATURE]: Rename EXCLUSIVE_JOIN to a more intuitive name

[aravindanr]

Please read our contributor guide before creating an issue.
Also consider discussing your idea on the discussion forum first.

Describe the Feature Request

The name EXCLUSIVE_JOIN does not do justice to the work that this task does. EXCLUSIVE_JOIN sounds like a specialized version of JOIN, when in fact the two tasks are not related.

JOIN : Join task is used to wait for completion of one or more tasks spawned by fork tasks. EXCLUSIVE_JOIN: Exclusive Join task helps capture Task output from Switch Task's flow.

Describe Preferred Solution

Rename the EXCLUSIVE_JOIN task to SELECT , while maintaining backwards compatibility with workflows using EXCLUSIVE_JOIN.

Describe Alternatives

N/A

[ZergRushJoe]

#2758 As I was confused by this. It maybe a good idea to have some examples with the each system task of the use cases that show images of the workflow. Current state: I could put together some prs for improving the docs

[aravindanr]

@ZergRushJoe Please do. Appreciate the help. the docs need some love.

[jkaipa]

@aravindanr When I introduced this System Task, I have reviewed several names and felt that Exclusive_Join makes better sense wrt the way the exclusive output is produced to the join.

I will prepare some examples and better documentation soon.

[jxfw]

Where can i find the docs about the EXCLUSIVE_JOIN? Anyone help?thanks.

[apanicker-nflx]

@jxfw The documentation for the EXCLUSIVE_JOIN was missed during the transfer to the new website, we will update this soon. Thanks for reporting.

[jkaipa]

@apanicker-nflx I will prepare some examples with usage instructions for this system task in next week or two. Its a long time due.

[apanicker-nflx]

Thank you @jkaipa , we will add this to the conductor docs site.