Automate

 View Only

  • 1.  File Re-organization

    Posted 01-16-2019 12:27
    Hi, everyone!

    Now that I am writing more scripts, we would like to organize them differently.  If existing scripts and data files are moved to another folder, will the new path be updated in each or do we need to re-save and/or republish them?

    Any information is greatly appreciated!

    Thank you.

    ------------------------------
    Sue Ellen Keyser | Head of Continuous Improvement
    ACTEGA North America, Inc. | [City] | 856-735-2033
    ------------------------------


  • 2.  RE: File Re-organization

    Posted 01-16-2019 13:52
    Hi Sue Ellen -

    If you have published the script(s) into a data file, and the end users are using the Excel add-in to run the scripts from those data files, then there's no path to worry about since there is only 1 file that is being used (the data file).  If end users are using the Winshuttle Studio client to run scripts and pointing to the data files, then if those data files have moved locations, they will need to point them to the new location. 

    Thank you!

    ------------------------------
    Jennifer Hwang | SE
    Winshuttle North America
    ------------------------------

    Original Message


  • 3.  RE: File Re-organization

    Posted 01-17-2019 04:41

    Hi All,

    This looks like an opportunity for an enhancement to the product.

    Have a paths file referenced by the ​users WS installation that contains something like this:


         Filepath1=C:\SomeFolder\
         Filepath2=C:\SomeOtherFolder\

    When the script is saved, the product checks to see if some or all of the path to the data file is listed in Paths file.  If it is, then while saving, the product saves a reference to the paths entry, not the whole path.

    Using the above example, in a saved script, the stored data file path would look something like:

        <Filepath2>\datafile.xlsx

    instead of:

        C:\SomeOtherFolder\datafile.xlsx

    You could also have only part of the path in the paths file.  So instead of:

        C:\SomeOtherFolder\a\further\path\datafile.xlsx

    you have:

        <Filepath2>a\further\path\datafile.xlsx

    Also, if your developer is using a different set of directories to create the scripts, you can have his Paths file say

         Filepath1=C:\Development

    and the users have

        Filepath1=C:\Production

    Thus the scripts don't need to be changed at all when moving from Development to Production.

    Just an idea. :)

    Regards

    Mark




    ------------------------------
    Mark Tiller | Delivery Enhancement Developer
    Transport for London (TfL) | [London] | 0203 054 4196
    ------------------------------

    Original Message