UiPath Community 2022.10 Stable Release

[Ionut_Babencu]

Hello,
could you please share more information?
What type of project, Legacy, Windows, or Crossplatform?
Any particular action takes a long time? Project validation, compilation or the running of the project itself?
Thanks!

[Ionut_Babencu]

Hello William,
thank you for reporting this!
It looks like an issue on our side, I’ve raised a bug and it will be prioritized and fixed in a future version.

[Steven_Raines1 (Steven Raines)]

Is it likely a similar issue as mine mentioned above? I’ve also created a thread of its own for this issue with some others that seem to be having a similar issue.

2022.10 slow to respond after making changes

After upgrading UiPath Studio to version 2022.10.1, it becomes unresponsive for about 10-30 seconds after making any change to my old projects. The old project main.xaml files are about 8MB in size and are Windows-Legacy. Environment details Studio 2022.10.1 - 10/11/2022 Community License Per-user Installation License Provider: Orchestrator Activation ID: Update Channel: Stable Microsoft Windows 10 Pro 64-bit 6.0.7 16 thread 2.5 GHz to 4.9GHz CPU 16GB RAM Activity package versions …

[Ionut_Babencu]

We are attempting to reproduce the behavior described.

[Marcelo_Vina (Marcelo Viña)]

Hello Community,
Afte upgrading my Studio to 2022.10.1 every simple accion into the Studio causes a delay of 20 seconds aprox. The app freezes and the CPU goes up!
It is impossible to work this way. I hope that UiPath support will give us a solution as soon as possible!!
My main.xaml file has 8.140 KB and Windows-Legacy dependencies.
Regards, Marcelo

[Whynotrobot]

In Studio 22.10.1 in the designer panel, the topmost scope in an XAML is not displayed anymore.

We now are missing the annotation at the top of each XAML file. See exampes from the REF in the sceenshot. Process.XAML only shows a log message and a comment placeholder, no scope around it .

Is that a bug or by design?

Edit; the information still exists in the source xaml files, for example

  <StateMachine InitialState="{x:Reference __ReferenceID3}" sap2010:Annotation.AnnotationText="[Process title]&#xA;[Process description]&#xA;[Additional information (e.g., author, contact information and applications involved and required external setup)]" DisplayName="General Business Process" sap:VirtualizedContainerService.HintSize="687.2,801.6" sap2010:WorkflowViewState.IdRef="StateMachine_1">
    <sap:WorkflowViewStateService.ViewState>

[...........................]
        <x:Boolean x:Key="IsAnnotationDocked">True</x:Boolean>

Also the topmost scope is seen from the variables panel in the scopes section. So strange it’s invisible and un-editable from the designer panel.

Update:
it’s a setting in Studio. Disable the setting Hide sequences to get view them again.

[Whynotrobot]

Blockquote In addition, we are not able to change the sub-header to align with the header when you copy scripts.

This is minor but can be annoying…

Workaround: You could edit the xaml files directly, using Notepad++ for example.

[coramia (Coramia Motoi)]

Hi @Whynotrobot, this is actually an improvement we implemented, but missed the annotations scenario. Don’t worry though, our team is on it!

The Sequence (container) is not shown in Studio 22.08 and 22.10

I pushed it to the issues tracker that we use for @alexandru and the Studio team to have a look.

To unblock yourself - you can toggle the new setting from Backstage called “Hide Sequences” on or off and display or not the topmost Sequence and see the Annotation:

Hope this helps!

[Whynotrobot]

Thanks, I found the setting!

Just an additional question; the code analyzer will still count the hidden sequences for counting the ‘depth’ right? And as they will all have default names like do or sequence, it will also show op in the analyzer, correct?

[coramia (Coramia Motoi)]

Yes, that’s correct. Both the ST-NMG-004 rule and the ST-MRD-009 rules are still triggered even if the Hide Sequence options is hidden, since they are actually still present in the source code (.xaml file).

[Vidhi_Patel]

I’m using community version 2022.10.1 , I’m facing this error in Assetvalue variable , it’s already defined in Re-Framework but still gives this error , it sems it’s bug!

[Whynotrobot]

Right, makes sense.

I do actually like not having the ‘useless’ sequences, so nice improved feature!

I’d really love it if the empty sequences (such as do/sequence/target does not appear) are not autocreated. (If you drag a single activity in there, the scope is not needed so it can remain gone. And if you drag a second one, it’s autocreated at that moment. )
Not looking forward to doing code reviews for code created by a dev that has the sequences hidden

[loginerror (Maciej Kuźmicz)]

Hi @Vidhi_Patel

Could you please make sure that your System activity package is also updated to the latest version?

[Vidhi_Patel]

yes it is updated!

[juancarlos.ramos]

“Same issue from Mike_Campbell MCampbell Junior Robot”

After upgrading, my test project was flagged as needing update from legacy to windows.
I ran the update and it appeared to compile.
After starting to run my test, I get the following exception, very early in my project…

“VisualBasicValue: Expression Activity type ‘VisualBasicValue`1’ requires compilation in order to run. Please ensure that the workflow has been compiled.”

I also updated the packages to current just to make sure there wasn’t a companion package needed… same result.

I started running it in debug mode and found that the expression it was hanging on was (I thought) a simple text test from a string variable:

[Ionut_Babencu]

Hello William, this should be fixed in System.Activities 22.10.2

[Ionut_Babencu]

Hello JuanCarlos,
I attempted to reproduce the issue. If I understood correctly,

I created a Legacy project, I added a Date variable, I assigned to it System.DateTime.Now, and a log message afterwards with variable1.ToString
Converted the project to Windows, and it runs without error.

Could you please share

what Studio version you had before the update?
what version of System.Activities your project uses?
Is it possible to share your initial Legacy Project?
Thanks!

[juancarlos.ramos]

Thxs @lonu_Babencu for your help.

My robot was made with the version 2022.4 as legacy project and the System.Activities used 21.10.4. The issues are shown when there is a legacy project created previously.
I saw that if into the updated version I retype the activity’s value, it works and the issue disapear. It seems that I must retyping all values again?..

Now I have problems with the activities from the UiPath.PDF.activities. I did update the dependencies to UiPath.PDF.Activities = 3.6.0 and then to v3.10.1 but it didn´t work.

I did that “Restart your Machine Ones then Select all source from Manage Packages and Try to repair packages.” , but the issues keep going.

[Werve]

After the notice of the future removal of support for legacy projects, I tried to convert a project with the relative convert button.
Unfortunately, I noticed that the UiPathTeam.Excel.Extensions.Activities dependency is no longer available in the new Windows project mode.
I could not find any combination of available activities and code to replace those legacy functions featured in that dependency.
Are there any plans to add them before the end of legacy support?

I also note that after the conversion there are some activities left such as UiPath.Excel.Activities.ExcelGetWorkbookSheet that do not have error warnings but which I did not find in the new activities available for addition.

[SohamKorgaonkar]

Thank you soo much
This “Hide Sequence” option was what I was looking for, as all my previous projects had annotations in the main sequence.