What's New in Grooper 2023.1: Difference between revisions

From Grooper Wiki
No edit summary
Line 138: Line 138:
* Sticky field support in web client
* Sticky field support in web client
* Display labels (Use “\auto” to use labels in Label Sets!)
* Display labels (Use “\auto” to use labels in Label Sets!)
== Misc Other Changes ==
The '''''Labeled Value''''' extractor can now function ''without'' a '''''Value Extractor''''' configured whether using Label Sets or not.
* Previously, this functionality was only accessible if the extractor's label was collected via the '''''Labeling Behavior'''''.
* Be aware, how the extractor collects results without a configured '''''Value Extractor''''' is very different from the extractor's typical logic.  It is intended as a "dumbed down" way of collecting the most simplest of data in the most simplest of layouts.

Revision as of 14:03, 17 October 2023

WIP

This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly.

This tag will be removed upon draft completion.

Welcome to Grooper 2023.1!


Grooper version 2023.1 is here!

Below you will find brief descriptions on new and/or changed features. When available, follow any links to extended articles on a topic.

Expanded Web Client

Light Mode

Let there be light (mode)!

Users can now toggle between dark mode and light mode in the Grooper web client.

  • Use the user information icon to switch from dark to light mode.
  • Custom Data Model styling supported for both dark and light modes via CSS classes.
    • "dark-mode" for dark mode
    • "lite-mode" for light mode

Improved Scripting for Web Client

Scripting for the web client is better than ever. Grooper users can now use the web client as their debug target thanks to the GrooperSDK Visual Studio extension.

  • The GrooperSDK extension is available for download in the Visual Studio Marketplace.
  • This extension allows users to set a web browser as their debug target.
  • Users can now download scripts and work on them independently of Grooper, saving changes directly from Visual Studio using the GrooperSDK extension.


Furthermore, users can edit scripts from any machine, not just the Grooper web server, with the following components must be installed:

  • Grooper (with a Repository connection made to the Grooper Repository hosted by the web server)
  • Grooper Web Client
  • IIS
  • Visual Studio 2019
  • GrooperSDK

For more information, be sure to check out the "Web Scripting" article COMING SOON!!.

New and Improved Processing Features

Secondary Types

Secondary Types is a new property assignable to Batch Folders. This feature allows a single document to be assigned multiple Document Types. Secondary Types can be used with the following activities:

  • Classify to save a classification result as a Secondary Type.
  • Extract to run extraction for all assigned types
  • Apply Rules to run Data Rules for all assigned types.
  • Convert Data to save converted data as a Secondary Type.
  • Export to run Export Definitions for all assigned types.


Multiple Document Types means multiple Data Models! This means you can collect data using more than just one Data Model. The Data Grid will display data for all assigned Types in Review

  • FYI: If desired, you can configure the Data Viewer's 'Content Type Filter property to limit display to specific Document Types.


For more information, be sure to check out the "Secondary Types" article COMING SOON!!

EDI Support

Grooper can create Data Models directly from an X12 EDI schema and load data from an EDI file directly into a Grooper document.

  • Data Elements adhering to an EDI schema can be created by right-clicking a Data Model, selecting Import Schema... and configuring the EDI Schema Importer.
  • Data from an EDI file can be loaded into Grooper using the Execute activity, configured with an EDI File - Load Data command.


Currently, Grooper can process the following EDI schemas natively:

  • X12 835
  • X12 837 Professional
  • X12 837 Dental
  • X12 837 Institutional

FYI: X12 refers to the organization developing and maintaining the EDI standards. X12 is the common EDI standard in the US and North America.

XML Data Interchange

Grooper users can now ingest and build XML files more effectively with our suite of "XML Data Interchange" capabilities. With this new funcitonality users can:

  • Create Data Elements from an XML schema file right-clicking a Data Model, selecting Import Schema... and configuring the XML Schema Importer.
  • Load data from an XML file that adheres to an XML schema using the Execute activity, configured with an XML File - Load Data command.
  • Validate an XML document against an XML schema using the Execute activity, configured with an XML File - Validate Schema command.
  • Generate an XML document according to an XML schema using a new Merge/Export Format (called XML Format).

New Node Type: Resource Files

Expression Variables

Lookup Improvements

New Lookup Type: XML Lookup

New Trigger Mode: Custom

Changes To Table Extraction

Header-Value Is Out. Tabular Layout Is In

Data Element Extensions

New Tabular Layout Property: Find Column Positions

Prescan Threshold for Labelset-Based Classification

New "Summary" Tabs

Batch Management & Review Enhancements

"FIFO" Batch Priority

Dynamic Value Lists

Review Improvments

  • Swap panes
  • Horizontal/Vertical view toggle
  • Double-click capture (alternative to rubberband OCR)
  • Data Grid zoom in/zoom out
  • Sticky field support in web client
  • Display labels (Use “\auto” to use labels in Label Sets!)

Misc Other Changes

The Labeled Value extractor can now function without a Value Extractor configured whether using Label Sets or not.

  • Previously, this functionality was only accessible if the extractor's label was collected via the Labeling Behavior.
  • Be aware, how the extractor collects results without a configured Value Extractor is very different from the extractor's typical logic. It is intended as a "dumbed down" way of collecting the most simplest of data in the most simplest of layouts.