The following list describes requirements and known limitations of the alert functionality:
Alerts require that you use Portal Interface with Internet Explorer 5.5 or 6.0. Netscape support is not currently available.
You can define alerts only on applications created in Mobile Web Studio; that is, you cannot define alerts on personal applications that are created in Portal Interface.
To define alerts on an application, you must select the Alert option on the Presentation tab when you save the application in Mobile Web Studio.
Once the Alert option is selected and users set rules on that application in Portal Interface, removing (unselecting) the Alert option on the application in Mobile Web Studio has no effect. That is, you cannot roll back alerts that have been defined on an application by existing users.
The Portal Interface alert capability uses the agent functionality of Mobile Web Studio. After an alert is defined on an application, an agent is created on the application by a user or by defining a schedule in the Alerts tab of MyInfo functionality. An agent is created in the background with the user’s name. If an agent exists in Mobile Web Studio with the same name as a user, the existing Mobile Web Studio agent is overwritten.
When Portal Interface users who have defined alert rules or schedules are deleted or disabled in Mobile Web Studio the administrator should delete or disable the operation to remove the alert agent associated with the user if one exists.
Creating alerts
This example procedure shows you how to create an alert in Mobile Web Studio.
Use the sample database application (sampledb) included with the product.
Log in to Mobile Web Studio.
Select Applications from the Build menu on the left pane.
Click New to access the Application Builder.
When the Application Builder displays, click the down arrow to the right of the Add button and select Database Element.
For this example, when the Mobile Web Studio – New Element window appears, select Connection Cache.
Complete the remaining fields:
Conn Cache Name – name of the connection cache for the sample database; for this example:
sampledb
SQL Query String – enter this SQL statement:
select c.lname, p.name, si.quantity, si.id, si.prod_id from customer c, sales_order s, sales_order_items si, product p where c.id = s.cust_id and s.id = si.id and si.prod_id = p.id
Click Preview to see the data that corresponds to the SQL query you entered.
Click Next.
On the next two windows (Define, and Filter), click Next.
In the Window Preview, enter Sales
Update
for the Element Name, then click Finish.
In the Application Builder, click Save and complete these options on the Web Studio – New Application Finish window:
Content tab – enter Sales
Update
for the application name.
Roles tab – click Add All to add all roles to the Assigned Roles list.
Presentation tab – select Alert, Display Within IFrame, and No Popup. Accept the default entries shown for the other options.
Click Finish.
In the confirmation pop-up window, click OK.
Click Close to exit the Application Builder.
Select New from the Application Manager Status menu.
Right-click the new Sales Update application in the right pane and select Approval Status | Approved.
In the confirmation pop-up window, click OK.
Add the new application to a page.
Select Pages from the Web Studio Build menu.
Select New from the Page Builder Status menu, then click New.
When the Page Builder displays, select the full layout icon (the far right layout icon), then click Add.
When the Search window appears, click Search.
Select the Sales Update application in the Results pane and click Add.
In the Page Builder, click Save and complete these options:
Name – enter Sales
.
Type – select Catalog from the drop-down list.
Active – verify that this option is selected.
Roles – click Add All to add all roles to the Assigned Roles list.
Click OK.
When you see the confirmation that the page was saved, click OK.
Click Close to exit the Page Builder.
On the Mobile Web Studio main window, select New from the Page Builder Status menu, right-click the Sales page, and select Status | Approved.
When you see the message that the page was saved, click OK.
Make the new page and application available to Portal Interface users.
Select Approved from the Page Builder Status menu.
Right-click the Sales page in the detail pane and select Update Users.
When you are prompted to reconfirm that you want to perform an update operation, click OK.
When a message displays that the update operation succeeded, click OK.
Log out of Mobile Web Studio.
Alerts do not start until you set up rules for the alert in Portal Interface. To set up rules for the application you created in the previous steps:
Log in to Portal Interface.
Click Manage Pages.
In the Add Page Group window, enter Information
as
the page group name, and click Done.
Click Add Page.
In the Add Page window, add the pre-made catalog page “Sales,” and click Done.
In the Sales page, click the “!” icon in the Sales Update application.
In the Alert window:
Name – select Playback from the drop-down list.
Rule Data – enter the text you want to
receive as a message in the alert. For this example: Sales
data update
.
Description – enter a brief description
of the alert. For example: Sales data has been
updated
.
Under Rules:
Rule Relationship – select “and”.
Select Fields By – select “label”.
Execute Alert When – select “field3”, “is greater than”, 25 in the three columns, then click +.
Enter another rule using the same values for Rule Relationship and Select Fields By.
Execute Alert When – select “field1”, “equals(text)”, enter Devlin, then click +.
Click Done.
In the confirmation pop-up, click OK.
Click Cancel to close the Alert window.
Set up a schedule for the alert:
Click MyInfo, and click the Alert tab.
In the Alert window, select Trigger Alert Based on a Schedule.
Select the Start Time, Recurrence, and Range.
Select No End Date.
Send Alerts To – enter the e-mail address where you want to receive the alert.
Click Done.
Click Start.
Log out of Portal Interface.
Log in to Mobile Web Studio to create a database update application, which can change the quantity of the Tee Shirts for Devlin in the sampledb and trigger an alert.
Select Applications from the Build menu on the left pane.
Click New to access the Application Builder.
When the Application Builder displays, click the down-arrow to the right of the Add button and select Database Element.
For this example, when the Database Element Definition window appears, select Connection Cache.
Complete the remaining fields:
Conn Cache Name – name of the connection cache for the sample database; for this example:
sampledb
SQL Query String – enter this SQL statement:
update sales_order_items set quantity = @OP["quantity"="13"] where id = @OP["id"=”-1”] and prod_id = @OP["prod_id"=”-1”]
In the Split, Define, Filter windows, and Database Element windows click Next.
In the Location: Database Element window, check all three variables (prod_id, id, and quanity).
In the Preview Window, in Element Name, enter:
Element Name – Devlin
id: – 2001
prod_id – 300
quantity – 25
Click Finish.
In the Application Builder, click Save and complete these options in the Finish window:
On the Content tab, enter Devlin
for
the application name.
On the Roles tab, click Add All to add all roles to the Assigned Roles list.
On the Presentation tab, select Alert, Display Within IFrame, and No Popup. Accept the default entries shown for the other options.
Click Finish.
When you see the confirmation message that the application was saved successfully, click OK.