Packages in autodeployment still shows in the "updates tab" in package library

Comments

1 comment

  • Jason Hanks

    Hi Espen,

    The package library existed before Auto Deployment but when the feature was introduced, the packages had to be separate so that they weren't able to be edited.  If we kept everything in the same list and you edited the name of the package and added some additional nested steps or a message followed by a logoff step, when the new package was released and downloaded it would overwrite all of those changes leaving you to do the work all over again and reset the schedules, etc.

    Another use case where you would want these types of packages separate is if you would like to give yourself a buffer to test packages before unleashing them.  A great example of this is Java.  Some customers will set up Java to Auto Deploy but will change the Approval Policy to a custom time or manually so that they can import the new package and test the impact it will have on their environment and staff before approving the Auto Deployment schedule.

    Until the Auto Deployment/Package Library is redesigned by the developers during an overhaul the Auto Deploy and standard downloads will remain separate.

    Jason

    0
    Comment actions Permalink

Please sign in to leave a comment.