What is Project Organization in UiPath RPA?
Project
Organization
• The project organization is very important. A project must be clean,
organized, modularized.
• The project must be structured into modules.
• Adjust the Project settings helps you to set different project settings
for the from the beginning.
____________________________________________
Project
Organization - Best Practices
5
general rules for understanding best practices:
1)
Pick an appropriate layout for each workflow.
2)
Break the whole process in smaller workflows.
3)
Use exception handling.
4)
Make your workflows readable.
5)
Keep it clean.
Benefits
of applying best practice principles:
• Reliable: it can handle a variety of external and
internal error exceptions.
• Efficient: Reduce development time; make programs
run smoothly in production environments.
• Maintainable: Easy to modify, merge, and transfer.
• Extensible: Easy to add new situations.
____________________________________________
Project Organization - Best Practices
1)
Pick
an appropriate layout for each workflow - When starting a project, choose the appropriate layout (FlowChart and
Sequence) for each process and subprocess.
• The main process uses Flowchart/State Machine. One is
to have a clearer understanding of the entire project.
• Higher level decisions or business logic use
Flowchart.
• UI interaction uses Sequence. The general interaction
is the execution of one activity and then one activity, and there are not many
changes.
• Try not to use nested If activities, it would be
easier to understand with Flowcharts instead.
• Use REFramework or Enhanced REFramework for complex
processes.
2) Break the whole process in smaller workflows - Decompose the entire process into several smaller
processes. Developers implement them by breaking down very complex applications
and algorithms into smaller, controllable tasks.
• Each small piece can be developed and tested
independently.
• Some processes can be reused in other projects to
reduce development time.
•
Developed in collaboration with multiple people in the same
project.
3) Use exception handling - Exception handling is used to capture and handle
errors, at least to record these errors for later analysis.
• Put the process that generated the problem into the
Try Catch activity.
• Put the called external process into the Try Catch
activity.
• Put the recovery operation in the Catch section.
4) Make your workflows readable - Make the process clear and readable. A readable
process is easier to debug, and in a team project, someone else might need to
use your process.
• Name the process component with a descriptive name.
• Use annotations for every activity, explaining the
purpose of it. Make comments and instructions.
• Record real-time execution progress, which helps to
pinpoint errors faster.
• Save the settings of Workflow to a separate file.
5) Keep it clean - Keep the operating environment clean. Let UiPath turn
off unused applications, windows, and web pages in a timely manner.
____________________________________________
Project Organization – Workflow Organization
____________________________________________
Invoke Workflow
The Invoke
Workflow activity is one of the main tools for breaking up a workflow in
smaller components. Right clicking any sequence, flowchart, container, or
activity and selecting Extract as Workflow will save it as a separate
workflow and replace it with an Invoke Workflow activity that points to the
extracted workflow
Comments
Post a Comment