"Import arguments" button for Workflow activity doesn't work anymore

Today, all of a sudden, the “import arguments” button for passing arguments to a workflow doesn’t work anymore.

It’s not only a matter of mine. I asked my mate and she’s experiencing the same behaviour, without doing anything on our side.

@pere ,Its working for me close the studio and retry again

Hi @pere
please find below screenshot for your reference you need to click on above there you can see the arguments.
Hope this will work for you

Happy Automation!

Of course that’s the 1st thing I attempted.

What about it not working on my mate’s machine, either?

Hi @pere

With the latest update in UiPath Studio the display of invoke Workflow has changed. Now, we are not getting the popup window to select the argument values like before.

1 Like

Not working means getting any error or not able to open arguments ?

We have indeed redesigned the Invoke Workflow a bit so that we can use 1 version for both Windows and Cross-Platform projects.

It automatically loads the arguments without even having to click the Import Button whenever you select your XAML file:

You only ever need the import argument button to fix things, in case there is a mismatch in the configuration of the Invoke Workflow File <> the XAML file.

The power of habit is strong though, which I totally understand and overlooked on the first iteration of the new design. This is why we will make a further adjustment to how the activity looks like in the very next patch to System activities:
image

The idea is to reduce the emphasis on the buttons a bit to reduce the confusion:

1 Like

Hello @pere

Take a look at this:

Regards
Soren

I attached a video. If you watch it you’ll find out what I mean.

Why you keep insisting? I already replied to that “solution”. Even if it worked, which doesn’t, it wouldn’t be a “fix”. Haven’t read that my mate has this same problem also? Do you think neither of us restart their machines?

Ok, so this is a feature.

As I thought I was using v.2024.10.1 for some time and didn’t notice this behaviour until now, I thought it came all of a sudden. If you explained this somewhere, in the release notes or whatever and I didn’t notice/read it, then ok, it’s my fault.

Thanks for explaining.

Yes, we had a note under System 24.10.0 release notes:

  • The Invoke Workflow File activity now offers the same user experience and configuration properties for both Windows and Cross-platform projects. Plus, it introduces several new properties to simplify arguments handling and setting up execution.

But that was clearly far from visible enough (plus the experience was still a bit confusing, as evidenced by this topic).

But the release notes for System 24.10.6 now explain this much better: