ZMF4ECL - Auto refresh packages and components after a developer action

by Joao Rolinho on January 17, 2019

ZMF4ECL - Auto refresh packages and components after a developer action

  • If the developer does a check out of a component to a package or does a build of a component in the package, the action is not reflected immediately and requires developer to manually refresh the package or the component to see the change in state. Automating this refresh option could be of an aid for Developers to see the changes immediately.

  • Please login to view any attachments.

  • This may not always be possible for every ZMF4ECL action. For example, where an asynchronous process is executed on the mainframe that results in an adjustment to the ChangeMan Explorer contents. However, ENH334041 has been opened requesting that we research the automatic refresh of this view's contents after developer actions wherever reasonable and viable.
    Steve Nevin Commented by Steve Nevin September 11, 2019
    Top 10 Reviewer  -  

    This may not always be possible for every ZMF4ECL action. For example, where an asynchronous process is executed on the mainframe that results in an adjustment to the ChangeMan Explorer contents. However, ENH334041 has been opened requesting that we research the automatic refresh of this view's contents after developer actions wherever reasonable and viable.

     

PrintEmail

Recent Tweets