Release Notes - July 2026

GenRocket Jar (3.12.0.2)

Engine Jar (3.12.0.2)

Generator Jar (3.12.0.2)

Receiver Jar (3.12.0.2)

GRepositoryClient Jar (3.12.0.2)

GRepository Jar (3.12.0.2)

InPlaceMasking Jar (3.12.0.2)

UDA Jar (3.12.0.2)

The following new features were in this release: 

• G-Repository Support for HTTPS Communication Protocol - Added support for HTTPS (TLS-encrypted) communication between the G-Repository Client and G-Repository Server. This provides an alternative to the existing WebSocket communication protocol and is recommended for all new and existing deployments.
  
  Many enterprise environments restrict or do not support WebSocket/TCP communication through proxies and firewalls. HTTPS communication addresses these limitations by using a standard HTTPS connection, improving compatibility with enterprise network policies while providing secure, encrypted communication.
  
  No immediate action is required if you are currently using WebSocket communication. Existing G-Repository Client and Server deployments will continue to operate normally using WebSocket until it is retired in a future release.
  
  Steps required to upgrade: 
  • Upgrade Both Components
    • G-Repository Server
    • G-Repository Client
  • Update Firewall Rules
    • Allow inbound and outbound HTTPS communication on port 8443 
  • Confirm Network Policies
    • HTTPS access to the G-Repository Server and Cloud is allowed
    • TLS inspection (if enabled) does not interfere with certificates
       
• LLMGen Generator - Integrates with Large-Language Models (LLMs) to generate contextual, AI-powered data for testing and data generation scenarios. It supports various LLM providers including OpenAI, Google Gemini, Anthropic Claude, and local models like Ollama.
   
• HashiCorp Vault Credential Management - Added support for retrieving sensitive credentials dynamically from HashiCorp Vault at runtime. This enhancement enables secure authentication to retrieve database usernames and passwords, as well as REST API authentication credentials, eliminating the need to store sensitive information directly in GenRocket configuration file.
   
• API to make Attribute Visible - The following Web API can be used to hide an Attribute in the output or make it visible. 
  
  rest/attribute/visible

         Payload

         { 

            "domainId": "<domainExternalId>", 

            "name": "<attributeName>", 

            "visible": false

         }
 

• GroovyScriptInlineReceiver  - This Receiver executes an in-line Groovy script supplied through the Receiver's data rather than reading it from a file on a disk like the GroovyScriptReceiver. Attribute values are substituted into the script before execution; for each mapped Attribute, a {variable} property key defines the token in the script to replace with the Attribute's current value. The script can be run before, during, or after each row iteration.
   
• TIFF Support in UDA - UDA now supports masking sensitive information in multi-page TIFF documents.

The following enhancements were in this release: 

• USCityZipCodeMapGen -  Enhanced USCityZipCodeMapGen to support case-insensitive key lookups. When City, State, State Abbreviation, or Zip Code is used as the keyDataPoint, the corresponding value specified in the reference Generator parameter is matched regardless of letter casing (e.g., "cleveland", "Cleveland", or "CLEVELAND" all produce the same result).
     
• G-Subset and IPM Schema Name Updates - Enhanced G-Subset and IPM to support renaming a configured schema after the initial setup has been completed. To do so, complete these steps: 
  1. Access G-Subset
  2. Select Change Schema Name
  3. Select a schema from the drop-down menu.
  4. Enter a new schema name
  5. Select Save
      
• Switch Project Versions through Breadcrumb Navigation - Users are now able to select a Project Version directly from the breadcrumb bar to switch between Project Versions. 

• Domain loopCount Bulk Update - Domain loopCounts can be updated from from one location, eliminating having to perform multiple steps to update each Domain's loopCount.  
  1. Expand the Global Editing menu
  2. Select Edit Domains LoopCount
  3. Use the Edit (Pencil) icon to make changes.
  4. Select the Green Checkmark to save. 
      
• XMLMergeSegmentV4Receiver - Added two new parameters to this receiver, which are used to include important headers in the generated output files. 
  • xmlProlog - Written as the first line of each output file.
    • e.g. <?xml version="1.0" encoding="UTF-8"?>
       
  • namespaces - One or more xmlns declarations placed on the root element only, separated by a semi-colon (;). Supports a default namespace plus any number of prefixed ones. 
    • e.g., xmins="http//a";xmins:id="http//b". 
    • Written verbatim. 
    • Leave blank to omit. 
    • Max 255 characters (~ 4 to 5 namepsaces)
       
• AWSRoleBasedS3Receiver - Read all files from directory that starts with a value. For example, JSONSegmentMergeReceiver files start with ‘data’, so this receiver would now read data from all subdirectories that start with ‘data’ and send them to the S3 bucket. 
   
• GenericSQLInsertV2Receiver - Enhanced the GenericSQLInsertV2Receiver to provide more flexible error handling during data insertion. Previously, an error such as a foreign key constraint violation or other database insert exception could interrupt processing. Two new parameters have been added to allow users to skip records that encounter insert errors and continue processing the remaining data, improving resilience during bulk data loads:
  
  
  • continueOnError - Defines whether to continue inserting records after an error occurs for a particular record. The default value is ‘false.’
  • logErrorDetails - Defines whether to record the failed records. Works with the continueOnError parameter. The default value is ‘false.’
     
• RestDirectoryV2Receiver - Added ability to configure a proxy with this receiver to make specific API calls rather than setting it globally. Sample XML shown below: 
  <configs> 

             <proxy> 

                <parameter name="GR_PROXY_HOST">192.168.0.104</parameter>
                <parameter name="GR_PROXY_PORT">3128</parameter>
                <parameter name="GR_PROXY_SCHEME">http</parameter>
                <parameter name="GR_PROXY_AUTH">false</parameter>
                <parameter name="GR_PROXY_USER">divya</parameter>
                <parameter name="GR_PROXY_PASSWORD">passwd123</parameter>
             </proxy>

             <login ...>

                  .….

             </login>
             <config tag="test">

                  ..... 

             </config> 

        </configs>

Bug Fixes

The following bug fixes were in this release: 

• Project Filtering in Project Dashboard - Users experienced issues with project counts not displaying correctly after filtering projects by the user's name.
   
• MultiWeightGen - The distributed result was not being generated correctly for certain use cases. 
   
• G-Repository Server - Users received 'Invalid Config Reg Type' error in G-Repository Server for ORC Projects. 
   
• Scratch Pad - When adding new Attributes to an existing Domain, the new Attributes were not being reflected at the SegmentDataCreatorReceiver level under the Receiver's Attribute Property Keys. 
   
• MultiMapKeyGen - This Generator was not working correctly with the pipe (|) delimiter.