Roles in solutions

You define roles at the solution level. You then associate roles with steps in tasks. You assign users and groups to roles in the Case Client to specify which users can access a particular task or step.

Roles can be shared by all the cases in the solution. For example, you define roles, such as Clerk, Approver, and so on, to organize the groups of users who must process different types of tasks in the application.

Restriction: You can define only one in-basket per role in the Case Builder. You can also define a personal in-basket and get access to the inbasket that contains all of the assigned work items. An in-basket filters work items in a queue to display only items that answer a specific query. If you want to define additional in-baskets, you must use the FileNet Process Designer.

Because you define roles at the solution level, you can reuse those roles across all case types when you design the solution. You can also choose to create a role that is applied only to a specific case type. When you create tasks or steps, you can assign roles to the task or step from roles that are already defined for the solution, or you can create a new role for the solution.

After you create the solution, you assign users and groups defined in your LDAP server to roles in the Case Client. For example, some roles that might create for an automobile claims solution are field agent, insurance agent, claims adjuster, supervisor, or fraud investigator. The roles define which in-baskets and Case Detail pages a case worker sees when using Case Client.