Analyzing Packages
After finding a package, you can perform a net change analysis before you download the package.
To analyze packages:
On the search results tab, select the packages that you want to analyze and click the Analyze button.
If you have selected more than one package and you choose the Analyze with Downloads option from the Analyze drop-down list box, the selected packages are compared to the superseded list. Next, the most current download found is used to perform the net change analysis by comparing the most current download to previously downloaded packages.
-
If you select the Summarize All option from the Analyze drop-down list box, Change Assistant will summarize the selected packages and will not perform a net change comparison.
When the analysis finishes processes, a report appears. Review the report.
Any special instructions selected in the Special Instructions option are included in the report.
(Release 9.2.6) You can use the AIS connection to enable the Anaylze Packages option to get a comprehensive impact analysis of all the packages that use EnterpriseOne data. The summary analysis report connects to the AIS Server and the analysis information is included in the report generated. You can use this information to evaluate the changes that can occur based on the objects.
You can apply any of the following options for package analysis:- All Packages
- Changed Objects
- New BUGs
- New Objects
- All BUGs
- All Objects
- Special Instructions
- Include BUG and Object Relationships
- (Release 9.2.6) Include Dependent Packages.
You can generate the comprehensive impact analysis report in an HTML, an XML, or a Comma Separated Values (CSV) format. If you select the CSV format then the report is exported in the form of a spreadsheet.
The summary analysis report provides the following information:- A list of selected packages.
- The list of changed objects and their details, for example, the date when the object was changed, when the object was last deployed, and in which environment. The report also provides information about the object and its pathcode. The report also helps you identify if an object has been copied and provides information regarding the base-object from which the object was copied.
- A list of new bugs. You can use this information to compare the new bugs and their information with the software updates history to identify the bugs which have been previously deployed. If a bug is not a part of any package, then it is considered as a new bug which needs to be assessed. By using the Include BUG and Object Relationships option, you can see the objects with which a bug is associated.
- All the bugs that are related to the packages. The report also provides information about whether the bugs have been previously deployed.
- A list of all the objects related to the packages. You can verify if the objects have been previously deployed, and view information with which the packages were deployed.