1. Alert Configuration Developer Guide
  2. Database Configurations

2 Database Configurations

All the configurations are explained with respect to Wallets request fund activity.

  1. The Activity entry is added in the DIGX_EP_ACT_B table.
    Description of alertconfig1.png follows
    Description of the illustration alertconfig1.png

    COLUMN NAME DESCRIPTION
    COD_ACT_ID Primary key of the table. An identifier for the activity raising the event. It is the combination of the fully qualified name for the class and the method name.
    TXT_ACT_NAME Name of the activity. As a convention it is ‘.’ separated combination of class name and method name.
    TXT_ACT_DESC Description of the activity.
    MODULE_TYPE Module type of the activity. It maps to the ModuleType enumeration.

    SVN Location for Seed Data Script : http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/alerts/DIGX_EP_ACT_B.sql

  2. The event is added in the table DIGX_PM_EVENT_ALL_B table.
    Description of alertconfig2.png follows
    Description of the illustration alertconfig2.png

    COLUMN NAME DESCRIPTION
    EVENT_CODE Primary key of the table. An identifier for the event occurred. It should start from the module type followed by the logical name for the event.
    EVENT_DESC Description of the event.
    ALERTS_FLAG Identifies whether the alert is required for this event or not. Possible values : ‘Y’ or ‘N’.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/alerts/DIGX_PM_EVENT_ALL_B.sql
  3. The activity Event combination is added in DIGX_EP_ACT_EVT_B table. Separate entries are required for all the events of the activity i.e. Suppose activity 'com.ofss.digx.app.wallet.service.core.Wallet.requestFunds' has two events one for success and other for failure, 2 entries will go in the table for both of them.
    Description of alertconfig3.png follows
    Description of the illustration alertconfig3.png


    Description of alertconfig4.png follows
    Description of the illustration alertconfig4.png

    COLUMN NAME DESCRIPTION
    COD_ACT_ID Activity Id. It must match to the COD_ACT_ID column of DIGX_EP_ACT_B table.
    COD_EVENT_ID Event Id. It must match to the EVENT_CODE column of DIGX_PM_EVENT_ALL_B table.
    TXT_ACT_EVT_DESC Description of the activity event combination.
    TXT_EVT_TYP Event type. It maps to EventType enumeration.
    TXT_ACT_EVT_TYP Activity Event type. It maps to ActivityEventType enumeration. Possible values : ‘BULK’ or ‘ONLINE’.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/alerts/DIGX_EP_ACT_EVT_B.sql
  4. Message templates are added based on the destination types to the table DIGX_EP_MSG_TMPL_B table.
    Description of alertconfig5.png follows
    Description of the illustration alertconfig5.png

    COLUMN NAME DESCRIPTION
    COD_TMPL_ID Primary key of the table. Uniquely identifies a message template. It should start from the module type followed by the logical name for the template.
    DESTINATION_TYPE Destination type of the template. It maps to DestinationType enumeration.
    MSG_TMPL_NAME Logical name of the message template.
    MSG_TMPL_DESC Description of the message template.
    TXT_MSG_TMPL It contains the format for the message body. It is stored as CLOB in the table.
    TXT_SUBJECT_TMPL It contains the subject for the message. It is also stored as CLOB in the table.
    DETERMINANT_VALUE It determines the entity code for the template.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/alerts/DIGX_EP_MSG_TMPL_B.sql

    As you can see in the above example, the data elements like wallet id, amount and sender name are defined in between ‘#’.The entry for those data elements(or attributes) is done in the following tables.

  5. Message attributes are added in the table DIGX_EP_MSG_ATTR_B table.
    Description of alertconfig6.png follows
    Description of the illustration alertconfig6.png

    COLUMN NAME DESCRIPTION
    COD_MESS_TMPL_ID Message template Id. It must match to the COD_TMPL_ID column of DIGX_EP_MSG_TMPL_B table.
    COD_ATTR_ID Name of the attribute. It must match to the one defined inside TXT_MSG_TMPL of DIGX_EP_MSG_TMPL_B table.
    ATTR_MASK Masking format for the attribute value. Characters given as ‘X’ will be masked and the ones given as ‘D’ will be displayed as it is.
    DETERMINANT_VALUE It determines the entity code for the template.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/metadata/DIGX_MD_SERVICE_ATTR.sql
  6. Service attributes are added in DIGX_MD_SERVICE_ATTR table.
    Description of alertconfig7.png follows
    Description of the illustration alertconfig7.png

    Description of alertconfig8.png follows
    Description of the illustration alertconfig8.png
    COLUMN NAME DESCRIPTION
    COD_SERVICE_ATTR_ID Primary key of the table. As a convention, ‘.’ separated combination of COD_SERVICE_ID, COD_ATTR_ID and TYP_DATA_SRC.
    TYP_DATA_AVAIL Possible values : ‘DIRECT’ or ‘INDIRECT’. ‘DIRECT’ only when ‘TYP_DATA_SRC’ is ‘INPUT’ and the attribute value is one of the arguments passed to the activity. Otherwise ‘INDIRECT’.
    TYP_DATA_SRC Possible values : ‘INPUT’ or ‘DTO’. ‘INPUT’ whentheattribute value can be obtained from the arguments passed to the activity. ‘DTO’ when the attribute value cannot be obtained from the arguments and is genertated/fetched within the activity.
    COD_ATTR_ID Name of the attribute.
    COD_SERVICE_ID Activity Id. It must match to COD_ACT_ID column of DIGX_EP_ACT_B table.
    PARAMETER_NAME The name of the argument passed to the activity. Its value will be null when TYP_DATA_SRC is ‘DTO’.
    REF_FIELD_DEFN_ID Fully qualified path from which the attribute value can be obtained.

    Here , in case of TYP_DATA_SRC as ‘INPUT’, there can be 2 cases :

    • The attribute value is passed directly to the activity i.e. the attribute value is one of the arguments passed to the activity. In this case, TYP_DATA_AVAIL will be ‘DIRECT’.
    • The attribute value is not passed directly to the activity , but it can be obtained from one of the arguments passed to the activity i.e. it is part of one of the DTOs which is passed to the activity. In this case, TYP_DATA_AVAIL will be ‘INDIRECT’.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/metadata/DIGX_MD_SERVICE_ATTR.sql
  7. Source of the message attributes are added in DIGX_EP_MSG_SRC_B table.
    Description of alertconfig9.png follows
    Description of the illustration alertconfig9.png
    COLUMN NAME DESCRIPTION
    COD_MESS_TMPL_ID Message template Id. It must match to the COD_TMPL_ID column of DIGX_EP_MSG_TMPL_B table.
    COD_ATTR_ID Name of the attribute. It must match to the one defined inside TXT_MSG_TMPL of DIGX_EP_MSG_TMPL_B table.
    COD_ACT_ID Activity Id. It must match to COD_ACT_ID column of DIGX_EP_ACT_B table.
    COD_SERVICE_ATTR_ID Service attribute id. It must match to COD_SERVICE_ATTR_ID of DIGX_MD_SERVICE_ATTR table.
    DETERMINANT_VALUE It determines the entity code for the template.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/alerts/DIGX_EP_MSG_SRC_B.sql
  8. The attributes which are input to the activity are added in DIGX_MD_SERVICE_INPUTS table.
    Description of alertconfig10.png follows
    Description of the illustration alertconfig10.png
    COLUMN NAME DESCRIPTION
    COD_SERVICE_ID Activity Id. It must match to COD_ACT_ID column of DIGX_EP_ACT_B table.
    PARAMETER_NAME The name of the argument passed to the activity.
    PARAMETER_INDEX Unique index of the argument for an activity. It starts from 0 for a particular activity.
    DATA_TYPE Data type of the argument passed to the activity.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/alerts/DIGX_EP_MSG_SRC_B.sql
  9. The generic attributes along with their datatypes are added in DIGX_MD_GEN_ATTR_LEGACY_B table.
    Description of alertconfig11.png follows
    Description of the illustration alertconfig11.png

    Description of alertconfig12.png follows
    Description of the illustration alertconfig12.png

    Table 2-1 Table9

    COLUMN NAME DESCRIPTION
    COD_CONSTRAINT_ATTR_ID Attribute Id.
    TXT_CONSTRAINT_ATTR_NAME Name or description of the attribute.
    DATA_TYPE Data type of the attribute to format the attribute value.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/metadata/DIGX_MD_GEN_ATTR_LEGACY_B.sql
  10. Entry for alert is added in DIGX_EP_ACT_EVT_ACN_B table.
    Description of alertconfig13.png follows
    Description of the illustration alertconfig13.png
    COLUMN NAME DESCRIPTION
    COD_ACT_ID Activity Id.
    COD_EVENT_ID Event Id.
    COD_ACTION_ID Action Id. Possible value : ‘A’ (means Alert)
    FLG_TRANSACTIONAL Possible values : ‘Y’ or ‘N’. This flag indicates whether events under this event category are transactional events or not.A Transactional event is an event which get processed within the same session of manager API.
    COD_DEC_ID Possible Value : 0
    FLG_CONDITIONAL Possible value : ‘N’.
    COD_ACN_TMPL_ID Possible values : 1 or 2 . 1 indicates the importance of alert is critical. 2 indicates the importance of alert is informational.
    ALERT_NAME Unique name for the alert.
    EXPIRY_DATE Expiry Date of the alert.
    ALERT_TYPE Alert Type. Possible values: ‘M’ or ‘S’. ‘M’ indicates the alert is of mandatory type and cannot be subscribed/unsubscribed by the user. ‘S’ indicates the alert is of subscribed type which can be subscribed/unsubscribed by the user.
    ALERT_DISPATCH_TYPE Alert Dispatch Type. Possible values: ‘I’ or ‘D’. ‘I’ indicates immediate i.e. the alert needs to be send immediately. ‘D’ indicates deffered i.e. the alert will be sent later.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/alerts/DIGX_EP_ACT_EVT_ACN_B.sql
  11. Entry for recipient message templates is added in DIGX_EP_EVT_REC_B table. Separate entries are required for all the destination types of the alert i.e. Suppose activity 'com.ofss.digx.app.wallet.service.core.Wallet.requestFunds' has two destination types, EMAIL and SMS, 2 entries will go in this table.
    Description of alertconfig14.png follows
    Description of the illustration alertconfig14.png

    Description of alertconfig15.png follows
    Description of the illustration alertconfig15.png
    COLUMN NAME DESCRIPTION
    COD_ACT_ID Activity Id.
    COD_EVENT_ID Event Id.
    COD_ACTION_ID Action Id. Possible value : ‘A’ (means Alert)
    COD_MSG_TMPL_ID Message Template Id. Foreign key to COD_TMPL_ID of DIGX_EP_MSG_TMPL_B.
    TXT_DEST_TYP Destination Type. Possible value : ‘EMAIL’ , ‘SMS’, ‘SECURE_MAIL_BOX’ , ‘PUSH_NOTIFICATION’
    SUBSCRIBER_TYPE Possible value : ‘PARTY’.
    SUBSCRIBER_VALUE Possible value : ‘CUSTOMER’.
    ALERT_TYPE Alert Type. Possible values: ‘M’ or ‘S’. ‘M’ indicates the alert is of mandatory type and cannot be subscribed/unsubscribed by the user. ‘S’ indicates the alert is of subscribed type which can be subscribed/unsubscribed by the user.
    LOCALE Locale to pick the location/language specific template for.

    SVN Location for Seed Data Script :

    http://obcpsvn.oraclecorp.com:8080/svn/clip/trunk/core/seed/oracle/alerts/DIGX_EP_EVT_REC_B.sql

    Note:

    Entries for most of the activities, events, corresponding activity events , message templates, message attributes are already added. Please check for the entries in the table to avoid repetition.