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
The Process.xaml equally qualifies to be part of "Framework" flows. It has got arguments which are closely associated with other flows. Not sure why it has been kept in the root folder.
Will it not be good to move it to be part of "Framework" folder?
The text was updated successfully, but these errors were encountered:
This is just my opinion. We should not just use the technical skills but also design & usability skills so as to give user/developer a better user experience with REFramework. Putting process at the root allows user/developer to delete it, replace it or modify it with their own process(es).
I agree with @mrmanojrai, this should be moved to the Framework folder. The Process.xaml file should never be deleted, the actual process logic should be added to it instead.
The
Process.xaml
equally qualifies to be part of "Framework" flows. It has got arguments which are closely associated with other flows. Not sure why it has been kept in the root folder.Will it not be good to move it to be part of "Framework" folder?
The text was updated successfully, but these errors were encountered: