You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Your documentation is not so different from classic ReFramework's Documentation. It doesn't have any information about some xaml files such as "CleanupAndPrep.xaml" and "GetSetTransactionData.xaml"
Will you gonna update this framework and will it be ever implemented in UiPath officially? What is the latest state? And how we can learn more information about processes. It is actually complicated because lots of "xamls" are the same. It confuses about logic.
In which processes we should use classic reframework or enhanced one? We thought this should have sub reframework parts but design is not like that. What is the logic behind folder structure like service layer or process layer? Why we are invoking "main.xaml" and process layer in every layer?
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
Your documentation is not so different from classic ReFramework's Documentation. It doesn't have any information about some xaml files such as "CleanupAndPrep.xaml" and "GetSetTransactionData.xaml"
Will you gonna update this framework and will it be ever implemented in UiPath officially? What is the latest state? And how we can learn more information about processes. It is actually complicated because lots of "xamls" are the same. It confuses about logic.
In which processes we should use classic reframework or enhanced one? We thought this should have sub reframework parts but design is not like that. What is the logic behind folder structure like service layer or process layer? Why we are invoking "main.xaml" and process layer in every layer?
Thank you.
The text was updated successfully, but these errors were encountered: