1. Development Workbench - Notifications
  2. Create Notifications

7 Create Notifications

This topic provides systematic instructions to generate new or modify the existing Notification.

  1. Log in to the Development Workbench.
    Development Workbench For Universal Banking screen displays.

    Figure 7-1 Development Workbench For Universal Banking


    Description of Figure 7-1 follows
    Description of "Figure 7-1 Development Workbench For Universal Banking"

  2. Click on the Notifications option under the Browser menu.
    Notification Maintenance screen displays.

    Figure 7-2 Notification Maintenance


    Description of Figure 7-2 follows
    Description of "Figure 7-2 Notification Maintenance"

    Notification Maintenance screen is used to create a new notification or modify an existing notification, here notification information gets captured for notification codes and the user needs to save notification details into XML.
  3. To create a new Notification, follow the steps given below:
    1. Specify the details in the Notification Maintenance screen and save it.

      Table 7-1 Notification Maintenance- Field Description

      Field Description
      Action Select either New or Load action. The New option is to create a new notification and the Load option is used to modify the existing one.
      Save XML Path Specify the path to save notification XML. This would be considered only if the Save Mode is Client and Work Directory specified as $CURRENT_DIRECTORY.
      Notification Function Specify the notification function-id name.

      Note:

      Naming Conventions- Notification Function must have maximum 8 characters and the 3rd letter must be N.
      For Example: FTNCONON
      Notification Code Enter the notification code to which we need to capture values. This is a mandatory field.

      Note:

      Recommended Convention for Notification Codes- NOTIF_<Module Code>_<Description>
      For Example: NOTIF_LD_CONTRACT, This is the notification indicating that an LD contract has been created/modified.
      Description Information field. A meaningful description of the Notification has to be provided in the field.
      Module This attribute signifies the module on which the notification is based.
      Module Description Information field. Module Description that would be defaulted from Module LOV.
      Notification XSD Notification XSD name will have to be provided in the corresponding Field.

      Note:

      The naming convention to be followed while naming Notification XSD is as follows- [Module Name] – [Notification Description] – Notif.xsd
      For Example: FT-Contract-Notif.xsd, Notification XSD has to be provided only if no Gateway Web Service Query Operation is configured to the Notification.
      Base Table Select the base table on which trigger needs to be applied.
      Firing Time Indicates the Operation on the base Table for which Notifications have to be sent. Options available are Insert, Update, or both.
      Filter Type This attribute can take the following values.
      1. Where Clause
      2. Plsql Block
      Pk Cols Enter Primary key columns of the Base Table.
      Pk Types Enter Primary key field Data Types. Provide details of Gateway Service, Operation, Type XSD Name, and Full-Screen Reply if a Query Web Service has to be mapped to the Notification.
      Gateway Operation The gateway operation name to execute the query for the mentioned Service.
      Gateway Service The gateway service is to be used to get the full-screen response.
      Gateway IO Request The gateway IO request node to be used in querying operations.
      Type XSD Name This field has to be entered if Notification is mapped to a Service and Request. The name of the Master Type XSD for the service and operation has to be provided here. This can be found in the included portion of the Request Msg XSD of particular Service-Operation. For Example: LC-Contract-Types.xsd
      Full screen Reply This attribute decides whether a full screen or primary key notification response is to be sent. This is applicable only if gateway Service details are provided.
      HO only This attribute is used to send notifications only from the head office.
      Filter Logic The filter logic decides whether the notification needs to be sent or not. This can be a simple where-clause on the base table or a complex pl/sql block.
      Web service Tags The columns selected from the base table as part of web service tags will be used to send the full-screen notification response. These tags define the elements of Notification XML when no Query service is mapped to it.
      Generate Rad Files screen displays.

      Figure 7-3 Generate Rad Files


      Description of Figure 7-3 follows
      Description of "Figure 7-3 Generate Rad Files"

    2. Click on the Generate button.
      An Information window displays confirming the successful generation of Notification.

      Figure 7-4 Information


      Description of Figure 7-4 follows
      Description of "Figure 7-4 Information"

  4. To modify the existing Notification RADXML, follow the steps given below:
    1. In Notification Maintenance screen, select the Action field as Load.
    2. Click on the BROWSE button at Load Screen XML field.
      Choose File to Upload folder window displays.

      Figure 7-5 Choose File to Upload


      Description of Figure 7-5 follows
      Description of "Figure 7-5 Choose File to Upload"

    3. Select the RADXML file to be modified and click on the Open button.
      Notification Maintenance screen displays with selected RADXML file details.

      Figure 7-6 Notification Maintenance


      Description of Figure 7-6 follows
      Description of "Figure 7-6 Notification Maintenance"

    4. Modify the details as required and click on the Save icon.
      Selected RADXML file gets modified.