Previous	Next		Contents	Index	Navigation	Glossary	Library

   To specify the alert details for an event or periodic alert:

1. With your alert definition displayed in the Alerts form, choose Alert Details. The Alert Details window that appears contains three alternative regions: Installations, Inputs, and Outputs.

2. In the Inputs alternative region, Oracle Alert automatically displays the inputs used in your Select statement, unless they are the implicit inputs: :ROWID, :MAILID, and :DATE_LAST_CHECKED. The values of the implicit inputs are as follows:

• ROWID--Contains the ID number of the row where the insert or update that triggers an event alert occurs.

• MAILID--Contains the email username of the person who enters an insert or update that triggers an event alert.

• DATE_LAST_CHECKED--Contains the date and time that the alert was most recently checked.

3. You can optionally add a description for each input, but you must specify the data type (either character, number, or date) for the input, because Oracle Alert uses the data type to validate the default values for inputs you enter in the Default Values field and in the Action Set Inputs alternative region of the Action Sets block.

4. Enter a default value for your input. You can enter up to 240 characters. This value automatically becomes the default value for your input in each action set you define.

For example, if you have an input APPLICATION_NAME, and you give it the default value "Oracle General Ledger," Oracle General Ledger will also be the value for the input in each action set you define, unless you change it in the action set to another value like "Oracle Payables."

Note: When you change an input value in an action set, you simply change the value for that action set. The new value does not get propagated as a new default value for other occurrences of that input.

5. In the Outputs alternative region, Oracle Alert automatically displays the outputs used in your alert Select statement without the ampersand (&) and any numbering format. You can add meaningful descriptions for the outputs.

6. You can specify the maximum number of output characters you want to display in your detail or summary message actions. See: Formatting Summary Message Actions.

7. If your output value is numeric, enter the SQL*Plus format mask in the Number Format field.

8. You can also check the Check for Duplicates check box to customize the combination of outputs you want to verify as a possible duplicate exception each time the alert is checked. A duplicate exception is an exception that existed in your database during previous alert checks. You can define Oracle Alert to perform certain actions based on the presence of these duplicate exceptions.

Note: You must save history for your alert to use duplicate checking. See: Overview of Oracle Alert History.

9. In the Installations alternative region, specify an Oracle ID if you want Oracle Alert to check your alert against that specific Oracle ID. You can select only those Oracle IDs that are associated with the application that owns your alert.

If you do not specify an Oracle ID in this region, Oracle Alert checks your alert against all installations in your database of the application that owns your alert.

10. Check the Enabled field if you want your alert to run against that Oracle ID.

11. Save your changes and close the window.

See Also