Help Center/ Cognitive Engagement Center/ User Guide/ Tenant Administrator Guide/ Configuring Intelligent IVR/ Reference/ Diagram Elements/ Connection Lines Between Diagram Elements

Connection Lines Between Diagram Elements

Appearance

The following figure indicates that no node is selected.
The following figure indicates that nodes are selected and the connection succeeds.
The following figure indicates that nodes are selected but the connection fails.

If the connection fails, a flow is not saved.

The following describes the meanings of line colors on the canvas:

(purple connection line): A diagram element is successfully inserted into two diagram elements connected by the line.
(blue connection line): The line is connecting diagram elements.
(dotted connection line): The source diagram element cannot be connected to other diagram elements.
(gray connection line): The line has connected diagram elements.
(red connection line): The line rules are not configured or are incorrectly configured. For example, a diagram element has two branch lines, but the default branch conditions are not configured.
(yellow auxiliary line): The line aligns with the horizontal or vertical center of the canvas.
(blue auxiliary line): The line aligns with the horizontal or vertical center of the adjacent diagram element.

Parameter Description

Branch Condition: branch condition corresponding to the current flow connection line.

Except the preset timeout or unmatched condition, other conditions are the branch conditions configured by the diagram element in the previous step.

The following table describes the preset branches.

**Table 1** Preset branches
Name	Description	Usage Method
timeout1	First timeout	This branch condition is triggered when a third party system (for example, the IVR) determines that a timeout occurs in receiving the customer feedback and sends a message to the OIAP, indicating that the value of input is timeout. This branch is generally used on the connection line between the Semantic Recognition diagram element to the subsequent node, indicating that semantic recognition times out before a response is received from the customer.
timeout2	Second timeout	During a call, timeout2 is triggered when timeout1 occurs for the second time. During script flow design, a flow retry is required when the first timeout occurs. If the second timeout occurs, the current step is skipped and the subsequent steps are performed.
nomatch1	First recognition failure	nomatch1 is triggered in either of the following scenarios: The Semantic Recognition diagram element does not match a result (that is, the diagram element returns the command word of an unknown intention). A third-party system (for example, the IVR) returns a message in which the value of input is nomatch. In this scenario, the ASR system fails to recognize the intention and sends a failure response to the IVR.
nomatch2	Second recognition failure	During a call, nomatch2 is triggered when nomatch1 occurs for the second time.
error3	Third error	If the trigger condition corresponding to timeout1 and nomatch1 occur for the third time during a call, error3 is triggered. If the number of error times does not need to be accumulated, use the Error Count Clearance diagram element to clear the number of error times before using this condition.
SYSERROR_INTERFACE	Business interface invoking failure	This branch condition is triggered if an error occurs when the Business Interface Invocation diagram element is used to invoke a third-party interface. This branch is generally used on the connection line between the Business Interface Invocation diagram element and subsequent node.
SYSERROR_INNER	ODFS internal error	This branch condition is triggered when other unknown errors occur in the ODFS.
slientInsertReply	Direct reply by silent agents	This branch condition can be used only when the Semantic Recognition diagram element of the silent agent system is configured. By using this diagram element, agents can directly answer the call and continue to execute other expected business flows.