أنت تعرض محتوى المساعدة للإصدار:

Task Management enables you to create Projects and Tasks to help manage content change and log change events:

  • Create projects that contain related tasks.
  • Create tasks to represent work to be performed on content.
  • Assign tasks to users or groups who perform the work.

For information about completing tasks that are assigned to you, see Working with Tasks.

Creating Projects

Create a project to organize a set of related tasks. Projects appear below the Task Projects folder in the left-hand frame of the Projects tab. Projects are automatically assigned to the user who creates the project.

After you create a project, you can populate it with tasks.

tmprojects

ملاحظة:

Members of the Task Administrator Group can see and modify all projects and tasks. If you are not a member of this group you can see and modify only the projects and tasks that you create.

  1. Open the Task Management administration page (http://localhost:4502/libs/cq/taskmanagement/content/taskmanager.html).

  2. In the left-hand frame, select the parent folder for the project and click New > New Project.

    ملاحظة:

    For a top-level project, select Task Projects as the parent. You can also use other projects as parents.

  3. Type a name and description and click OK.

Creating and Assigning Tasks

Create a task to track the work performed on a content item (page) in the repository. After creating the task, users can open the associated content from the WCM Inbox. (See Working With Tasks.)

Task assignment

Assign a task to the user that should perform the work. When assigned a task, the task appears in the user's Workflow inbox. You can also assign a task to a group. The task appears in the inbox of each user in the group so that any group member can perform the work.  

Scheduling

Specify the priority of the task and the deadline for completing the task. 

Task lifecycle

Tasks can have a status of Created or Completed:

  • Created: The task is created and appears in the user's inbox. With this status, all content changes are logged. 
  • Completed: The user has performed the work on the content. The user sets this status manually upon completing the work. With this status, content changes are no longer logged.

Subtasks

Create a heirarchy of tasks to represent task dependencies. Add a task as the child of another task to indicate that the parent depends on the child. The task tree provides a visual representation of task dependency. Dependencies are not enforced, so that parent tasks can be completed before child tasks are completed. 

Note: If you are archiving tasks, do not complete parent tasks until all subtasks are complete. See Archiving Tasks.

Select the parent folder of the task to see the details in the right-hand panel.

Manually Creating Tasks

Use the Task Management console to create tasks for a project.

ملاحظة:

Members of the Task Administrator Group can see and modify all projects and tasks. If you are not a member of this group you can see and modify only the projects and tasks that you create.

  1. In the project tree, select a project or another task and click New > New Task.

  2. Specify values for the task properties:

    • Name: The name of the task to appear in the Workflow inbox.
    • Assign To: The name of the user or group who is to work on the task. When assigned to a group, the task appears in each group member's inbox.
    • Content Path: The path of the resource that the task is associated with. Multiple tasks can be associated with the same path.
    • Description: Information about the task, such as instructions to users.
    • Task Priority: The relative priority of the task. The priority is useful for sorting tasks on the Task Management page.
    • Due Date: The date and time by which the user must complete the task.
  3. Click OK.

Automatically Creating Tasks Using Workflows

Use the Create Task step in a workflow to automatically create a task. The following workflow-specific properties can be configured for the task:

  • The task content can either be the workflow payload or a content item that you specify. 
  • You can specify one or more actions that the user selects upon completing the task. The action can then be used to determines the workflow route to follow.
  • You can provide a script that runs before the task is created. For example, you can manipulate the task content according to logic and runtime data.

For more information, see Create Task

Modifying Tasks

When a task is in the Created state, you can change all but the Name property.  When a task is completed, you cannot change property values. In either state, you cannot delete a task.

  1. Double-click the task.
  2. To change task details, edit the form fields to change property values and click Save.
  3. To change the status to Complete, click Complete Task.

Archiving Tasks

Automatically archive tasks when they are no longer immediately useful. Archived tasks are moved to a location in the repository so that data is persisted for auditing and the tasks do not appear on the Task Management page. Archiving can also improve the responsiveness of the Task Management page when retrieving task data. Responsiveness depends on the number of task nodes that need to be iterated, and the available resources of your server.

Archiving is not peformed by default. When you activate archiving, a cron expression determines when archiving occurs. Only tasks that have been in the completed state for a specified length of time are archived. Furthermore, only top-level tasks (first children of projects) are evaluated for archival. If a top-level task is ready for archival, it and any child tasks are archived.

By default, tasks are stored below the /etc/taskmanagement/archivedtasks node in the repository. You can configure the TaskManagement JCR Storage Implementation service to change the storage location.

ملاحظة:

You can also specify the location to store in-use tasks.

The following procedures assume that you have an application folder below /apps.

ملاحظة:

When working with AEM there are several methods of managing the configuration settings for such services; see Configuring OSGi for full details.

Configure task archival:

Using the appropriate method configure the OSGi service:

  • TaskManagement Archiving Service (com.adobe.granite.taskmanagement.impl.jcr.TaskArchiveService)

Configure the following properties to override default values, according to the following table:

Name

Type

Value

archiving.enabled

Boolean

true enables archiving. false disables archiving. The default value is false.

scheduler.expression

String

A cron expression that schedules archiving. The default value is 30 0 * * * ? (daily archival at 12:30 AM). 

archive.since.days.completed

Long

The number of days after the task is completed when the task is eligible for archiving. The default value is 365.

Configure task storage locations:

Using the appropriate method configure the OSGi service:

  • TaskManagement JCR Storage Implementation (com.adobe.granite.taskmanagement.impl.jcr.TaskStorageProvider)

Configure the following properties to override default values, according to the following table:

Name Type Value
taskstorage.historyrootpath String The path of the root folder in the repository where tasks are archived. The default value is /etc/taskmanagement/archivedtasks.
taskstorage.rootpath String The path of the root folder where tasks are stored. The default value is
/etc/taskmanagement/tasks.
taskstorage.jcrFilterImplementation Boolean Set to true to use the jcr query filter implementation, false to use the legacy filter. The default value is
true.

Changing the Task Administrator Group

ملاحظة:

When working with AEM there are several methods of managing the configuration settings for OSGi services; see Configuring OSGi for more details and the recommended practices.

The user group that is set as the Task Administrator Group can see and change all Task Management projects and tasks. The administrators group is the default Task Administrator Group.The Task Administrator Group property of the Task Manager Adapter Factory service stores the name of the group. 

To use a sling:OsgiConfig node to configure the service, use the following node properties: 

  • Node name: com.adobe.granite.taskmanagement.impl.service.TaskManagerAdapterFactory
  • Node property:
    • Name: taskmanager.admingroups
    • Type: String
    • Value: The group name.

For information about using sling:OsgiConfig nodes, see Configuring OSGi.

Use the following procedure to use the Web Console to configure the service: 

  1. Open the Web Console page and click the Configuration tab. (http://localhost:4502/system/console/configMgr)

  2. Click Task Manager Adapter Factory.

  3. In the Task Administrator Group box, type the name of the user group and then click Save.

تم ترخيص هذا العمل بموجب الترخيص العام غير المعدل الخاص بالإسناد وعدم التجارة والمشاركة الإصدار 3.0 ‏من ‏‏Creative Commons‏‏  إن بنود Creative Commons لا تشمل منشورات Twitter™‎ وFacebook.

إشعارات قانونية   |   سياسة الخصوصية على الإنترنت