Skip to main content
Submitted

Multi-Environment Transfer + Version Notes

  • February 28, 2018
  • 6 replies
  • 1 view
D
Forum|alt.badge.img

I had a request come from a customer today which seems like a good idea.  They have to maintain strict SOX controls, so knowing what version was deployed, by who, and when are important pieces of information their auditors need to know.

Currently, when a project is transferred between environments, there isn't any notation in the project version notes.

It would be very useful to simply add the information displayed after a successful transfer to the target environment's new version created by the transfer:

 

Bv8tQakV10cjDgMc8EdFIg.png

 

So, in this case version 69 was created in PROD.  It would be very nice if the information circled above was entered into version 69's notes.  Otherwise my SOX compliant customer will need to maintain manual logs of transfers.

    6 replies

    D
    Forum|alt.badge.img
    • doug.wynkoop
    • Known Participant
    • March 6, 2018

    Hi Ryan,

    I know that compliance is high on our priority list right now, and this seems like a small tweak that could result in a big improvement for our SOX clients.  Please accept my upvote on this!

    Best regards,

    Doug Wynkoop

    D
    Forum|alt.badge.img
    • david.zebrowitz
    • Author
    • Known Participant
    • March 6, 2018

    Taking this a step further, it would also be of huge benefit to automatically populate the Version Notes box with a list of modified objects at the bottom.  Obviously it would be tremendously cool to have a list of all modifications, but I know that would be a major pain to implement.

    Simply a list of the modified objects (currently red) when being saved/deployed would probably be a minor tweak which could help ensure that even the most rushed developers have some notes in there... because we never hit OK without typing relevant information in, right?  :)

    D
    Forum|alt.badge.img
    • doug.wynkoop
    • Known Participant
    • March 6, 2018

    Also not a bad idea!  I know that the notes include work items, but flagging everything is a lot of extra labor to go through, especially if you don't have multiple developers enabled.  

    I've often wished I could see which objects were actually modified in a given deployment, so I'll go ahead and upvote this idea as well!

    Best regards,

    Doug Wynkoop

    S
    Forum|alt.badge.img

    Upvote for both!

    Additionally, in my (limited!) experience, version notes are a one-way flow, never to be heard of after saving. That's partly because a "save" happens so often during intermediate development steps. Environment transfer notes would be much more useful

    W
    Forum|alt.badge.img
    • william.wynkoop
    • Participating Frequently
    • November 8, 2018

    I'm working with yet another client who would really like this functionality!  Just being able to leave a normal save comment would be a huge improvement. 

    J
    • JTreadwell
    • Community Manager
    • February 26, 2021

    Thanks for submitting your ideas! Your continued feedback on our product is very important to us. 

    We will be evaluating your input for future improvements in the product.

    At the time of this posting, the current product roadmap is focused on a major evolution in foundational pieces of our software including splitting the development into ODX, MDW, Semantic Layer and User Portal. With this evolution, we will continue to see incredible innovation in the product that may exceed your expectations or make the need for this feature obsolete.

    If you have any questions or would like to discuss further, please reach out to me or the dedicated TimeXtender Solution Specialist in you region. Thanks!

     
    Terms & ConditionsCookie settingsAccessibility statement