Automate

Welcome to the Automate community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Here are some useful links where you can find more information:

Product Announcements  Ideas Portal

Discussions

Members

Resources

Events

 View Only

  • 1.  Methodology for tracking changes to Workflow solutions

    Posted 02-28-2020 15:39
    We're trying to implement some changes to better track and document changes that we make to our Winshuttle workflow solutions.

    For example, if we make some changes to a solution to add a new field, or change some rules, or import a new version of a Transaction script, we want to somehow keep track of the changes that were pushed to production for each version of the solution... maybe even keep track of additional changes we need to monitor (such as eventually removing old scripts no longer in use, once requests which might use those scripts complete workflow).

    I can think of a couple ways of doing this, but I'm curious to hear what others might be doing, or if there are any software programs out there that were created specifically for this purpose.  I know that Git exists for keeping actual code or file changes, but I think Git is a bit overkill for what we are trying to do.  I could create a custom database for something like this for my own use, but I'm more interested in something multi-user, hosted online (maybe Sharepoint) that multiple developers could potentially use.

    Anyone else doing something similar to what I describe above, who'd like to share their methodology?

    ------------------------------
    Jeremie Dippel
    Project Engineer @ Rockwell Automation
    Wisconsin Local Wug Leader
    I'm your huckleberry.
    ------------------------------


  • 2.  RE: Methodology for tracking changes to Workflow solutions

    Posted 02-29-2020 10:53
    One way is to use TFS or another agile-enablement tool to track changes through work effort cards.

    ------------------------------
    Joshua Whitener | Technical Advisor
    Exxon Mobil Corporation | 8326258441
    ------------------------------



  • 3.  RE: Methodology for tracking changes to Workflow solutions

    Employee
    Posted 03-01-2020 05:32
    Hi,

    I developed my own software for tracking changes, version control, archive of old scripts and deployment of new. This is integrated in to outlook via a outlook addin I have also developed.

    i tried many different apps and online software for managing the deployment and changes but everything I tried was either too simple or as you say, overkill.

    happy to share some details with you if you think it may help.

    ------------------------------
    Many Thanks,
    Adam Treadwell
    Business Development Manager - IT/Tech
    Jaguar Land Rover
    ------------------------------

    Original Message


  • 4.  RE: Methodology for tracking changes to Workflow solutions

    Employee
    Posted 03-02-2020 05:38

    Hello Adam, 

    Yes! This is definitely of interest to me as we are in the process of doing a study to find the best solution for Version Control ourselves. 

    Andy



    ------------------------------
    Andy Ciesielski | MDM
    BRITISH GYPSUM | 01159451200
    ------------------------------

    Original Message


  • 5.  RE: Methodology for tracking changes to Workflow solutions

    Posted 03-02-2020 08:45
    We go old school here and have documents on Foundation to track updates:
    - For Scripts - we have Supporting Docs associated to them that contains a Change Log that the developer is responsible to manually update, encouraged by the script approver
    - For Solutions - we have an Excel "cover sheet" that has a Change Log that is also a manual update to be done by the Developer and to be reminded by the COE Team that moves solutions to Production

    ------------------------------
    Scott Gorski
    General Mills | Data Analyst
    ------------------------------



  • 6.  RE: Methodology for tracking changes to Workflow solutions

    Posted 03-02-2020 09:49
    "One way is to use TFS or another agile-enablement tool to track changes through work effort cards."
    Joshua, I'm not familiar with TFS, but some initial digging suggests that it may be a bit more than what we're trying to do here. Essentially, just trying to track the following information (at least initially):
    - name of solution the changes are being made to
    - developer making the changes
    - date of changes
    - reason for changes
    - actual changes (possibly in a 'main table/child table' type setup, with the child table containing all the individual changes records, tied to a solution in the main table)

    Composer tracks the version history, and the varying versions of the solutions, so we just need to keep track of the "what was done, why, by whom, when, etc".


    Adam, I know I could develop my own system (I already have a 'single use' database that I use for a different project), was more curious to learn if there are 'easy to use' software packages out there, or plug-in's for MS Teams I wasn't aware of, or Sharepoint plug-in's, or something along those lines to investigate further. And again, trying to figure out something that could be used by at least 4 or 5 developers (all working on different solutions)... so has to be easy enough to use if I want to enjoy any success of our other developers using the solution I propose. I am curious why you are integrating into Outlook, rather than with Sharepoint or Teams (we have a heavy push for Sharepoint and Teams here).

    ------------------------------
    Jeremie Dippel
    Project Engineer @ Rockwell Automation
    Wisconsin Local Wug Leader
    I'm your huckleberry.
    ------------------------------

    Original Message