Is it good Approach use multiple flow chart in single application
it is not a good practice
may be multiple flow decision you can use
Your question says is it good to use multiple flowcharts in a single “Application”
If you consider the entire solution, it is okay to have multiple flowcharts in different xaml files where needed.
However, if you are considering “one xaml file” as a application, I do not recommend to use flowcharts inside another flowchart. It will basically make it more complex and hard to understand.This is similar to using if activities inside another if activity. It makes the flow complex. To avoid such scenarios, I would recommend use multiple decision nodes inside one flowchart. Inside a flowchart, you may use sequences if required.
So I am trying to do with flow decision.when I am asking this help no one give me even reply.I do not know understand my requirement or not.they just run away…lol.Hope you will guide me.
thanks for your valuable time for reply.what my requirement is flow decision inside sequence.As I mention in description below comment why I want flow decision instead of if inside sequence.Hope you can understand my requirement
I would say the requirements are right but to implement it will take time for multiple flowchart you can create a number of xamls and based on that you can invoke main xaml and implement the logic
I hope this give you a good one
Sorry for the late reply. Was driving…
Just went through your diagram, and I believe this is a good fit for one single flow chart. Dont worry about the max width and the height of it as it will expand when you add more items to it. I have seen more complex flowcharts which are very nicely organized within a single flowchart activity.
So go ahead with the flow chart, and use flow decision activities to branch your conditions.
Hope it helps…
Let know if you have any further questions…
@Lahiru.Fernando no problem I am happy at least you reply me.Actually I am also new in Uipath.I create my application I am attaching this application.My team lead review this code and reject this told me
If you use Nested if, it is very difficult to understand the workflow, because the IF activity splits a sequence vertically and is perfect for short balanced linear branches. Challenges come when more conditions need to be chained in an IF… ELSE IF manner, especially when branches exceed available screen size in either width or height
Now I did not understand how can I resolve this
Main.xaml (190.3 KB)