Query : Workflow Connectors Limit? (1 Comment)

Topic by MB

Hi,

We are trying to replicate a custom rule engine developed by customer for which I've built a workflow based on below logic.

It works fine but I need to know if there is a limit to number of connectors which can be used from a single workspace element.Here is my flow.It's a multiple profile single workspace type

Customer Ask:

Whenever a certain product is selected, a series of cascading tasks should get created.E.g. for 1 selection there could be 3 tasks viz task1, task2 and task3 and for other it could be 4 or xx. 

When task1 gets completed, only then task2 should appear and so on.

Note: This is we are talking about just 1 selection.Like this there could be many selections:tasks combo

My Solution

Using WF, I was able to achieve this ask.Its bit complicated to explain here though but it works fine

1. CSR selects certain product value in incident workspace which fires a named event
2. Based on named event, my parent workflow calls another embedded workflow that has the logic
3. Then there is a Main Task WF that comes into play based on certain CF set in logic at #2

My only challenge is that in above scenario,based on customer requirement, I've upto 400 distinct named event that originate depending on the product selection.Each embedded workflow has a distinct logic and hence I cannot keep a generic WF for all

The only option for me is to have 400 named event firing WS rule , 400 connectors from parent workflow and 400 distinct embedded workflows.

Now I've only tested with 4-5 named event and before proceeding further would like to know

• if there is a better way to implement above scenario
• If there isn't, will there be performance impact on WS loading if I go with my available option as described above

Can someone from Oracle Product development team advice on this?

Thanks,

MB