Why cant i not see the input argument of a invoked workflow in the properties pannel?

Help Studio
,
1

i can see the output argument but not the input argument?
Is there a way to fix this?

The image displays a workflow configuration for the SAP_HandleStatusBar activity in UiPath Studio, showcasing input and output arguments with a blacked-out content area. (Captioned by AI)
The image displays a workflow configuration for the SAP_HandleStatusBar activity in UiPath Studio, showcasing input and output arguments with a blacked-out content area. (Captioned by AI)1337×573 36.4 KB

2

Hey @lr101
Try this:

  1. Close UiPath studio and assistant
  2. Delete Project.json file
  3. Reopen main.xaml

Thanks!

3

@lr101

Click on

A software workflow interface is shown with options for specifying arguments and opening an expression editor. (Captioned by AI)
A software workflow interface is shown with options for specifying arguments and opening an expression editor. (Captioned by AI)479×217 37.5 KB

Then you will see input/out arguments

The image shows a workflow editor for iterating through Excel rows and invoking a 'TakeScreenshot' XAML file with specified arguments configured in a dictionary interface. (Captioned by AI)
The image shows a workflow editor for iterating through Excel rows and invoking a 'TakeScreenshot' XAML file with specified arguments configured in a dictionary interface. (Captioned by AI)1063×496 83.5 KB

4

hi i tried that but doesnt work

5

i can see the agruments here fine but i would like to see them in the properties pannel just like the output information

6

I believe this is missing feature that indeed makes a inconsistent user experience.

I will say, the MVPs got to see the next version of Studio coming out soon, and in the new experience every argument for a card is moved over to that panel, and the activity card itself will be always collapsed and small.

This should be a good change cause it will stop this experience of some arguments being visible on the card, and others on the panel etc, and centralize them in one place.

2 Likes
Forum Engagement Daily Reports
7

I would advice people against this always as a trouble shooting method unless a clear reason why this might work is provided.
This can destroy useful information in your project. You will lose your test cases, which will be changed to normal workflows, you will lose any dependencies you added, you will lose your project version.

This is not good advice to do unless you have a clear reason to thing something is wrong with the project.json, and nothing here suggests that.

1 Like