Automatic repairs
The following issues can be repaired automatically. The table shows the issue that is written to the WorkflowCleanup.log file and the corresponding description and automatic repairs.
| Issue | Description |
|---|---|
| Added the required End step structure and definition information. | Valid workflows require an End task step and one cannot be found. The process adds an End task step to the workflow. Review the workflow to verify that the step was added correctly. |
| Changed step with missing definition to a No-Op. | The properties for a task step cannot be loaded. According to past behavior, when the properties for a step cannot be loaded, the step was skipped and processing was continued with the next step. Because the properties for steps other than an End or Stop task are specific to the workflow, the process cannot create them. However, because the step was skipped in the past, the process replaces the task step with a No-Op task step. A No-Op (or No Operation) task step is a task step that does nothing. The log entry provides information about what was replaced so the workflow can be reviewed. Review previous versions of the workflow to determine the purpose of the step and replace the step if necessary. The task types Switch, Fork, Loop, Iterator, and DataConnect cannot be converted to a No-Op step. Missing properties for these task types results in retiring the workflow. (This condition is covered by the table of issues that cannot be automatically repaired by the process.) |
| Converted obsolete task type step to a No-Op. | Older workflows might contain task steps that were not supported since the Workflow Builder was released in 2005. These obsolete types are most likely to exist in workflows that were originally created with the older non-graphical workflow editor. According to past behavior, the process skipped these task steps and continued to the next step. The process converts these task steps to No-Op steps. |
| Flow control value was invalid. Set step to normal flow (non-swapped). | Switch and Break task steps contain an internal value that indicates whether the condition must be used as-is or swapped. If the internal value is not valid for either a normal or swapped step, the process replaces it with the value for a normal step. This value is an internally used value and not the condition expression for the step. Review the listed Switch or Break and verify that the step is correct. Swap the step if necessary. |
| Removed the entry from WF_LOOKUP because the workflow is not in a published state. | An entry for the workflow existed in the WF_LOOKUP table, but the workflow is not currently published. Only published workflows must have an entry in the WF_LOOKUP table, so the entry was removed. The workflow can be published if it is necessary for current business processes. |
| Retired the workflow because its Business Object could not be found. | The business object for which the workflow is defined does not exist. If the business object does not exist, then this workflow cannot run. The process retires the workflow. |
| Retired the workflow because its Module could not be found. | The module for which the workflow is defined does not exist. If the module does not exist, then this workflow cannot run. The process retires the workflow. |
| Retired the workflow because there isn't a corresponding entry in WF_LOOKUP. | The workflow entry in the WF_TEMPLATE table has a status of Published, but there is no entry in the WF_LOOKUP table. Since the WF_LOOKUP table locates workflows at run time, this workflow cannot run. The process changes the status from Published to Retired. The workflow can be published if it is necessary for current business processes. |
| Step definition added for Block-End step. | The properties for a Block-End task step cannot be loaded. A Block-End task step is the bottom of a Switch or Loop task step. All task steps require valid properties to be run. However, the properties for this task type do not contain any values that are specific to the workflow. The process creates valid properties for them. |
| Step definition added for End step. | The properties for an End task step cannot be loaded. All task steps require valid properties to be run. However, the properties for this task type do not contain any values that are specific to the workflow. The process creates valid properties for them. |
| Step definition added for No-Op step. | The properties for a No-Op task step cannot be loaded. A No-Op task step is a task step that does nothing, but sometimes it is added to a workflow by the Workflow Builder. All task steps require valid properties to be run. However, the properties for this task type do not contain any values that are specific to the workflow. The process creates valid properties for them. |
| Step definition added for Stop step. | The properties for a Stop task step cannot be loaded. All task steps require valid properties to be run. However, the properties for this task type do not contain any values that are specific to the workflow. The process creates valid properties for them. |
| Updated the workflow name in WF_LOOKUP. | The name of the workflow in the WF_LOOKUP table does not match the name in the WF_TEMPLATE table. The process repaired this condition by updating the name in the WF_LOOKUP table. Review the name and verify that this name is expected. |