# WikiData

PageData:
==Table of Contents
[[TOC]]
== Changes to generation of NodeSpec files
 1. Email and Web NodeSpec files are now generated via the same code
 1. Packages with VIX are treated in the same way as packages with erg_logo.gif
 1. All Keys in the NodeSpec file are quoted

PrevPageData:
@@@@@@@@@@@@@@@@8/6/2013 3:55:38 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Changes to generation of NodeSpec files
 1. Email and Web NodeSpec files are now generated via the same code
 1. Packages with VIX are treated in the same way as packages with erg_logo.gif
 1. All Keys in the NodeSpec file are quoted
Another list
 * aaaa
 * bbbb
 * ccccc

@@@@@@@@@@@@@@@@8/6/2013 3:49:59 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Changes to generation of NodeSpec files
 1. Email and Web NodeSpec files are now generated via the same code
 1. Packages with VIX are treated in the same way as packages with erg_logo.gif
 1. All Keys in the NodeSpec file are quoted

@@@@@@@@@@@@@@@@8/6/2013 3:05:09 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]


@@@@@@@@@@@@@@@@8/6/2013 3:00:10 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Changes to generation of NodeSpec files
 :* Email and Web NodeSpec files are now generated via the same code
 :* Packages with VIX are treated in the same way as packages with erg_logo.gif
 :* All Keys in the NodeSpec file are quoted

@@@@@@@@@@@@@@@@8/6/2013 2:55:16 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

== Changes to generation of NodeSpec files
1) Email and Web NodeSpec files are now generated via the same code
2) Packages with VIX are treated in the same way as packages with erg_logo.gif
3) All Keys in the NodeSpec file are quoted


PageData:
==Table of Contents
[[TOC]]
== Creating a new Wiki page
>'''Method 1'''. Writing a Wiki''''''Word automatically creates a link to an editable the page.
 * Edit a page (by Edit button or by double clicking a page)
 * Simply type any WikiWord ( which is a joined capitalized word like-> ThisIsWikiWord ) in the page and click Save. 
 * The WikiWord becomes a hyperlink to create a new page.
 Examples:  ThisIsWikiPage,  MyVacation,  MyAlbumIn2005
This method is currently disabled. Wiki Links must be specific.

>'''Method 2'''. Use  [''''''[  and  ]''''''] to enclose just about any  page topic
 Examples:  [''''''[The Old Wise Man of Fantasia]'''''']
            [''''''[2006-02-15 Birth of my cousin]'''''']
>'''Method 3'''. Use  [''''''=  and  ]  works similar to method 2
 Examples:  [''''''=The Old Wise Man of Fantasia]
            [''''''=2006-02-15 Birth of my cousin]

== Basic Formatting   

'''Paragraphs''' [1]
 * '''Avoid indenting''' paragraphs.
 * '''Use blank lines''' to separate paragraphs.
 * You can use {'''br'''} to insert line break within a paragraph.   {red}'''NEW'''!{/red}

'''Monospace'''
	* Starting a line with space makes the whole line monospaced.
 This is an example of a monospaced line.

'''Lists'''
 * This is unnumbered list using '''space-asterisk''' 
 * You can also use '''tab-space'''. (If you can't type a TAB, use 8 spaces).  Or better yet just use  1 space.

Numbered List example:

 :* This is numbered list using '''tab-colon-asterisk'''.
 :* You can start a line with <space>:*<space>  
 :* or <space>:*<space> or <space>1.<space>  for lists.


'''Horizontal Line'''
	* Four dashes at the left margin: ''''''--''''''--

'''Emphasis'''
	* Use doubled single-quotes ('') for emphasis (usually italics)
	* Use tripled single-quotes (''') for strong emphasis (usually bold)
	* Use five single-quotes ('''''), or triples within doubles, for some other emphasis 
	* Use Six single-quotes, or triples within triples, to Break''''''Up Long''''''Bumpy''''''Words so that they do not become Wiki Name''''''s.
	* You can also use them to separate suffixes (like 's') from Wiki Name''''''s.  
	* Emphasis can be used multiple times within a line, but cannot cross line boundaries.
	* Use "-''_''" and "''_''-" for  -_underlining_-.

'''References'''
	* JoinCapitalizedWords to make local references. If the page is NOT YET created the link will LookLikeThis.
	* You can also use '''double brackets''' to create wiki words, for example, the format would be  '''[['''Wiki Word''']]''' [3]
	* Precede URLs with "http:" to create links automatically as in: http://www.c2.com/ 
	* Other kinds of links are mailto:my@email.com, ftp://www.ftp.com, news://ggroup.com
	* ISBN and Amazon(c) book link, use ISBN'':''0672320681 for example ISBN:0672320681

'''Imbedded Images'''
 * Imbedded images preceding url with '''img:''' like this:
  img''':'''http''':'''//c2.com/sig/wiki.gif  or image''':'''http''':'''//c2.com/sig/wiki.gif
img:http://c2.com/sig/wiki.gif 

'''Referencing files relative to the document root. (Local reference shortcut) {red}NEW!!12/2005{/red}'''
 * Note: '''local''': is not followed by slash characters.  For example, writing...
 1. link local file examples  
 
   writing... {blue}local'''''':wiki.css{/blue}      results to this link ->  local:wiki.css
   writing... {blue}local'''''':icon.png{/blue}      results to this link-->  local:icon.png
   If file is sub folder , simply write like this --> {blue}local'''''':images\icons\icon.png{/blue} 

 2. local image extensions

   The keyword $''''''image$ results in a reference to local'''''':images/page_Current''''''Page''''''Name. This allows each page to have a directory of local images.
   The keyword $''''''Page$ results in the name of the current page

 3. local image examples    
 
   writing... {blue}image'''''':local:icon.png{/blue} results to this --> image:local:icon.png  
   writing... {blue}imageleft'''''':local:icon.png and  imageright'''''':local:icon.png{/blue} work as follows...
imageleft:local:icon.png  
imageright:local:icon.png

{br}
'''Footnotes'''
	* You can use numeric and square bracket for a footnote. [2]
	* At the bottom, just add square bracket at first character of a line and the number.

== Other Types of Formatting
	* Three blank lines creates 1 blank line
	* '==','===','====' at the start of line creates Topic
	* Coloring text for {red}red{/red}, {green}green{/green}, {blue}blue{/blue} and {black}black{/black} are allowed but must be kept at minimum.  Remember wiki is not about fancy presentation but more about quality content.
	* Use ">" to indent a paragraph (first level).   You can  also use ">>" for second level. ">>>" for third level indentation or block quote. ''' Formerly, the pipe character '|' was used for this purpose.'''  Pipe character is now used for tables. see below.
	* Use also '''{'''italic'''}''' or '''{'''bold'''}''' to {italic}highlight longer texts or paragraphs.{/italic}
	* Precede url with image with  '''Imageleft:''' or '''Imageright:'''  or '''Imagecenter:'''to justify image.

== Alternate Labels to Links and Wiki Words
 * Use alternate label to hide URL or hyperlink  like this...
 #@91;Go to Cnn News|http''''''://cnn.com#@93;
yields this...   [Go to Cnn News|http://cnn.com] !!!
 * Use alternate label to hide WikiWord like this:  
 #@91;Go to my Wiki homepage=wikiasp#@93;
yields this...
[Go to my Wiki homepage=Wikiasp] !!!

== InterWiki Links
Examples:
 #@91;My Website=ElreySite::Vacation''''''Page#@93;   -> ''Goes to the page VacationPage of database ElreySite using My Website as link alias.''
 #@91;My Website=Elrey''''''Site::#@93;               -> ''Goes to default start page of database ElreySite using My Website as link alias.'' 
 #@91;Elrey''''''Site::Vacation''''''Page#@93;              -> ''Goes to the page VacationPage of database ElreySite using no link alias.''
 #@91;Elrey''''''Site::#@93;                          -> ''Goes to default start page of database ElreySite using no link alias.''

== Table of Contents
Each page may contain a Table of Contents. It will be calculated based on the Top Level Tops that start with a space that are found at the beginning of a line. ie ''''''== Name 

The table will be inserted in the output to replace a line that starts with [''''''[TOC]''''''].

== Clickable Images
 * Use same technique above to create clickable (note the space aroung the img link)
 #@91; img'''''':http''''''://c2.com/sig/wiki.gif |http''''''://c2.com#@93;
yields this...
[ img:http://c2.com/sig/wiki.gif |http://c2.com]

== Tables
 * {red}'''NEW'''!{/red} - Use '||' character to construct tables.  Each row can have a color scheme by using '|!', '!|', or '!!'. Each row need not end with '||'. For example

|| This is || Ordinary Row || a New WikiAsp Feature
!| This color scheme || Sample || One
|! This color scheme || Sample || Two
!! This color scheme || Sample || Three
|| Great feature 

|! S|| M|| T|| W|| T|| F|| S
||  ||  || 1|| 2|| 3|| 4|| 5
|| 6|| 7|| 8|| 9||10||11||12
||13||14||15||16||17||18||19
||20||21||22||23||24||25||26
||27||28||29||30||31||  || 

== Sample HTML ({red}'''NEW'''!{/red})

If you know HTML, you can also enter it and tailor your wiki pages to your heart's desire.

>This is useful for imbedding Source Code and programs.  [Search Google for the utility|http://www.google.com/search?q=CopySourceAsHTML]


   22     <microsoft.web>

   23         <converters>

   24             <add type="Microsoft.Web.Script.Serialization.Converters.DataSetConverter"/>

   25             <add type="Microsoft.Web.Script.Serialization.Converters.DataRowConverter"/>

   26             <add type="Microsoft.Web.Script.Serialization.Converters.DataTableConverter"/>

   27         </converters>

   28     </microsoft.web>

   29     <appSettings/>





>CopySourceAsHTML is a utility that preserves syntax coloring



    9 using System.Web.UI.WebControls.WebParts;

   10 using System.Web.UI.HtmlControls;

   11 

   12 public partial class AddData : System.Web.UI.Page {

   13 

   14     protected void Button1_Click(object sender, EventArgs e) {

   15 

   16         int numItemsToAdd = Int32.Parse(NumAdd.Text);

   17         string categoryName = Server.HtmlDecode(Category.Text);

   18 

   19         ListManager lists = new ListManager();

   20 

   21         for (int i = 0; i < numItemsToAdd; i++) {





== Collapsible Panel

5/2006 - uses the syntax [Drop#] .. 

[Drop#001## View the code]
   14     protected void Button1_Click(object sender, EventArgs e) {

   15 

   16         int numItemsToAdd = Int32.Parse(NumAdd.Text);

   17         string categoryName = Server.HtmlDecode(Category.Text);

   18 

   19         ListManager lists = new ListManager();

   20 

   21         for (int i = 0; i < numItemsToAdd; i++) {



[/Drop]

[4]

== NEW bullet list (using the >* notation)
>*Level 1
>>*Level 2
>>>*Level 3
>>>>*Level 4
>>>*Level 3
>>*Level 2
>*Level 1



----
[1] This page was revised to reflect changes by  ElreyRonald.
[2] A sample footnote. Clicking on this link takes you back and forth between the text and footnote.
[3] This is not standard in C2.com wiki but implemented in most engines.  Useful for other languages like German.


PageData:
==Table of Contents
[[TOC]]
==Update Products Form (DEVI-56200)
The "Update" form submit button on this form has been re-labelled "Update Selected". 
Use this button to update only the products that you have selected via the checkboxes. 

A new button labelled "Update All" has been added to the form. 

Use this new button to update/add all new items to the SBOM. There is no need to select every item via its associated checkbox. Using this new button does that for you automatically. 

This new button does not auto-check any of the "Hide" checkboxes. It only auto-checks the Update and Add checkboxes. Any user selections made via the "Hide" checkboxes will be satisfied just as would be the case when using the "Update Selected" form submit button.

PrevPageData:
@@@@@@@@@@@@@@@@8/6/2013 3:05:54 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]


@@@@@@@@@@@@@@@@8/6/2013 3:01:19 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== BOM Difference Reports
Some projects use JIRA instead of, or in addition to ClearQuest for issues management. 
The BOM Difference Report tool can now query the JIRA database and display JIRA issues that are relevant to the product versions in the BOM. 

Note also that the BOM Difference Report form has a new checkbox on it that allows ALL the issues found to be displayed, rather than just the first one found in a query.


PageData:
==Table of Contents
[[TOC]]
== BOM Difference Reports
Some projects use JIRA instead of, or in addition to ClearQuest for issues management. 
The BOM Difference Report tool can now query the JIRA database and display JIRA issues that are relevant to the product versions in the BOM. 

Note also that the BOM Difference Report form has a new checkbox on it that allows ALL the issues found to be displayed, rather than just the first one found in a query.

PrevPageData:
@@@@@@@@@@@@@@@@8/6/2013 3:05:32 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Changes to generation of NodeSpec files
 :* Email and Web NodeSpec files are now generated via the same code
 :* Packages with VIX are treated in the same way as packages with erg_logo.gif
 :* All Keys in the NodeSpec file are quoted


PageData:
==Table of Contents
[[TOC]]
== Remove Dependency Upon BUILD_ENVIRONMENTS and PACKAGE_BUILD_ENV tables
Some reports (eg. BOM Difference) provide "Build Environment" details. 

This used to be displayed as per the following examples:
>*Build Environment: JATS Solaris
>*Build Environment: ANT Solaris
The information to do this was taken from the BUILD_ENVIRONMENTS table with keys obtained from the PACKAGE_BUILD_ENV table. 

It was discovered that the tables in question represented a "dirty hack". For example, no means existed of maintaining the data in the BUILD_ENVIRONMENTS table, and worse still, the build-machine ID was being used as a Build Environment ID and placed into the PACKAGE_BUILD_ENV table, later on being used as if it were a Build Environment ID. Code in the data base massaged the value of the key specifically for the ANT world. 

In this version of Deployment Manager, the reports are based upon the BUILD_MACHINES and BUILD_STANDARDS tables. This is the same information used by the build tool and so should be reliable. It is imperative that Release Manager users configure this data correctly, however that is not such a big ask since most projects now use the build daemons. 

Thus, the reports will now display:
>*Build Environment: JATS, Solaris
>*Build Environment: ANT, Solaris
The crucial difference being that the displayed data is based upon values from two tables, the first being the BUILD_STANDARDS, and the second from BUILD_MACHINES. Hence the value is:
>*<JATS | ANT>,<Solaris | Win32 | Linux | Generic>
This will now work for current any any future build standards and build machines that might get invented.
About Page Changes


PageData:
==Table of Contents
[[TOC]]
== DEVI-068922


PageData:
==Table of Contents
[[TOC]]
== DEVI-069415


PageData:
==Table of Contents
[[TOC]]
== DEVI-070966
== DEVI-070968


PageData:
==Table of Contents
[[TOC]]
== DEVI-070968


PageData:
Table of Contents
[[TOC]]
These are release notes made by Rupesh Solanki/Jeremy Tweddle prior to the handover of development to the current package owner.

== Version: 3.11.0
Release Date: 11-June-2008

>* Fixed a bug in BOM comparison that caused products that had been updated to also be shown as having been removed.
>* Fixed a bug that caused server error pages when removing an OS from a node, or a product from an OS.
>* DEVI-041197 BOM Home of Deployment Manager Shows Incorrect Changes Made to an SBOM DEVI-041672 Nodespecs are Incorrectly Generated when Packages are Removed from a Node DEVI-042895 Ability to view list of all Devis associated with an SBOM
== Version: 3.10.0
Release Date: 5-January-2007
>* Added Production Manager Configuration
== Version: 3.9.0
Release Date: 13-October-2006
=== Escrow Report - Paul Blain Request
Added the functionality to generate the escrow report.
=== BOM Base Configuration Products
Added a new tab that would show the Base Configurations for a given BOM
=== Find Product In BOM
This has been added under the Tools > Advanced Search section.
=== BOM NOTE Functionality - George Christidis Request
All BOMs should display the BOM Notes regardless of the state of the BOM.
== Version: 3.8.0
Release Date: 19-July-2006
=== BOM Difference Report
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.
=== AutoProducts View Added
Packages/Products from AutoProducts view from Release Manager would now be available for the user.
=== Hide/UnHide Products/Patches
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.
=== BOM Release Manager Reference
The option to select the Release Manager Reference when creating a new BOM has been added.
=== Node Versions
Node Versions would now be updated depending on the changes in the BOM compared to the previous one when XML BOM generation is clicked.
=== Obsolete Patches
Bulk obsolete patches in a platform in a given node can now be removed in one go by selecting the obsolete icon.
=== Upgrading Products with Patches in a Platform
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.
== Version: 3.7.0
Release Date: 19-May-2006

There are changes in Release Manager and Deployment Manager so that the generation of node spec files is automated and the business processes involved made efficient and less time-consuming. This involves the introduction of a mechanism that would enable users to add/import processes to package versions in Release Manager and to the platforms in a given node in a BOM (Bills Of Materials) in Deployment Manager.

In general, the mechanism can be described in the following steps: 

1. Insert processes/instances of processes in a given package version in Release Manager. 
2. Import the processes/instances of processes to the platforms in a given node in Deployment Manager. 
3. Generate the NodeSpecFiles from Deployment Manager to be used.

== Version: 3.6.0
Release Date: 12-May-2006
=== Support to Add Patch Electronic Name
This functionality has been added to support the generation of patch names in the XML BOMs.
=== NodeSpec File Generation
The process change in the nodespec files generation is: 
 :* Emailing of the nodespec files to the user. 
 :* Generating of the nodespec files under releases in auperaunx26. (NB: Nodespec filenames should be existing for these to take place)
=== Message Board Added
Important messages or tasks can be scheduled and posted on the message board.
=== BOM Diff and Merge Manager re-located
These have been moved under the "Tools" section on the top-right menu bar. This is where useful tools would be placed so as to assist the business process.
=== All Process Fields Editable
Pkg_health_tag and package/product fields for a process in a given OS in a node can now be changed upon user request.
== Version: 3.5.0
Release Date: 04-Apr-2006
=== BOM History Report
This tool has been added under the new "Reports" link on the header menu on the home page. Select the "BOM History Tracker" from the "Bom History" as this is the initial report functionality that has been officially released. This would help users in identifying the Bom, Node, OS changes that occur in an SBOM between certain periods:
=== Bom Difference Report
The difference report that gets emailed as per the user's request has been extended once again, so that now it would be able to display the patches that have been added to the new BOM selected compared to the old BOM.
== Version: 3.4.0
Release Date: 13-Mar-2006
=== New Functionality Under Additional Tools
The functionality to merge and diff two given SBOMs have now been split into two so that the user can get more detailed information regarding the differences between the SBOMs.
The SBOM Merge Manager would display the changes as per node, operating systems applied to the node and the product versions existing.
The SBOM Version Difference Report would display the changes as per the product versions existing in the SBOMs.
=== History Tab
History tabs have been added to most of the sections in Deployment Manager so as to track and record the action logs of Deployment Manager users.
=== NOT_XML functionality
Each operating system would now have an option whether to display or not to display in the XMLs generated for CFengines.
=== Is_Interface Edit Option
There is now support to edit the "is_interface" value for given processes.
=== Support for Windows E-name
Package names would now support both SunOS and WIN electronic names for CFengines.
===Products In the Node Spec File
Deployment Manager can now support the ability to add several products in the node spec file.
=== Bom Difference Report
The difference report that gets emailed as per the user's request has been modified so that now it would be able to display the product/package versions that exist between the two versions employed in the BOMs.
=== XML files for CFEngines
The XML files being generated for CFengines would now be zipped and emailed to the user instead of having Deployment Manager displaying the path to access the files previously.
== Version: 3.2.0
Release Date: 31-Jan-2006
>* SBOM Difference Report
>* XML Bom Generation Path Modified
>* DEVI-021016: Need deployment manager support for managing what patch goes to which node

Stephen, 
As per your suggestions, I have written 2 scripts to support this. One has been implemented in the Deployment Manager GUI.

The other can be run from the server to extract data required by you for the patches without the HTML contents.

(For example, run_patch.asp?project=SYDNEY (SYD)&release=SITS Legacy&sbom=1.4.2&node=Central System Off-line Server(OFS)&OS=Solaris))

PrevPageData:
@@@@@@@@@@@@@@@@8/6/2013 3:16:23 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Table of Contents
[[TOC]]
These are release notes made by Rupesh Solanki/Jeremy Tweddle prior to the handover of development to the current package owner.

== Version: 3.11.0
Release Date: 11-June-2008

>* Fixed a bug in BOM comparison that caused products that had been updated to also be shown as having been removed.
>* Fixed a bug that caused server error pages when removing an OS from a node, or a product from an OS.
>* DEVI-041197 BOM Home of Deployment Manager Shows Incorrect Changes Made to an SBOM DEVI-041672 Nodespecs are Incorrectly Generated when Packages are Removed from a Node DEVI-042895 Ability to view list of all Devis associated with an SBOM
== Version: 3.10.0
Release Date: 5-January-2007
>* Added Production Manager Configuration
== Version: 3.9.0
Release Date: 13-October-2006
=== Escrow Report - Paul Blain Request
Added the functionality to generate the escrow report.
=== BOM Base Configuration Products
Added a new tab that would show the Base Configurations for a given BOM
=== Find Product In BOM
This has been added under the Tools > Advanced Search section.
=== BOM NOTE Functionality - George Christidis Request
All BOMs should display the BOM Notes regardless of the state of the BOM.
== Version: 3.8.0
Release Date: 19-July-2006

BOM Difference Report

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.
AutoProducts View Added

Packages/Products from AutoProducts view from Release Manager would now be available for the user.
Hide/UnHide Products/Patches

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.
BOM Release Manager Reference

The option to select the Release Manager Reference when creating a new BOM has been added.
Node Versions

Node Versions would now be updated depending on the changes in the BOM compared to the previous one when XML BOM generation is clicked.
Obsolete Patches

Bulk obsolete patches in a platform in a given node can now be removed in one go by selecting the obsolete icon.
Upgrading Products with Patches in a Platform

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.

== Version: 3.7.0
Release Date: 19-May-2006

There are changes in Release Manager and Deployment Manager so that the generation of node spec files is automated and the business processes involved made efficient and less time-consuming. This involves the introduction of a mechanism that would enable users to add/import processes to package versions in Release Manager and to the platforms in a given node in a BOM (Bills Of Materials) in Deployment Manager.

In general, the mechanism can be described in the following steps: 

1. Insert processes/instances of processes in a given package version in Release Manager. 
2. Import the processes/instances of processes to the platforms in a given node in Deployment Manager. 
3. Generate the NodeSpecFiles from Deployment Manager to be used.

== Version: 3.6.0
Release Date: 12-May-2006

Support to Add Patch Electronic Name

This functionality has been added to support the generation of patch names in the XML BOMs.
NodeSpec File Generation

The process change in the nodespec files generation is: 
1. Emailing of the nodespec files to the user. 
2. Generating of the nodespec files under releases in auperaunx26. (NB: Nodespec filenames should be existing for these to take place)
Message Board Added

Important messages or tasks can be scheduled and posted on the message board.
BOM Diff and Merge Manager re-located

These have been moved under the "Tools" section on the top-right menu bar. This is where useful tools would be placed so as to assist the business process.
All Process Fields Editable

Pkg_health_tag and package/product fields for a process in a given OS in a node can now be changed upon user request.
== Version: 3.5.0
Release Date: 04-Apr-2006

BOM History Report

This tool has been added under the new "Reports" link on the header menu on the home page. Select the "BOM History Tracker" from the "Bom History" as this is the initial report functionality that has been officially released. This would help users in identifying the Bom, Node, OS changes that occur in an SBOM between certain periods:
Bom Difference Report

The difference report that gets emailed as per the user's request has been extended once again, so that now it would be able to display the patches that have been added to the new BOM selected compared to the old BOM.
== Version: 3.4.0
Release Date: 13-Mar-2006

New Functionality Under Additional Tools

The functionality to merge and diff two given SBOMs have now been split into two so that the user can get more detailed information regarding the differences between the SBOMs.
The SBOM Merge Manager would display the changes as per node, operating systems applied to the node and the product versions existing.
The SBOM Version Difference Report would display the changes as per the product versions existing in the SBOMs.
History Tab

History tabs have been added to most of the sections in Deployment Manager so as to track and record the action logs of Deployment Manager users.
NOT_XML functionality

Each operating system would now have an option whether to display or not to display in the XMLs generated for CFengines.
Is_Interface Edit Option

There is now support to edit the "is_interface" value for given processes.
Support for Windows E-name

Package names would now support both SunOS and WIN electronic names for CFengines.
Products In the Node Spec File

Deployment Manager can now support the ability to add several products in the node spec file.
Bom Difference Report

The difference report that gets emailed as per the user's request has been modified so that now it would be able to display the product/package versions that exist between the two versions employed in the BOMs.
XML files for CFEngines

The XML files being generated for CFengines would now be zipped and emailed to the user instead of having Deployment Manager displaying the path to access the files previously.
== Version: 3.2.0
Release Date: 31-Jan-2006

SBOM Difference Report

XML Bom Generation Path Modified

DEVI-021016: Need deployment manager support for managing what patch goes to which node

Stephen, 
As per your suggestions, I have written 2 scripts to support this. One has been implemented in the Deployment Manager GUI.

The other can be run from the server to extract data required by you for the patches without the HTML contents.

(For example, run_patch.asp?project=SYDNEY (SYD)&release=SITS Legacy&sbom=1.4.2&node=Central System Off-line Server(OFS)&OS=Solaris))

@@@@@@@@@@@@@@@@8/6/2013 3:12:03 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Table of Contents
[[TOC]]
== Version: 3.11.0
Release Date: 11-June-2008
Fixed a bug in BOM comparison that caused products that had been updated to also be shown as having been removed.

Fixed a bug that caused server error pages when removing an OS from a node, or a product from an OS.

DEVI-041197 BOM Home of Deployment Manager Shows Incorrect Changes Made to an SBOM DEVI-041672 Nodespecs are Incorrectly Generated when Packages are Removed from a Node DEVI-042895 Ability to view list of all Devis associated with an SBOM

== Version: 3.10.0
Release Date: 5-January-2007
Added Production Manager Configuration


PageData:
Table of Contents
[[TOC]]
== ClearQuest interactions
>* Removed use of 4 ,unused and unavailable, ClearQuest databases
== Release Notes
Migrated the storage of the Deployment Manager Release Notes from the (deprecated) MASS Wiki into the Deployment Manager tool itself.
== Merged several features from Release Manager into Deployment Manager
>* The use of an internal Wiki Engine
>* Common header generation on all pages
>* Common header to highlight use on non-Production machines and databases
>* Tooltips
>* Authentication process
>>* Use Authentication domain as provided by Access Manager
>>* No password when used on Development Database
== Account Details Pages
These have been enabled. Some changes have been imported from Release Manager. In particular the ability to display details on the users access permissions.


PageData:
Table of Contents
[[TOC]]
== ClearQuest interactions
Corrected problem with Querying the ClearQuest Issues database. The problem was introduced in the last release when several ClearQuest databases where removed.
== BOM Difference Report
>* Expanded the page header to show the Project, Branch and BOM Version.
>* Added Jira Issues.
>>* Previously the report only included issues from ClearQuest. This change adds issues that have been held in Jira. The extraction is still experimental. 
>* Fixed issues with the Expand/Collapse of sections.
>>* Previously, do to incorrect HTML, only a part of the section would collapse.
>* Add a control to Expand and Collapse all sections in the report
All feedback welcome.

PrevPageData:
@@@@@@@@@@@@@@@@9/2/2013 3:34:37 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Table of Contents
[[TOC]]
== ClearQuest interactions
Corrected problem with Querying the ClearQuest Issues database. The problem was introduced in the last release when several ClearQuest databases where removed.
== BOM Difference Report
Added Jira Issues.

Previously, the report only included issues from ClearQuest. This change adds issues that have been held in Jira. The extraction is still experimental. All feedback welcome.

@@@@@@@@@@@@@@@@8/23/2013 1:39:14 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Table of Contents
[[TOC]]
== ClearQuest interactions
Corrected problem with Querying the ClearQuest Issues database. The problem was introduced in the last release when several ClearQuest databases where removed.


