Architecture regarding execution of vbscripts and how to move it accross environments

[Nannevan_der_Wa]

Hi all,

Part of my process is executing a VBScript. We are now in the phase of testing the robot in the acceptance environment after which we will migrate it to production. I am wondering how it works with locating and moving the scripts that need to be executed by this process and if there are any best practices in this area.

Right now the path of the vbscript to be executed is hardcoded in the object, and the location of the script is in a random documents folder on my local machine. This is of course not workable when testing the robot in acceptance environment and then migrate it to production. Any thoughts on setting this up properly? 

Looking forward to hear them!

Best,
Nanne

------------------------------
Nanne van der Wal
Advisor
EY
Europe/Amsterdam
------------------------------

[MattPalmer]

Our processes have Dev / Test / Prod folders out on the network.  Within those folders our processes will have an Excel config file.  Each process will have different needs of what is contained in the config file, but they usually include network file paths to template files, scripts, email distributions, sql code, etc.  When our processes run the first thing they will do is open the config file and load the items into a collection and then use those items throughout the process.  That way, at some point in the future, if file paths change, email distributions change, sql code changes, all we need to do is update the Excel config file and we don't have to re-factor the process.


------------------------------
Matt Palmer
Business Process Specialist
Chesapeake Energy
America/Chicago
------------------------------