4 Source Refresh

This topic provides information on Source Refresh.

Source Refresh allows the customer to upgrade its existing release with the latest release of FLEXCUBE without affecting its custom changes. By using the Source Refresh option all the extensible RADXML‘s of older versions can be updated with the latest version changes.
  1. Source Refresh is possible only for the extensible screens. Hence for non-extensible screens customization on the screens can’t be retained in case of an upgrade.
  2. Source Refresh is done for RADXMLs in different releases.
  3. All system units need to be regenerated after source refresh. A thorough unit testing is recommended after the deployment of all generated units.
  4. Child Refresh and Screen Child Refresh will be done implicitly during Source Refresh if any child/screen child screens are present. Hence if source refresh of any child/screen child has to be done, include parent RADXMLs also in the source and base file lists.
  5. Select proper release types for source and base while upgrading in Refresh Page.

It is meaningless to do Source Refresh between two Kernel versions (or two cluster versions etc) as we can replace the entire source with the latest version in such a scenario. Hence Source and Base Release types can never be the same for Source Refresh.

Source release type can not be Kernel, it can be either Cluster or Custom. Base Release type options will depend on the source release type selected.

Table 4-1 Release Type for Source and Base

Release Type Option 1 Option 2
Source Release Type Cluster Custom
Base Release Type Kernel Kernel, Cluster
  • If the user selects Custom as source release type, the user has the option to upgrade release based on either cluster pack or Kernel.
  • If the user selects Cluster as source release type, the user has only one option as base release type i.e. Kernel.