Custom Grid
Use the Custom Grid to enable bi-directional capability to display, enter and update multiple database table records via a spreadsheet-like interface. This includes robust integration enabling:
- Users to dynamically update existing database information
- Data to be pulled into the grid for display and updates
- Users to add new records to a database
- Process rule configuration based on data from the grid
Please Note: Due to its robust features, the Custom Grid Plugin will not work via Integrify Mobile.
Below, we will show how to configure a Custom Grid to be used by users in a process:

Once you have added your Custom Grid and then selected the Configure Task option, you will be presented with the following:

Options tab:
| Fill and Display Settings Attributes | Options | Required |
Description
|
| Fill grid from data source | Checkbox | No | Allows grid to be filled from a data source. |
| Separate source and destination grids | Checkbox | No | Allows for drag and drop for one grid to another. This will default to 'No' (unchecked) |
| Add, Edit, Delete Settings Attributes | Options | Required |
Description
|
| Add user to create new records | Checkbox | No | This will default to 'Yes' (checked) |
| Add new records to be pasted in from a spreadsheet | Checkbox | No | This will default to 'No' (unchecked) |
| Allow user to edit existing records | Checkbox | No | This will default to 'No' (unchecked) |
| Allow user to delete existing records | Checkbox | No | This will default to 'No' (unchecked) |
We'll use an example of managing a list of applicants with the Custom Grid, allowing a user to create new and edit or delete existing records:

Source Settings tab:
The Source Settings tab will allow you to define how you want to interact with the source of the data:

| Settings Attributes | Options | Required |
Description
|
| Data Source Query or Table | Yes | Allows grid to be filled from a data source. | |
| Data Source Command Type | Text, Stored Procedure, Table | Yes | This will default to 'No' (unchecked) |
| Connection | Custom or Integrify DB | Yes | Choose source connection with the Integrify DB or an external DB |
| Connection String | No | If Custom connection, you will need to enter a connection string here | |
| Provider | SQL Server, Oracle, OleDb | No | If Custom connection, you will need to select a provide type here |
| Grid Page Size | All Records, 5, 10, 15, 20, 25, 50 | No | # of records within the Grid Page to be rendered |
| Source Grid Height | No | Height of the Grid | |
| Source Grid Title | No | Title of the Grid |
Destination Settings tab:
The Destination Settings tab will allow you to define how you want to interact with the destination table for the data:

| Settings Attributes | Options | Required |
Description
|
| Destination Table | Yes | The table where data will be save when inserting or editing records. | |
| Destination Primary Key | Text, Stored Procedure, Table | Yes | This will default to 'No' (unchecked) |
| Primary Key Data Type | Custom or Integrify DB | Yes | Choose source connection with the Integrify DB or an external DB |
| Primary Key Data Sequence or Identity | No | If Custom connection, you will need to enter a connection string here | |
| Connection | Custom or Integrify DB | Yes | Choose source connection with the Integrify DB or an external DB |
| Connection String | No | If Custom connection, you will need to enter a connection string here | |
| Provider | SQL Server, Oracle, OleDb | No | If Custom connection, you will need to select a provide type here |
| Source Grid Height | No | Height of the Grid | |
| Source Grid Title | No | Title of the Grid |
Columns tab:
The Columns tab will allow you to manage what data will be presented in the Custom Grid:

The Columns tab will allow you to add Columns to your Custom Grid for user interaction. Here, you can see the different options to define a column:

| Settings Attributes | Options | Required |
Description
|
| Alias | Yes | Alias of the Column | |
| Source Column | Yes | Source Column of data | |
| Destination Column | Yes | Destination Column for data | |
| Default Value | None, @newguid, @timestamp, @request_ID, @request_SID, @task_ID, @task_SID, @user_name, @user_ID, @user_SID | No | built-in variables associated with the request that may be used to fill columns. |
| Data Type | Auto, String, Integer, Date, Decimal, Guid | No | Data types |
| Entry Field Type | Read-only, Text, Select, Checkbox, Calendar, Hyperlink, Attachment | No | Determines how the data will be displayed |
| Hidden? | No, Yes, Source Grid Only, Destination Grid Only | No | Determines if and where a column is visible |
| Width | No | Width size of the column | |
| Sort? | Checkbox | No | Allows sorting for the column |
| Filter? | Checkbox | No | Allows sorting for the column |
| Rules? | Checkbox | No | Exposes the data for a process rules definitions |
Auto-generate Columns: this allows you to auto generate the column settings based on the destination settings table.
Query Parameters tab:
The Query Parameters tab will allow you define..... in the Custom Grid:

Destination Queries tab:
The Destination Queries tab will allow you define..... in the Custom Grid:

- Query that will be used when inserting new records: Optional query that defines how data is inserted when adding new records. When left blank, the task will attempt the insert based on the defined columns.
- Query that will be used when updating new records: Optional query that defines how data is updated when editing new records. When left blank, the task will attempt the update based on the defined columns.
- Query that will be used when deleting new records: Optional query that defines how data is deleted. When left blank, the task will attempt the delete based on the primary key of the Destination Grid.
- Query that will be used to return the primary key of a newly inserted record if primary key is auto-generated without a sequence or identity: For returning a primary key.
Comments