Alert Intelligence

So Easy Education Guide

© 2008 Document Version So-Easy Education Guide

Page i 1.0 Commercial in Confidence
Pronto is a registered trademark and PRONTO-Xi is a trademark of Pronto Software Pty Ltd
(ABN 47 001 337 248).
All other products mentioned are trademarks or registered trademarks of their respective companies.
Copyright  2008 Pronto Software Pty Ltd. All rights reserved.
PRONTO-Xi Version: 660.0
Permission is granted under the Software Licence Agreement to incorporate the contents of this training
guide into your own procedure manuals, only for the purpose of assisting your staff in the use of
PRONTO-Xi.
Any documents incorporating all or part of this training guide must bear notice of Pronto Software's
ownership of copyright of the content of this training guide.
All businesses referred to in examples are entirely fictitious. Any resemblance to any company or
individual is accidental.
 Table of Contents

Table of Contents
Table of Contents ..................................................................................................................................................... 1

Course Overview ...................................................................................................................................................... 1

Objective................................................................................................................................................................ 1
Prerequisites........................................................................................................................................................... 1
Audience ................................................................................................................................................................ 1
Assumptions .......................................................................................................................................................... 1
Scope of the Course ............................................................................................................................................... 2
Course Duration ..................................................................................................................................................... 2
Conventions ........................................................................................................................................................... 2

About Alert Intelligence .......................................................................................................................................... 3

Alert Intelligence ................................................................................................................................................... 3
Implementation Prerequisites ................................................................................................................................ 4
Administration Prerequisites ................................................................................................................................. 4
What is a Database Trigger? .................................................................................................................................. 5
Database Trigger Flowchart .................................................................................................................................. 7
Alert Intelligence Security ..................................................................................................................................... 8
Review of User Security Settings ........................................................................................................................ 10
Event Table Security ........................................................................................................................................... 12
Event Administration Setup ................................................................................................................................. 13
SCREEN FIELDS ........................................................................................................................................... 13

Creating and Maintaining Events......................................................................................................................... 14

Event Maintenance (AI M001) ............................................................................................................................ 14
DATA GRID FIELDS..................................................................................................................................... 14
Event Entry Wizard ............................................................................................................................................. 16
WHAT DOES AN EVENT LOOK LIKE? ..................................................................................................... 17
Creating a Message Box ...................................................................................................................................... 21
Event Maintenance – [Launch] Mode ................................................................................................................. 25
WHY TEST YOUR EVENTS USING ‘LAUNCH’? ..................................................................................... 25
LAUNCHING YOUR EVENT MANUALLY ............................................................................................... 25
Event and Recipient Log ..................................................................................................................................... 29
RECIPIENT LOG ........................................................................................................................................... 29
PURGE EVENT LOG..................................................................................................................................... 29
Event Maintenance – [Detail] Mode .................................................................................................................... 31
CREATING AN EMAIL NOTIFICATION ................................................................................................... 32
EMAIL NOTIFICATION – SETTING UP RECIPIENTS ............................................................................. 35
MORE PRE-PACKAGED EVENTS – ANOTHER EXERCISE ................................................................... 40
Understanding and Defining Filters ..................................................................................................................... 41

© 2008 Document Version So-Easy Education Guide

1.0 Commercial in Confidence
Table of Contents

UNDERSTANDING EVENT FILTERS ........................................................................................................ 41

DEFINING EVENT FILTERS ....................................................................................................................... 44
Creating Your Own Event ................................................................................................................................... 46
FINDING FIELD NAMES ............................................................................................................................. 47

Other Alert Intelligence Event Features .............................................................................................................. 52

Linking Events ..................................................................................................................................................... 52
Using the Scheduled Call Event Initiation Method ............................................................................................. 53
Event Subscriptions ............................................................................................................................................. 56
Manual Joins ........................................................................................................................................................ 60
Using the External Call Initiation Method ........................................................................................................... 61
SMS Notification Events ..................................................................................................................................... 61
External Processes / Workflow / Tasks ............................................................................................................... 61
Using the Advanced Edit Feature ........................................................................................................................ 61

Appendix ................................................................................................................................................................. 62
Reference Guide for Screen Fields and Buttons .................................................................................................. 62
EVENT ADMINISTRATION SETUP SCREEN ........................................................................................... 62
- DATA GRID FIELDS .................................................................................................................................. 62
EVENT MAINTENANCE SCREEN ............................................................................................................. 63
- DATA GRID FIELDS .................................................................................................................................. 63
- MODE BUTTONS ....................................................................................................................................... 64
EVENT MESSAGE BOX MAINTENANCE SCREEN ................................................................................ 65
- DATA GRID FIELDS .................................................................................................................................. 65
MANUAL EVENT LAUNCH SCREEN ....................................................................................................... 66
- DATA GRID FIELDS .................................................................................................................................. 66
EVENT AND RECIPIENT LOG SCREEN ................................................................................................... 68
- DATA GRID FIELDS .................................................................................................................................. 68
- MODE BUTTONS ....................................................................................................................................... 69
PURGE EVENT LOG SCREEN .................................................................................................................... 69
- FORM FIELDS ............................................................................................................................................. 69
EVENT DETAILS SCREEN .......................................................................................................................... 69
- FIELDS AND BUTTONS ............................................................................................................................ 69
EVENT EMAIL MAINTENANCE SCREEN ................................................................................................ 75
- FIELDS AND BUTTONS ............................................................................................................................ 75
EVENT FILTER MAINTENANCE SCREEN ............................................................................................... 76
- FIELDS AND BUTTONS ............................................................................................................................ 76
MANUAL JOINS SCREEN ........................................................................................................................... 78
- DATA GRID FIELDS .................................................................................................................................. 78
- MODE BUTTONS ....................................................................................................................................... 78
MY EVENT SUBSCRIPTIONS SCREEN ..................................................................................................... 79
- FIELDS AND BUTTONS ............................................................................................................................ 79

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0
 Table of Contents

Using Proman to Find Field Names ..................................................................................................................... 80

Product Brief........................................................................................................................................................ 83
List of Available Pre-Packaged Event Templates................................................................................................ 85

© 2008 Document Version So-Easy Education Guide

1.0 Commercial in Confidence
 Course Overview

Course Overview
Objective
The attendee will be able to:
• understand the purpose and uses of AI and be able to explain the concept of AI to other
people their organisation;
• create, maintain, test, troubleshoot and activate AI events within PRONTO-Xi;
• understand the security features available within AI;
• setup and initiate scheduled events;
• understand and manage user and external subscriptions to events;
• read, analyse and purge (as necessary) the event log.

Prerequisites
The attendee should have completed the following training sessions.
• PRONTO-Xi Overview;
• Overview Training for System Administrators;
• PRONTO-Xi /System Administration.
It is helpful if the attendee has:
• a general understanding of general database concepts, that is, tables, records, fields,
insert/update/delete actions, and so on;
• some experience with how PRONTO-Xi works at the database level. Some familiarity with
the ‘Proman’ tool is beneficial;
• some experience with writing SQL queries/reports.

Audience
This course is intended for System Administrators who have the knowledge and understanding to
interpret business requirements for AI, and who will be responsible for creating suitable events as
required.

Assumptions
In this course, it is assumed that the attendee:
• has PRONTO-Xi version 660.0 or greater installed;
• has access to the administrative functions of the Alert Intelligence module;
• is familiar with the general navigation and functionality available within PRONTO-Xi.

© 2008 Document Version So-Easy Education Guide

Page 1 1.0 Commercial in Confidence
Course Overview

Scope of the Course

This course will cover the following topics:
• General overview of the PRONTO-Xi AI module;
• Creating a ‘CUS’ dictionary area to store AI trigger information;
• Awareness of the AI user security roles that must be granted to maintain PRONTO-Xi AI
events and functions;
• Quick review of the ‘Proman’ database table viewing utility to assist in event creation;
• Maintaining, creating, testing, activating PRONTO-Xi AI events;
• Setting up scheduled events;
• Setting up subscriptions to events (dynamic, code/conditional, user and external
subscriptions);
• Understanding and managing the event log;
• Discussion of SMS capability, guide to SMS setup requirements;
• Discussion of Task Intelligence.
Note: Advanced editing functions assume 4GL programming knowledge and are beyond the
scope of this course.
For a complete list of all the available training sessions, contact your local Pronto Support Centre
or visit the PRONTOPlus website at http://www.prontoplus.com.au.

Course Duration
This course will take a full day to complete.

Conventions
The following symbols are used in this guide.

Symbol Purpose
Indicates a sequence of steps to be followed.

Indicates that this is a Pronto Software recommendation.

Indicates an important item of information.

Indicates that there is an alternative function(s) that can be used to obtain the
same result.

Indicates that caution should be taken before proceeding with an action.

Indicates a learning exercise for the student to complete

The images shown in this training guide are for illustrative purposes only and may not reflect the
settings relevant to your company’s dataset.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 2
 About Alert Intelligence

About Alert Intelligence

This section provides a brief overview of Alert Intelligence and the concepts and tools that
support it. It also covers the specific setup requirements for Alert Intelligence.

Alert Intelligence
PRONTO-Xi Alert Intelligence is a technology for capturing defined business events and then
triggering one or more predetermined actions in response to such events.

✭ Should an activation error be displayed on selecting any of the Alert Intelligence functions,
please contact your local Pronto Support Centre to obtain an activation key

An event can be defined as a specific change, or lack of change, in data in the PRONTO-Xi
database. Events can be captured by the following:
• Monitoring transactions on the PRONTO-Xi database, for example the entry of a purchase
order above a defined monetary value.
• Monitoring the passage of time, for example an invoice or delivery becoming overdue.
• Manually triggered from a custom program.
Relevant persons can be notified of captured events by a variety of methods, including:
• Displaying a message box.
• Sending an email, SMS or fax.
• Launching a workflow package or external application.
• Creating a log entry.
A range of pre-packaged event templates that can be used as-is or tailored to specific
requirements are provided. Full details of these are provided in the Appendix.
The recipients of a notification can be specified explicitly or selected dynamically, for example
via the details stored against a sales representative, customer or supplier. In addition, the content
of the notification can be tailored to the particular recipient and, in the case of emails, can
provide drill-backs to the relevant screen in PRONTO-Xi.
The Alert Intelligence module leverages the data triggers feature of the PRONTO-4GL
programming language to execute automatically generated code after a database record is
inserted, updated or deleted. For further information about data triggers refer to the Dictionary
Maintenance manual.
Additional features of the Alert Intelligence module include the ability to:
• Release events for self-service subscription by PRONTO-Xi users.
• Manually check for and process time-based (overdue type) events.
• Manually launch events using sample or actual data.
• View and customise the automatically generated database trigger code via an
[Advanced Edit] mode.
• Enhance the content of emails to include HTML mark-up or the results of an SQL query.

© 2008 Document Version So-Easy Education Guide

Page 3 1.0 Commercial in Confidence
About Alert Intelligence

Implementation Prerequisites
Since the Alert Intelligence module creates custom database trigger code, the following System
Administration prerequisites apply. If you are not confident to perform any of the functions
described below, please work through them in consultation with your local Pronto Support
centre:
• a custom dictionary must exist;
For instructions on how to create a custom dictionary, refer to the ‘Dictionary Maintenance’
section of the Programming and System Utilities manual. This will involve the setting of the
‘PROUSRDICT’ environment variable.
• the CUS environment variable must be set, for example ‘/home/pronto/cus’ on UNIX, or
‘C:\program files\pronto\cus’ on Windows (local install or at main windows server), or
something like ‘\\psdsql01\pronto\cus’; This setup should be performed in consultation
with Pronto’s Technical Services Department.
• the path specified by the PROPATH environment variable must include $CUS.
To use the SMS alert feature of the Alert Intelligence module, the following additional setup
must be performed:
• SMS email encryption control.
Set up the SMS email server and contact your local Pronto Support Centre to obtain a public
and private key. These keys must then be entered into the Event Administration Setup (AI
M003) function.

Administration Prerequisites
To maintain the Alert Intelligence module, the administrator of this module needs to:
• have the required system permissions to access the functions within this module. At the
time of writing the reserved roles ‘P_S7’ and ‘P_AI_MAINT’ contained all necessary
functions to maintain Alert Intelligence.
• be familiar with general database concepts, that is, tables, records, fields,
insert/update/delete actions, and so on.
• have some experience with how PRONTO-Xi works at the database level, that is, the
contents of fields in key database tables, how often and when records are updated in the life
cycle of purchase orders, sales orders, and so on.
Defining filters for events is similar to writing SELECT statements in SQL reports so SQL query
writing experience is also beneficial.
To use the more advanced features of the Alert Intelligence module, it is useful for the
administrator to have experience in the following:
• writing SQL queries.
• writing and compiling programs in the PRONTO-4GL programming language.
Note: Editing the data trigger code is an advanced feature and assumes programming knowledge.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 4
 About Alert Intelligence

What is a Database Trigger?

So we’ve read that Alert Intelligence leverages off the database triggers feature of the PRONTO-
4GL programming language and can create custom database trigger code; what does this mean?
To better understand AI, it is helpful to have a basic understanding of what a database trigger is,
and how AI uses triggers to achieve its functionality.
For the purposes of understanding AI, a database trigger is a routine that is automatically invoked
(triggered) whenever a specific condition occurs against a database table. Looking at the example
event below, we can see that in AI, events related to database tables can be initiated in three
ways. We can launch an event:
• AFTER a record is INSERTED (e.g. A new sales order is created)
• AFTER a record is UPDATED (e.g. A purchase order is received. PO Status changes
from ‘On Order’ to ‘Goods Received’)
• AFTER a record is DELETED (e.g. An inventory record is removed)

Think of a trigger as a tool constantly ‘watching’ a database table. When a PRONTO-Xi program
or a user comes along and is about to modify that table in some way, the trigger ‘asks’ “Is there
anything I should do here?” and then does whatever we’ve defined it to do. For example, if there
is an AFTER UPDATE trigger set, the trigger will then ‘call’ a program to run if it detects a
record was updated in a table. The called program may initiate a pop-up message box, send an
email or write an entry to a log file.

© 2008 Document Version So-Easy Education Guide

Page 5 1.0 Commercial in Confidence
About Alert Intelligence

Alert Intelligence provides an easy to use Graphical User Interface (GUI) that builds in the
background:
• both the trigger
• and the code to run when that trigger is activated
For more information on Triggers, refer to the ‘Custom/User Data Triggers‘ page in the
‘Programming and System Utilities’ reference manuals.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 6
 About Alert Intelligence

Database Trigger Flowchart

© 2008 Document Version So-Easy Education Guide

Page 7 1.0 Commercial in Confidence
About Alert Intelligence

Alert Intelligence Security

In recognition of the fact that various dictionary tables in PRONTO-Xi contain sensitive business
data, the Alert Intelligence module provides a number of security features to ensure that
notifications relating to sensitive data can only be set up by authorised persons.
By default, only a high level system administrator assigned the ‘P_S7’ (System Administrator -
Level 7) role has unrestricted access to all event definitions and dictionary tables.
The following table summarises the available roles and functions for configuring access to the
event maintenance functionality for non-system administration users.

Function/Role Purpose
P_AI_MAINT Use this role to configure a user as an “Event Manager” who has access
to the following AI functions:

(Alert Intelligence Event Maintenance (AI M001)

Maintenance)
Preview Scheduled Events (AI E005)
Submit Individual Scheduled Event (AI M008)
My Event Subscriptions (AI M002)

Note: Having assigned this role to a user, the ‘not granted’ conditions
apply to the AI S001 and AI S002 security functions described below,
that is, the user initially has no access to database tables, and can only
access their own events.
AI S001 When not granted, the user can only view and maintain events owned by
them. The creator of an event is always the owner unless ownership has
subsequently been reassigned as described above.

(Access all Events) When granted, allows the user to:

• view and maintain all events listed in the Event Maintenance

function;

• change the owner of an event using the [Owner] mode on the Event
Maintenance screen.
AI S002 When granted, every dictionary table is visible and selectable at all table
selection fields throughout the Alert Intelligence module.

(Access all When not granted, the user can only see and select those dictionary tables
Dictionary Tables) that have been granted within the Event Table Security (AI M007)
function.
AI M007 Use this function to define which dictionary tables a PRONTO-Xi user
can see and select when creating or maintaining events.

(Event Table Note: A user granted the AI S002 (Access All Dictionary Tables)
Security) function will have access to all dictionary tables regardless of any entries
relating to them that have been created in this function.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 8
 About Alert Intelligence

Example 1:
Requirement: There are two Event Manager users and each should only see their own events.
Solution: Assign each user the ‘P_AI_MAINT’ role, and configure their access to the dictionary
tables in the AI M007 function.

Example 2:
Requirement: There are two Event Manager users. Event Manager A (full-access user) is allowed
to define events based on any data within the company, and can maintain all existing events
regardless of who created them. Event Manager B (restricted-access user), however, is not
allowed to set up notifications relating to payroll data and can only maintain his/her own events.
Solution: In the user access control settings of Event Manager A, assign the ‘P_AI_MAINT’ role
and grant the AI S001 and AI S002 functions. No further setup is required. In the user access
control settings of Event Manager B, assign only the ‘P_AI_MAINT’ role and then create the
following entries in the Event Table Security (AI M007) function:

User ID Table Name Grant/Deny

<user-id> * G
<user-id> pay* D

© 2008 Document Version So-Easy Education Guide

Page 9 1.0 Commercial in Confidence
About Alert Intelligence

Review of User Security Settings

Let’s take a quick look to see if your User Security settings are adequate to complete today’s
training

MENU PATH
Administration
System Administration
User and Company Maintenance
User Access Control (SYS M195)

To review the roles assigned to your user name

1. With your username highlighted, click the [Select] mode.
Next with the current company you are working in highlighted, click the [Roles] mode:

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 10
 About Alert Intelligence

2. Using the [Find] mode, confirm you have either the ‘S7’ (or S8 or S9) role. You may or may
not also have the ‘P_AI_MAINT’ role.

As long as you have the S7, S8 or S9 role, you can fully maintain all functions within AI.

© 2008 Document Version So-Easy Education Guide

Page 11 1.0 Commercial in Confidence
About Alert Intelligence

Event Table Security

This function is used to define which dictionary (database) tables a user can see when creating or
maintaining events. Please keep in mind that there is also a Table Security Maintenance feature at
a system administration level, which has often been preset to exclude all users from the Payroll
tables.

MENU PATH
Alert Intelligence
Event Table Security (AI M007)

Example: Creating an entry ‘D’enying access to the EDI tables

1. Select the [Entry] mode and enter your user ID in the first column.
2. In the Table Name column, press F2 (Lookup Help) to access a list of the database objects, or
enter edi* to indicate all tables beginning with ‘edi’.
3. In the Grant/Deny column, enter D to deny access to these tables whilst using AI Event
Maintenance.
The following dialog may briefly appear as the table securities are rebuilt:

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 12
 About Alert Intelligence

Event Administration Setup

Use this function to maintain SMS email encryption control and email control details for the
Alert Intelligence module.

MENU PATH
Alert Intelligence
Event Administration Setup (AI M003)

Screen Fields
Please refer to the Appendix for a detailed description of the fields on this screen.

© 2008 Document Version So-Easy Education Guide

Page 13 1.0 Commercial in Confidence
Creating and Maintaining Events

Creating and Maintaining Events

Event Maintenance (AI M001)
Use this function to create and maintain event definitions. This function can be used to create a
new event, duplicate an event, configure events, test an event that has been set up and manually
edit the PRONTO-4GL data trigger code on which the event is based.
Note: This data grid may only display events owned by the current user, depending on the
security settings implemented by the system administrator.
Following the menu path below, open up the Event Maintenance data grid. There should be some
example events already setup that we will examine shortly.
In order to get a feel for how the Event Maintenance area works, and how to setup some basic AI
events, we will first examine some existing events, before moving on to create our own. Once
you have a good grasp of the concept of AI and how to setup events, you are only limited by your
imagination as to the variety of events you can create!

MENU PATH
Alert Intelligence
Event Maintenance (AI M001)

Data Grid Fields

Please refer to the Appendix for a detailed description of the fields on this screen.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 14
 Creating and Maintaining Events

To change the owner of an event

1. Select the [Owner] mode.

Note: The Owner column is located at the far right of the data grid and you may have to drag
the scroll bar across to see it.

2. Press F2 (Lookup Help) to select a different user and then click [OK].

The change is now reflected in the data grid. This person is the new owner and depending on
security settings may now be able to edit and maintain this event.

© 2008 Document Version So-Easy Education Guide

Page 15 1.0 Commercial in Confidence
Creating and Maintaining Events

Event Entry Wizard

This wizard, which is accessed via the [Entry Wizard] mode of the Event Maintenance function,
is used to create a new event. When creating new events you have the option of creating events
from a list (at time of writing) of around 35 Pre-Packaged events. You still have the ability to use
these as a ‘template’ and modify them if needs be to suit your needs. You can also ‘Create Your
Own’ Events.
The Pre-Packaged templates are also great to use as a tool to ‘reverse engineer’ AI events, and
can be useful to review how an event is created and triggered if it’s been awhile since you’ve had
to edit or maintain an event.
Note: For maximum flexibility, all templates allow the filter criteria and filter value(s) to be
edited; however, the pre-defined fields can not be changed. To change the fields in a template,
create the event first and then edit the required details.
The following table summarises the 5 pages of the Event Entry Wizard. For full details of a
particular wizard page, click the [Help] button on the wizard page. Full details of each of the Pre-
Packaged events and the filters they use are available in the PRONTO-Xi online help.

Step 1 of 5 Create New Event

Step 2 of 5 One of the following two pages is displayed depending on whether the ‘pre-
packaged event template’ or ‘design your own event’ option is selected in Step
1 of the wizard.
• Select Event Template
• Select Table for User-Defined Event

Step 3 of 5 Select Notification Method and Initiation Triggers. (After Insert, After
Update, After Delete, Scheduled Call etc)
Step 4 of 5 One of the following two pages is displayed depending on whether the ‘pre-
packaged event template’ or ‘design your own event’ option is selected in Step
1 of the wizard.
• Complete/Modify Filters
• Define Filters
Step 5 of 5 One of the following pages is displayed depending on which notification
method is selected in Step 3 of the wizard.
• Create Email Notification
• Create Message Box
• Create Short Message Service (SMS) Text
• Create FAX Cover Page Content
• Setup External Process (Workflow Package or Program)
• Create Event Log Text

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 16
 Creating and Maintaining Events

What does an event look like?

MENU PATH
Alert Intelligence
Event Maintenance (AI M001)

[Entry Wizard] Mode Button

Let’s have a look through one of the pre-packaged event templates to get a feel for what an event
looks like, and how they are set up. Each event in its most basic form needs to know 5 things
(this can vary for special applications of events):
• What database table am I monitoring?
• What action type am I monitoring for: Inserts, Updates or Deletes (or a combination of)?
• How do I ‘Alert’ you if the event has occurred?
• Under what conditions (filters) should I alert you?
• If an email/SMS, whom should I alert?

We are going to work through an example using a Pre-Packaged Event Template. We are going
to create a Message Box Alert. Actually creating the text displayed in the message box comes in
Step 5 of the wizard.

© 2008 Document Version So-Easy Education Guide

Page 17 1.0 Commercial in Confidence
Creating and Maintaining Events

Exercise:
1. Select the [Entry Wizard] mode.
2. Select the Pre-Packaged Event Template option and then click [Next].

3. Highlight the Event entitled “Inventory Levels – Below Minimum”, then click [Next].

4. In the Notification Method options, select Display Message Box and then click [Next].
Notice the trigger type is ‘After Update’. This event is therefore monitoring for update
actions on the ‘stock-warehouse-detail’ database table.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 18
 Creating and Maintaining Events

The ‘stock-warehouse-detail’ object is where the Stock Balances, Min/Max stock levels and
Average Cost (to name a few fields) for each warehouse is kept

5. Review the Complete/Modify Filters page and edit the Event Description to include your
name:

Note: The ‘n’ and ‘o’ prefix are referring to monitoring the ‘n’ew and ‘o’ld values of the
fields in question.
Let’s examine the filters and the notation of these filters.
An ‘After Update’ trigger implies that we want to know when something has been updated or
changed. In this case we want to know if the stock balance has fallen below the present
‘Minimum Stock’ level defined in the stock-warehouse-detail object – this is stored under the
[Warehouse] mode in ‘Inventory Maintenance’

© 2008 Document Version So-Easy Education Guide

Page 19 1.0 Commercial in Confidence
Creating and Maintaining Events

Here is an example record. The Minimum Stock Level is set to 5, and the quantity on hand is 8.
We want this event to ‘trigger’ if a stock movement causes the stock level to fall below 5.

You will see in the following style of notation in the Create/Modify Filters area:

• n.whse-qty-on-hand LESS THAN n.whse-min-stock AND … etc

• the ‘n’ and ‘o’ prefix are referring to monitoring the ‘n’ew and ‘o’ld values of the fields in
question.
• We need to know the old and new values to be able to determine what has changed in
an ‘Update’ situation, and the filters are the limits we set to determine when we are
notified (and the event is triggered)
Written out, this filter is saying:
• If the NEW warehouse Qty on Hand (QOH) is LESS THAN the NEW Minimum Stock
Level AND the OLD warehouse Qty on Hand is NOT EQUAL TO the NEW Warehouse
Qty on Hand (indicating there has been a stock movement) – then trigger the event and
notify me as defined in the event.

Exercise: If you were to edit the Stock Warehouse record and increase the Min Stock level
to 10 (so the QOH is now LESS THAN the Min Stock Level) – would this event be
triggered?

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 20
 Creating and Maintaining Events

Creating a Message Box

This page of the Event Entry Wizard, which is accessed via the [Entry Wizard] mode of the Event
Maintenance function, is used to configure the message box that is displayed in the PRONTO-Xi
client of the user whose action launched the event.
So continuing on with the example:
1. Next you need to define what the message box will display. As well as text you can
optionally add fields from the stock-warehouse-detail table and/or fields from linked tables
(where a link exists)
a. Enter your own Message Box Title.
b. In the Text Area, we are going to create a message that tells us the:
i. Item code
ii. First line of description
iii. Stock level before and after the update
iv. Min stock level
v. Warehouse where the stock movement occurred
c. We will add the database fields using the field picker
2. Type in the first line: ‘Please review Item: ‘ and then using the [Field Picker] button append
the stock code field to the Message Box. It should now look like this:

© 2008 Document Version So-Easy Education Guide

Page 21 1.0 Commercial in Confidence
Creating and Maintaining Events

3. Select the [Field Picker] tool and click [Other Table] to display the first line of the stock
description.
To display fields from other tables, you need to be able to join to the ‘Other table’. In some
cases auto joins may be formed between two tables; in other cases you will need to specify
the fields used to join the tables.
Note: Table joins, and ‘auto joins’ are further explained in the ‘Manual Table Joins’ section
later in this manual. Feel free to ask your trainer what an auto join means.

4. In the Table Picker dialog, select the [Find] mode, click the entry for the stock-master table
(which is where the stock description lines are stored) then click [Select].

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 22
 Creating and Maintaining Events

5. In the list of fields for the stock-master table, highlight the stk-description field and select
the [Append Field] mode to append it after the ‘stock-code’ field.

The Message Box should now look like this:

© 2008 Document Version So-Easy Education Guide

Page 23 1.0 Commercial in Confidence
Creating and Maintaining Events

Exercise:
1. Add a second line and third line showing the Quantity on Hand before and after the stock
movement and the warehouse it occurred in.
2. Click the [Preview] button to check the format of the message.
If you have prepared the message correctly, it should look (something) like this when you
later actually trigger it:
Add a second line and third line, describing and showing the Quantity on Hand before and
after the stock movement and the warehouse it occurred in. Preview your message box, and if
prepared correctly, it should look (something) like this when you later actually trigger it:

3. When you are satisfied with the message box, click [Create] in the Event Entry Wizard.
You are returned to the Event Details screen.
4. In the Event Status options, ensure that Testing is selected.
The status of all newly created events should default to ‘Testing’.
5. Click [OK] to return to the Event Maintenance data grid screen.

Next you will test the event using the manual launch feature.
To ensure the event is only triggered at the appropriate times, you should always test your
event thoroughly before setting it to active!

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 24
 Creating and Maintaining Events

Event Maintenance – [Launch] Mode

As stated in the ‘Tip’ on the previous page, testing your events manually before setting them to
‘Active’ is highly recommended!

MENU PATH
Alert Intelligence
Event Maintenance (AI M001)
• ‘Launch’ Mode Button

Why Test Your Events using ‘Launch’?

From our experience to date, the single most important reason to test your events, is because you
may have set your ‘Filters’ up in such a way that your event(s) will trigger far more often than
intended. This is particularly the case with ‘After Update’ triggers. There are update routines in
PRONTO-Xi (e.g. Integrity Reports in Correct Mode) which can ‘Update’ huge numbers of
records in a short time.
To ensure that event is only triggered at the correct times, it is therefore very important to
accurately define the conditions you wish to trap.
Testing is Important!!

Launching your Event Manually

This screen, which is accessed via the [Launch] mode of the Event Maintenance function, is used
to test existing events to verify that they will launch under the required conditions. It is highly
recommended to perform this testing prior to setting the status of the event to Active in the Event
Details screen!
Note: Testing or manually ‘Launching’ an event will ONLY write to the Event Log, it will not
actually produce an email, message box or SMS.
What you are looking for during your testing, is that the event is not triggered many many
times, when you expected it to be triggered only once.

© 2008 Document Version So-Easy Education Guide

Page 25 1.0 Commercial in Confidence
Creating and Maintaining Events

Exercise Part 1:
1. Select the [Launch] mode to test the event you created.
2. Use the ‘Sample Test Data’ option and set up some test data to represent the New Stock
Level falling below the Old Stock Level, AD falling below the Min Stock level you
nominate.

Once you have set up your test data and click [OK], the following dialog box is displayed:

Note: This dialog box will appear anytime you edit an event and exit the Event Maintenance
screen, or when you click the [Generate] mode.
When you see this window, PRONTO-Xi is auto-generating the 4GL trigger code associated with
the event notifications that have been defined.

Once the test is complete, PRONTO-Xi prompts you to view the Event Log.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 26
 Creating and Maintaining Events

3. Click the [Event Log] button and check to see that an entry has been written to the event log,
which indicates that the event was successfully triggered.

4. Check the date/time stamps to verify the latest entry in the log.

Tip: A secondary way to test run an event is to select the ‘Event Log Only’ notification method
and set the status to Active. Now, every time the event is triggered an entry is created in the event
log and you can check that the event is functioning as desired. If all is okay after some testing,
you can set the Notification Method back to Email/Message Box etc.

Please review this section of the Training Manual as necessary to test Scheduled or External Call
Events, or to test your event against the Actual Table Data.

© 2008 Document Version So-Easy Education Guide

Page 27 1.0 Commercial in Confidence
Creating and Maintaining Events

Exercise Part 2: Actually Triggering your Event (Real life testing):

1. Now that you’ve tested your event, click the [Detail] mode on the Event Maintenance Data
Grid, and set your Event to a status of ‘Active’:

2. With the guidance of the trainer: Select the Inventory Console [INV.E005] screen and
review the current Minimum Stock level for the AI-TEST-ITEM (Warehouse Tab >
Warehouse Balances > Details).
3. Next have the trainer demonstrate how to adjust the stock level below the minimum stock
level using the ‘Adjust Item Levels’ function [INV.T011] and then perform your own stock
adjustment, sending the AI-TEST-ITEM below the Min Stock Level to test the operation of
your AI event. Did the Message Box work?

Next we will look at the Event Log and the details stored within it.
We will come back to revisit Event Maintenance again to explore the many other options available
when creating and maintaining events.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 28
 Creating and Maintaining Events

Event and Recipient Log

The Event Log records many details associated with any triggered event, including both the
information that triggered the event, and the recipients (where applicable) that were notified of
the event.

MENU PATH
Alert Intelligence
Event Log (AI E001)

Use this function to review details of events that have launched.

Exercise: Find in the Event Log the Inventory Level Below Min Stock event you created and
triggered. Use the mode buttons to review the information stored against each mode button.

Tips:
• Remember as the Event Log fills up you can use Column Sorts and Filters to ‘Search’
through the log to find specific entries as required.
• You can always set an event with a notification method of ‘Event Log Only’. No email,
message box or SMS will be created, although if you have created the text for these
notification methods, it will still be saved if you ever decide to change the notification
method again. This way, the event can simply write to the Event Log (any event triggered
will ALWAYS write to the log), and you can periodically review it as necessary.

Recipient Log
Use this function to review recipient details for all events that have launched.

MENU PATH
Alert Intelligence
Recipient Log (AI E002)

Purge Event Log

Use this function to delete some or all records in the event log.
Note: Pronto Software recommends that this function be used periodically to ensure that the
event log does not consume an unnecessarily large amount of disk space.

MENU PATH
Alert Intelligence
Purge Event Log (AI M006)

• Click [OK] to launch the purge action.

© 2008 Document Version So-Easy Education Guide

Page 29 1.0 Commercial in Confidence
Creating and Maintaining Events

On completion, the number of records that were deleted is confirmed in a message box. Note that
the record count may be higher than excepted as each line of notification text is considered a
record.
Note: In determining which event log entries to purge, this function takes into consideration the
following AI related security settings:
• whether the user has access to all events or only their own;
• whether the user has access to all dictionary tables or only those granted by the system
administrator.

Note: The following Event Log purge would result in ALL log entries for ALL events being
deleted prior to 31-DEC-07, but only for the DEM company.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 30
 Creating and Maintaining Events

Event Maintenance – [Detail] Mode

You have now seen how to create an event from a pre-packaged event template, and how to edit
the wording in the chosen method of notification, a message box. Next we will look at the
information stored under the [Detail] mode in Event Maintenance and review some of the other
functionality that can be maintained and modified for an event

MENU PATH
Alert Intelligence
Event Maintenance (AI M001)

This screen, which is accessed via the [Detail] mode of the Event Maintenance function, is used
to configure the details of an event, including the notification description, method, event status,
and the recipients of the event.
Note: The fields and buttons that are available in this screen depend on the selected Notification
Method.
Please refer to the Appendix for a detailed description of the fields and options on this screen.

© 2008 Document Version So-Easy Education Guide

Page 31 1.0 Commercial in Confidence
Creating and Maintaining Events

Creating an Email Notification

We have now successfully set up an event that creates a popup message box when the stock level
in a particular warehouse falls below the minimum stock level for that warehouse. We are now
going to change the notification method to an email message.
Note: Whilst we will create the email notification event in this training session, it will not
actually create an email if you are being trained at Pronto Software premises, unless email access
has been granted to you for the purposes of training.
Email notifications for events are great in that the event is captured both in the event log, and the
relevant person’s inbox. The email sent to the recipient can also contain hyperlinks, so if the
recipient has a PRONTO-Xi session open, the hyperlink can allow them to drill straight into the
relevant screen in PRONTO-Xi to further act on, or investigate, the reason for the alert.

MENU PATH
Alert Intelligence
Event Maintenance (AI M001)

[Detail] Mode Button
o [Define Text] Button

To prepare for this next exercise, select the Event Maintenance function, highlight the
‘Inventory Levels – Below Minimum’ event and click the [Detail] mode.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 32
 Creating and Maintaining Events

Exercise Part 1:
You will now change the existing event from a message box notification to an email
notification, and have a look at some of the recipient setup options.
1. As shown on the previous page – change the Notification Method to ‘Email Notification’ and
leave the ‘Method’ option set to ‘Direct’.

Tip: ‘Batch’ method: The batch queue to use to send batched emails is specified in the Event
Administration Setup function. Batching the sending of emails (if this is the notification
method) is a great idea, otherwise the user that (perhaps unknowingly) initiated the event,
will have their screen ‘freeze’ (actually it’s pausing) while the server sends the email.

2. Click the [Define Text] button as highlighted in the screenshot on the previous page.
A quick review of the fields on this screen are given below:

Note the ‘bold’ html tags included in the example above.

3. Create your own Email Message using the Field picker to insert fields you believe will make
a meaningful message
4. Click the [Preview] button to preview the layout of your email.

© 2008 Document Version So-Easy Education Guide

Page 33 1.0 Commercial in Confidence
Creating and Maintaining Events

The message preview should look something like the following. The underlined text denotes
the drill back available on certain fields included in the email, in this case the item code and
warehouse code.

Here is a screenshot of the email generated from this event:

Note the bold text here from the <b></b> html tags

In this example we didn’t include an attachment.

5. After completing the email text, click the [Attachment] button in the Event Detail screen.
This feature provides the ability to attach a standard document to any event with an email
notification. For example, you could attach the procedure to be followed if the event occurs.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 34
 Creating and Maintaining Events

Email Notification – Setting up Recipients

In summary, the options available are:

• Log Recipients: Select this option to record the addresses that the notification was sent to.
• Dynamic: Use this option to dynamically select the recipients of the notification based on
the specific data that launched the event.
• Code Based: Use this option to specify the recipients of the notification by entering specific
account, role or representative codes. The contact details (email address, mobile phone
number or fax number) are obtained via the relevant master record of the specified account.
• User: Specify the PRONTO-Xi user ID of the intended recipient.
• External: Specify the contact details (email address, mobile phone number or fax number)
of a recipient who is external to the PRONTO-Xi system.

The following is a more in depth discussion of the available options:

Define this event’s Email/SMS/Fax recipients

Log Recipients Select this option to record the addresses that the notification was sent to.
Note: This does not verify that the notification arrived at the intended address.
Dynamic Use this option to dynamically select the recipients of the notification based on
the specific data that launched the event.
Example:
Commonly in a company there will be more than one Credit Administrator and
they will be territory based. Therefore, either multiple events with different
territories could be set up or this option used to set up one event with a
conditional email on top of conditional filters.
Specify the recipient contact details (email address, mobile phone number or fax
number) based on the dynamic email type.
The following dynamic recipient selection options are available:
F Field Value
Selects the recipient of the notification based on the results of a logical
operation performed on a selected field (or calculated field).
For example, the following two rules could be entered to define the
recipient based on the territory field on the sales order:
• n.so-territory-code EQUAL TO “MEL”
email address = [email protected]
• n.so-territory-code NOT EQUAL TO “MEL”
email address = [email protected]
C Customer
Obtains the recipient details by looking up a customer account via a
specified field (or calculated field), for example, the ‘so-cust-code’ field

© 2008 Document Version So-Easy Education Guide

Page 35 1.0 Commercial in Confidence
Creating and Maintaining Events

in the ‘sales-order’ table.

S Supplier
Obtains the recipient details by looking up a supplier account via a
specified field (or calculated field), for example, the ‘cre-accountcode’
field in the ‘purchase-order’ table.
M CRM
Obtains the recipient details by looking up a CRM account in the
Customer Relationship Management module via a specified field (or
calculated field).
V Engineer
Obtains the recipient details by looking up an engineer account in the
Service module via a specified field (or calculated field).
E Rep
Obtains the recipient details by looking up a representative account via a
specified field (or calculated field), for example, the ‘so-rep-code’ field
in the ‘sales-order’ table.
T Task
Obtains the recipient details by looking up the PRONTO-Xi user account
specified in the ‘tm-allocated-to’ field in the ‘task-master’ table.
P Employee
Obtains the recipient details by looking up an employee account in the
Human Resource Management module via a specified field (or
calculated field).
Z Custom
Use this option to select the recipient by passing the value of a specified
field (or calculated field) to the public exportable procedure ‘clib801-
determine-dynamic-custom-address’.
Contact your local Pronto Support Centre for assistance or to obtain a
Software Development Kit for customising PRONTO-Xi.
Code Based Use this option to specify the recipients of the notification by entering specific
account, role or representative codes. The contact details (email address, mobile
phone number or fax number) are obtained via the relevant master record of the
specified account.
The following code-based recipient selection options are available:
C Customer
Use this option to send the notification to a selected customer by
entering their customer account code.
S Supplier
Use this option to send the notification to a selected supplier by entering
their supplier account code.
M CRM Account
Use this option to send the notification to a selected contact stored in the
Customer Relationship Management module by entering their account
code.
R Security Role
Use this option to send the notification to all PRONTO-Xi users who

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 36
 Creating and Maintaining Events

have been granted a selected security role.

E Representative Code
Use this option to send the notification to a selected representative by
entering their representative code. The contact details are obtained via
the login ID stored against that representative. If an address is specified
in the Email Address column for that login ID in the User Access
Control (SYS M195) function, then that email address is used.
P Use this option to send the notification to a selected employee by
entering their employee number, as maintained in the Human Resource
Management module.
User Specify the PRONTO-Xi user ID of the intended recipient.
External Specify the contact details (email address, mobile phone number or fax number)
of a recipient who is external to the PRONTO-Xi system.

• Exercise Part 2:
• You will now assign a dynamic email address based on the warehouse. This approach is
meaningful when there are different warehouse managers who would manage the event of
an item falling below minimum stock.
1. On the Event Detail screen, click the [Dynamic] button.
The following screen is displayed:

2. Enter the two lines as shown above and have some discussion as to other possibilities with
the ‘Dynamic’ allocation of email addresses.
3. Press <Esc> to exit the recipient list and click [OK] on the Event Detail screen.
4. Go and manually trigger the event.
5. Check the [Event Log] button and find the latest entry for your event in your company.
6. Click the [View Text] mode to see if your email text was created as you entered it.

© 2008 Document Version So-Easy Education Guide

Page 37 1.0 Commercial in Confidence
Creating and Maintaining Events

7. Next click [View Rendered Text] to see the HTML output of the email notification.

Feel free to ask your trainer about Code Based, User and External type recipient lists.

• Discussion Exercise:
For reference, if we were to have an event related to a sales order (‘sales-order’ database
table), we could use a ‘C’ (Customer) type data lookup and pass the customer code on the
sales order to Alert Intelligence. Alert Intelligence would then lookup the customer’s email
address at the time the event was triggered and send an email to the customer.
The email address used in this case would be the address stored in the Email Address field
accessed via the [Delivery] mode in the Customer Maintenance (AR.M001) function, as
shown on the following page.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 38
 Creating and Maintaining Events

The customer’s email address is stored here (see below). This would be used in the case
where a ‘C’ type Dynamic address was setup:

• Optional Exercise:
• If you have the ability to send emails on the test system (your trainer will advise) – feel free
to save the changes to the event and trigger it to test the generation of the email.

© 2008 Document Version So-Easy Education Guide

Page 39 1.0 Commercial in Confidence
Creating and Maintaining Events

More Pre-Packaged Events – Another Exercise

We have now seen how to create an event from one of the Pre-Packaged templates. To further
cement your knowledge gained so far, let’s setup one more Pre-Packaged Event with a Message
Box notification method. Follow the steps listed as you would when creating your own real event
in your PRONTO-Xi company(s).

Exercise:
As a group, select one of the pre-packaged event templates to work with. Try to pick a template
that has some meaning for you.
This exercise is designed to let you try creating event by yourself (as much as possible), to give
you the confidence to do the same when you return to your work place!
The aim is to create a meaningful message box notification for the event that you choose to
create. After creating the event, testing it and setting it to Active, you will trigger it in your test
system to see it actually working. Please follow these steps when creating your next event:
1. Use the Entry Wizard to select a pre-packaged event template.
2. Select the Display Message Box notification method.
3. Leave the Event Initiated method settings at their default.
4. Review with the trainer the filter conditions for the event you’ve chosen. Do they make
sense?
5. Create a meaningful message box including some fields using the ‘Field Picker’ – perhaps
even try joining another table to display some additional information.
6. Test your event using the ‘Launch’ feature.
7. Set the event to a status of ‘Active’.
8. With the help of your trainer, decide on a way to trigger the event in your test
system/database.
9. Check the event log to see your triggered event..

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 40
 Creating and Maintaining Events

Understanding and Defining Filters

If the Message Box, Email or SMS are the usual mode of communication generated by an event,
it is the Filters you set up and define that are the ‘brains’ behind whether or not the event is
triggered. The effectiveness and complexity of the event you set up is usually dictated by the
effectiveness and complexity of the filters you define. A good understanding of filters will allow
you to create robust and creative events.

MENU PATH
Alert Intelligence
Event Maintenance (AI M001)

[Detail] Mode
o [Define Filters] button

Understanding Event Filters

Event filters serve the same purpose as the WHERE clause of an SQL SELECT statement, that is,
they are used to narrow down which records of the master table selected for the event contain the
specific data conditions under which the event is to be launched.
Field names
In contrast to SQL queries where only the current value of each field in a record can be queried,
event filters can test the value of fields before and after a record is inserted, updated or deleted.
The ‘old’ and ‘new’ value of a field is referenced by prepending ‘o.’ or ‘n.’ to the field name.
For example, ‘o.accountcode’ refers to the value of the account code field prior to the record
update, and ‘n.accountcode’ refers to the value of the account field after the record update.
Comparison operators
The comparison operators provided when setting event filters are the same as those available
when applying a filter to a data grid column.
Tip: If you are unsure about the expected outcome of a particular comparison, for example the
result of a GREATER THAN comparison between strings of differing capitalisation, you can
‘practise’ using the operator on any suitable data grid in the PRONTO-Xi application.

© 2008 Document Version So-Easy Education Guide

Page 41 1.0 Commercial in Confidence
Creating and Maintaining Events

Order of evaluation
If multiple filters are specified, they are evaluated top down. As soon as a filter fails, no further
filters will be evaluated. It is therefore important to place critical filters higher up than less
critical ones. For example, a filter that tests for the value ‘zero’ in order to prevent a divide-by-
zero error in a calculated field should always be placed at the top of the list.
Calculated fields
Since the Alert Intelligence module generates and then compiles native PRONTO-4GL code, it
is possible to use not only the standard algebraic operators + (addition), - (subtraction), /
(division) and * (multiplication) but also any of the numerous expressions or functions supported
by the PRONTO-4GL programming language when defining a calculated field.
For a full list of supported operators and functions see the ‘Expressions and Operators’ and
‘Function Calls’ sections of the 4GL Reference Manual. This manual can be accessed by
clicking either the [Syntax Help] or [Function Help] button when defining the calculated field.
The calculated field is displayed as calc.fieldname, where fieldname is a name you have selected.
Note that the ‘o.’ and ‘n.’ prefixes can only be used for the fields referenced in the calculation,
not the calculated field itself.
If the calculation expression contains a syntax error, an error warning is displayed when the code
for the event is generated.
If any of the filters fail, the program will stop and no further filters will be checked, hence
the event will not be launched.
For examples of calculated fields, see the description of the ‘Sales Order Line under Minimum
GP’, ‘Inventory Average Cost Change’ or ‘Project - Actuals as a Percentage of Budget’ event
templates in the ‘About Pre-Packaged Events’ section.
Alternatively, feel free to setup a Pre-Packaged Event such as the ‘Sales Order - Under Minimum
GP%’ Event. Once you have created it you can go to the ‘Define Filters’ screen and do an F2
Lookup on the calc.<fieldname> field and see how the GP% has been calculated. Here is a
screenshot of the GP% calculation:

An [F2] lookup on the calc.order-gp-% field shows the following:

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 42
 Creating and Maintaining Events

The full calculation is:

( ( (n.so-order-total-shipped-amount - n.so-order-total-shipped-tax) - n.so-order-total-
shipped-cost) / (n.so-order-total-shipped-amount - n.so-order-total-shipped-tax)) * 100

Referencing filter values or calculated fields in notification text

When entering the text of a notification, filter values or calculated fields can be selected using the
[Calc.] or [Function] modes in the Field Picker dialog. They can also be entered manually using
the following syntax:
Filter value: {filter-value(n)}, where n is the number of the filter (1 - 5)
Calculated field: {calc.fieldname}, where fieldname is the name given to the calculated field.

General tips – THESE ARE VERY IMPORTANT TO NOTE!

• Do not assume that a field is set, for example, always test that a date field has a non-zero
value.
• When creating an event to capture a specific change in a status field or other field, always
check that the ‘n.’ and ‘o.’ values of the field are different as well as testing for the
relevant field value. For example, the single filter:

n.so-order-status EQUAL TO 17

will not only launch the event when the sales order status changes to 17, but also every time
a sales order with status = 17 is updated, for whatever reason!
The correct approach is to create two filters!
n.so-order-status EQUAL TO 17
AND
o.so-order-status NOT EQUAL TO 17
• When using a calculated field that includes a division operation as a filter, always add a
prior filter to test for a zero value in the denominator.
• When using a calculated field as a filter, for example to test for a certain threshold value,
always test that something that influences the calculation has changed.
• PRONTO-Xi includes a number of audit functions that you can take advantage of to capture
more complex events. Rather than writing filters to detect the relevant data changes in the
original database tables, you can write a single filter to test for the insertion of a specify
type of log entry in the audit table. A notification can then be constructed from the data
values written to the audit log record. For an example of this, see the ‘Sales Order - Audit
Trail - Price Override’ event in the Appendix section.

© 2008 Document Version So-Easy Education Guide

Page 43 1.0 Commercial in Confidence
Creating and Maintaining Events

Defining Event Filters

Event filters can be defined whilst using the [Entry Wizard] mode of the ‘Event Maintenance’
function, or by using the [Detail] mode in Event Maintenance and clicking the [Define Filters]
button. Please refer to the Appendix for a detailed reference guide to setting up filters.
Use this page to create and modify the filters for the event, which specify the condition(s) that
need to occur for the event to launch. Each filter consists of either a field in the selected database
table or a calculated field, the type of comparison to make, and the value for comparison.

Exercise:
Let’s modify our original Minimum Stock event to once again be a message box. What we are
going to do this time is create a calculated field to check if the stock level has fallen below a
percentage of the Maximum stock level. The maximum stock level is set at 24, so we are going to
set the event to check if the stock has fallen below 25% of the Max Stock level (an implied limit
of 6).

1. In the Event Maintenance data grid, locate the event you created and select the [Detail]
mode.

2. Click the [Define Filter] button.

3. Highlight the first field in the filter and press F2 (Lookup Help).

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 44
 Creating and Maintaining Events

4. Select the [Calculation] mode to access the Create or Modify a Calculated Field dialog.
5. Enter the following formula using the Field Picker tool to find the ‘max-stock’ field:

6. Click [OK].
We now have to reverse the logic of our test, because we want to know when the New Qty
on Hand is LESS than this calculated amount. This is the same as saying we want to know
when the Calculated % of Max Stock is GREATER than the New Qty on Hand:

7. Click [OK] here, then also click [OK] on the Detail page of the event.
When you exit the Event Maintenance data grid, the Event Code Generation window is
displayed.

8. As you did earlier, perform a stock movement so that the resultant Quantity on Hand of the
AI-TEST-ITEM is less than 6.
Did your event trigger?

© 2008 Document Version So-Easy Education Guide

Page 45 1.0 Commercial in Confidence
Creating and Maintaining Events

Creating Your Own Event

You have now successfully:
• Reviewed the security setup of Alert Intelligence;
• Learnt what a database trigger is;
• Created events from the Pre-Packaged templates;
• Tested and manually launched our events;
• Reviewed the event log;
• Looked at creating and modifying recipient lists for email notifications;
• Reviewed filters and some rules around their creation.

So we are now ready to get creative and setup an event that is not in the Pre-Packaged templates.
There are endless possibilities for events you could setup, and the example given here is only a
suggestion. After this worked example, if you can think of another example you would like to
work through with your trainer, this may be possible (time and complexity permitting!).

MENU PATH
Alert Intelligence
Event Maintenance (AI M001)

[Entry Wizard] – ‘Design Your Own Event’

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 46
 Creating and Maintaining Events

Before creating an AI event, you need to do some planning and investigation to find out:
• What company(s) the event is needed to be active in;
• What Data Table do we need to monitor to trigger the event?
• Are we monitoring for an INSERT, UPDATE or DELETE ?
• Under what conditions do we want to trigger the event?
• Who do we want to notify?
• How do we want to notify them?
• What text do we want to include in the notification?
• Is this event a Scheduled Call type event? (covered later in the training manual)

It might even be a good idea to create an internal ‘AI Request’ form for your company so you can
get the users requesting the events to give you as much detail as possible. This will allow you to
create their suggested event more quickly and accurately.

Exercise:
Let’s create an event that notifies us when a Customer’s Account Balance exceeds their Credit
Limit Amount. This will be a somewhat simplistic check, as it will not check if the customer has
exceeded their aging credit limit rules. It will purely check if the Current Balance Amount + the
Future Balance Amount is greater than the Credit Limit Amount. All of this data is stored in the
table called ‘deb-master’. This exercise will (briefly) cover how to find the field names we need
to create the filters for the event.

Finding Field names

Refer to the Appendix “Using Proman to find Field Names” if you are unsure of how to find the
appropriate field names to use.

Creating a new event

1. Select the Event Maintenance function and click the [Entry Wizard] mode.
2. On the Create New Event page, select the ‘Design Your Own Event’ option and click [Next]:

© 2008 Document Version So-Easy Education Guide

Page 47 1.0 Commercial in Confidence
Creating and Maintaining Events

3. Select the [Find] mode, highlight the table deb-master and click [Next].

4. In the Notification Method options, select Display Message Box.

Question: Which event initiation method would you select in this case, bearing in mind that
you want to monitor a change in the customer’s balance versus their credit limit? Mark it on
the screenshot below, and select the correct initiation method on your screen:

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 48
 Creating and Maintaining Events

Creating your own filters

Now we have to create our own filters to decide whether this event should be triggered or not.
We need to check if the:
(balance + future-bal) IS GREATER THAN (dr-credit-limit-amount)
Rembering to check also if the new values for balance, future-bal or dr-credit-limit-amount are
different to the old values for these fields!

Here is a suggestion for your filter setup. Have some brief discussion about the setup of these
filters. Do they look okay to you?

Calculated field detail is:

Once your filters are created you can then create some meaningful text in your message box.
Here is a suggested sample output. Setup your message box text as you wish:

© 2008 Document Version So-Easy Education Guide

Page 49 1.0 Commercial in Confidence
Creating and Maintaining Events

The steps remaining to getting this Event up and running are:

1. Test your Event using the ‘Launch’ feature
2. Set the event to a status of ‘Active’
3. With the help of your trainer, decide on a way to trigger the event in your test
system/database
4. Check the Event Log to see your triggered event

Note: We suggest raising a Manual Invoice for a value above the Credit Limit in AR
Transactions to trigger this event. Your trainer will demonstrate how to do this once you are
ready to actually trigger your event to launch.

Work through any problems triggering your event with your trainer. Don’t forget to visit
Customer Maintenance [AR.M001] again to check the displayed Balances and Credit Limit to
verify your event triggered correctly!

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 50
 Creating and Maintaining Events

Greater Than 

© 2008 Document Version So-Easy Education Guide

Page 51 1.0 Commercial in Confidence
Other Alert Intelligence Event Features

Other Alert Intelligence Event Features

Linking Events
In the [Detail] view of Event Maintenance, it is possible to link events together. This means that
when one event is triggered, it can then trigger another event linked to it. You can chain a number
of events together in this way.

Note: Only events that are based on the same table can be linked.

In the screen shot above Event 6 (also for the sales-order table) will be launched if Event 15 is
launched.

Why might you want to do this?

One example is you wish to notify different people in different ways from the one event. Since
only one notification method can be selected per event record. To associate multiple notification
types with an event, create an event for each notification method and then link the events to one
another using the Linked Event ID field.

Tip: To send both plain text and HMTL format notifications, define a 'parent' event for one of
these formats, a 'child' event for the other format, and then enter the ID of the child event in the
Linked Event ID field in the parent event details.

Note:
When linking an event, the first event launches based on its filter criteria and initiation method.
The filters of the second (linked) event are not checked, as linked events are not typically
launched as an individual event.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 52
 Other Alert Intelligence Event Features

Using the Scheduled Call Event Initiation Method

A Scheduled Call is an initiation method that can be used to identify time-based events. For
Example, Purchasing Officers can use a scheduled call to identify overdue purchase order
deliveries and email themselves and/or the supplier.

MENU PATH (VARIOUS)

Alert Intelligence
Preview Scheduled Events (AI E005)
Submit Scheduled Events (AI M004)
Submit Individual Scheduled Event (AI M008)

The time-based events detected by a scheduled call can be processed either manually or
automatically:
1) Manual processing
1. Select the Preview Scheduled Events (AI E005) function.
2. Highlight the relevant scheduled call event and then click [Preview Event].
The master table associated with the event is now scanned to identify all records that meet
the filter criteria of the event.
3. To launch the event for all records in the data grid, click [Process All].
4. To launch the event for selected records, use the [Mark Item] mode first to select the
relevant records and then click [Process Marked].
2) Automatic processing
Scheduled call events can be automatically processed by adding them to a report sequence as
follows:
1. Select the Submit Individual Scheduled Event (AI M008) function
2. Highlight the scheduled event to be processed and click [Submit Event].
3. Highlight the report sequence to which the scheduled event should be added, click
[Select] and confirm the action.
4. To verify that the scheduled event task has been created, select the Maintain Report
Sequences (SYS M175) function and scroll down to the report sequence selected above. The
First Rpt/Program field shows ‘usr-events’ and the full details of the task can be viewed by
clicking [Maintain].

© 2008 Document Version So-Easy Education Guide

Page 53 1.0 Commercial in Confidence
Other Alert Intelligence Event Features

Note: There is also a Submit Scheduled Events (AI M004) function that can be used to submit all
scheduled events associated with a table to a selected report sequence. Access to this function
must be granted by the system administrator. Use this function with caution!! It will submit ALL
‘Scheduled Call’ events associated with a table.

Automatic processing works by using the Batch Queue function in PRONTO-Xi. Just like you
can submit PRONTO-Xi Reports to sequences to run daily, weekly, monthly etc; you can also
submit events to be included in these sequence ‘runs’. If the filter criteria are tested and are true,
the scheduled event will be launched, and the notification method you have selected will do the
rest.

Exercise: Follow the trainer on the screen as they submit an existing Individual Event to a
sequence on the server.
1. Select the Submit Individual Scheduled Event (AI M008) function.
Note that only ‘Scheduled Call’ type Initiation Method events will be displayed here
2. Highlight one of the events and select the [Submit Event] mode.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 54
 Other Alert Intelligence Event Features

In this example we could select the ‘NIGHT’ sequence to have this event checked and
launched once every night.

To ensure the event is only triggered at the appropriate times, you should always test
your scheduled event using the Preview feature before setting it to active!

For further information on these three screens refer to the online reference manual.

© 2008 Document Version So-Easy Education Guide

Page 55 1.0 Commercial in Confidence
Other Alert Intelligence Event Features

Event Subscriptions
There is an ability to view the users notified for email and SMS notification methods other than
using the [Detail] mode in the Event Maintenance function. When a user is ‘Subscribed’ to an
event, it means they are listed as one of the Recipients for that event. Any enquiries on User or
External Subscriptions as described below, are viewing the same recipient list as stored in the
[Detail] mode of the Event Maintenance function:

If the appropriate user security has been set up, each user can view their user and external
subscriptions to email/SMS events using either of the following functions:

MENU PATH (VARIOUS)

Alert Intelligence
User Subscriptions (AI E003)
External Subscriptions (AI E004)

Managing your own Event Subscriptions

It is possible for users (if granted access to AI M002) to manage their own subscriptions to
email/SMS events. They can choose to either subscribe or unsubscribe to relevant events for the
company they are currently logged into.

MENU PATH
Alert Intelligence
My Event Subscriptions (AI M002)

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 56
 Other Alert Intelligence Event Features

Exercise: View these three menu options, and have a try of Unsubscribing and Subscribing to
some events in your company (if there are some email and SMS events active for your company).
Notes:
• Only email and SMS alerts can be subscribed to.
• When you are subscribed to an event you will receive a notification email. You can choose
to unsubscribe yourself from the event by following the hyperlink in the email to ‘My Event
Subscriptions’ and managing your subscriptions there.

Example Email

1. Select the My Event Subscriptions (AI M002) function.

You will see a listing of the events you are currently subscribed to.
2. If you wish to unsubscribe from an event, tick the box next to that event, then click the
[Unsubscribe] button at the bottom of the screen.

3. Next select the [Available Events] button to view other events you are not yet subscribed to.
Other published events are available for you to subscribe to. Events will only be unavailable
if the Event Administrator/creator has applied security restrictions.
4. To subscribe to additional events, tick the relevant event(s) then click the [Subscribe] button.

© 2008 Document Version So-Easy Education Guide

Page 57 1.0 Commercial in Confidence
Other Alert Intelligence Event Features

Icons
Here is a brief explanation of the three clickable icons in the ‘My Event Subscription’ screen:
• The first icon on the right will display notes about the event, providing the administrator has
created them.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 58
 Other Alert Intelligence Event Features

• The second icon, the drill down tool, is used to display the full details of the event in the
Event Details screen. This will be security dependant and will be greyed out if the user is
denied access.

• The third icon lets you know the method of notification. In this example, email.

More information on Event Subscriptions can be found in the PRONTO-Xi Online Help
Manuals.

© 2008 Document Version So-Easy Education Guide

Page 59 1.0 Commercial in Confidence
Other Alert Intelligence Event Features

Manual Joins
This function is further to the ‘Other Table’ option in the field selection area in Defining Filters.
It may be that you wish to setup some other table joins, or edit the ones you have already setup.
This function can be used to manually join tables so fields from more than one table can be used
in the filter definition or notification text of an event.
Note: A manual join can only be made if at least one field in the two tables contains related
information. An Auto-join may be formed if a key field in two tables has the same name in each
table. For example, the stock-master table and the stock-warehouse-detail tables both have a field
titled ‘stock-code’ so these two tables will auto-join.

MENU PATH
Alert Intelligence
Manual Joins (AI M005)

Once the table join exists, an event notification can be created that utilises the information from
both tables.
The Manual Joins screen is shown below.

[Correct] Mode

The above example shows a manual join that exists between the tables:
o sales-order AND
o sales-order-archive
The common field they are joining on is the ‘so-order-no’ field.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 60
 Other Alert Intelligence Event Features

Using the External Call Initiation Method

The external call initiation method is used to launch an event from a customised program or
PRONTO-Xi Screen Customiser. The circumstances under which the event is launched is
determined solely by the logic in the calling program, rather than an action on the database. The
external call initiation method allows the PRONTO-4GL developer to take advantage of the
standard notification infrastructure provided by the Alert Intelligence module, that is, sending an
email message or SMS alert, displaying a message box, starting a workflow package and so on.
Exploring the setup of an Externally called event is outside the scope of this course. Please refer
to the PRONTO-Xi Online Help Manuals for more information and some tips on setting up
Externally Called events, and how to link to them using PRONTO-Xi Screen Customiser.

Example Integration of Alert Intelligence with the Screen Customiser

PRONTO-Xi Screen Customiser can, for example, utilise the Alert Intelligence notification
infrastructure to display a message box if the user enters an invalid or unexpected value in a field.
A child event could be linked to the above event to also notify relevant persons via email or SMS
of what has occurred, for example, a sale below minimum GP%.

SMS Notification Events

Setting up SMS Events is no different to setting up message box or email notifications. You have
to be mindful of the amount of text you enter, and you definitely have to TEST
THOROUGHLY before setting an SMS notification event to ‘Active’!

It is highly recommended that an SMS notification event first be run as an email notification
event for testing purposes. Sending emails is free, sending an SMS is not!

As mentioned in the Event Administration Setup section, activating the SMS service in
PRONTO-Xi requires consultation with your Local Pronto Software Support Centre.

External Processes / Workflow / Tasks

As mentioned in the beginning of this manual, setting up of External Processes / Workflow and
Tasks is beyond the scope of this course.

Using the Advanced Edit Feature

As mentioned in the beginning of this manual, using the Advanced Edit feature is beyond the
scope of this course.

© 2008 Document Version So-Easy Education Guide

Page 61 1.0 Commercial in Confidence
Appendix

Appendix
Reference Guide for Screen Fields and Buttons
Event Administration Setup Screen

- Data Grid fields

Field Description
SMS Email – Encryption Control
The following two fields are used to activate the SMS messaging service
hosted by Pronto Software. To use this service, contact your local Pronto
Support Centre to obtain the keys that need to be entered here.
SMS transmission via a third-party message service requires customer-
specific customisation. Contact your local Pronto Support Centre for
assistance or to obtain a Software Development Kit for customising
PRONTO-Xi.
Email Domain Enter the public key allocated to this PRONTO-Xi site.
Password
Private Key Enter the private key allocated to this PRONTO-Xi site.
Message Control
Display name for email Enter the name to be displayed in the ‘From’ field of the email.
notifications Note: This option is not supported when using a MAPI-based mail client
in conjunction with a PRONTO-Xi Windows workstation client.
Reply (return address) Enter an address to which an email or SMS that has failed to reach its
for failed email/SMS intended recipient should be sent.
Display name for reply Enter the name to be displayed in the ‘From’ field of the email sent when
to address an email or SMS could not be delivered.
Note: This option is not supported when using a MAPI-based mail client
in conjunction with a PRONTO-Xi Windows workstation client.
Batch queue for Specify a queue for batched emails. The batch queue can be a value in
batched email/SMS the range ‘0’ -‘9’ or ‘A’ -‘J’.
Automatically append Specify whether or not a drill-back to the event that launched the email
event identifier to is to be appended to the email.
email

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 62
 Appendix

Event Maintenance Screen

- Data Grid fields

Here is a description of each of the fields in the Data Grid and what they represent. Important
points are highlighted in bold.

Field Description
Identifier A number that uniquely identifies the event. As events are created, they are
assigned numbers in sequential order.
Company Displays the company that the event has been created for, or blank if the event
is configured to launch for all companies.
The company to associate with the event can be changed in this screen.
Status Displays the current status of the event. The status can be changed in this
field, or by selecting the [Detail] mode and changing the status in the Event
Detail area.
The following statuses are available:
A Active – An event must be active for it to work! Don’t forget to
‘Activate’ your event after testing it!
I Inactive
T Testing – in testing mode your event will not do anything other than
write to the Event Log file. If your event isn’t working when you
expect it to, always check that you have set it to Active before
investigating further.
Description of Displays the event description. The description can be changed in this field, or
Event by selecting the [Detail] mode and changing the Description field.
Method Indicates the notification method configured for the event.
The following notification methods are available:
E Email Notification
D Message Box
S Short Message Service (SMS)
F Fax Cover Page
W Start Workflow Package
P Launch Program/Task
L Event Log Only
Master Table Displays the database table that the event is based on.
Insert Indicates whether or not the event is configured to launch after an ‘insert’ action
occurs in the selected database table. That is, a new database record is created.
Update Indicates whether or not the event is configured to launch after an ‘update’
action occurs in the selected database table. That is, an existing database record
is updated.
Delete Indicates whether or not the event is configured to launch after a ‘delete’ action
occurs in the selected database table. That is, a database record is deleted.
Scheduled Indicates whether or not the event is configured to launch based on a scheduled

© 2008 Document Version So-Easy Education Guide

Page 63 1.0 Commercial in Confidence
Appendix

call. Scheduled events are called using PRONTO-Xi’s Batch Queue

Administration system. These events are time-based, e.g. Alert me if a purchase
is overdue as of Today.
External Indicates whether or not the event is configured to launch based on a call from
an external program.
External Indicates whether or not the event filters are applied when the event is launched
Trigger Apply by an external program.
Filter
Active From Displays the date from which the event is active and will launch.
Active To Displays the date after which the event is no longer active and will not launch.
Linked Event Displays the number of the linked event that is triggered when this event is
launched.
Note: If there are no linked events, a zero (0) is displayed in this column.
Module Module (& Function) code user must have access to, to subscribe to this event
Function (Module &) Function code user must have access to, to subscribe to this event
Log Recipients Indicates whether or not the addresses of the recipients of the notification
associated with this event are to be written to a log. Logging is always useful
for auditing purposes in the future
Last Modified Displays the date and time that the event was last modified.
Owner Displays the login ID of the user who created or last modified the event.

- Mode Buttons
The [Find], [Correct] and [Remove] modes are available for use on records in this data screen.
The following modes are also available. Important points are highlighted in bold.

Mode Description
Entry Wizard Accesses the Event Entry Wizard allowing an event to be created from either a
pre-packaged event template, or a user-defined event.
This is a great feature to get started with , and has many useful Pre-
Packaged Events for you to customise.
Duplicate Duplicates the highlighted event. Enter the required identifier, company, status
and description for the new event.
Detail Use this mode to configure the highlighted event. This training course will
review this screen in depth.
This is the primary mode button you will use to modify existing events.
Launch Manually launches the highlighted event. This allows the event to be tested
before being set to the ‘Active’ status in the Event Details screen.
Note: This is a highly recommended step, as it is easy when learning AI to
‘spam’ yourself if your event filters are not setup correctly.
Advanced Edit Displays the PRONTO-4GL data trigger code so that it can viewed or edited
directly. A Terminal Mode window opens in which the code for the event can be
edited. The environment variable ‘EDIT’ must be set for this feature to work.
Note: Editing the data trigger code is an advanced feature and assumes
programming knowledge. It is beyond the scope of this course.
Generate Generates and compiles the PRONTO-4GL data trigger code for all existing

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 64
 Appendix

events. This code generation must be performed after adding a new event or
modifying an existing one.
If you have modified an event and exit this data grid, PRONTO-Xi will
automatically ‘Generate’ the data trigger code for you – this mode button
makes it possible for you to force a generation of the data trigger code.

Special Note for Windows Sites !!

When PRONTO-Xi has been installed on a Windows server, it may not be
possible for Windows workstation clients to execute the regenerated code because
the operating system on the client has cached and locked the previous version of
the compiled library. No error or warning message is given - the new or revised
event will simply not be available. To resolve this issue, it is necessary to exit and
restart the PRONTO-Xi client and then select the [Generate] mode to regenerate
the library.
Owner Allows ownership of the highlighted event to be assigned to a different
PRONTO-Xi user.
If you do not have access to the AI S001 (Access All Events) security function,
you will only be able to see events that you are the ‘Owner’ of.
Note: This mode is only accessible to users that have been granted the AI S001
(Access all Events) security function.

Event Message Box Maintenance Screen

- Data Grid fields

Field Description
Message Box Enter the title to be displayed in the message box.
Title
Text Enter the text to be displayed in the message box. This can be a combination
of plain text, and information from the database by picking fields to include
in the message.
Field Picker Add database fields to the text in the message box. The data
in the field will be included in the message when the event is
launched. The following modes are available:
Append Appends the highlighted field to the last line
Field of text in the message.
New/Old Toggles between displaying the new (n.) and
old (o.) values for the fields in the current
table.
Other Table Opens the Table Picker screen which is used to
select a different table in the dictionary.
Note: Access to certain dictionary tables, for
example payroll-related tables, may have
been restricted by the PRONTO-Xi system
administrator.
Calc. or Enter data from the Value / Field / Function
Function column in the Filters page of the Wizard:

© 2008 Document Version So-Easy Education Guide

Page 65 1.0 Commercial in Confidence
Appendix

• Today()
• Login-id()
• Time()
• Program()
• Company-name()
• Filter-value(1) - Filter-value(5)
For further information refer to the
‘Understanding Event Filters’ section.
Hyperlink Specify (if required) a link to a document, website or directory to be included
in the message box.
Text to Display Enter the ‘clickable’ text to be shown for the hyperlink in the message box.
Icons Specify the appropriate icon to be included in the message box. For example,
if the message is informational only, then one of the two blue icons with the
“i” (Information) symbol would be appropriate.
Specify the required icon to use.
No icon Specifies that no icon is shown in the message box.
User Icon To use a different icon in the message box instead of the
Path default icons available, select this option and enter the path
to the icon.
Tip: Press F2 (Lookup Help) to open the Choose File dialog
box and navigate to the required file. The *.gif and *.jpg
image file formats can be used.
Preview Displays a preview of the message box.

Manual Event Launch Screen

- Data Grid fields

Field Description
Launch Type
Launch Select the method to use to launch the event:
Method
Sample Test Use this method to simulate the launching of a specified event,
Data or all events associated with a specified table, without actually
changing values in the database or launching the event.
Select the initiation methods to test, enter ‘0’ in the Event
Identifier field to test all events in a table, or enter the ID of a
specific event to test, then enter the test data in the lower half
of the screen.
Note: The initiation method options and the ID = ‘0’ (Test all
Events in Table) option is only available to users who have
been granted the AI S001 (Access all Events) security function.
This method will generate a test program to determine whether
or not the event would have launched based on the entered test
values and as if the changes were actually occurring in the
database.
A dialog is displayed showing which of the selected initiation

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 66
 Appendix

methods launched successfully.

Scheduled Call A scheduled call is used to identify time-based events. It scans
the master table associated with the event to identify records
that meet the filter criteria.
Use this method to test that the scheduled call selects and/or
processes the correct records of the table on which the event is
based.
Event Enter the ID of the event to be launched, or
Identifier press F2 (Lookup Help) to access a list of all
events where Scheduled Call (in the Event
Initiated options) is selected.
Show Select this option to display a progress window
Progress with a progress bar while the relevant table is
being scanned.
Preview Select this option to display all matching
Results records in a data grid in a preview window.
Specific records can then be selected for
processing. Refer to the ‘Preview Scheduled
Events’ section for a description of this
preview window and its modes.
If this option is deselected, the relevant event
for all matching records is launched
immediately.
Warning: To avoid generating large numbers
of unnecessary notifications, only turn this
option off once the filter criteria for the
associated event have been thoroughly tested
and found to be reliable.
Max. Enter the maximum number of records to be
Sample processed in the master table associated with
the event, or accept the default value ‘0’ to
process the entire table.
External Call Tests that an external program launches the specified event.
Enter the required event identifier.
The filters specified for the event will not be tested when this
method is used.
Event Enter the ID of the event to be launched, or
Identifier press F2 (Lookup Help) to access a list of all
events where External Call (in the Event
Initiated options) is selected.
Actual Table Functions in a similar way to the Sample Test Data method,
Data except that this test will be performed in the actual database on
real data.
Note: Care should be taken when using this method. This
launch method is only available to users who have been
granted the AI S001 (Access all Events) security function.
Launch Events based on Table
Table Name Enter the name of the master table on which to base the event. Press F2 (Lookup
Help) to access the Master Table data grid and select from the available list.

© 2008 Document Version So-Easy Education Guide

Page 67 1.0 Commercial in Confidence
Appendix

Note: Access to certain dictionary tables, for example payroll-related tables, may
have been restricted by the PRONTO-Xi system administrator.
Sample Data for Field Filters
Test Field / Note: These fields are only available if the Sample Test Data launch method is
Filter Value selected.
1-10
Field Enter the name of the field to test. Press F2 (Lookup Help)
to access a Field Picker data grid and select from the available
list.
The [Select] mode is available on this screen. The
following mode is also available:
New/Old Use this mode to toggle between the new (n.)
and old (o.) values for the fields in the
current table.
Test Value Enter a test value to test against the data in the
corresponding field.

Event and Recipient Log Screen

- Data Grid fields
A description of the data grid columns and mode button functionality is given below:

Column Description
Day The day that the event launched.
Launch Date/Time The date and time that the event launched.
Identifier The number of the event.
Description of Event The name of the event.
Company The name of the company in which the event was launched.
Triggered by User The user ID of the person who performed the action that triggered the
event.
Triggered by The program that triggered the event.
Program
Log Text The email, message box, SMS, fax or log text that was entered for the
event via the Event Details screen.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 68
 Appendix

- Mode Buttons
The [Find] mode is available for use on rows in this data grid. The following modes are also
available:

Mode Description
View Recipient Review the list of people who received the notification. The Email/SMS/Fax Log for
Event screen shows the company, recipient and recipient description/name.
The [Next-scr], [Prev-scr], [Next] and [Prev] modes are available for use on
rows in this data grid.
View Filters Review the filters used in the event. The Event Log Filters screen shows the
company, database table, field name, operator (comparison type), value and
relationship.
The [Next-scr], [Prev-scr], [Next] and [Prev] modes are available for use on
rows in this data grid.
View Text Review the text used for the event. The Text Log for Event screen shows the text
details in code format. Use the [View Text] mode to view this information in
rendered format (as would appear to the recipients for this event).
Detail Display full details of the highlighted event.

Purge Event Log Screen

- Form Fields
Field Description
Event Identifier Enter a range of events for which log entries are to be purged, or accept
From/To the default values to select all events.
Purge Event Log up to Enter a cut-off date for the purge operation. Log entries with dates prior
and Including to and including that date are considered for purging.
Purge Event Log for Enter the company code for which log entries are to be purged, or press
Company Code F2 (Lookup Help) to access a list of company codes.
Note: Only those companies for which the current user has been granted
the AI M001 (Event Maintenance) function can be selected.

Event Details Screen

- Fields and Buttons

Field Description
Event Details
Event (Display only) Shows the unique identifier for the event.
Identifier
Description Enter a description for the event.
Event Based (Display only) Shows the database table on which the event is based.

© 2008 Document Version So-Easy Education Guide

Page 69 1.0 Commercial in Confidence
Appendix

on Table
Notification Select the type of notification to be given when the event is launched.
Method Note: Only one notification method can be selected per event record. To
associate multiple notification types with an event, create an event for each
notification method and then link the events to one another using the Linked
Event ID field.
Email Select this option to send an email to selected recipients when
Notification the event is launched.
After selecting this option, specify whether the email should
be sent immediately (Direct), or via a Batch Queue (Batch) in
the Method options.
Tip: The Batch Queue to use to send batched emails is
specified in the ‘Event Administration Setup’ function.
Batching the sending of emails (if this is the notification
method) is a great idea, otherwise the user that (perhaps
unknowingly) initiated the event, will have to wait while the
server sends the email.
Message Box Select this option to display a message box on the screen of
the user whose action caused the event to be launched.
If the event will be launched via an external call, specify the
value to be returned to the calling program when the user
acknowledges the message box by selecting from the
following Exit Status options:
OK Returns the value ‘0’ to the calling program.
Fail Returns the value ‘1’ to the calling program.
Tip: Select this option if this event will be
associated in the Screen Customiser with an after-
accept trigger on a field and the user is required to
re-enter the value when the message box is
displayed.
Fax Cover Select this option to send a one-page fax to selected recipients
Page when the event is launched.
Short Message Select this option to send an SMS to selected recipients when
Service (SMS) the event is launched. The notification is first sent as an email
to the SMS server and then forwarded as an SMS to the
relevant mobile phones.
After selecting this option, specify whether the SMS should
be sent immediately (Direct), or via a Batch Queue (Batch) in
the Method options.
Tip: The Batch Queue to use to send batched emails (for
SMS) can be specified in the ‘Event Administration Setup’
function.
Start Select this option to start a workflow defined in the
Workflow Workflow module when the event is launched.
Package For full details refer to the Workflow manual.
Launch Select this option to launch an external program, or create a
Program/ Task task in the Task Intelligence module, when the event is
launched.
Note: When this option is selected, ensure that the workflow

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 70
 Appendix

details, or program/task details are specified via the

[Workflow/Program] button at the bottom right of this screen.
Note: This is beyond the scope of this course, and is covered
in the Task Intelligence Training Manual.
Event Log Select this option to only write an entry to the event log when
Only the event occurs. The log entry includes time and date
launched, intended recipients, and the notification text.
Event logs can be viewed using the ‘Event Log’ and
‘Recipient Log’ functions.
Event Initiated Specify the types of actions that will initiate the event:
After Insert Select this option to configure the event to be launched after
an ‘insert’ action occurs in the selected database table. That
is, a new database record is created.
After Update Select this option to configure the event to be launched after
an ‘update’ action occurs in the selected database table. That
is, an existing database record is updated.
After Delete Select this option to configure the event to be launched after a
‘delete’ action occurs in the selected database table. That is, a
database record is deleted.
Scheduled Call Select this option to configure the event to be launched when
a time-related criterion is applied to the data in the selected
database table, for example an order or delivery being
overdue.
For further information refer to the ‘Using the Scheduled Call
Event Initiation Method’ section.
External Call Select this option to configure the event to be launched based
on a call from an external program.
For further information refer to the ‘Using the External Call
Initiation Method’ section.
Apply Filter Select this option if the filter criteria are to be applied when
this event is initiated via an external call.
Parameters Displays the command line parameters that the external
program must pass when initiating this event.
Linked Event Enter the ID of an event to launch when the current event is launched, or ‘0’ if
ID this event is not to be linked to another event. Press F2 (Lookup Help) to access
the ‘Events for Table’ data grid and select from the available list.
Note: Only events that are based on the same table can be linked.
When linking an event, the first event launches. The filters of the second (linked)
event are not checked, as linked events are not typically launched as an
individual event.
Linked Events Accesses a table listing all events linked to the current event.
Subscription Enter the function that users need security access to in order to see this event in
Security the Available Events view of the Event Maintenance function.
This option is only available for the email and SMS notification methods.
Note: If this field is left blank, the event is unsecured and all users can subscribe
to the event.

© 2008 Document Version So-Easy Education Guide

Page 71 1.0 Commercial in Confidence
Appendix

Event Status Specify the required status for the event:

• Active
Select this option to make the event active in the PRONTO-Xi
system. That is, the event will launch when all of the conditions
defined for the event are met.
• Inactive
Indicates that the event exists in the system but is no longer required.
• Testing
Select this option if you need to investigate an event that is not
working as expected. It will only write a log of what would happen if
the event was launched. An event with this status cannot be
subscribed to in the ‘My Event Subscriptions’ function.
Active The event will be active in the PRONTO-Xi system between the dates specified
From/To in these fields.
Notes Enter any additional information relating to this event. The entered text is for
informational purposes only.
Event Log Review details of each launch of the current event. The details shown include the
company, date and time launched, who launched the event, which program was
running when the event was launched, and log text. The [View Recipient], [View
Filters] and [View Text] modes provide additional details relating to the
currently selected event log entry.
Define the actual condition(s) that will launch this event.
Define Filters Maintain filter definition logic used for this event.
For further information on defining filters refer to the ‘Defining Filters’ section.
Maintain the email, message box, SMS, fax or log text for this event
Attachments Maintain email attachment details for this event. Enter the full path and file
name for the attachment.
The particular browse facility provided when pressing F2 (Lookup Help)
depends on whether PRONTO-Xi has been installed on a UNIX/Linux or
Windows server.
Define Text Define the message that is displayed in the notification. This option is available
for all notification methods except Start Workflow Package and Launch
Program/Task.
Tip: The email editor supports basic HTML code, for example, <font>,
<colour> and <size> tags. For further information on HTML, refer to the
numerous HTML tutorials available on the Web, for example, the W3 Schools
tutorial: http://www.w3schools.com/html/default.asp.
Define this event’s Email/SMS/Fax recipients
Log Recipients Select this option to record the addresses that the notification was sent to.
Note: This does not verify that the notification arrived at the intended address.
Dynamic Use this option to dynamically select the recipients of the notification based on
the specific data that launched the event.
Example:
Commonly in a company there will be more than one Credit Administrator and
they will be territory based. Therefore, either multiple events with different
territories could be set up or this option used to set up one event with a
conditional email on top of conditional filters.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 72
 Appendix

Specify the recipient contact details (email address, mobile phone number or fax
number) based on the dynamic email type.
The following dynamic recipient selection options are available:
F Field Value
Selects the recipient of the notification based on the results of a logical
operation performed on a selected field (or calculated field).
For example, the following two rules could be entered to define the
recipient based on the territory field on the sales order:
• n.so-territory-code EQUAL TO “MEL”
email address = [email protected]
• n.so-territory-code NOT EQUAL TO “MEL”
email address = [email protected]
C Customer
Obtains the recipient details by looking up a customer account via a
specified field (or calculated field), for example, the ‘so-cust-code’ field
in the ‘sales-order’ table.
S Supplier
Obtains the recipient details by looking up a supplier account via a
specified field (or calculated field), for example, the ‘cre-accountcode’
field in the ‘purchase-order’ table.
M CRM
Obtains the recipient details by looking up a CRM account in the
Customer Relationship Management module via a specified field (or
calculated field).
V Engineer
Obtains the recipient details by looking up an engineer account in the
Service module via a specified field (or calculated field).
E Rep
Obtains the recipient details by looking up a representative account via a
specified field (or calculated field), for example, the ‘so-rep-code’ field
in the ‘sales-order’ table.
T Task
Obtains the recipient details by looking up the PRONTO-Xi user
account specified in the ‘tm-allocated-to’ field in the ‘task-master’ table.
P Employee
Obtains the recipient details by looking up an employee account in the
Human Resource Management module via a specified field (or
calculated field).
Z Custom
Use this option to select the recipient by passing the value of a specified
field (or calculated field) to the public exportable procedure ‘clib801-
determine-dynamic-custom-address’.
Contact your local Pronto Support Centre for assistance or to obtain a
Software Development Kit for customising PRONTO-Xi.
Code Based Use this option to specify the recipients of the notification by entering specific
account, role or representative codes. The contact details (email address, mobile
phone number or fax number) are obtained via the relevant master record of the

© 2008 Document Version So-Easy Education Guide

Page 73 1.0 Commercial in Confidence
Appendix

specified account.
The following code-based recipient selection options are available:
C Customer
Use this option to send the notification to a selected customer by
entering their customer account code.
S Supplier
Use this option to send the notification to a selected supplier by entering
their supplier account code.
M CRM Account
Use this option to send the notification to a selected contact stored in the
Customer Relationship Management module by entering their account
code.
R Security Role
Use this option to send the notification to all PRONTO-Xi users who
have been granted a selected security role.
E Representative Code
Use this option to send the notification to a selected representative by
entering their representative code. The contact details are obtained via
the login ID stored against that representative. If an address is specified
in the Email Address column for that login ID in the User Access
Control (SYS M195) function, then that email address is used.
P Use this option to send the notification to a selected employee by
entering their employee number, as maintained in the Human Resource
Management module.
User Specify the PRONTO-Xi user ID of the intended recipient.
External Specify the contact details (email address, mobile phone number or fax number)
of a recipient who is external to the PRONTO-Xi system.
Define workflow or external program/task call
Workflow/ Specify the workflow package, external program or task to call for this event.
Program/ Task This topic is outside the scope of this course. Calling Workflows or External
Programs is an advanced feature of PRONTO-Xi. Please contact your local
Pronto Support Centre for assistance or to obtain a Software Development Kit
for customising PRONTO-Xi..
Calling tasks is covered in the Task Intelligence Training Manual.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 74
 Appendix

Event Email Maintenance Screen

- Fields and Buttons

Field Description
Subject Enter the email notification subject. This text is used as the subject line in the
email.
Email Enter the content of the email to be sent. This can be a combination of plain text,
and information from the database by picking fields to include in the email.
Example:
The following simple example is based on the ‘Service – New Call’ template:
Attention: New Service Call
Call Number: {n.call-no}
Customer: {n.customer-code} {shortname}
Caller: {n.call-name-of-caller} Phone: {call-phone-of-caller}
Service Centre: {n.call-service-centre}
Tip: The email editor supports basic HTML code, for example, <font>, <colour>
and <size> tags. For further information on HTML, refer to the numerous HTML
tutorials available on the Web, for example, the W3 Schools tutorial:
http://www.w3schools.com/html/default.asp.
Field Picker Add database fields to the email. The data in the field will be
included in the email when the event is launched. The
following modes are available:
Append Appends the highlighted field to the last line
Field of text in the message.
New/Old Toggles between displaying the new (n.) and
old (o.) values for the fields in the current
table.
Other Table Opens the Table Picker screen which is used to
select a different table in the dictionary.
Note: Access to certain dictionary tables, for
example payroll-related tables, may have
been restricted by the PRONTO-Xi system
administrator.
Calc. or Enter data from the Value / Field / Function
Function column in the Filters page of the Wizard:
• Today()
• Login-id()
• Time()
• Program()
• Company-name()
• Filter-value(1) - Filter-value(5)
Email Editor Edit the content of the email in a simple word processor.
Preview Displays a preview of the email in a pop-up window.
Email Format Select whether the email is to be sent in plain text or HTML

© 2008 Document Version So-Easy Education Guide

Page 75 1.0 Commercial in Confidence
Appendix

format.
Drill-back functionality is not available for plain text
emails.
Tip: To send both plain text and HMTL format notifications,
define a ‘parent’ event for one of these formats, a ‘child’
event for the other format, and then enter the ID of the child
event in the Linked Event ID field in the parent event details.

Event Filter Maintenance Screen

- Fields and Buttons

Field Description
Event Enter a name for the event.
Description
Filters
Field Name Enter the name of the field to apply the filter to, and prefix the field name by
either ‘o.’ (old) or ‘n.’ (new) if the value of the field is to be tested before or after
the database record is updated respectively.
Press F2 (Lookup Help) to access a Field Picker table displaying a list of all fields
in the database table selected in Step 2 of the wizard. A value greater than 1 in
the Occurs column indicates that the field is an array of the indicated number of
elements.
The following modes are available in this screen:
Select Selects the highlighted entry and closes the window.
New/Old Use this mode to toggle between the new (n.) and old (o.)
values for the fields in the current table.
Other Table Displays a Table Picker window listing all database tables. Use
this mode to define a filter based on a field in a different table
to the one selected in Step 2 of the wizard.
Note: Access to certain dictionary tables, for example
payroll-related tables, may have been restricted by the
PRONTO-Xi system administrator.
Note: If you select a field from a table that does not have a
‘join’ relationship with the master table, a message is
displayed prompting to perform a ‘manual join’.
Calculation Use this mode to create a calculated field for use in the event.
Comparison Specify the comparison operation to be performed on the entries in the Field
Name column (Field1) and Value/Field/Function column (Field2) of this row:
EQUAL TO Use this option to test whether the value in Field1 is equal to
the value in Field2.
NOT EQUAL Use this option to test whether the value in Field1 is not equal
TO to value in Field2.
GREATER Use this option to test whether the value in Field1 is greater
THAN than value in Field2.
GREATER Use this option to test whether the value in Field1 is greater

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 76
 Appendix

OR EQUAL than or equal to value in Field2.

TO
LESS THAN Use this option to test whether the value in Field1 is less than
value in Field2.
LESS OR Use this option to test whether the value in Field1 is less than
EQUAL TO or equal to value in Field2.
BETWEEN Use this option to test whether the value in Field1 lies between
the two comma-separated limit values specified in Field2. The
two limit values are included in the range.
NOT Use this option to test whether the value in Field1 does not lie
BETWEEN between the two comma-separated limit values specified in
Field2.
CONTAINS Use this option to test whether the value in Field1 contains the
sequence of characters specified in Field2.
Great for partial searching of Alpha strings
DOES NOT Use this option to test whether the value in Field1 does not
CONTAIN contain the sequence of characters specified in Field2.
IN Use this option to test whether the value in Field1 matches one
of the multiple, comma-separated values specified in Field2.
Values tested must be separated by commas!

NOT IN Use this option to test whether the value in Field1 does not
match one of the multiple, comma-separated values
specified in Field2.
Value / Field / Enter the value to be used for comparison. Press F2 (Lookup Help) to access the
Function following options:
Field Help Select this option to access the ‘Field Picker’ table. The following
modes are available:
Select Use this mode to select the highlighted field.
New/Old Use this mode to toggle between the new (n.)
and old (o.) values for the fields in the current
table.
Function Select this option to access the following functions:
Help
Today() Substitutes for the current date when the filter
criterion is tested.
Login-id() Substitutes for the login ID of the current
PRONTO-Xi users when the filter criterion is
tested.
Time() Substitutes for the current time when the filter
criterion is tested.
Program() Substitutes for the name of the currently
running PRONTO-Xi program when the filter
criterion is tested.

© 2008 Document Version So-Easy Education Guide

Page 77 1.0 Commercial in Confidence
Appendix

Company- Substitutes for the company code when the

name() filter criterion is tested.

Manual Joins Screen

- Data grid Fields

Field Description
Seq no. A unique numeric ID assigned to each entry created in this data grid.
Note: The number range 1 to 99 is reserved for manual join definitions
supplied by Pronto Software.
Table From Displays the name of the table to join from.
Table To Displays the name of the table to join to.
Field From Displays the name of the field to join from. Up to three fields can be used in
the join.
Field To Displays the name of the field to join to. Up to three fields can be used in
the join.
Table Intermediate Displays the name of an intermediate table to be used in a two-level join.
Fields Intermediate Displays the name of the field in the intermediate table to be used in the
two-level join. Up to three fields can be used in the join.

- Mode Buttons
The [Find], and [Remove] modes are available for use on rows in this data grid. The following
modes are also available.

Mode Description
Entry Displays a Manual Joins dialog box for entering the information in the data grid
columns described above.
Correct Displays a Manual Joins dialog box for correcting the information in the currently
highlighted row.
Note: Table entries with a sequence number in the range 1 to 99 can not be
edited.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 78
 Appendix

My Event Subscriptions Screen

- Fields and Buttons

Button Description
Available Events Displays a list of all events that that the currently logged in PRONTO-Xi
user is not currently subscribed to.
Subscribed Events Displays the list of events that you are currently subscribed to.
Event Notification Displays the list of available events or subscribed events based on the
List current view (that is, available events or subscribed events).
The icon to the right of the event name indicates the type of notification that
is associated with the event.
Subscribe / Toggles between subscribe and unsubscribe based on the current view (that
Unsubscribe is, available events or subscribed events).
Select the event(s) that your subscription status is to be changed for, and
then click either [Unsubscribe] or [Subscribe].
An email or SMS notification will be sent confirming that the event has
been subscribed or unsubscribed.

© 2008 Document Version So-Easy Education Guide

Page 79 1.0 Commercial in Confidence
Appendix

Using Proman to Find Field Names

So we have an idea of the event we want to create, but we need to know the field names relevant
to our event so that we can set up our filter correctly. Proman is a PRONTO-Xi tool that allows
you to search through the database tables directly, reading field names as you go.

This will be a brief run through as using Proman is covered in more depth in the System
Administration training manual.

How do we even know which table to start looking at? Let’s go to Customer Maintenance
[AR.M001] to get this information. [Find] the customer “AI-TESTCUS”, and once the details are
displayed on the screen, press [F9].
You will see a variety of information presented here. What we are interested in is the information
stored next to the ‘PRIMARY’ title. This denotes the database table name we need to look into to
find the field names for:
• Current Balance
• Future Balance
• Credit Limit

• To launch Proman, whilst in a PRONTO-Xi session, Press [F3] then [F2] and then either:
a) Click on the ‘Proman’ option if ones exists OR

b) Click on ‘Command’ and type in ‘Proman’

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 80
 Appendix

You should be presented with a screen similar to this.

[Browse] mode

• Select the [Browse] mode.

• Next click the [Find] button and search for the ‘deb-master’ table (earlier versions of
Proman may look slightly different to this, your trainer will talk you through what to do if
this is the case):

• Once you have found the ‘deb-master’ table and it is highlighted, click the [Browse] button
again to view the data in the table – it should look something like this:

© 2008 Document Version So-Easy Education Guide

Page 81 1.0 Commercial in Confidence
Appendix

• Use [Find] again to find our test customer ‘AI-TESTCUS’ and then click the [Screen]
mode. The first screen view you will see should look like this. Click the [Title] mode to get
the true field names displayed (see next screenshot):

We can now see the three field names we will use in our filters:
balance
future-bal
dr-credit-limit-amount

• Escape out of Proman to return to the Event Maintenance function.

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 82
 Appendix

Product Brief

© 2008 Document Version So-Easy Education Guide

Page 83 1.0 Commercial in Confidence
Appendix

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 84
 Appendix

List of Available Pre-Packaged Event Templates

A collection of templates based on real-life business scenarios has been included with the Alert
Intelligence module as a starting point for working with and understanding events. These
templates can be accessed by choosing the Pre-Packaged Event Template option on the first page
of the Event Entry Wizard.
Many templates can be used as-is with no modification, however some will require user input, for
example to specify a threshold value or percentage, before they can be used.
The available templates are summarised in the following table. Click on the template name for
detailed information.

Event Category Template Name

Time-based events Accounts Receivable – Follow Up

Accounts Receivable – Overdue Invoices

Work Order – Production Overdue

Purchase Order – Overdue Delivery - Internal

Purchase Order – Overdue Delivery - Supplier

Purchase Shipment – Overdue Delivery - Internal

Payroll – Birthday Notice

Approvals / authorisations Accounts Payable – Invoice Authorised

Accounts Payable – Invoice Requires Authorisation

Accounts Payable – Payment Approved

Accounts Payable – Payment Requires Approval

Sales order / purchase order Purchase Requisition – Created

tracking
Purchase Shipment – Change to Arrival Date

Sales Order – Audit Trail – Price Override

Sales Order “Credit Hold”

Sales Order – Despatch Advice

Sales Order Line – Under Minimum GP%

Sales Order “On Hold” – Customer Alert

Sales Order – Under Minimum GP%

Unusual transactions or Accounts Payable – Unusual Transaction Amount

postings
General Ledger – Unusual Account Balance

© 2008 Document Version So-Easy Education Guide

Page 85 1.0 Commercial in Confidence
Appendix

Inventory Average Cost Change

CRM CRM – Account Activity

CRM – Lead Conversion to Opportunity

CRM – Opportunity Lost

Inventory management Inventory Levels – Below Minimum

Inventory Supercession

Warehouse Management – Dedicated Location – Zero Stock

Project / service management Work Order – Production Completed

Project – Actuals as a Percentage of Budget

Service – New Call

Service – Notify Engineer

Service – Finished Calls - Not Invoiced

Supplier master changes Accounts Payable – Banking Details Changed

Accounts Payable – Payment Type Changed

Full details of these events are available in the PRONTO-Xi Online Help Manuals

So-Easy Education Guide Document Version © 2008

Commercial in Confidence 1.0 Page 86