Database Condition

Description

Monitors a Microsoft SQL or Oracle database for a specific operation to be performed and evaluates as TRUE when the condition is met. Supported database operations include INSERT, DELETE, DROP, ALTER or UPDATE. This condition can be set as one of the following workflow elements:

Practical Usage

Ideal for automated execution of database related tasks. For instance, a SQL query task can start upon entry of specific data into the table being monitored.

Related Topics

Parameters

General

Property

Type

Description

Database type

Options

The type of database to monitor. The available options are:

  • SQL - MS SQL database will be monitored.

  • Oracle - Oracle database will be monitored.

Server

Text

The name of the database server to be monitored.

Username

Text

The username used to authenticate with the database.

Password

Text

The password linked with the username used to authenticate with the database.

Notification port

Number

Indicates the port number that the notification listener listens on for database notifications. If the port number is set to -1 (default), a random port number is assigned to the listener when started. This parameter is active only if the Database type parameter is set to Oracle.

Prerequisites

Property

Type

Description

Table

Text

The database table which holds the data element(s) to be monitored. This value must include the schema name and table name separated by a dot (.) entered in the following format (minus the brackets):

[Schema_Name].[Table_Name].

Insert

Yes/No

If set to YES, the condition evaluates to TRUE when an INSERT is performed on the specified database (set to YES by default). The INSERT statement is used to add new rows of data to a table.

Drop

Yes/No

If set to YES, the condition evaluates to TRUE when a DROP is performed on the specified database (set to NO by default). The DROP command permanently deletes a table from the database.

Delete

Yes/No

If set to YES, the condition evaluates to TRUE when a DELETE is performed on the specified database (set to NO by default). The DELETE statement is used to delete rows from a table.

Alter

Yes/No

If set to YES, the condition evaluates to TRUE when an ALTER is performed on the specified database (set to NO by default). The ALTER command is used to alter the definition (structure) of a table by modifying the definition of its columns.

Update

Yes/No

If set to YES, the condition evaluates to TRUE when an UPDATE is performed on the specified database (set to NO by default). The UPDATE statement is used to modify the existing rows in a table.

Behavior

The Behavior properties dictate how the system should react upon the occurrence of a condition. These properties are significant in determining whether the condition should act as a trigger object (used to fire off workflow execution), wait object (used to suspend workflow execution) or conditional (decision making) object.

More on Condition Behavior

Additional Notes

AMTrigger

When the Database condition is used to trigger workflow execution, it automatically creates an AMTrigger dataset which can be used much like the datasets created by the SQL Query and E-Mail actions. The fields that AMTrigger generates can be used to determine properties of the object that caused the workflow to launch, such as the type of trigger, when the trigger was activated and what system event or condition took place to activate the trigger. Along with a collection of global AMTrigger fields that are created and populated by every instance of AMTrigger, a unique set of AMTrigger fields exclusive to each AutoMate trigger are created as well.

To view AMTrigger values exclusive to the Database condition, see AMTrigger - Database.

AMCondition

When the Database condition is used in the middle of a workflow as wait or conditional object, it automatically creates an AMCondition dataset. Similar to AMTrigger, the fields that AMCondition generates can be used to determine properties of the object that caused the condition to activate. Along with a collection of global AMCondition fields that are created and populated by every instance of AMCondition, a unique set of AMCondition fields exclusive to each AutoMate condition are created as well.

To view AMCondition values exclusive to the Database condition, see AMCondition - Database.