What is FlowChart best practice?

Hi I tried finding in this forum but couldnt find an answer to my question.

For linear processes without branching or logical operators, can I use flowchart for that particular automation or should I just create multiple sequence boxes one after another to demonstrate the linear workflow?

Thanks and appreciate any replies!

Hi @Alson

Linear process can be implemented in any kind of workflow, sequence, flowchart, state machine, etc.
The one that you should select would depends on the process you have, for example if it is a simple process you can build in based on secuencies, if it is multiple logical validations, then you should choose flowchart or state machine (Reframework)

Hope this helps

Regards

1 Like

@Alson

For a linear process ideally you would use sequences…

and I believe you want to create multiple sequences to show different set of activities …if so it would be better to modularize by developing different xaml files and invoke them one after the other

cheers

1 Like

@Alson
In general, for linear processes without branching or logical operators, you have the flexibility to choose between using a Flowchart or multiple Sequence activities to represent the workflow. Both options can effectively demonstrate the linear flow of the process.

Using a Flowchart: A Flowchart provides a visual representation of the workflow, allowing you to easily see the sequence of activities and their connections. It allows for clear visualization and can be helpful if you have decision points or multiple paths in your process, even if you don’t use branching or logical operators. Flowcharts offer flexibility in representing complex workflows, and they can be easier to understand and maintain in the long run.

Using multiple Sequence activities: Alternatively, you can use multiple Sequence activities, one after another, to depict the linear workflow. Each Sequence activity would represent a step in the process, and you would organize them sequentially. This approach is more straightforward and may be preferred for simpler linear processes.

Ultimately, the choice between using a Flowchart or multiple Sequence activities depends on factors such as the complexity of the process, personal preference, and the need for visual representation. Both options are valid, and you can select the one that suits your specific requirements and the clarity you want to achieve in your automation project.

Remember to document your workflow adequately and ensure that it is easily understandable and maintainable by you and other team members.

1 Like

Its recommended to use sequences for reusable, linear, smaller and simple workflows. So break your process into granules using sequences.
Use flowchart for complex business validations, for creating design of parent pages.

Thanks.

1 Like

Can I check if example I have a single activity, can I put it as per the image? Like the flow chart consists of activities or should I group single activity into one sequence?

@Alson did you get your answer. If yes please mark it as a solution. Thanks

Hi @Alson

If the process that you are developing is linear, simple and small then better to go with the Sequence.
If your process have much logics and decisions then better to go with the Flow chart.
If you want to work with Queues and transactions then go with the RE Frameworks.

Note : In Flow chart also you can develop the workflows and you can easily invoke in to the code.

Hope it helps!!

For linear processes without branching or logical operators, it’s absolutely fine to use a flowchart. A flowchart is a great tool for visually representing the sequence of steps in a process, even if it’s a straightforward, linear workflow. The benefit of using a flowchart, even in this case, is that it provides a clear and structured visual representation, which can be helpful for better communication and documentation.

Best practice for linear workflows:

Use a single flowchart: You don’t necessarily need to break the process into multiple sequence boxes. A single flowchart with steps in sequential order is sufficient.
Avoid clutter: Keep the flowchart simple and clean by ensuring that each step is clearly labeled and the connections between steps are obvious.
Use appropriate shapes: Utilize standard flowchart symbols like ovals for start and end points, rectangles for processes, and arrows for flow direction.
For more complex linear processes, tools like Creately allow you to easily design flowcharts with multiple steps while keeping everything organized and visually clear.

To create an effective flowchart, it’s essential to follow best practices for clarity and usability. Start by clearly defining the purpose and understanding the process, inputs, and outputs. Use standardized symbols, such as ovals for start/end, rectangles for processes, and diamonds for decisions, while maintaining consistent usage throughout. Keep the flowchart simple and easy to read by organizing it logically, typically from left to right or top to bottom, and avoid overcrowding. Label each step concisely and use decision points sparingly to avoid complexity. Finally, ensure arrows clearly indicate the flow of the process for smooth navigation and understanding. I saw there are some good best practices have been mentioned by a tool called creately have a look might be useful to you’ll like me.