WorkflowGen.com | Knowledge Base | Documentation | Downloads | Support | RSS

Entries from April 1, 2006 - May 1, 2006

What are the security rights defined for Process Supervisors and Folder Managers?

Posted on Monday, April 17, 2006 at 03:15 by Registered CommenterWFG Team in | CommentsPost a Comment

A Process Supervisor can:
- Cancel Requests
- Re-assign actions (action follow-up screen)
- Follow-up on all requests and actions of the process
- View process statistics
- Delete requests for processes with "In Test" status
 
A folder manager can:
- Cancel Requests
- Create new process definitions within his folder (administration module)
- Follow up on all requests and actions for all processes of the folder
- View statistics for all processes of the folder
- Launch requests for processes with "In Test" status (if the user is a member of the participant with the Requester role in a process)
- Delete requests for processes with "In Test" status

Please note: There is no "Manager" profile per se. A user is defined as a Folder Manager when he belongs to a Participant (Global) who's associated to that folder.


How to manage security rights for process users?

Posted on Monday, April 17, 2006 at 03:13 by Registered CommenterWFG Team in | CommentsPost a Comment

Process supervisor participants have the following security rights:
1. Re-assign actions
2. Cancel requests
3. View statistics

- A user who wants to follow up on current requests and is not a process actor needs to be associated to a participant with Process Supervisor role (without any other options checked).

- A user who wants to view statistics of a process needs to be associated to a participant with Process Supervisor role (with the option "view statistics" checked).

- A user who wants to view statistics of all processes has to be associated to a participant with Process Supervisor role (with the option "view statistics" checked) for all processes.

For change management purposes you can define a non-synchronized group in the directory that will be used to define the Process Supervisor participants systematically.

A synchronization action is never started

Posted on Monday, April 3, 2006 at 03:09 by Registered CommenterWFG Team in | CommentsPost a Comment

It is necessary to check if among the ways to this synchronization action there is not a loop whose at least an action would be started. This behavior is new since the version 4.2 R2 where this type of actions synchronize complete routes and not only the directly preceding actions. 
More info