What are the underlying mechanisms?

Firstly, the team members are grouped together using the “manager” attribute, as defined in W4Admin administration, which is either inherited or not from a LDAP directory. When a user logs on to W4 BPM Workspace, the list appears of the players for which he or she is responsible. If the list is empty, access to this module is not available on the home page. This list is stored in a cache on the server in order to optimise the calculation of workloads. These are either displayed by number of tasks (by default), or by workload, expressed either in days or in hours. In the latter case, it is vital that the standard duration of each activity has been defined in W4 Studio during modelling.

Significance of the various pictographs and other useful indications…

•	In this table, the applications are sorted in descending order of priority with regard to the parent process. For each application, leading and initiating roles are indicated by the icons and respectively, and the players involved are marked by the pictographs and . The procedures for which the connected players are responsible are indicated by the icon .
•	Un clic sur le nom de l'acteur affiche ses propriétés, incluant le paramétrage de sa présence et de son substitut. L’absence du pictogramme à côté du nom de l’acteur signifie qu’il est absent. Le choix du remplaçant est facilité par la mise en fin de liste des acteurs absents.

•	• When clicking on the icon after a player’s name, the task recycle bin for this player is displayed for all applications combined. Clicking on the workload figures on the table gives a partial view of the user’s recycle bin, either in terms of the procedure, or in terms of the application.
•	The display may be targeted by means of a number of filters.