Painfully slow job processing

Hello all. I am a new user and have just compiled my first working automation. It is a work in progress, but it has raised several major concerns with this tool. For some background, my team is responsible for running mass updates to our mainframe using a tool called Foxtrot that is put out by EnableSoft. It worked like a macro, duplicating user functions in our Mainframe emulator. Using this, we could run about 1000 transactions in roughly 20 minutes.

That tool is no longer going to be available to us, so we are looking to replicate that function and processing speed with UiPath using attended robots, at least until we are able to progress far enough to make the change to unattended robots. My workflow replicates one of the simpler processes, but is taking 5-8 minutes to run through 10 transactions. Is there a way to speed this up with an attended robot? I have attached the two .xaml files used for reference.

This job is intended to ingest the data from a .CSV file, add a couple of columns, and use that data to enter into our mainframe. Thank you in advance for any suggestions!

ILTL Entry.xaml (53.9 KB)
GetInputData.xaml (16.0 KB)

1 Like

Hey @brian.p.kassler!! Tell me which of the .xaml takes the longest? A great way is to change your activities from “Filter Datatable” to “Assign” with LINQ queries. For DTs with a large number of lines you will gain an absurd time!

And Welcome to the community!! :tada: :mechanical_arm:

1 Like

Hi Gabriel!

The .xaml that takes the longest is the ILTL Entry. I will replace the filters with queries and give it shot!
Thanks for the advice!

Any questions on how to filter the DTs with LINQ send the question here!

1 Like

@Gabriel - I am trying to write a LINQ query that will give me a count of rows in the data table called BFEE_VALUES where the LOGTEXT field contains “Requested processing” OR “No changes”.

This is what I have so far - can you help get the rest of the way?

BFEE_VALUES.asEnumerable.Where(“LOGTEXT”).toString Contains(“Requested processing”) Or (“LOGTEXT”).toString Contains(“No changes”)).Count