EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. If you want to respond to the error instead of simply bypassing it, you can configure any number of other activities between Capture Workflow Error A and No Operation A. Instead of stopping as a result of the error, Flow A reaches the Join activity and completes successfully. If there is an error in Activity A, the workflow jumps to Capture Workflow Errors A, which connects to the No Operation A activity. Connect the Capture Workflow Error activities to the No Operation activities as follows: For example, if Activity A (in Flow A) and Activity B (in Flow B) connect to a Join activity, insert a No Operation activity between each activity and the Join activity, and then add a Capture Workflow Errors activity to each flow. When a workflow has multiple flows that meet at a Join activity, you can prevent an error from stopping the flow by adding error handling and a No Operation activity. The Join activity is the last activity to complete successfully, so the work item status is Succeeded. For example, if all outgoing connectors on any activity are conditional, and the workflow does not meet any of the conditions, the workflow stops. If a workflow cannot continue, the status of the work item is the status of the last completed activity. Status of Incomplete Work Item = Succeeded
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |