Are you looking for a more
efficient way to monitor the pulse of your business? The PrimeObjects business
alert, an impressive module designed to keep you and your personnel “in
the know.” The business alert feature from PrimeObjects allows monitor
all your critical business data 24x7 and notify you right in time by emails.
The alerts also help monitor, control and improve the business processes and
information quality. The alert engine gives users full control to define the
business alerts against all business entities based on any tailored business
rules with the highest flexibility. The out-of-the-box alert functions work
perfectly with activity management features including Calendar Management, Task
Management, Event Management and Appointment Management, so you can easily
manage all your business activities by leveraging the powerful business alert
features.
What you can do by using PrimaryObjects Business Alert
- Monitor date and time sensitive
events
Use Cases:
- Task over due
- Payment over due
- Event reminder
- Monitor business sensitive
events.
Use Cases:
- Alert to service manager - if
the service/support cost related to a product is higher than 20% of total
service/support cost, the improvement of the product quality or better
documentation may need to be considered.
- Alert to sales manager - if a
client's age gets into 18, the sales manager can start selling some new
products to him/her.
- Alert to mutual fund account
manager - if the foreign asset of the client's portfolio higher than
pre-defined 30%, a rebalance may need to be reviewed.
- Alert to
accountant or financial advisor - be automatically informed regarding
credit holds, inventory thresholds, sales ratios, urgency levels, and
priority client transactions
- Create
new alerts to fit your business needs or customize the existing ones
- Alert based on the changes of
the monitored list such as new records in the list, removed records in the
list or persistent/old records in the list.
Use Cases:
- A mutual fund company defined
a stock list to monitor stocks that have Price/Earnings ratio below 2.
Being interested in the existing stocks that fit into the criteria, the
mutual fund managers also want to be notified by new stocks added into
the list. An alert is defined to monitor only new records of the list and
email will be sent to the fund manager with a list of new stocks having
PE<2, so they can make right investment decision in time.
- The sales
manager has a list of customers with good credit. Instead of knowing who
are already in the list, the manager is more interested in the customers
whose credit was downgraded recently (customer who were removed from the
list). An alert monitoring the removed customers from the list will give
the manager an email with the detail information of the downgraded
customers for him/her to review or follow up.
- Merge data
into e-mail messages by using customized email templates. The data
comes from any field of the regarded business record(s).
This means the email content can contain complex business data from the
business record(s).
- Include
HTML link in the body of the email to allow open the related business
record directly.
- Support
email in both HTML and text format.
- Define the
recipients of the alert. The recipients can either be a manual picked list
of users, user groups, contacts, companies and customers, or a custom
query.
- Integration
with business processes and workflows.
- Scheduling the alert.
How to create a new alert
1.
Create a new or select an existing business query
In this step a
query will be created or selected. The query should return the data that is
going to be monitored by the business alert.
The screenshot below is a query defined by a mutual fund manager for all
“Cash Cow Stocks” based on their proprietary criteria.
1.
Create a Business List
Business List
will allow the PrimeObjects Business List Engine to process the associated
query by following a certain schedule. The list items contained in the business
list will be classified as new records, persistent/old records and removed
records. The list items are the feed of the business alert.
1.1.
Create a new Business List
1.2.
Define the Business List and save it
2.
Create Business Alert
2.1.
Create a new Business Alert
2.2.
Define name and recipients of the Business Alert
2.3.
Select the Business List for the Business Alert
2.4.
Select a existing email template or define a new one
2.5.
Define the schedule and coverage
3.
The PrimeObjects Business List Engine will process the business list
right before processing the business alert by following the schedule.
After the
business list is processed, a list of records will be ready as list items and
the status of each list item will tell whether it is an persistent/old record,
new record or removed record in the current list.
You can always review the latest list items of a business list by opening the
form of the business list.
The status of the list item
|
State Code
|
Status Code
|
Description
|
|
0 -- Active
|
0 -- New
|
The list item that was not in the previous list updated by the
previous process but it is included in the latest list.
|
|
0 -- Active
|
-1 -- Persistent/Old
|
The list item that is included in both the previous list updated by
the previous process and the latest list.
|
|
1 -- Inactive
|
1 -- Removed
|
The item was in the previous list but not in the latest list.
|
4.
After the business list was updated, the business alert will be
processed based on the same schedule
The
AlertStatusCode and AlertExecutedOn will tell the status of the business
alert.
|
Code
|
Name
|
|
-3
|
Failed - List Update
|
|
-2
|
Failed
|
|
-1
|
Idle
|
|
0
|
In the queue
|
|
1
|
Processing
|
|
2
|
Completed
|
5.
The email detail can be seen in the Email record
The screenshot
of the email received in the Outlook
Notes to system administrators
and developers:
1.
If the list on an alert is changed to another one, the original one will
be set as Completed and its schedule will be turned off, therefore the original
list will not be processed anymore. The new list associated with the alert will
have the status set to "In the queue" and will follow the same
schedule defined for the alert.
2.
The schedule settings on the Alert will synchronize with the schedule
settings on the associated business list. If a list is updated successfully,
the AlertUpdateStatusCode of the corresponding alert will be changed to
"In the queue". The Business Alert Engine will pick in-the-queue
alerts to process and send emails.
Frequencies of the schedule
|
Code
|
Frequency
|
Options
|
|
0
|
One Time
|
OneTimeStartOn
|
|
1
|
Daily/Intraday
|
DailyFrequency, DailyFrequencyUnit (0 Minutes, 1 Hours and 2 Days)
|
|
2
|
Weekly
|
WeeklyMonday, WeeklyTuesday, WeeklyWednesday, WeeklyThursday,
WeeklyFriday, WeeklySaturday and WeeklySunday
|
|
3
|
Monthly
|
MonthlyDayCode
1 - First Day
2 - 2
...
30 - 30
31 - Last Day
|
3.
When ListUpdateStatusCode is set to "In the queue" the
AlertUpdateStatuCode will be set to "Idle". If the business list is
detached from the associated business alert, the business list will be
deactivated.
4.
There are settings called “Coverage” on the business alert
to decide what kind of records that the recipients want to be notified. The
available coverage options include “Cover
Persistent Items”, “Cover New
Items” and “Cover Removed
Items”.
5.
The business list used in the business alert will be updated based on
the frequency defined in the business alert. There's an attribute called
ListUpdateStatusCode on the List entity. If the value equals -1 (In the Queue),
the list will be updated by the next process of the PrimeObjects Business List
engine. The status of the business lists used by the business alerts are
maintained by the Business Alert Engine based on the frequency settings of the
business alert. One business list can only be associated with one
business alert.
6.
The “Regarding” field (InstanceId attribute) on the email
record will keep the business alert by which the email was generated.
7.
Recipients of the alert.
The AlertRecipientAttributeId attribute on the Entity record tells which
attribute will be used as recipient of the alert when the business list query
against a certain entity. For example, the AlertRecipientAttributeId of the
Task entity is "AssignToIds", it mean if the Recipient field on the
business alert has no value, the Assigned people in the task will be the
recipients of the alert email. The table below tells who will get the alert
notification based on different settings.
|
AlertRecipientAttributeId of the entity
that the business list is querying
|
Recipient defined on the alert record
|
Recipient will be used for notification
|
|
defined
|
Has value
|
Send alert to the recipients defined in the alert. The content of the
alert will be the consolidation of all records in the list.
|
|
defined
|
Has no value
|
Each record in the list will render an alert and send to the
recipients defined in the Alert Recipient Attribute of each record.
|
|
not defined
|
Has value
|
Send alert to the recipients defined in the alert. The content of the
alert will be the consolidation of all records in the list.
|
|
not defined
|
Has no value
|
There's no alert will be rendered
|