Transportation Management

Get Involved. Join the Conversation.


    Kelly Cooper
    SCM – OTM & GTM Cloud Moving to Quarterly Updates in 19B, 2...
    Topic posted January 31, 2019 by Kelly CooperGold Trophy: 10,000+ Points, last edited March 20, 2019 by Sona SrinivasanSilver Medal: 2,000+ Points, tagged SCM 
    180 Views, 1 Comment
    SCM – OTM & GTM Cloud Moving to Quarterly Updates in 19B, 28 March 2019, 9 a.m. PT - Submit Questions

    Submit your questions for the SCM – OTM & GTM Cloud Moving to Quarterly Updates in 19B session to have them answered during the live event. Post your questions by posting a new comment to this topic.

    Please submit your questions by Wednesday, 27 March 2019.



    • Eric Westlund

      1. Why is the customer validation period only 2 weeks (patch applied week 1 for Test and week 3 for Production)?  Previously, when quarterly patches were just bug fixes, this was enough time, but now there may be major new functionality introduced.  Two weeks may not be enough time to test all the changes.  Also, it may not be enough time to modify existing configurations to work with the changed functionality.  Can this be extended?

      2. What if show-stopper issues are found during customer validation period?  Can we submit an SR to postpone the patching on Production until the issue is resolved?

      3. What about Dev instances?  FAQ says they will be updated "based on the cadence they have selected for each environment – i.e., either at the same time as the Test environment or at the same time as Production."  How do we check that "cadence" selection?  Also, is there any way to request it to be earlier, like 2 weeks before Test, to provide more time for testing and configuration changes?  That's the purpose of having the Dev instance.