Database Schema

A Database Schema is used to synchronize the rule application schema with an external database.

To add the schema, click on the Schemas icon in the Navigation Pane and then click the Add button - > Database Schema

The following is a description of the Database Schema Definition form:

Name

The logical name of the Database Schema Definition.

Connection String

Specifies the parameters the rule engine should use when connecting to this database such as the type of database server, the computer name or IP address, the database name, the user id, etc. This must be an "OLEDB" format connection string at authoring time (but may specified to be any type of connection string at runtime).

The button launches the connection string wizard to assist with the construction of a valid connection string.

Reload

Reloads the database schema information based on the connection string. Use this to resynchronize the rule app with updated database information.

"Apply To RuleApp" must be subsequently selected in order to complete the synchronization of the rule app with the selected "Entity" classes and properties / fields.

Apply to RuleApp

Synchronizes the selected tables and elements with the rule app. All existing same-named rule app Entities and Fields are preserved.

"Last Applied" indicates when this was last performed.

Any fields, collections or calculations not present in the imported columns set will be removed from the rule app for the selected Entity on Apply, except for "Temporary Storage" Fields, Collections and Calculations which may exist in the rule app schema without being selected in the End Point.

Show XSD

Displays the configuration of the schema in XSD format in a browser.

DeSelect All

De-selects all checked tables in the schema configuration pane.

Options

Ignore Readonly Settings

When this option is checked the readonly attribute of a column being imported will not be propagated to the corresponding schema field. For example, an identity column is typically a readonly column. If this option is checked and then the database schema is applied to the rule application, the corresponding field created in the schema will not be readonly. Therefore, during rule application execution values can be assigned to the schema field which corresponds to the identity column.

By default this option is not checked and readonly settings are enforced.

Create Child Fields

If this option is checked fields or collections are created to reflect one-to-one or one-to-many relationships, respectively. For example, for the following one-to-many relationship between Orders and Order Details, 

two entities will be created: "Order_Details" and "Orders." The entity "Orders" will contain a collection called "Order_Detailses" whose members are of entity type "Order_Details." If this option is not checked, the collection "Order_Detailses" will not be created.

By default this option is checked.