Assigning and Managing Tasks

A task is a request from one user to another to perform an action within Ektron. Examples of a tasks include:

• updating content
• publishing content
• updating an image
• reordering a collection

If you are not in the administrators group or assigned the Task-create role, the Tasks folder only displays tasks assigned to you or that you assigned to another user or user group. You can also assign tasks to yourself.

Administrators can view all tasks, regardless of who they are assigned to or by.

A task may or may not be related to a specific piece of content. If it is, you can access content then “attach” a task to it. This kind of task is managed just like the other tasks, but you can also view and update it via the attached content.

The following are some of the concepts and procedures related to tasks:

• Task Permissions
• Task Categories and Types
• Task States
• Creating a Task via the Tasks Folder
• Creating a Task from the Web Site
• Creating a Task via the View Content Screen
• Viewing a Single Task
• Viewing All Tasks
• Viewing a Task’s History
• Editing a Task
• Adding Comments to Tasks
• Archiving a Task
• Deleting a Task
• Deleting Several Tasks at Once
• Purging a Task
• Task Email Notification
• Automatically Creating Tasks Associated with Content

NOTE: Tasks can also be created automatically when forms are submitted. See Also: Assigning a Task to a Form

Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task