1. Custom RAD Extensibility Transaction Screens
  2. Approach

2 Approach

For demo purpose, we will be taking a transaction screen: PWDOTONL (Fedwire outgoing Transaction screen). We will create a demo table, add it to the RAD with 3 fields and then Save/query the record.

  1. Select Options –> User Preferences.

    Figure 2-1 User Preferences


    Description of Figure 2-1 follows
    Description of "Figure 2-1 User Preferences "

  2. Select the Custom release.
  3. Select the environment.
  4. And then click ok.
  5. Select the function generation.

    Figure 2-5 Function Generation


    Description of Figure 2-5 follows
    Description of "Figure 2-5 Function Generation "

  6. Select the RAD file to be uploaded (Using PWDOTONL for Demo purpose).
  7. Creating a new table for Demo purpose- CUSTOM_TEST:
  8. Added a new data source in the data source list and added fields for it. New table name CUSTOM_TEST.

    Figure 2-8 New Data Source


    Description of Figure 2-8 follows
    Description of "Figure 2-8 New Data Source"

    Note:

    • Here Num1 is used only for mapping with parent table. It must be part of Data Block and a fieldset (although it could be made invisible, but it has to be present in one of the fieldsets).
    • Relationship given: PWTBS_BRANCH_OUT_TXN.TXN_REF_NO=CUSTOM_TEST.NUM1
  9. Added new Data Block- CUSTOM_TEST and then added three fields to it- Field1, Field2 and Num1 (PK field, and to be used for entity/table mapping). Make sure the PK is mentioned in Block PK fields.
    Field1 and Field2 are visible, Num1 is made invisible.

    Figure 2-9 Data Block- CUSTOM_TEST


    Description of Figure 2-9 follows
    Description of "Figure 2-9 Data Block- CUSTOM_TEST"

  10. Created a new Field set FST_CUSTOM and added all the three fields to it. Added it in the Header section.
  11. Generated files:
    1. Using the RAD utility (local sources)

      Figure 2-11 RAD utility (local sources)


      Description of Figure 2-11 follows
      Description of "Figure 2-11 RAD utility (local sources) "

    2. Using RADTOOL:
      Check Java functions in preferences

      Figure 2-12 Java Functions


      Description of Figure 2-12 follows
      Description of "Figure 2-12 Java Functions"

      While generating, check Java Classes.

      Figure 2-13 Java Classes


      Description of Figure 2-13 follows
      Description of "Figure 2-13 Java Classes"

  12. Generated folders

    Figure 2-14 Generated folders


    Description of Figure 2-14 follows
    Description of "Figure 2-14 Generated folders"

    Note:

    • The generated artifacts need to be added to the project.
    • Common Files and Entity files will replace existing kernel files. Others will be of different names, e.g., BrnFwOutTxnCustomSys.java (instead of BrnFwOutTxnSys.java as in case of Kernel files).
    • These files extend kernel files, and hence all kernel functionality would be retained and additional code can be added in these Custom files as need be.
    • Please note that any additional business logic/validations can be added in <MasterBlockName>Custom.java file (for example, in this case, BrnFwOutTxnCustom.java).
  13. After deploying the java files, UIXML and JS the screen (Blue Circled are the Custom fields).
  14. Creating a new record:
  15. Record saved
  16. While querying the record

    Figure 2-18 Querying record


    Description of Figure 2-18 follows
    Description of "Figure 2-18 Querying record "

  17. Backend table Entry