Objects involved in workflow
Build
Time:
·
dm_process
·
dm_activity
Runtime:
·
dm_workflow- Runtime workflow object created from
dm_process workflow template.
·
dmi_workitem- Runtime instances created for each
workflow activity.
·
dmi_queue_item- Information about tasks for a
aspecific user. If for particular activity, User A is assigned performer or in
a group of performer then dmi_queue_item object will be created for the same.
All inbox items we see in user’s inbox are dmi_queue_items.
·
dmi_package- This is the object which gives
information about the documents attached in the workflow.
Now let’s discuss about the possible errors that can come
while running a workflow.
If you have workflow notifications on, you will get a mail
notification if there is any error while
processing a aworkitem.
dm_changedactivityinstancestate:-
In docbase "ABC":
User "superuser" posted event
"dm_changedactivityinstancestate" with this message: "Activity instance, 0, of workflow,
4a012a53802ssscc, failed.".
If any error comes(Timeout error/ code error in auto
activity method) workitem is put into paused state. Not while processing
workitem if it’s in paused state, such workitem could not be completed and can
throw above error.
Possible
causes:
ü Check
the timeout value set for respective workflow auto activity.
ü Check
the content server settings. Sometimes it happens because of multiple content
servers trying to process same workitem.
dm_wf_resolve_failure:-
In docbase "ABC":
User "xyz" posted event "dm_wf_resolve_failure"
with this message: "An error was
encountered in a workflow for which you are the supervisor. The system was unable to find a performer for
'Group_processor'. This task has been
assigned to you.".
If
for an activity particular Group(Group_Processor)has been assigned and if no
user is present in that particular group
when workitem is in progress, above error will be thrown. As no user is found
the error notification will be sent to workflow supervisor.
Possible
causes:
ü Check
the error group if any user is added in it or not.
ü Check
the activity performer configuration. The configuration options are like,
select all users from a group/ select any single user from a group of
performers.
There are n number of such workflow events. All are not
error related. So no need to panic if you receive notification with event name
like “dm_startedworkitem”
All such events are listed in dm_event_sender.ebs file.
Check the event names associated with routers/ tasks. The dm_event_sender.ebs file is placed at
path ../Documentum/product/6.7/bin
Below is the list of such events for your reference J
dm_startedworkitem
dm_selectedworkitem
dm_completedworkitem
dm_delegatedworkitem
dm_terminateworkflow
dm_changeworkflowsupervisor
Enough spoon feeding done now. Login to your content server and
check at the above path for rest of the names J
Happy Learing!!!
J