Create a Solution architecture for 2000+ xmal

Help Studio
1

Create a Solution architecture for 2000+ xmal

Use Case Description

Hello All,

Need your input to know about how we can manage a project where we have 2000+ xmal in one solution, what be the best approarch to manage it.

Thanks in advance.

AS-IS WORKFLOW, TO-BE WORKFLOW

-

Other information about the use case

Industry categories for this use case: Customer Service

Skill level required: Intermediate

UiPath Products that were used: UiPath Studio

Other applications that were used: Web based xmal

Other resources: -

What is the top ROI driver for this use case?: Accelerate growth and operational efficiency

2

Hi @Sumit_Sharma3,

2000+ XAMLs in one solution is massive.
I would recommend several things:

  1. breaking up to multiple stages, for example:
    1.1. Dispatcher and Performer
  2. organize the XAMLs by folders following some sort of logic
    2.1. For example, all excel related XAMLs in Excel folder, etc
  3. identify repetitive and reusable sequences and consolidate them as reusable workflows
    3.1. Rather than having Step1a.xaml, Step1b.xaml, Step1c.xaml which are very similar, consolidate into one Step1.xaml so total number of XAMLs reduce
  4. number the XAML files by chronological order
    4.1 Rather than have XAML files called OpenExcel.xaml, EditExcel.xaml, CloseExcel.xaml, rename them to 11_OpenExcel.xaml, 12_EditExcel.xaml, 13_CloseExcel.xaml
    4.2. This way any developers unfamiliar can quickly navigate through and understand the process flow without having to know the process intimately

Use REF and Queue(s) (multiple queues if needed for different stages).