Basic Information Page

You can enter a name and description on the Basic Info page of each trigger and invoke adapter in your integration.

Element Description

Element	Description
What do you want to call your endpoint?	Identifies the connection with a meaningful name that defines the purpose of connection. For example, `CreateEmployeeInDB` for a database connection that adds new employee data. The name can include English alphabetic characters, numbers, underscores, and dashes. The name cannot include: Blank spaces (for example, `My DB Connection`) Special characters (for example, `#;83&` or `righ(t)now4`) Multibyte characters
What does this endpoint do?	Enter an optional description of the connection’s responsibilities. For example: `This connection receives an inbound request to synchronize account information with the cloud application`.
What operation do you want to perform?	Selects the operation performed by the connection in the outbound (invoke) direction: Invoke a Stored Procedure: Allows the selection of a stored procedure to run on the database. Run a SQL Statement: Allows the selection of a SQL query to run against the database. Perform an Operation On a Table — Select to perform one of the following operations on a table. You can insert, update, or extract multiple records in a single request. Insert Update Insert or Update (Merge) Select In the inbound (trigger) direction, you can only poll for new or changed records. Note: When operations in a SQL statement such as Update, Concat, and Merge accept values for the inbound invocation of an integration, they do not work. For example, the following query does not work: `select concat(empname, 'ss') from DB_AQ where empno=#empno` `select empno from DB_AQ where empname=concat(#empname, 'YY')` As a workaround, handle these scenarios during payload mapping. For example, perform a concatenation during mapping of the payload. The final output can then be passed as input to the SQL query.

What do you want to call your endpoint?

Identifies the connection with a meaningful name that defines the purpose of connection. For example, CreateEmployeeInDB for a database connection that adds new employee data. The name can include English alphabetic characters, numbers, underscores, and dashes. The name cannot include:

Blank spaces (for example, My DB Connection)
Special characters (for example, #;83& or righ(t)now4)
Multibyte characters

What does this endpoint do?

Enter an optional description of the connection’s responsibilities. For example: This connection receives an inbound request to synchronize account information with the cloud application.

What operation do you want to perform?

Selects the operation performed by the connection in the outbound (invoke) direction:

Invoke a Stored Procedure: Allows the selection of a stored procedure to run on the database.
Run a SQL Statement: Allows the selection of a SQL query to run against the database.
Perform an Operation On a Table — Select to perform one of the following operations on a table. You can insert, update, or extract multiple records in a single request.
- Insert
- Update
- Insert or Update (Merge)
- Select

In the inbound (trigger) direction, you can only poll for new or changed records.

Note: When operations in a SQL statement such as Update, Concat, and Merge accept values for the inbound invocation of an integration, they do not work. For example, the following query does not work:

select concat(empname, 'ss') from DB_AQ where empno=#empno

select empno from DB_AQ where empname=concat(#empname, 'YY')

As a workaround, handle these scenarios during payload mapping. For example, perform a concatenation during mapping of the payload. The final output can then be passed as input to the SQL query.