appSettings - appSettings - The appSettings section specifies the configuration options for the Titan application. The subsections are described below. - Perceptive Content - Titan - Perceptive-Content/Titan/Foundation-26.1/Titan-Installation-and-Setup-Guide/Appendix-A-app.config.json-file/appSettings - Foundation 26.1 - Foundation 26.1

defaultDocumentType

The defaultDocumentType section specifies the default document type to use when indexing if the document type is cleared.

Example

"defaultDocumentType": "Unindexed Document Type"

barcodeSeparatorMapping

The barcodeSeparatorMapping section specifies one or more regular expression patterns for identifying separator pages during batch capture. If any barcode on a page matches one of these patterns, the page is flagged as a separator sheet and not saved.

Example

  "barcodeSeparatorMapping": [
    "^T$|^3$|^HEADER.*"
  ]

dateFormat

The dateFormat property defines the default date format for the module. The value can be a raw Unicode pattern string or a JSON object that describes formatting options. The default is "MM/dd/yyyy".

String Value

When dateFormat is a string, it is passed as a raw Unicode pattern directly to the formatter. Patterns follow the Unicode CLDR standard and are case-sensitive, for example, M = month, m = minute; d = day of month, D = day of year. If dateFormat is not specified at all, the default format is "MM/dd/yyyy".

Example Pattern Strings

Example

"dateFormat": "MM/dd/yyyy HH:mm"

Object Value

When dateFormat is a JSON object, the following properties are available.

Options

Examples

Short date format (07/04/15):

"dateFormat": { "datePattern": "short" }

Medium date with time (Jul 4, 2015 13:21):

"dateFormat": { "datePattern": "medium", "includeTime": true }

Custom pattern with time (2015-07-04 13:21):

"dateFormat": { "pattern": "yyyy-MM-dd", "includeTime": true }

lookups

The lookups section specifies named lookup configurations referenced by other settings. Each key is a lookup name and each value is either an HTTP or iScript lookup, distinguished by the type field.

Common Base properties - Options

HTTP (type: "HTTP") - Options

Example

"lookupOrderByOrderNumber": {
  "type": "HTTP",
  "url": "https://example.com/rs/hdb/orders/{orderNumber}",
  "method": "GET",
  "authentication": true,
  "timeout": 5000,
  "retryPolicy": {
    "maxRetries": 2,
    "delayMs": 1000
  },
  "cacheTTL": 60000,
  "urlParameters": {
    "orderNumber": {
      "source": "orderNumber",
      "type": "STRING"
    }
  },
  "response": {
    "recordStructure": {
      "mrn": {
        "path": "encounter.patient.mrn",
        "type": "STRING"
      },
      "orderDate": {
        "path": "orderDate",
        "type": "DATE",
        "format": "yyyy-MM-dd"
      }
    }
  }
}

iScript (type: "SCRIPT") - Options

Example

"getVendorSearch": {
  "type": "SCRIPT",
  "scriptName": "VendorLookup.js",
  "inputParameters": {
    "lookupType": {
      "source": "VendorSearch",
      "type": "LITERAL"
    },
    "vendorName": {
      "source": "vendorName",
      "type": "STRING"
    }
  },
  "response": {
    "dataRoot": "results",
    "recordStructure": {
      "vendorName": {
        "path": "vendorName",
        "type": "STRING"
      },
      "creationDate": {
        "path": "created",
        "type": "DATE",
        "format": "MM-dd-yyyy"
      }
    }
  }
}

lookupParameter - Options

response - Options

recordStructure - Options

dependentPropertyUpdates

The dependentPropertyUpdates section specifies lookups triggered outside of application plans. The outer key is the trigger ("*" = on load or document type change, or a field name = on that field's change). The inner key is the target field. Each target supports two actions: setEditable and setListValues.

setEditable - Options

Runs a lookup; if the response at a given path matches a value, makes the target field editable.

setListValues - Options

Runs a lookup; extracts values from the response for an autocomplete list.

Example

"dependentPropertyUpdates": {
  "*": {
    "field2": {
      "setEditable": {
        "lookup": "checkFieldEditable",
        "responsePath": "isEditable",
        "valueMatch": true
      }
    }
  },
  "field1": {
    "field3": {
      "setListValues": {
        "lookup": "getDepartmentList",
        "responseMapping": {
          "value": "departmentId",
          "name": "departmentName"
        }
      }
    }
  }
}

workflow

The workflow section specifies the options used in the workflow process.

Options

Example

"workflow": {
  "openNextItem": true
}

workflowProcess

The workflowProcess section specifies a set of configurations for each workflow process that should appear in the Capture and Indexing module. Each entry is keyed by process name. Only processes configured in this section are displayed in the Capture and Indexing module.

Options

Example

  "workflowProcess": {
    "CnI WF": {
      "enableValidation": false,
      "properties": {
        "field1": "disabledAllowLookups",
        "field5": "disabled"
      },
      "batchHeader": {
        "batchNameLabel": "Order Batch",
        "columnsPerRow": 4,
        "propertyFields": [
          { "id": "workflowQueueName", "label": "Batch Step" },
          { "id": "batchContent", "label": "Batch Content" },
          { "id": "priority", "label": "Priority" },
          {
            "customPropertyName": "Batch Capture - Description",
            "label": "Batch Description",
            "isEditable": true
          }
        ]
      }
    }
  }

batchHeader

The batchHeader section configures the batch header area shown in the viewer. This functionality provides flexibility in defining the layout, content, and appearance of batch headers.

Options

System Property Field

Custom Property Field

Custom Properties can be displayed in the batch header except Array and Composite. The editable fields are displayed based on the user permissions, ensuring secure and role-based access.

workflowQueue

The workflowQueue section specifies queue-level configuration overrides, keyed by queue name. Can be specified at both super-queue and sub-queue levels. Configuration is applied based on the queue from which the batch is opened.

Options

Example

  "workflowQueue": {
    "1 QA": {
      "enableValidation": true,
      "properties": {
        "field1": "enabled",
        "field2": "disabled",
        "field3": "hidden",
        "field4": "disabledAllowLookups",
        "type": "enabled",
        "notes": "disabled",
        "customProperties": {
          "Date": "disabled",
          "Flag": "enabled"
        }
      }
    }
  }

properties

The properties section controls visibility and editability of document property fields in the properties pane.

Options

All property values accept the following display settings:

documentTypeList

The documentTypeList object contains one or more document type list objects. Each document type list object is keyed by the document type list name in Perceptive Content. In Capture and Indexing application, indexing rules can be defined for each document type via a document type list. For each class of document type, you can define an indexing application plan, database mappings, and one or more contexts. These contexts provide additional contextual metadata for aiding the user with indexing and validation.

Options

Example

  "documentTypeList": {
    "Unindexed Documents": {
      "applicationPlan": ""
    },
    "Manager Review Documents": {
      "applicationPlan": "Manager Review"
    }
  }

originMapping

The originMapping section specifies regular expression filter rules matched to origin names. Only matching origins are displayed. If multiple regular expressions are defined, an origin displays when its name matches any of the regular expressions.

Example

"originMapping": ["^IC"]

captureProfileMapping

The captureProfileMapping section specifies regular expression rules for filtering capture profiles. Only capture profile names matching one of the regular expressions will be displayed in the application. Multiple regular expressions can be defined; a capture profile displays when its name matches any of the regular expressions.

Example

"captureProfileMapping": [
  "/^CI.*/", "HIM"
]

originDrawerMapping

The originDrawerMapping section specifies global mappings for origin to drawer. It allows capturing to a specific drawer based on the selected origin. Each key is an origin name and each value is a drawer name string. The system uses this mapping if a match is not found under the application plan's originDrawerMapping. The origin can be a partial match.

Example

"originDrawerMapping": {
  "North": "NorthDrawer",
  "South": "SouthDrawer"
}

routeBatch

The routeBatch section defines the name of the iScript to route a batch after the capture process. The iScript expects the batchFolderId single input parameter and will then return four output parameters.

Options

iScript Parameters

The following table describes the input and output parameters of the iScript.

If routeBatch is not configured, batch capture will skip the route step and log an error.

Example

"routeBatch": {
  "serverAction": "CI_RouteBatchFolder.js"
}

submitBatch

The submitBatch section specifies the iScript to be invoked after the batch is completely indexed and submitted for processing. The iScript expects three input parameters and returns two output parameters.

Options

iScript Parameters

The following table describes the input and output parameters of the iScript.

Example

"submitBatch": {
  "serverAction": "CI_SubmitBatch.js"
}

batch

The batch section specifies options used in batch indexing.

Example

"batch": {
  "confirmPageDeletion": true
}

applicationPlan

The applicationPlan section specifies per-application-plan overrides.

Options

indexing

Under applicationPlan.indexing, keyed by application plan name, then by field ID. Each field maps to a fieldIndexingLookup.

Example

"applicationPlan": {
  "capture": {
    "HC Scan": {
      "originDrawerMapping": {
        "Medical Records": "HC Drawer",
        "Lab Results": "Lab Drawer"
      },
      "barcodeDocSplitMode": true,
      "lookups": [
        {
          "name": "lookupPatientByMRN",
          "parameters": {
            "mrn": {
              "path": "field2",
              "isRequired": true,
              "type": "STRING"
            }
          },
          "columns": [
            { "source": "patientName", "label": "Patient Name" },
            { "source": "dob", "label": "Date of Birth", "format": { "datePattern": "short" } }
          ],
          "updates": {
            "field3": {
              "sourceType": "RECORD",
              "source": "patientName"
            },
            "field4": {
              "sourceType": "LITERAL",
              "source": "Reviewed",
              "default": "Pending"
            }
          }
        }
      ]
    }
  },
  "indexing": {
    "Order Level Indexing": {
      "field4": {
        "lookup": "lookupOrderByOrderNumber",
        "parameters": {
          "orderNumber": {
            "path": "field4",
            "isRequired": true,
            "type": "STRING"
          }
        },
        "columns": [
          { "source": "orderNumber", "label": "Order #" },
          { "source": "customerName", "label": "Customer" },
          { "source": "amount", "label": "Amount", "format": { "minimumFractionDigits": 2, "maximumFractionDigits": 2 } }
        ],
        "updates": {
          "field1": {
            "sourceType": "RECORD",
            "source": "customerName"
          },
          "field5": {
            "sourceType": "RECORD",
            "source": "orderDate",
            "format": "yyyy-MM-dd"
          }
        },
        "advancedSearch": {
          "searchByCustomer": {
            "name": "Search by Customer",
            "lookup": "lookupOrderByCustomer",
            "searchParameters": [
              { "id": "customerName", "name": "Customer Name", "type": "STRING", "isRequired": true }
            ],
            "columns": [
              { "source": "orderNumber", "label": "Order #" },
              { "source": "customerName", "label": "Customer" }
            ],
            "updates": {
              "field1": { "sourceType": "RECORD", "source": "customerName" },
              "field4": { "sourceType": "RECORD", "source": "orderNumber" }
            }
          }
        }
      }
    }
  }
}

fieldIndexingLookup

Configures auto-lookups and advanced search for a specific field.

Options

captureLookup

Used within applicationPlan.capture.[planName].lookups.

Options

captureLookupParameter

The captureLookupParameter section defines parameters passed to a lookup, specifying which field provides the value and whether it is required for the lookup to execute.

Options

columns

The columns section specifies the column definitions displayed in the lookup results grid. Each entry maps a field from the lookup response to a labeled column, with optional formatting.

Options

updates

The updates section specifies how document fields are populated when a lookup result is selected. Each entry maps a target field to either a value from the result record or a static literal value.

Options

advancedSearch

Within advancedSearch on a field indexing lookup, keyed by search name.

Options

searchParameters

The searchParameters section specifies the user-editable input fields displayed in the advanced search dialog. Each parameter maps to a lookup parameter and can optionally be pre-populated from a document field.

Options

format

Number Format

The number format configuration controls how numeric values are displayed in lookup result columns.

Options

Date Format

The date format configuration controls how date values are displayed in lookup result columns.

Options

Boolean Format

The boolean format configuration controls how boolean values are displayed in lookup result columns.

Options