SmartAssist: Split isn't working on a context variable

SmartAssist
1

I’m running into an issue with a Split in a SmartAssist Experience Flow. It doesn’t seem to be reading my context variable correctly.

Here are the relevant steps in the flow:

A screenshot of three nodes in a SmartAssist Experience Flow: a Script Task node, followed by a Message Prompt node, followed by a Split node.
A screenshot of three nodes in a SmartAssist Experience Flow: a Script Task node, followed by a Message Prompt node, followed by a Split node.446×741 61.2 KB

Steps To Reproduce

  1. Create an Experience Flow with these steps:

    1. ScriptTask0001 (Script Task)

      context.isClaimFound = 'yes';

    2. MessagePrompt0001 (Message Prompt)

      The value of isClaimFound is {{context.isClaimFound}}

    3. IsClaimFound2 (Split)

      A screenshot of the configuration of a Split node. There are two if conditions. The first says that if context.isClaimFound equals "yes", take Branch 1. The second says that if context.isClaimFound equals "no it is not", take Branch 2. Otherwise, take Branch 3.
      A screenshot of the configuration of a Split node. There are two if conditions. The first says that if context.isClaimFound equals "yes", take Branch 1. The second says that if context.isClaimFound equals "no it is not", take Branch 2. Otherwise, take Branch 3.470×893 32.5 KB

    4. Three Message Prompts, each connected to one of the Split branches (not shown in screenshot)

      • Have each Message Prompt say the name of its branch (Branch 1, Branch 2, Branch 3).

  2. Press Test Flow.

Expected Behavior

  1. SmartAssist says:

    The value of isClaimFound is yes

  2. SmartAssist says:

    Branch 1

Actual Behavior

  1. SmartAssist says:

    The value of isClaimFound is yes :white_check_mark:

  2. SmartAssist says:

    Branch 3 :x:

Additional Information

Branch 3 runs regardless of what value I assign to context.isClaimFound. I can assign it yes, no it is not, or test. Branch 3 always runs.

However, MessagePrompt0001 always correctly reads the value that I assign. So the value is getting set, but the Split doesn’t seem to be seeing it.

2

Still stumped on this one. Any ideas as to what’s going on?

3

@ashish.sankhala Any ideas on this one?

4

@eeskildsen - This seems like a product bug. I will check and circle back.

5

Thanks! I talked with Mike Piotrowski Monday afternoon and he thought the same thing. He may have opened an issue for it already—not sure.

6

@eeskildsen Can you please use context value in the following format inside the split node. {{context.key}}

Let us know if you are still facing the issue

1 Like