What's the best way to track ID's which have already been processed?

Help Activities
, ,
1

Hi everyone,

I’m building a process which needs to remember the (application-generated) ID’s of transactions which have already been completed. The workflow is:

  1. Get a list of available ID’s from the application,
  2. Subtract the ID’s which have previously been processed by RPA,
  3. Process the next unprocessed ID,
  4. Add the ID from step 3 to the list of processed ID’s
  5. Return to step 1 until no more unprocessed ID’s remain.

What’s the most appropriate design to achieve this? It’s an important criteria that nothing gets picked up twice. Should I just write the ID’s to an Excel file or is there a better option?

Thanks for any help

2

@rpa_jay

If you are using queues …then straight way woulde to add id as reference and use unique reference

Or

Instead of excel you can try using data services to add and check the data…or basically yes end goal would be to save them some where…

Also i hope this condition needs to check all the previous values and not only the current run id’s

Hope this helps

Cheers

3

Data service was exactly what I was looking for. I’ve got a prototype running already!

Thank for your help :slight_smile:

1 Like
4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.