2 Overview of Customer Landing Page Development

This topic describes the process of customer landing page development for Oracle FLEXCUBE Universal Banking.

Oracle FLEXCUBE Universal Banking Open Development Tool provides the developer with a user-friendly console for designing and developing screens for Oracle FLEXCUBE Universal Banking.

Open Development Tool assists developers in designing screens with the capability of generating front-end scripting files, PL/SQL packages, Static data scripts, XSDs, Excel templates, and HTML files. This generated code performs validations and does some processing which is common across screens in Oracle FLEXCUBE Universal Banking, only the Business Logic specific to the screen has to be added by the developer in the back end and front end units.

For example,
  • Release Name - FC 12.1
  • Release Type - KERNEL, CLUSTER, CUSTOM

Open Development Tool generates all files, and developers are supposed to add the business logic in designated units depending on the Release Type.

RADXML

Open Development Tool saves all the activities carried out by the developer in an XML file hereby referred to as RADXML. The persistence of the screens is achieved through RADXML. All the units required to work a screen can be generated from its RADXML.

If some changes are required on the screen in a future release, the same RADXML can be loaded and changes can be done on this RADXML. Open Development Tool can segregate the changes done on different releases and save the RADXML accordingly.

Naming convention of the RADXML: Function ID Name + _RAD.xml

For example, STDCULND_RAD

Extensible Development

In an extensible framework, any development on Oracle FLEXCUBE Universal Banking is classified on any of the following stages (also referred to as release type):

Table 2-1 Development Stages

Development Stages Description
KERNEL This refers to the core product. For example, FC 12.1
CLUSTER This refers to any region-specific enhancements/developments done on top of the kernel product. The changes done in a cluster pack will be non-invasive to the kernel product. For example, FC 12.1 India cluster
CUSTOM Any enhancements required by the customer/bank are done on this level. It will be non-invasive of the changes done in kernel and cluster packs. For example, Customizations for the MODEL bank on FC 12.1 India cluster
Open Development Tool can segregate the changes done on different releases and save the RADXML accordingly. It generates the files depending on the release type and developers can add the business logic to the release type-specific files. Thus the code remains non-invasive of the existing code.

Design Steps

The sequence of steps to be followed while developing a screen in the Open Development Tool:
  1. Identifying the Data Sources and their Relations
  2. Logically Grouping the Data Sources into Data Blocks
  3. Designing Screen Layout
  4. Logically Grouping the Block Fields into Fieldsets
  5. Attaching Call Forms and Launch Forms if any
  6. Defining LOVs
  7. Designing Summary
  8. Defining Actions
Refer to respective sections for a detailed explanation of each step.

While development, save RADXML at constant intervals. Click Save in the top right to save the work. RADXML would be saved in the user directory maintained.