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: CMIS Query (Concept)#Unsupported Query Configurations
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.
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	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 ]
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 web client only	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 web client only	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 web client only	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 web client only	When sorting Batches from the Batches page (or any other Batches View) by the Stats column, the status value is not sorted alphabetically. This is because these values are stored as integers in the Grooper database and translated to a text-based equivalent (1=Ready, 2=Working, 3=Completed, 4=Paused, 5=Error, 6=Cancelled). Batches are sorted by these numbers. This is intended to sort all "Ready" Batches at the top of the list and all "Error" and "Cancelled" Batches at the bottom for quicker identification. [REF#7469]
2021	The Grooper REST API's CreatePage endpoint fails to recognize PDF MIME types. This issue is fixed in all later Grooper versions. [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. This issue is fixed in a all later Grooper versions. [REF#7336]
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 (?r)\n(?-r)). If the regex pattern matches something at the beginning of a string (For example, the first line of text on the first page of a document), the extractor will match the result and return it, even though there is no new line character present. [REF#6689]
2021 to 2023 Windows client only	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. PLEASE ADVISE: Since 2.72 is an EOL version, development has placed this issue on low priority. Users will need to delete the PDF Text Extract step before upgrading. After upgrading, users will need to add the Recognize activity to the Batch Process and move it to the appropriate spot in the Batch Process. [REF#7212]

Resolved issues

Version	Issue
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. ISSUE RESOLVED AS OF VERSIONS: 21.00.0070, 22.00.0019, 23.00.0014
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. ISSUE RESOLVED AS OF VERSION 23.00.0037 ISSUE REMAINS UNRESOLVED IN VERSION 2022
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. ISSUE RESOLVED AS OF VERSION 23.1.0007 The Folder Viewer now has the "Confirm Page" command in version 2023.1. ISSUE REMAINS "UNRESOLVED" IN VERSION 2023
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] ISSUE RESOLVED AS OF VERSION 23.00.0016
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] ISSUE RESOLVED AS OF VERSION 23.01.0007 ISSUE REMAINS UNRESOLVED IN VERSION 2023 Implementing this feature in version 2023.1 required some major changes to the web client architecture. To ensure Grooper version 2023 remains stable, Development will 'not be porting these changes down to version 2023. Users wanting to use "sticky fields" in the web client will need to upgrade to version 2023.1 or later