This tip is for System Administrators that may find issues with their Workflow Requests in ESE.

When a request is created, this data is stored in the Absences table.  The corresponding workflow is stored in the Requesttasks table.

The request data and workflow are designed to communicate and function in a certain manner with each other.

However, some causes like interference to the database can cause an inconsistency in the process.  This process allows you to conduct a consistency check for inconsistent situations and make repairs.  This process is found at Workflow / Setup / Workflow: Actions / Consistency Check.

I recommend that you run the Check OPtion first to see if there are any issues, be

Workflow: Orphan

Workflows should have reference to the original request data.  However, in inconsistent situations, the workflows might not have the original request data.

Workflow: Type and/or Workflow: Category

The request data and the corresponding workflow should refer to the same request type or category. However, in inconsistent situations, the request data and the corresponding workflow might not refer to the same type or category.

Approve: Document

When saving a document to be approved for publishing, a task is created for the approver. When the document is deleted, the corresponding requests and workflows should be automatically deleted too. However, in inconsistent situations, they might not be automatically deleted.

Reference: Person, Reference: Account, Reference: Item 1, Reference: Serial number 1, Reference: Item 2, Reference: Serial number 2, Reference: Project and/or Reference: Document

When you link a request to these references, you should not be able to delete the references. However, in inconsistent situations, they might be accidentally deleted.