nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Behavior of TaskService.deleteTask

limcheekin

Hi,

I would like to find out more about the behavior of TaskService.deleteTask. What happened if this method being invoked when the task have assignee or without assignee and what is it impacts to the process instance? Will the process instance be terminated?

Best regards,
Chee Kin

Find more posts tagged with

Comments

jbarrez

The task record will simply be deleted from the database.

The process will actually be stuck, since there is no way to continue anymore through that path.
So this method should only be used in admin applications, where people know what they are doing.

Deleting a task makes no sense for an end-user. Closing the task, while providing a reason (eg 'task invalid, John already did this for me') is cleaner and a more traceable approach.

limcheekin

The process will actually be stuck, since there is no way to continue anymore through that path.

Noted. Is that means the process instance is always active?

Regards,
Chee Kin

limcheekin

The process will actually be stuck, since there is no way to continue anymore through that path.

Noted. Is that means the process instance is always active in this case?

Closing the task, while providing a reason (eg 'task invalid, John already did this for me') is cleaner and a more traceable approach.

Is that means provide a way for user to terminate the process (Let's say the user initiates a process by mistake)?

Regards,
Chee Kin

jbarrez

Noted. Is that means the process instance is always active in this case?

Yes, the process will be active (it will live in the runtime database tables forever if not removed).

Is that means provide a way for user to terminate the process (Let's say the user initiates a process by mistake)?

No, that would be this method on the RuntimeService:

<br> /** Delete an existing runtime process instance.<br>&nbsp;&nbsp; * @param processInstanceId id of process instance to delete, cannot be null.<br>&nbsp;&nbsp; * @param deleteReason reason for deleting, can be null.<br>&nbsp;&nbsp; * @throws ActivitiException when no process instance is found with the given id.<br>&nbsp;&nbsp; */<br>&nbsp; void deleteProcessInstance(String processInstanceId, String deleteReason);<br>

Deleting a process instance this way, will also delete all attached tasks.

limcheekin

Noted. Thanks for your advice.

Regards,
Chee Kin