From eb818452ff453271557c29d7489c6ae0249aa48c Mon Sep 17 00:00:00 2001 From: seshukm Date: Wed, 23 May 2018 16:06:56 +0530 Subject: First take warning correction Issue-ID: SO-635 Change-Id: I3c5051db8b8361df1cc1a5f555b32ce8578ed8b2 Signed-off-by: seshukm --- docs/BPMN_Subprocess_Process_Flows.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/BPMN_Subprocess_Process_Flows.rst') diff --git a/docs/BPMN_Subprocess_Process_Flows.rst b/docs/BPMN_Subprocess_Process_Flows.rst index cf2da40e87..fc36cc54c9 100644 --- a/docs/BPMN_Subprocess_Process_Flows.rst +++ b/docs/BPMN_Subprocess_Process_Flows.rst @@ -22,7 +22,7 @@ Characteristics The current best practice for reporting errors from subprocess is described here: - * The subprocess should create a WorkflowException object and store it in an execution called WorkflowException. + * The subprocess should create a WorkflowException object and store it in an execution called WorkflowException. * The WorkflowException object contains an error code and an error message. * The subprocess should then throw an MSOWorkflowException BPMN event which may be handled by the calling flow. -- cgit 1.2.3-korg