Unwieldy Setup Participants table

[matthew.yacono]

We have a task in our workflow that requires some one to populate 10-30 roles that each have 5-20 principals to choose from. The issue we have now is the table that results from using Setup Participants in conjunction with the resource pool function is about 250 people long and 30 roles wide. Is thereanother way to allow this person to perform this setup participants task without having to deal with such a large table? Perhaps individual tables per role can be generated or perhaps each role shown as a drop-down populated with principals from its resource pool? Has anyone else dealt with an issue like this and how did you resolve it?

TIA

Matt Yacono | Research & Development | Alcon Labs | (949) 727-7559 | matthew.yacono@alconlabs.com

[avillanueva]

It the team being altered is the ECN team, you could direct the user to
just modify the team for the ECN. The team editor might be easier to
use. The workflow should pickup the users from the
primaryBusinessObject team.



I also have a DataUtility that limits users in a drop down list to just
Product members. If you have a workflow user variable, it would normally
appear as a drop down with every user in the system, 250 in your case.
Do you have a case where its one person per role? If so, you could
create user variables in place of each role. The task would have each
role as a drop down list. To do multiselect would take more
investigation. After the user variable is obtained from the task,
workflow code can add that user to the role you need.



The DataUtility is defined in the config XML files and called out in the
task form template like this:

<jca:describepropertypanel var="ecCreatorPanelDescriptor">

<jca:describeproperty id="EC_Creator"&lt;br"/>dataUtilityId="goodrichPrincipalSelector" />

</jca:describepropertypanel>