Actions Flashcards
What are actions?
Actions are used to send notifications to bank customers via in-app notifications, email, SMS messages, or other channels when a business event occurs. For example, if account balance goes below $100, send an email to the account holder.
How are business scenarios for action notifications defined?
Business scenarios for notifications are defined in action recipe specifications. You can define your own or use out-of-the-box specifications that come pre-integrated with other DBS capabilities.
Account low balance New message received New unassigned conversation New message in assigned conversation Payment status updated Contact status updated Savings goal completed Limits consumed Account statement ready
What are some examples of the reasons for a notification?
A new transaction has occurred
An account has low balance
A new message is received
A payment status is updated
A contact status is updated
A savings goal is completed
Limits are consumed
Account statement ready
What are the frequencies in which action notifications are delivered?
Real-time notifications
Actions sends a notification via the specified channel every time when the corresponding business event occurs. For example, a bank customer receives a text message whenever a new transaction is made on their current account. Real-time notifications are the default option.
Digest notifications
Actions accumulates all occurrences of business events over the previous period and delivers a single digest notification at the scheduled time. For example, at 9 AM every Monday a bank customer receives an email with all transactions made on their current account over the previous week.
What are the components that make up an action?
Action recipe specification - A blueprint created by a developer that defines the business event that an action handles. It also defines the available notification channels and notifications templates used to notify users when these business events occur..
Action recipe - a particular instance of the blueprint implementation created by the bank customer or created by Actions using the default values from the specification.
What makes up an action recipe specification?
Action type
This defines whether the specification is for a User or a System action.
User actions - created by customers of the bank. For example: notify me when I receive a transaction with an amount higher than 1,000.
System actions - defined in the backend system. Customers cannot disable, enable, change, or remove these. For example: send an email to the Compliance Department for each transaction with an amount higher than 20,000.
Event
This defines what backend system event triggers the action. DBS capabilities already emit some events based on business logic. However, you can emit events from any custom service. You can also use HTTP or JMS to emit events from third-party applications or core banking systems.
Action
The following components are defined for every action:
Adapter
The adapter is the channel through which the action is delivered. The following adapters are supplied out of the box:
DBS Notifications
SMS - pluggable with your provider of choice
Email - pluggable with your provider of choice
Notification template
The action recipe specification must define at least one notification template for every delivery channel. This is known as the fallback notification template. In most of the cases, actions use custom templates rather than the fallback template.
Digest availability
This defines whether customers can set up digest notifications instead of real-time ones.
Recipe defaults
The default values that are used to create a recipe when a customer does not provide custom values.
What makes up an action recipe?
The action recipe implements the action recipe specification. It defines the following:
The triggered actions: which of the actions defined in the specifications are triggered by this action recipe.
Additional optional data, such as:
The arrangement ID that the action recipe applies to.
The amount that triggers the action.
