Task Engine 10.11 | Task Engine Webhelp | webMethods Task Engine User's Guide | Administering Tasks | Configuring Support for Collaboration Tasks
Configuring Support for Collaboration Tasks
In general, most administrative functions for collaboration tasks are the same as regular tasks. Additional administration procedures for collaboration tasks include:
*Grant collaboration permissions—a set of permissions pertaining to collaboration tasks can be granted to users, roles, and groups. For a list of task collaboration permission, see About Task Type Functional Permissions.
*Enable/disable collaboration—you must enable a task type for collaboration to allow user to create and work with collaboration tasks from within instances of that task type. For more information, see Disabling and Enabling Task Collaboration.
*Enable/disable task data sharing—you must enable task data sharing if you want task business data to be shared between parent and child tasks. For more information, see Disabling and Enabling Task Data Sharing.
*Specifying allowed collaboration tasks—you can assign specific task types for selection by the user when the user creates a collaboration task. For more information, see Specifying Allowed Collaboration Tasks.
*Set display options for collaboration process diagrams—you can specify the layout of the collaboration process diagram on the Process Details page (horizontal or vertical), and the icon used to represent a task step in the collaboration process diagram. For more information, see Setting Display Options for the Collaboration Process Diagram.
*Specify a task e-mail listener—a user can reply to a specially configured task notification by e-mail. To process these replies, you must specify and configure an e‑mail server and account for this activity. For more information, see Configuring a Task E-mail Listener.
Although it is not strictly a collaboration administration procedure, you must also configure a connection to an instance of webMethods Monitor if you want to monitor collaboration processes started from a running business process.