The Sun SeeBeyond Enterprise Designer– Business Rules Designer includes Input and Output columns to map and transform data between Activities displayed on the Business Process Canvas.
Figure 1–2 displays the business rules between the FileClient.write and otdSybase.Db_employeeDelete Activities. In this example, the whereClause appears on the Input side.
The following table lists the expected Input and Output of each database operation Activity.
Table 1–2 Sybase Operations
eInsight Operations |
Activity Input |
Activity Output |
---|---|---|
SelectAll |
where() clause (optional) |
Returns all rows that fit the condition of the where() clause. |
SelectMultiple |
number of rows wherels() clause (optional) |
Returns the number of rows specified that fit the condition of the where() clause, and the number of rows to be returned. For example: If the number of rows that meet the condition are 5 and the number of available rows are 10, then only 5 rows will be returned. Alternately, if the number of rows that meet the condition are 20, but if the number of available rows are 10, then only 10 rows are returned. |
SelectOne |
where() clause (optional) |
Returns the first row that fits the condition of the where() clause. |
Insert |
definition of new item to be inserted |
Returns status. |
Update |
where() clause |
Returns status. |
Delete |
where() clause |
Returns status. |