To help assist in creating automated testing, I would like to make a tooltip available to help anyone using an activity to know what to send as an argument. Basically - what are the available options that can be passed as arguments.
This is for activities that come from custom libraries - imported as packages.
I added a notation to the arguments like in this topic
But when you use the activity, there is no tooltip or notation. That notation is only available within the library.
How do I help guide developers what information to pass as arguments? As is, they’ll have to go to the library, look up the activity and hunt down wherever that argument gets used (or hope that whoever set it up left helpful comments).
This question was asked years ago too and I’m surprised that it still has no solution.
It seems like such a basic design need. Is there an option that I’m missing, something I should be doing to make this possible?
Yes, but you have to go to that library to view it. I want to be able to view it from a test case or a process that would import the library as a package.
What do you mean by
Which field?
When I view it, it just shows me the arguments and their type. It doesn’t show the tooltip annotation I’ve given each argument.
To reinforce what ppr said, these are indeed handled very effectively via the activity layout.
There did used to be some bugs in older versions related to the annotations coming through, so they would only work under certain conditions and having any non .xaml files would break them, but the activty layouts work reliabily from what I have experienced as you can see here.
@ppr and @Jon_Smith You were right. Using activity layout made a difference. I used it to change the placeholder, and now that I’ve “touched” the layout, the tooltip for each argument is showing - it wasn’t before.
