Introduction to Task Management Components in ADEP

As we know, ADEP has released a set of UX components in SDK. UX stands for ‘User Experience’. Reflected by the meaning, the purpose in designing these components is to bring users wonderful experience in the new platform.

Task management components are part of all UX components. They are designed for enterprise business process management purpose. With them, users can easily present data and content view of a defined task and manage the whole lifecycle of a task through from creation to completion. Task management components are Flex-based and provide strong APIs for users’ development.  It supports the integration with Document Services.

To achieve the ‘experience’ goal is a gradual process. In current phase, task management components on one hand make strength in data processing capability. It now can handle diversity of data types, such as raw data, document, image and so on. Moreover, it is extensible to support integration with different products, like Document Services. On the other hand, the components make the use to end users as easy as possible. Users can present task view in their applications just by a component and a few properties bound with data.

In the following, I list task management UX components so that you can have a glimpse on their functionalities.

  • Task Attachments

It is a component to display a task’s attachments.

  • Document Submit

It is an aggregate component of Task Payload Viewer and Task Actions. This component helps manage the submit functionality exposed through the task action component.

  • Task Actions

It is a component to display the possible completion actions (aka ‘User Actions’ in Document Services Process Management) for a given task.

  • Task Details

It is a component to display the details of a task and manage its status.

  • Task List

It is a component to browse a list of tasks.

  • Task Manager API – Default Implementation

It is a foundation component for task management.

  • Task Manager API – Document Services Bridge

It is a foundation component for task management to integrate with Document Services.

  • Web Document Viewer

It is a component that given an URL and a content type will display that content in a web-based flex application.

With ADEP release, Sample team has provided sample applications about task management components. You can access through ‘Getting Started’ entry on welcome page after ADEP installation. Also you can begin with the following guidance:

http://www.adobe.com/go/learn_dep_samples_taskmgmt_standalone

http://www.adobe.com/go/learn_dep_samples_taskmgmt_docservices

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)
This entry was posted in ADEP and tagged , . Bookmark the permalink.

One Response to Introduction to Task Management Components in ADEP

  1. Christa Kovac says:

    A few comments…
    . It would be nice if there was an explanation on the difference between standalone tasks and Document Services tasks. Standalone tasks are created on the web tier and stored in CRX. The Document Services tasks are “LiveCycle” tasks initated and stored on the Document server. All the PM UX components can be used for Document Services tasks; but, for standalone tasks, only the TaskList, TaskDetails and WebDocumentViewer components can be used.
    . The Task Manager API – Default Implementation is used for standalone tasks, whereas the TaskManager – Document Services bridge is used for Document Services tasks.
    . The Web Document Viewer does not provide AIR support.