Release Assurance app

The Release Assurance app is provided with a QA system, a Production system, and a set of custom transports from the QA system. It finds a set of changed or missing dependent objects that may cause errors when the transports are imported from the QA system into the production environment. These objects should be reviewed for inclusion in the release.

Dependent objects are those that either:

  • Use the objects from the input transports directly (parent objects) or
  • Are used by the objects from the input transports directly (child objects).

Dependent transports are transports from the QA system that contain dependent objects.

A user with LiveCompare Editor privileges must prepare this app by running the Create Object Links Cache workflow for the ‘QAS’ RFC Destination. See the ‘Prerequisites’ section below for details.

DevOps categories

Operations.

Prerequisites

Before running the Release Assurance app for the first time, you will need to run the Create Object Links Cache workflow from the Prerequisites package to create an object links cache database for your QA system. Check the system’s RFC Destination in the LiveCompare hierarchy first, and select the OLC tab to verify whether an object links cache database has already been created. The Create Object Links Cache workflow may be run incrementally to update the object links cache database with any recent object dependency changes.

Run the app

To run the Release Assurance app, select the app from the Apps screen and create an app variant. Set the ‘QAS’ field to the RFC Destination for the QA system, and the ‘PRD’ field to the RFC Destination for the Production system. Edit the ‘Transports’ table to provide a set of custom transports to be analyzed.

Click ‘Run’. When the variant has completed, its results may be accessed from the App Cockpit screen.

App results

The Release Assurance app generates a Dashboard report which includes the following charts:

  • The Source Transports panel lists the number of custom transports that were analyzed, and includes a migration path in the form ‘From <QA system> to <Production system>’.
  • The Source Objects panel lists the number of distinct source objects found in the input transports on the QA system.
  • The Total Dependent Objects panel lists the total number of parent and child dependent objects found for the source objects on the QA system.
  • The Dependency Alerts panel lists the number of distinct parent and child dependent objects that are either different on the QA and Production systems, or missing from the Production system.
  • The Dependency Summary pie chart summarizes the dependent objects by their comparison status on the QA and Production systems.
  • The Alerts by Type column chart summarizes the changed or missing objects by their object type.
  • The Dependency Transports by Owner column chart summarizes the dependent transport objects by owner.
  • The Dependency Transports by Request Type column chart summarizes the dependent transport objects by request type.

The Dashboard report also includes links to the following reports:

Release Assurance Details

This Excel report includes the following spreadsheets:

Dashboard

This spreadsheet includes the panels and charts described above.

Help

This spreadsheet provides help for each of the spreadsheet reports.

Source Objects

This spreadsheet lists objects from the input transports on the QA system with dependent objects that have changed or are missing on the Production System. The Alerts column displays the number of missing or changed dependent objects. Click a link in this column to display the dependent objects in the Alerts spreadsheet.

Alerts

This spreadsheet lists dependent objects from the QA system with a comparison status other than ‘Same’ on the Production system. The relation column stores the dependency relation.

  • ‘Parent’ indicates that the source object is used by the dependent object.
  • ‘Child’ indicates that the source object uses the dependent object.

Click a link in the Dependent_Name column to display Tier 2 comparison details for the dependent object on the QA and Production systems.

The Transports column lists the number of transports on the QA system that include the dependent object. Click a link in this column to display the transports in the Alert Transport Info spreadsheet.

Alert Transport Info

This spreadsheet lists the comparison status for each dependent object on the QA and Production systems, excluding objects that are the same on each system. It also includes details for the transports that include each dependent object on the QA system. The spreadsheet has the following columns:

Column Description
Dependent_Type The type of a dependent object.
Dependent_Name The name of the dependent object.
Dependent_Status The comparison status of the dependent object on the QA and Production systems.
E070_Type The type of the dependent object, obtained from the QA system’s E070 table.
E070_Name The type of the dependent object, obtained from the QA system’s E070 table.
Request The name of a request that includes the dependent object on the QA system.
Task The task associated with the request.
Request_Text The descriptive text associated with the request.
Request_Type The type of the request.
TRSTATUS The status of the transport that includes the dependent object on the QA system.
AS4USER The user who last modified the transport.
AS4DATE The date when the found transport was last modified.
AS4TIME The time when the found transport was last modified.
TRKORR_QAS The request or task name containing the dependent object, obtained from the TPALOG table on the QA system.
TRDATE_QAS The date when the request or task was last modified, obtained from the TPALOG table on the QA system.
TRTIME_QAS The time when the request or task was last modified, obtained from the TPALOG table on the QA system.
TRKORR_PRD The request or task name containing the dependent object, obtained from the TPALOG table on the Production system.
ADMIN_PRD The user who last changed the request or task on the Production system.
TRDATE_PRD The date when the request or task was last modified, obtained from the TPALOG table on the Production system.
TRTIME_PRD The time when the request or task was last modified, obtained from the TPALOG table on the Production system.

The following are removed from the app’s results:

  • Methods (METH) that are components of a source Class (CLAS).
  • Functions (FUNC) that are components of a source Function Group (FUGR).
  • Screens (DYNP) that are components of a source Program (PROG).

Analysis Input Data

This Excel report contains a copy of the input parameters used to produce the app’s Dashboard report. The value of each input parameter is stored in a separate worksheet, which is named after the parameter whose value it contains.

Standard apps