Any knows issues yet with 6.9?

[PetriKaukua]

Hello everyone!

Have anyone encountered any issues with 6.9 yet?

------------------------------
Petri Kaukua
Certified Blue Prism Architect
Digital Workforce
Europe/Helsinki
------------------------------

[PatrickAucoin]

Hi Petri,

Known issues with 6.9 will be updated here:

What are the known issues in Blue Prism Version 6.9?
http://portal.blueprism.com/customer-support/support-center#/path/1535133752

------------------------------
Patrick Aucoin
Senior Product Consultant
Blue Prism
------------------------------

[RamonVillarreal]

While it has not been confirmed yet, we are exploring possible issues with using calculation stages not evaluating correctly if collections are used for the variables.

------------------------------
Ramon Villarreal
------------------------------

[PetriKaukua]

Does it look like this a 6.9 specific issue or would this be present also in 8.1?
Basically issue of this magnitude would render 6.9 completely unusable, especially when you think that any retrieved workqueue data is basically a collection and is being handled usually somehow in different calculation stages.

------------------------------
Petri Kaukua
Certified Blue Prism Architect
Digital Workforce
Europe/Helsinki
------------------------------

[Espen]

Any details on this?

------------------------------
Espen
------------------------------

[RamonVillarreal]

It is 6.9 specific at this moment.

------------------------------
Ramon Villarreal
------------------------------

[GabeKirchner]

Just to be clear, the issue has to do with debugging using the calculation stage. Running calculation stages with collections (or any other variable type) in control room or studio works perfectly fine. Calculations will perform as before. The specific problem is that if you open a calculation stage in the debug studio and try to use the expression validator tool when debugging a calculation stage that uses a collection, it gives an "Object reference not set to an instance of an object" error. The error occurs when you click the button that says "Validate". The issue will be a nuisance to developers and they will need to use data items to check that the expressions they design relating to collections are evaluating in a predictable way.

------------------------------
Gabe Kirchner
Customer Support Engineer
Blue Prism
America/Chicago
------------------------------

[Espen]

Is there a patch in the works for this issue? Will the patch require updates on database as well, or will it just be a small fix client side?

------------------------------
Espen
------------------------------

[GabeKirchner]

This item has been evaluated by our product team and has been added to the known issues of version 6.9. As far as I am aware, there is no fix yet for this issue. It will be fixed in a future version and documented in the release notes of the version with the fix. Unfortunately, I can't speculate whether it will be included in the next release or when it will be fixed. Furthermore, since there is no fix, I can't say whether it will be a patch or a client side fix. 

------------------------------
Gabe Kirchner
Customer Support Engineer
Blue Prism
America/Chicago
------------------------------