You are here: Integration > Integration Connectors category > Connect SQL rules > Connect SQL rules - Completing the New or Save As form

Connect SQL rules

Completing the Create, Save As, or Specialization form

  1. About
  2. New
  3. Open
  4. Delete
  5. Save
  6. Browse
  7. History
  8. More...

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Based on your use case, you use the Create, Save As, or Specialization form to create the record. The number of fields and available options varies by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:

This information identifies the key parts and options that apply to the record type that you are creating.

Create a Connect SQL rule by selecting Connect SQL from the Integration-Connectors category.

Key parts:

A Connect SQL rule has three key parts:

Field

Description

Apply to

Select a class associated with the database table on which you want to operate.

Package Name

Enter a value that indicates any SQL language variant. For example, you can enter:

  • MSSQL for Microsoft SQL Server
  • Oracle for Oracle.
  • DB2 for IBM DB2
  • UDB for IBM DB2 Universal Database (UDB)
  • Sybase for Sybase

This key part is required but unrestricted. As a best practice, use this key part to record which flavor of SQL is present in the rule.

Request Type

Enter a name for this rule. Begin the name with a letter and use only letters, numbers, the ampersand character, and hyphens.

Rule resolution

When searching for Connect SQL rules, the system filters candidate rules based on a requestor's RuleSet list of RuleSets and versions.

The system does not search the class hierarchy. References to Connect SQL rules (such as in method parameters) must match the Apply to key part.

Time-qualified and circumstance-qualified rule resolution features are not available for Connect SQL rules.