The following provides SDK documentation for each type category.
Name | Description |
---|---|
Grooper.Activities.ActivityTester | Activity Testers are Node Views which display in Grooper Design Studio when a Batch Process Step object is selected. The specific testers which display will depend on what type of Activity the step is configured to execute. |
Grooper.Capture.CaptureDevice | Capture Devices provide connectivity to hardware capture devices, such as ISIS or TWAIN document scanners. |
Grooper.Capture.CaptureProtocol.ProtocolSettings | Provides custom settings for the TWAIN and Isis scanner protocols. |
Grooper.Capture.SeparationProvider | Separation Providers organize Batch Pages into Documents in accordance with defined instructions or criteria. |
Grooper.CMIS.CmisBinding | A CMIS Binding provides connectivity to an external storage platform over CMIS. |
Grooper.CMIS.CmisPropertyDefinition | A CMIS property definition provides information about a property of a CMIS content type. |
Grooper.CMIS.HttpAuthenticationMethod | HTTP authentication methods define how an HTTP client authenticates with an HTTP server. |
Grooper.CMIS.QueryElement | A CMISQL Element is an individual component of a CMISQL Query. |
Grooper.Core.BatchProcessingActivity | Activities define work to be performed on objects in a Batch during a Batch Process Step. |
Grooper.Core.BatchView | Batch Views are controls which display Grooper Batches in the Attended Client application. |
Grooper.Core.BatchView.BatchViewSettings | Batch View Settings define the appearance and behavior of Batch View controls in Attended Client. |
Grooper.Core.CaptureZone | Capture Zones associate regions on a page with Data Elements in a Data Model, and are used to facilitate zonal data capture. |
Grooper.Core.ClassifyMethod | Classify Methods define classification mechanisms which are used in Content Models. |
Grooper.Core.CollationProvider | Collation Providers define various methods for converting the raw extractor results of a Data Type into a final result set. |
Grooper.Core.ContentLink | Content Links define references to content stored outside of Grooper, such as file on a file system or a document in a CMIS Repository. |
Grooper.Core.DataElementProfile | Data Element Profiles store settings for Data Elements such as sections, tables, and fields on a Content Type. |
Grooper.Core.DataInstance | A Data Instance represents a segment of text content within a document. |
Grooper.Core.EdgeAdjustment | Defines a mechanism for adjusting edges of a region in Geometric section extraction. |
Grooper.Core.ExportProvider | Export providers define export connectivity to external systems such as file systems, content management repositories, mail servers, and etc. |
Grooper.Core.ImportProvider | Import providers enable import of file-based content from a variety of sources such as file systems, mail servers, and content repositories. |
Grooper.Core.LayoutProvider | Layout Providers define the various layouts in which arrays can be detected. |
Grooper.Core.LookupSpecification | A Lookup Specification defines a query against an external data source, which is used to validate and/or populate field values. |
Grooper.Core.MimeTypeHandler | MIME Type handlers define properties and commands relative to the Mime Type of a native file attached to a Batch Folder. |
Grooper.Core.ResultProcessor | Result processors define post-processing operations which can be applied to each output value of an extractor. |
Grooper.Core.SectionExtractMethod | A Section Extract Method defines an extraction method for use with Data Section objects. |
Grooper.Core.StorageType | Storage Types indicate types of data represented by Data Types and Data Fields. |
Grooper.Core.TableExtractMethod | Defines settings and logic for a Data Table extraction method. |
Grooper.Core.ValueExtractor | Values extractors define various mechanisms for extracting the value of a Data Field or Data Column. |
Grooper.Core.VariableProvider | Variable Providers represent custom character sets or pipe delimited lists that can be used in Regular Expression patterns. |
Grooper.DatabaseConnectionSettings | Database Connection Settings represent the settings necessary to connect to a Database. |
Grooper.DialogBox | Dialog Boxes are popup windows which collect information from or present information to an end user. |
Grooper.GrooperControl | Controls are user interfaces from which Grooper applications are built. |
Grooper.GrooperNode | Grooper Nodes are objects which appear in the main tree structure of a Grooper repository. |
Grooper.GrooperObject | Grooper Objects are the primary base class from which all Grooper Types are derived. |
Grooper.IP.IpCommand | IP commands perform image processing work, such as image cleanup, format conversion, or feature detection. |
Grooper.MainWindow | Main Windows represent the top-level window of a Grooper application. |
Grooper.NodeView | Node Views are administrative user interfaces which display as tabs in Grooper Design Studio as nodes are selected from the Grooper tree structure. |
Grooper.ObjectCommand | An Object Command is an action which can be performed on a specific type of object. |
Grooper.OCR.OcrEngine | OCR Engines extract text from images using optical character recognition. |
Grooper.Reporting.Report | Reports display statistical information on operations performed within Grooper. |
Grooper.Reporting.ReportRange | Defines a period of time for which a Report should be generated. |
Grooper.ServiceInstance | A Service Instance is a Grooper Service that has been installed on a Server or Workstation. |
System.Attribute | Represents the base class for custom attributes. |
System.ComponentModel.TypeConverter | Provides a unified way of converting types of values to other types, as well as for accessing standard values and subproperties. |
System.Drawing.Design.UITypeEditor | Provides a base class that can be used to design value editors that can provide a user interface (UI) for representing and editing the values of objects of the supported data types. |