Yeah, that’s the DTO approach that was mentioned earlier. Good to hear it worked for your cases as well
Downside is, a lot of people needed to rediscover how to do it, so the main focus right now (at least for me) is how to make it easier and preferably doable from within the UiStudio itself (thats what the prototype project posted above actually does right now, even if in a messy way).
Ready package is available now here with a sample project, and a walkthrough video here:
Will publish to Go! as soon as I’ll have time to do proper documentation (and figure out how to go through it as it seems to like to bug out on edits).
@badita is this feature still in UiPath’s roadmap? If so, is it planned for any specific release?
I really liked @andrzej.kniola component and the video makes it really easy to understand how to use it.
Although, since this is a complex feature it would be nice to have a UiPath implementation so maintenance is assured for future releases.
Thank you for the answer, however, I meant using the collections and the data types that are already provided by UiPath, without writing your own code.
Entity model is planned for a future release (I don’t have any details though). It’s nice to see others looking for similar solutions as well, as that might help getting it earlier
I think it would be awesome if there was an easy way to define an own data structure or class (only properties, no methods) in UiPath Studio.
For example, if I had a RPA job which processes cars (just as sample) I would like to create a variable type “car” which has different properties like manufacturer (string), color (string), top speed (float), weight (int), tires (list) etc.
This would allow me to easily pass objects (i.E. a car) from one workflow to another workflow (via invoke wf). If I want to do something like this now, I have to either
a) create a variable for each property and pass a long list of arguments (manufacturer, color, etc,). This can quickly become confusing and is hard to maintain as soon as I need a new property
or
b) create i.e. a dictionary which is then restricted to one datatype (ie dictionary). This is ok but also a little bit nasty imho.
I know this might be hard to implement. But if there is a way, I think this would enrich and simplifiy a lot of workflows.
I find it very helpful to have the possibility to create complex datatypes (object orientation) . For example I create an object person which have the following fields: firstName from type string, lastName from type String, age from type int, etc. When I invoke an existing workflow it is now easier and quicker to deliver the needed variables, because in this example you have all your information in the object person. In this object is only your input for this workflow.
Greetings Simon