D6.5 workflow

Documentum 6.x compatible
workflow, workflow definition, workflow template and process and process definition are synonymous terms
work item = task

Workflows or processes serve the purpose to transform  the core business operations into  documentum activities.


A process consists of activities linked together via flows.

The activity (manual or automatic) describes the task or work item that must be performed.

The flow is the link between the activities and the package is the information “on” the flow including the document content and document properties.

The performer is a manual activity (green icon) that must be executed by a human user.

A process definition is stored as dm_process which refers to one or more activity definitions dm_activity.

The Content Server execute the process definition and creating a workflow instance of dm_workflow.

The dm_workflow instance includes one or more activity instances. Each activity instance generates one or more work items as dmi_workitem objects.

One or more packages (dmi_package) routed through the activities instances.

A simple validated process created with the Process Builder 6.6 (red colored arrows are added in the screenshot tool).

Workflow template

This illustration shows the correlation among Workflow Template and Activity

Workflow States

The failed state is also called as terminated state.
  • Dormant: A workflow is dormant when it has just been created or if it has been restarted from a halted state
  • Running: A workflow is running when it has started execution from a dormant state or has been resumed from a halted state
  • Halted: Halting a running workflow moves it to the halted state
  • Failed: Aborting a running or halted workflow moves it to failed/terminated state
  • Finished: Normal completion of a running workflow moves it to the finished state


The attributes of an activity definition describe the characteristics of the activity, including:

  • How the activity is executed
  • Who performs the work
  • How the performer is assigned
  • What starts the activity
  • What triggers are necessary
  • What is the transition behavior when the activity is completed

Manual Activity

A manual activity is performed by a person or multiple people.

This screenshot was taken from the Process Builder 6.6

The following performer options are available for a manual activity:

  • Workflow supervisor (the user who initiates the workflow)
  • Repository owner
  • Previous activity’s performer
  • Specific user
    • explicitly selected at design time
    • resolved at run-time by performer of another activity or via an alias
  • All users in a group: All users in the performer group must complete the task for the workflow to move forward
    • explicitly selected at design timer
    • esolved at run-time by performer of another activity or via an alias
  •  Single user from a group: All users in the group are notified and it can be specified which one user will perform the task:
    • first one to acquire the task from his/her Inbox
    • user with fewest unfinished tasks in his/her Inbox
    • The group itself can be selected the same way as for All users in a group
  • Some users from a group: It is similar to Specific user except that multiple users or groups could be specified and they all perform the activity in parallel.
  • Multiple sequential performers: Multiple performers can be selected and ordered. They perform the task one after another in the specified order. Optionally, each performer can be allowed to reject the task to the previous performer
This figure was taken from the Process Builder.

Automatic Activity

An automatic activity is performed by the system on behalf of a user. Per default the Workflow supervisor is set.

Screenshot from the automatic activity template "Link to Folder"
select a performer for a automatic activity

 Quick Flow (ad hoc wokflow)

A Quick Flow is a out-of-the-box workflow and has one activity per performer and can be structured in sequential or parallel form.