Seperate items that are ECL driven vs Metastorm native client.

Michael_Turek

Is there a way for me to show process information depending on what drives the process?

 

For example - we have 2 processes:

1) ECL driven - we design todo watch list and forms

2) native metastorm client

 

I'd like the native metastorm client to not show the ECL driven process.  This means todo list / watch list / blank forms etc...

 

The reason being is that, the forms that are created for the ECL are of little use for the user and do not want them to see something on the todo list of the metastorm client when they should go somewhere else...

 

Ideally somewhat that is used similar to discern mobile and regular metastorm forms.

 

 

Brian Mellert

The mobile/regular forms process does not hide things from the web client.  Folders show in either case, though perhaps its possible to build a dynamic role that checks for the user's connection method instead of using standard role assignments.

 

Might it be as simple as don't assign users on the ECL enabled process ... then it won't be on their ToDo / Watch lists? 

 

An alternative may be to have distinct roles in the two processes/solutions.  One has users applied that show only on the standard interface.  Another has users applied to show only on the ECL interface.  Separating by roles shouldn't be difficult, but I'd think users would then have two separate log-in IDs then.

 

Another possibility may be to have separate engines for the two "types" of processes.  Somehow that seems like overkill.  I doubt that is an ideal situation, and the user would have to log into two different places (which I guess they do if you want to separate them anyway).

 

I'm sure others will have better ideas.