Best Practices using UIPATH STUDIO

UiPath Studio Best Practices:

  1. Organizing your project
    Reliable - create solid, robust workflows that can handle errors.
    Efficient - create a structure that:
    Helps to short down development time.
    Helps to reduce errors in production.
    Maintainable - create a structure that makes it easy to update when needed.
    Extendable - new requirements should be able to be implemented easily.

  2. Choose the right layout
    The main workflow works best as a Flowchart or a State Machine.
    Business logic works best in Flowcharts as it is easier to visualize.
    Consider using ReFramework if you are using Orchestrator-queues.
    UI interactions work best as sequences as it does not involve much logic.
    If one sees that there is a need for much if-else checks and the like, then one should consider
    using a Flowchart.
    Avoid nested IF statements, use Flowcharts instead; It gives a tidier flow.

  3. Break up your workflow
    Keywords: Extract as Workflow.
    Makes it possible to develop and test the various parts separately.
    Allows you to reuse workflows.
    Makes it easier to cooperate in a team when working on different files (use Invoke Workflow File).
    Easiest if you send pure string parameters and not lists and the like (is easier to set default parameters on primitive types like string, int32, etc.).

  4. Exception handling and logging
    Put problematic workflows in try / catch blocks.
    Implement sequences within the Try / Catch blocks that allow you to restore the workflow.
    Use the Retry Scope for fragile parts in the workflow.

  5. Readability
    Give good, explanatory names to all components (workflows, activities, variables, etc.).
    Enter notes and comments where necessary. Annotations are very useful.
    Log real-time execution.
    Have environmental variables in a separate file.

  6. Cleanup
    Close applications, windows and web pages. If you do not, many interactions will have numerous instances of these running, which can eventually crash the machine.
    Always try soft-close applications first if the kill process is not used.

  7. Naming conventions
    When creating very large automations, it can be very easy to forget what every variable does. That is why it is important to have a good naming system in place.

    We recommend that you always use descriptive and accurate names, such as userName for a variable that stores the name of a user. This allows you easily identify the information the variable stores.

    Finally, we recommend that you write variable names in Camel Case, so that you can read them easier

I hope this help :smiley: :smiley: :smiley:
Please free to reply if you have any tips to help one another and help the community become more lively :smiley: :smile: :smiley:

73 Likes

Great post bro… every point is in one place :slight_smile:

6 Likes

Thanks @Lahiru.Fernando :smiley:

8 Likes

Thanks for this @pattyricarte :slight_smile:

8 Likes

This is really good @pattyricarte! Would be nice to get this posted somewhere so more people could see :clap:

2 Likes

@Gemlan,

Hope this will be helpful to you.
cheers

8 Likes

Thanks @mcicca You can share the link if u want or repost to spread. To help our community more lively .

cheers

8 Likes

Thanks for sharing @pattyricarte :slightly_smiling_face:

8 Likes

@dimpzdhel,
Happy to help!
Happy learning
cheers!

8 Likes

Hi @loginerror

Thanks for fixing the format of my topic! Hope this will spread to our community to make a reference in using best practices on UIPATH Studio .

cheers :smiley:

Happy learning :smiley:

12 Likes

I will share the post when ever possible…

I already have it book maked :slight_smile:

5 Likes

Thanks @Lahiru.Fernando

cheers
Happy learning

11 Likes

Hi @pattyricarte

See my post here:

I created a pinned wiki topic to gather all best practices in one place. If you like the idea, feel free to edit it :slight_smile:

11 Likes

Thanks for sharing…!! By combining up into single document…

5 Likes

Thanks for det great guide!!
Keep up the good work, sir.

Any chance for some example pictures of more experienced UiPath workers? (Thinkin of workflow designs and layouts etc) :slight_smile: :+1::+1:

5 Likes

Hi @loginerror

That’s great! I guess that’s the right deeds to create a collaborative thoughts to help the community.

cheers :smiley:

Happy learning :smiley:

11 Likes

Thanks for sharing! I’m a beginner. Your sharing really helps me a lot!

6 Likes

Hi @Owen_ACM

No worries happy to help :smiley:

cheers :smiley:

Happy learning :smiley:

10 Likes

Thanks for Posting :clap::clap::heart_eyes:

6 Likes

@kaluri
Welcome bro!

cheers

Happy learning

9 Likes