-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TransactionItem with tuples #2
Comments
Hi zaszlo, First off, the point of the TransactionData/TransactionItem variables from the main framework body or the included services are conceptually just the data being exchanged between the Data layer and the process layer and as such, should have the datatype the user chooses. The io_TransactionData is the structure of data that can be returned from a task or service, but FirstTask is not in the DataLayer, so it would break principles if it returned data to the main Task. It can however be used to write data to a queue or external source. I chose to put tuples as an example there and it highlights the following potential usage:
The services are the same and i very much like the possibility of easily copy pasting a new service (framework) and having to do minimal configuration to get it to work. Different names would be cumbersome, but yes it is slightly weird. However, i think in the end this is better, especially as services are optional. You are correct on the doc, i have not had time to rewrite it and it does not correctly reflect the full behaviour of the Enhanced ReFramework. I hope to be able to provide docs soon! |
There is not available any tutorial like example to work this framework, would be excellent if you make a video how to work with this framework to get his max potentially. |
That is exactly what I can here asking. |
In the FirstRun task the TransactionData/TransactionItem has Tuples, like List<Tuple<String, Object>> in the variables tab and has the default List in its io_TransactionData argument.
In the service layer, like GetData's Main.xaml there are no tuples.
I'm confused now, isn't using kinda the same name in variables and arguments a worst practice thing? And why not be consistent inside a framework's layers to use only one kind of variable type for TransactionData?
No clue on this or on its usage in the docs.
Related forum topic: https://forum.uipath.com/t/query-on-enhanced-robotics-framework/36798
The text was updated successfully, but these errors were encountered: