4.1 Release Detailed

The topic explains about the release master screen.

Only a user with Administrator rights can create Release. It is recommended to use RADTOOL users for creating new releases.

Table 4-1 Release Master - Field Description

Field	Description
Release Code	Release code/Project Code is a mandatory field. It should follow the FLEXCUBE naming convention. For Example: FC_UBS_V.UM_11.4.US.1.0.0.0
Description	A meaningful description of release can be provided here.
Release Type	Select the release type. This is a mandatory field. Kernel: This option should be used by the kernel team only. Cluster: A regional development team has to select this option. Custom: Either offshore development team for client changes or development in Onsite has to select this option.
Release Number	Enter the version number of the FLEXCUBE development.
Base Release	Select base release from the list of values. All available releases will be shown in the List of values. The base release is of significance for migrating test case data Example: If the developer is working on customization on top of the 11.3EU Cluster pack, the base release will be 11.3EU.
Environment	Select default environment.
Remarks	Enter if any additional info is required regarding Release. This is the information field.
Release SPC	This would be used for in-house developments. This is not required for custom developments.
Stream Name	The stream name should be the same as the DDL stream name. This is not applicable if DDL integration is not required.
Cluster Name	This is an information field. If the release is a Cluster pack, the name of the Cluster release can be provided here, the same name as maintained in DDL Tool.
Custom Name	This is an information field. If the release is a Customization, the name of the customer can be provided here, the same name as maintained in DDL Tool.
Release Stage	This is the information field. The release stage can be Development, SQA, ITR etc.
Application Name	Provide the name of the application for which the release is created. Example: FLEXCUBE, FCIS, FGL, etc.
Migrate Test Case Data from Base Release	If the check box is checked,all the test case data from the base release will be migrated to the new release.

The below figure shows sample entries for creating custom release done for MODEL BANK.

Figure 4-2 Release Master

Description of "Figure 4-2 Release Master"

Querying a Release

If user want to modify existing release Details click on Release Detailed node in tree and click enter query option.

Figure 4-3 Querying a Release

Description of "Figure 4-3 Querying a Release"

Release code field gets enabled. If release name known already enter directly or select release code from provided List of values.

Figure 4-4 Selecting Release from LOVs

Description of "Figure 4-4 Selecting Release from LOVs"

After selecting release code click on execute query.

Figure 4-5 ExecuteQuery

Description of "Figure 4-5 ExecuteQuery"

Modifying a Release

Click on unlock button.

Figure 4-6 Modifying a Release

Description of "Figure 4-6 Modifying a Release"

After unlock button clicked except release code all fields will be enabled. Release administrator can update the required fields. Click on save.

Figure 4-7 Release after unlock

Description of "Figure 4-7 Release after unlock"