DriveWorks Pro 15: Connectors - Database [send feedback...]

Database Connector

The Database Connector continuously observes a table in a database and creates specifications from rows with specific values.

About Connectors

Connectors send information into Constants or Controls of a specification by name. Connectors will observe the following behavior when driving data into a specification:

  • If the constant name is found with the same name as the name of the value being applied, then the constant will be driven.
  • If there is a control with the same name as the constant, the control will NOT have its value set.
  • If however there is no constant with that name, but there is a control with that name, the controls value will be set.

The Database Connector requires a valid database to monitor.

The Table in the database must include a field for the Connector to read and write the Status of the entry.

Setup the Data Source

The following settings are applied in the Data Source section of the settings screen.

  1. Type - Specifies the type of database to be observed. The available options are:
  2. Server Address (When Type is SQL Server) - The Connector will list all SQL Servers that the computer can see. Select the required server from the drop down.

    Source (When Type is ODBC) - The Connector will list all ODBC connections set up on the computer. Select the required source from the drop down.

  3. Username - Enter a valid username to connect to the data source.
  4. Password - Enter a valid password for the username.
  5. Is Trusted Connection (When Type is SQL Server) - Check if the data source requires a trusted connection.
  6. Database (When Type is SQL Server) - Select the required SQl database to monitor.
  7. Table Name - Select the table name to monitor.

Field Bindings

Once connected to a database and table (from the settings above) the fields from the table are read into the Field Bindings section and are listed in the Name column.

Set a binding Type for each field. The available bindings are:

  • No Binding - DriveWorks will ignore any fields mapped to this binding type.
  • ID Field (mandatory) - Used to mark a field type as an Identity Field.
  • Specification Name Field - Used to select an existing specification to be edited.
    The binding Specification Id Field can also be used. If both are used Specification Id will take preference.
  • Specification Id Field - Used to select an existing specification to be edited.
    The binding Specification Name Field can also be used. If both are used Specification Id will take preference.
  • Input Field - DriveWorks will pass the value in this field to a Constant or Control Name in the project.
    • Constant/ Control Name - Enter the name of the Constant or Control the value is to be passed into.

      For example: OrderNumber - Will first look for a Constant, and then a Control with the name OrderNumber.

      Constant Names should not be prefixed with DWConstant

      Control Names should not have Return appended to the name.

  • Process State Field (mandatory)
    The database must contain a field that DriveWorks can use to detect if a specification requires processing. The same field will be updated by DriveWorks to report its current status.
    • Process Value - Is the value that will allow the Connector to recognize a new record exists and is to be processed. The default value is set to New.
    • Processing Value - Is the value to be written into the field when the Connector is processing the record. The default value is set to Processing
    • Success Value - Is the value to be written into the field when the Connector has successfully processed the record. The default value is set to Complete
    • Failed Value - Is the value to be written into the field if the Connector failed to process the record. The default value is set to Failed
  • Project Name Field* - Is the name of a valid project in the Group the data is to be applied to.
  • Transition Name Field* - Is the name of a valid Transition (as created in Specification Flow) that will be run once the data has been passed to the new specification.
  • Operation Name Field* - Is the name of a valid Operation (as created in Specification Flow) that will be run once the data has been passed to the existing specification.
* Note

When the table has no field for Project Name or Transition Name, these bindings must be set in the Additional Options (see below).

Additional Options

The following additional options are available:

  • Project Name - Use when only a single project can be processed by the connector and no field binding exists for this property.
  • Transition Names - Use when only a single project can be processed by the connector and no field binding exists for this property.
  • Scan Interval - Set how often (in seconds) the connector will scan for new entries in the database.

See Also

Web Service

Folder Watcher

Table of Contents