24
In situations where there are workflow line approvals and the corresponding transactions are deleted, this orphans the workflow line in it's current state and prevents the header workflow status updating to an Approved status when all the other lines are Approved.

We have this occurring in expense reports where a rejected expense line is deleted. Despite that line no longer appearing on the expense report, this prevents the header Approval status from updating to Approved. Consequently, the fully approved expense report cannot be posted. The current approach to resolve this is to Reset the status on the expense report or Recall the expense report and re-submit through workflow. This creates much additional redundant work for the approvers.

At a minimum, it'd be preferred that the deletion of the corresponding line changes the line item workflow status to one that will NOT prevent the Header from moving to Approved. An alternate approach could be the deletion of the orphaned workflow item when the line item is deleted. Anther option may be having the ability to update the status of the orphaned workflow line.
Category: Workflow
STATUS DETAILS
Needs Votes

Comments

C

This is a major issue and a functionality update will be very useful

Category: Workflow

C

We have this issue with Invoices that have been deleted and the workflow not recalled back, and the workflow becomes orphaned and stuck in the users "assigned to me" list and errors when they user tries to action it.

This would also be very useful on the back of the fixes introduced for unrecoverable items that are now able to be pulled back into draft status, the unrecoverable workflow item remains as unrecoverable, and does not change to cancelled, if the instance can be deleted, then its easier to identify new instances that land as unrecoverable that need to be resolved.

Category: Workflow

C

Very much an issue in our company too. This will ensure better control over resolving real workflow issues.

Category: Workflow