The actionable alert framework allows you to define an action inside a message template.

By using this action (which can be in form of a hyperlink or button), the OBDX user can navigate to the desired screen directly from alert. The alert could be from any destination type like EMAIL, SMS, On-Screen Alert or push notification.

Following are the important tables regarding configuration of actionable alert. Both the tables are multi-entity specific tables.

1. DIGX_EP_MSG_ACN_B

   This table contains the primary information about the action needs to be taken on the alert.

   Table 3-1 DIGX_EP_MSG_ACN_B

   NAME	DESCRIPTION
   COD_ACT_ID	Activity id of the template
   COD_MESS_TMPL_ID	Unique identifier of the template
   COD_MESS_ACN_ID	Unique action identifier for the respective template
   MESS_ACN_DESC	Description of the action. This description will be visible to the admin user in alert maintenance screen in read-only mode
   MODULE_ID	The module in which the UI component lies
   COMPONENT_ID	UI Component identifier
   DISPLAY_TXT	The text will appear on the hyperlink or button in the message body of alert. Admin users can modify this text from the alert maintenance screen.
   MSG_ACN_HLDR	ANCHOR
   FLG_ENABLED	Y/N (Specifies whether the action is currently enabled or disabled. Admin user can enable/ disable an action from alert maintenance screen)
   FLG_LOGIN_REQD	Y/N (specifies whether user login is required to redirect to the desired screen in OBDX application)

2. DIGX_EP_MSG_ACN_PRM_B

   This table is used if any parameters need to be passed along with the action. These parameters can be used in the destination screen for further processing.

   Table 3-2 DIGX_EP_MSG_ACN_PRM_B

   NAME	DESCRIPTION
   COD_ACT_ID	Activity id of the template
   COD_MESS_TMPL_ID	Unique identifier of the template
   COD_MESS_ACN_ID	Action identifier of the respective template for which parameters are required
   COD_MESS_ACN_PRM_ID	Unique identifier of the parameter. This value will be available as key in the params element of the redirected page
   MESS_ACN_PRM_VAL	The data attribute id of the template whose dynamic value should be passed in the URL along with the key mentioned in COD_MESS_ACN_PRM_ID

Steps to include action in an alert:

1. Identify the template id for which actionable alert needs to be configured (refer entry in DIGX_EP_MSG_TMPL_B'.
2. Identify the UI component of OBDX application to which the link should be redirected. This information is needed to insert entry in ‘MODULE_ID’ and ‘COMPONENT_ID’ columns of DIGX_EP_MSG_ACN_B table.
3. Insert an entry in DIGX_EP_MSG_ACN_B for the action.
4. e.g.

   Insert into DIGX_EP_MSG_ACN_B (COD_ACT_ID,COD_MESS_TMPL_ID,COD_MESS_ACN_ID,
   DETERMINANT_VALUE,MESS_ACN_DESC,MODULE_ID,COMPONENT_ID,DISPLAY_TXT,MSG_ACN_HLDR,
   FLG_ENABLED,OBJECT_VERSION_NUMBER,CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATED_DATE,
   DOMAIN_OBJECT_EXTN,FLG_LOGIN_REQD) values ('com.ofss.digx.app.approval.service.transaction.
   Transaction.checkApprovals.financial','Financial_Transaction_Pending_Approval_EMAIL',
   'act1','*','Description','approvals','transaction-detail','click here','ANCHOR','Y',1,null,
   sysdate,null,sysdate,'CZ','Y');

5. If any parameters need to be passed in the URL, make an entry in DIGX_EP_MSG_ACN_PRM_B.
6. e.g.

   Insert into DIGX_EP_MSG_ACN_PRM_B (COD_ACT_ID,COD_MESS_TMPL_ID,COD_MESS_ACN_ID,
   COD_MESS_ACN_PRM_ID,DETERMINANT_VALUE,MESS_ACN_PRM_VAL,OBJECT_VERSION_NUMBER,CREATED_BY,
   CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATED_DATE,DOMAIN_OBJECT_EXTN) 
   values ('com.ofss.digx.app.approval.service.transaction.Transaction.checkApprovals.financial',
   'Financial_Transaction_Pending_Approval_EMAIL','act1','transactionId','*','TxnReferenceNo',
   1,null,sysdate,null,sysdate,'CZ');

7. After the entries are seeded, the actions will be available in Alert maintenance transaction for the respective template. Using the Alert Maintenance transaction the message body can be updated to place action at the desired location.
8. The action id should be inserted as #<action_Id># in the message body. (In the same way, as data attributes are inserted currently).
9. After the maintenance is done, the alert will contain the action in the form of hyperlink in the message body. Taking the action on the alert will redirect the user to the desired page. If login is required for the corresponding action, the user will be prompted for the login screen. If the user is already logged in or if the action does not require login, user will be directly navigated to the desired page.