Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Connect SQL rules - Completing the Create, Save As, or Specialization form

Updated on August 16, 2022

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 using the following Developer Help topics:

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.

A Connect SQL rule has three key parts:

Apply toSelect 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
Note: 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 TypeEnter a name for this rule. Begin the name with a letter and use only letters, numbers, the ampersand character, and hyphens.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us