Robotic Process Automation (RPA)

 View Only
  • 1.  Same script - different login information: how to schedule the best way

    Posted Mon July 05, 2021 12:12 PM
    Dear RPA community,

    I have some scripts which are working fine and I would like to schedule them to run in the early morning.
    The issue is that there are multiple accounts (more than 10) where the exact same script has to run. Instead of now creating 10 different scripts which are exactly the same besides the login information in each, it would be great to set like a general variable, so that I can set username and password when scheduling. Moreover, besides being annoying with 10 different scripts, it would also be a pain in terms of updating the scripts.
    Does IBM RPA provide any solution for that? I took a look on parameters but when scheduling the script in the web portal, I was not asked for entering the parameter values.

    Any help or tips are appreciated!

    Thanks,

    ------------------------------
    Jan Lorenz
    ------------------------------


  • 2.  RE: Same script - different login information: how to schedule the best way

    Posted Tue July 06, 2021 04:04 AM
    Hi Jan,
    Maybe you could create an 'account script'  that calls the main script.  The 'account script' would extract the appropriate credentials and then invoke the main script passing these credentials as script parameters.  You would create a schedule for each 'account script', not the main script.

    ------------------------------
    NIGEL CROWTHER
    ------------------------------



  • 3.  RE: Same script - different login information: how to schedule the best way

    Posted Tue July 06, 2021 10:44 AM
    Hi Nigel,

    that's a good idea! I hope in the long-term there comes a function within the tool to enable that.

    Thank you

    ------------------------------
    Jan Lorenz
    ------------------------------



  • 4.  RE: Same script - different login information: how to schedule the best way

    Posted Wed July 07, 2021 01:14 PM
    Hi @Jan Lorenz, I think you have a valid use case requirement: feeding bot parameters right from the scheduler, so you can reuse the bot passing different parameters, and the parameters could also come from built-in features like specifying a credential as a parameter.

    Can you please raise this idea in the portal here: https://dba.ideas.aha.io/ideas?project=WDGRPA​

    ------------------------------
    Joba Diniz
    Product Manager
    IBM
    ------------------------------