Global variable - availability

[dougmaloney]

Hi.

Waiting with bated breath here for global variables to be available in May. It was originally April but pushed out to May - here's hoping. There really is no workaround for these.

Any news ? Anyone ?

https://docs.microsoft.com/en-us/power-platform-release-plan/2020wave1/power-virtual-agents/use-glob...

[RezaDorrani]

Hi @dougmaloney,

The 2020 wave 1 timelines have been impacted due to COVID-19.

I did follow the PVA sessions on MBAS. They were a lot of mentions of public preview of new features like bot sharing, composer etc. by Aug and then GA in Oct.

There was no mention of global variables but assuming timelines are similar.

--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

Thanks,
Reza Dorrani, MVP
YouTube
Twitter

[renatoromao]

I saw or heard (I don't remember) Microsoft employees explaining that in the next weeks will be released. (It's not a promise, but we are hoping a lot of this feature)

But COVID-19 impacted a lot of deliveries. (like Reza says) 

[CleberM · Accepted solution]

Hey @dougmaloney ,

We just released Global Variables (named Bot variables in PVA). Fresh out of the oven!

You can see the documentation here: https://docs.microsoft.com/en-us/power-virtual-agents/authoring-variables-bot. You should see it right away if you create a brand new bot.

Let us know what you think! 

cc: @renatoromao  @RezaDorrani 

[renatoromao]

Really nice @CleberM !! 🙂

I tested here and works well.
https://www.linkedin.com/posts/renatoromao_mtac-powervirtualagents-pva-activity-6671550956947169280-...

[dougmaloney]

@renatoromao @RezaDorrani 

very pleased that this has been released. I am experiencing some weirdness with bot variables though....

I have a PA action within a topic which returns 4 variables - one of them is set to "Bot - any topic can access". When I try to access this value later in another topic by displaying it in a message or passing it to another PA action, I get some strange behaviour :

• The variable shows as "x Undefined" in the message block - even though I have checked and double checked to select the right one.
• The PA action fails
• The variable list/helper in the bottom left hand side of screen shows the variable listed more than once.

[renatoromao]

@dougmaloney ,

Did you try to delete the message inside the "Show a message" card and insert it again?

Because maybe the issue was after the updates inside the variable (like name or something like that)

[dougmaloney]

@renatoromao hi - yes I did - several times over.

it is very strange - I have reproduced the issue 5 times and was about to send a video screen capture to demonstrate and the issue just went away.

i just reproduced it again. here's the demo ...

https://www.loom.com/share/607b308d9bfb41cd97d83d2be0b90196

[renatoromao]

It's strange because your workflow returns value to the variable.

@CleberM  Do you know anything about it?

[dougmaloney]

@CleberM @renatoromao Global variables doesn't work reliably.

My observation & guess is that any PA action which attempts to return a value to a global variable does not do so reliably, and subsequent evaluations and tests of that variable do not work as expected.

I have a scenario where in one PVA topic I call a PA action which sets a boolean global variable to true as it returns.

In a later topic, this variable is tested with a condition for true/any other conditions.

The branch for "any other conditions" always executes.

I expanded the condition to include a check for false, so it now checks for true/false/any other conditions (I considered that maybe the variable is not set at all) and added messages to display the value of the boolean, before the branch and after each branch execution.

Now, the 'any other conditions branch' is still always taken, even though the message displayed AFTER the branch is that the boolean is set to True. See attached.

n.b. The widget to display variable values displays multiple values for variables - the variable in question always shows = True.