41.5 FAQ

1. What is a significance of Mandatory and Subscribe types of alerts?

   Recipients will get an alert by default for the alert types defined as Mandatory and will have to subscribe for those alerts for which the alert type is defined as ‘Subscribe’.

2. What is a reason for applying attribute masking?

   The main reason for applying masking to a data field is to protect data that is classified as personal identifiable data, personal sensitive data or commercially sensitive data as a communication between the customer and Bank.

3. Can I define the masking for data attribute available in subject?

   No, data attribute masking can be defined only for the data available in the message body.

4. Can I add an attribute masks for more the one data attribute for a specific recipient and channel?

   Yes, you can add multiple attribute masks for different data attributes for a specific recipient and channel.

5. Can I delete specific recipient added for an alert event in Alert Maintenance?

   Yes, administrator can delete specific recipient mapped to an event.

6. What happens to the in-transit transactions if I edit the alert maintenance for specific recipient?

   An updated maintenance will be applicable for any new event performed after maintenance is saved successfully.

7. Can the administrator define any of the existing alerts as an actionable alert by defining the Action ID and Action Text?

   No, actionable alerts cannot be configured by the Administrator, these alerts are factory shipped or can be defined at the time of implementation. Administrator can only define the Action Text for and can enable/disable the actionable alert.