Subversion Repositories DevTools

Last modification

• Rev 0 – 6720 d 10 h
• Author: rsolanki

• Log message:

  DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
  <b>BOM Difference Report</b>
  This has been amended for the following reasons:
  - fix some human errors that were present.
  - include VTSUP database issues.
  - include dependencies changed comments and fixed issues between the 2 versions of a product in a BOM.
  
  <b>AutoProducts View Added</b>
  Packages/Products from AutoProducts view from Release Manager would now be available for the user.
  
  <b>Hide/UnHide Products/Patches</b>
  This functionality has now been added to hide products/patches from a given node when you select the "Update Products" button from the menu. You can also unhide them by selecting the "Unhide Products" button.
  
  <b>BOM Release Manager Reference</b>
  The option to select the Release Manager Reference when creating a new BOM has been added.
  
  <b>Node Versions</b>
  Node Versions would now be updated depending on the changes in the BOM compared to the previous one when XML BOM generation is clicked.
  
  <b>Obsolete Patches</b>
  Bulk obsolete patches in a platform in a given node can now be removed in one go by selecting the obsolete icon.
  
  <b>Upgrading Products with Patches in a Platform</b>
  Deployment Manager had a slight issue where it would enable you to update/edit a package version even though patches related to that version existed. For example, ERGoracs 25.2.0000.syd had a number of patches in a given OS in a given node. Previously, you could then upgrade that package from 25.2.0000.syd to 25.2.1000.syd because of XYZ. That would mean that patches related to the previous version would still exist in the BOM.
  
  To resolve this issue, I have put a routine check where if the patches that are related to a given package version exist then the buttons for editing would not be displayed
  
  
  <b>Release Date:</b> 19-July-2006