Known Issues
Known issues in Grooper
These issues are not considered bugs at the time and persist due to esoteric client needs or are less of a priority in the development roadmap.
If and when these issues are resolved, they will be documented in the "resolved issues" section of this article. The full build number in which the issue was resolved will also be documented. Be sure to check your minor build number (e.g. 00.00.0000) when evaluating the issue.
|
Version |
Issue |
|
All versions |
There are a number of unsupported CMISQL query configurations. For a running list, please visit the following link on the Grooper Wiki: |
|
All versions |
There is an issue with the Send Mail activity's FlagMessage variable. Because of an issue with order of operations, this value will always be blank by the time the email is created. Grooper clears any flags on nodes before the step runs. So, the flag is cleared by the time Send Mail creates the email. [REF# 7787] |
|
All versions |
An issue can occur with Dispose Batch when sending Batches to a different File Store. If the Activity Processing service is interrupted when moving the Batch (the server crashes, a network error occurs, etc.), the move operation cannot be completed. The Batch will be stuck between the two File Stores, with some files being in the source File Store and others being in the destination File Store. Resuming the Batch after the service reestablishes connection to the Grooper database will not complete the task. [REF# 7864] |
|
2025 |
When configuring CMIS Export to export to a Box Repository, you must select a Target Folder before configuring the "Subfolder Path" property. The Target Folder cannot be the default "/All Fields" (e.g. the Box Repository's root). If you do not select a Target Folder and Subfolder Path is configured, the export will error or produce undesirable results. [REF# 7875] |
|
2024 and above |
Properties that allow users to free-type text can be double-clicked to easily highlight all text in the input box. However, any property that can be typed in that also has a dropdown selector whose default value null will behave differently. In these cases, double-clicking the property will cycle back to the null value, effectively removing all text in the input box. Example: The "Display Label" property change's a Data Element's displayed name to something different in the Data Viewer (usually this is done to make it more user-friendly in Review). When a "Display Label" property has text in it, double-clicking it will clear the text. [REF# 7908] |
|
2024 and above |
When a published Batch Process is moved to the Archived folder, its "Fixed Contents" attribute is changed from True to False. This technically means a user can add steps to a published Batch Process in the Archived folder. It is unlikely this will cause problems in real-world scenarios. However, users should never make changes to an archived Batch Process to avoid issues with Batches in production. [REF# 7843] |
|
2023 and above |
The Data Rule's "Shortcut Keys" property does not function in the Grooper web client. This feature was developed for the older Grooper thick client and relies on a Windows Forms control to work. [REF# 7359] |
|
2021 and above |
The Tabular Layout method's multiline row detection is limited in at least one specific scenario. If a multiline row is the the last row of a table but also spans to the next page (meaning there are no rows after it), only the row content from the first page will be extracted. [REF#7176] |
|
2021 and above |
If you’re creating a custom CodeActivity in C# using the built-in template, it does not create the namespace, which prevents the Activity from showing up in Design Studio. |
|
2021 and above |
When cloning a Content Model that has a Training Set Batch, the documents in the cloned Training Set will retain their original classification. Be advised, you should re-classify the documents in a Training Set Batch after cloning a Content Model (or a folder or Project containing a Content Model). You can do this manually or using the Classify activity. [REF#5819] |
|
2023 and above |
There are rare circumstances where you cannot "Clear" an overridden Data Element property without first "Resetting" it. For example, if a Data Table's Extract Method is set to Tabular Layout and one or more of its sub-properties are overridden, and you want to change the Extract Method to Row Match, you must first "Reset" the Extract Method before the "Clear" command is available. [REF#7191] |
|
2023 and above |
There is an issue that can occur when scrolling rows in a Data Table with large numbers of rows in the Data Viewer. This issue only occurs when the Data Table's "Maximum Display Rows" property is configured. When scrolling through the table very quickly the UI can appear "stuck", where users continue scrolling but the UI displays previously rendered rows instead of the rows further down. In these cases, Grooper can't clear out previously rendered rows from the browser cache quick enough to keep up with how quickly the user is scrolling. Leaving the "Maximum Display Rows" unconfigured will circumvent this issue, but will cause the Data Grid to load slower. However, for users tabbing through table cells or using "F8" to navigate to invalid fields, this issue should not present itself. [REF#7571] |
|
2023.1 and above |
The Separation Viewer and ESP Auto Separation Tester behave differently than in previous versions. In previous versions, moving pages will auto update the color spans, indicating after moving the page which folder it will be included in (or if it will become a loose page). In these versions, moving a page out of order will turn the page and subsequent pages in the folder span red. Users will need to manually select all pages in the folder span and reclassify them to update their color span. [REF#7457] |
|
2023 and above |
There is a caching issue when using commands like "Send To Production" and "Send To Test". If you execute these commands and do not see a sent/cloned Batch in the node tree, simply refresh the tree structure (Use the "Refresh tree structure" button in the upper right corner of the web client UI). [REF#7305] |
|
2021 and above |
In cases where a PDF has both native text and image based text, Recognize will need to reference an OCR Profile to get both native text and OCR text segments. This OCR Profile must have the Synthesis property enabled. Otherwise, you will get two sets of overlapping text data instead of a single text flow. [REF#7274] |
|
2022 and above |
When sorting Batches from the Batches page (or any other Batches View) by the Stats column, the status value is not sorted alphabetically.
|
|
2021 to 2023 |
If you delete a step in a Batch Process, the Order number does not update. You have to refresh the node (ex: navigate to a different node and back to the Batch Process) for the Order number to update. |
|
2.72 Upgrade Issue |
On upgrading a 2.72 Grooper Repository, the PDF Text Extract activity does not appropriately upgrade to the Recognize activity. This will cause an unhandled exception when attempting to select/execute the Batch Process.
|
Resolved issues
|
Version |
Issue |
|
2023.1 |
The "Batch Object - Flag" command will not flag items when used by the Execute activity. [REF# 7951]
|
|
2023-2024 |
There is a navigation issue when editing string property values directly from a nodes property grid. Examples include all nodes' "Description" property and a Data Field's "Default Value" property. In some cases, if users edit these fields from the property grid, then navigate to a different node in the node tree without saving, the Grooper UI will lock up. Users will need to refresh the page in order to continue. [REF# 7562]
|
|
2021-2023 |
If you use multiple named groups in a Pattern Match with an "OR pipe |" - and any of them do not appear on the document, the Output for the Group that did not appear will be the group name in curly brackets.
|
|
2021-2022 |
There is an issue with Fuzzy RegEx and "Required Mode" in situations where a new line character is marked required in the Prefix Pattern (i.e. when the Prefix Pattern is set to
|
|
2022-2023 |
When a Processing Queue or Review Queue is configured on a batch process step as the assigned Queue Name, if the assigned queue is renamed it will no longer appear in the Queue Name property. Although the queue is still assigned as it is present in the JSON File under the original name, but it appears as though it is blank.
|
|
2023 |
The "Confirm Page"/"Mark as Reviewed" command is not present for the Folder Viewer in the Review step. This command is present in the Thumbnail Viewer. The Thumbnail Viewer should be used to confirm pages/mark as reviewed in 2021.
|
|
2023 |
If you expand a published Batch Process and select any of its child steps, you can edit and save that step's configuration in the web client, regardless if the node's "Read Only" property is enabled or not. [REF#6850]
|
|
2023 web client only |
"Sticky fields" do not work in the web client. Enabling a Data Field's Sticky property will have no impact in Review using a Data Viewer. Development was not able to implement "sticky fields" in version 2023. [REF#7014, 7270]
|
|
2021 |
The Grooper REST API's CreatePage endpoint fails to recognize PDF MIME types. [REF#7372]
|
|
2021 |
Using the Merge/Export activity to generate a PDF using a PDF Data Mapping behavior can cause an error when inserting annotations. [REF#7336]
|
|
2023 and above |
The "Render" Activity is only supported in web client when an Activity Processing service processes a Batch. This means you cannot right-click a Batch Folder and apply Render nor can you use the Activity Tester tab to unit test a Render step in a Batch Process. You can, however, use the Render Activity Tester tab to submit a Job (which will be processed by an Activity Processing service). [REF#6528]
|