Woritem Deletion Issue - Websphere

This is a discussion on Woritem Deletion Issue - Websphere ; The workflow API docs mention this about the deletion of a workitem. "If the work item is in the Ready state and represents the only work associated with the activity instance and when the associated process instance is not Terminating ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Woritem Deletion Issue

  1. Woritem Deletion Issue

    The workflow API docs mention this about the deletion of a workitem.

    "If the work item is in the Ready state and represents the only work associated with the activity instance and when the associated process instance is not Terminating or Terminated, then deletion is rejected."

    I dint really understand the purpose of this kind of restriction on deletion of a workitem. And can anybody please elaborate on this condition as to what it real means.

    Some of my ready state woritems behave like just notify type items (not notifications), which need not be finished an the user can directly delete them from the java custom client, but arbitrarily some of these items get deleted and others give an exception, this description above seems to be the reason, but I aint clear about the reason. Please help in understanding.

  2. Re: Woritem Deletion Issue

    Hi,

    if this condition is met, the error code is 507 (ERROR_NOT_ALLOWED.
    The reason for this logic is that MQWF wants to prevent users from loosing
    the only 'handle' to this workitem.
    If there are multiple workitems for the same activity threre is no reason
    to do so. However if there is only a single
    workitem that represents the activity it must not be deleted otherwise you
    could not continue process navigation.

    You can alway forceFinish() a workitem and so implicitely delete it.

    Volker Hoss
    IBM WebSphere MQ Workflow Development

+ Reply to Thread