March 2024

For this release, you will need to update your Jar files. A runtime update is not required.


Release DateJar FilesNew Features
March 28, 2024GenRocket jar (3.5.42.1)

Engine jar (3.5.42.1)

Generator jar (3.5.42.1)

Receiver jar (3.5.42.1)

GRepository jar (3.5.42.1)

GRepository client jar (3.5.42.1)		The following new features were in this release:
  • RandomIncDecMultiPeakGen - Similar to the RandomIncDecPeakGen, this Generator can be used to generate a random increasing and decreasing sequence of numbers, where the position of multiple "peaks" in the sequence can be defined. The total of the numbers will be the "targetsum." 
    • Example -  Give me 20 numbers totaling 35, with the sequence peak in positions 5, 10, and 15.

  • CopyBook Import - Added the ability to import Domains and Attributes into a Project using a CopyBook file.

  • GenericSQLInsertThreadReceiver - This Receiver works similarly to the GenericSQLInsertV2Receiver and can be used to insert generated data into a database table via JDBC-prepared statements. However, the GenericSQLInsertThreadReceiver can be configured with multiple DataCollectors, each with many buckets and each bucket containing many values. When a DataCollector's buckets are full, they are prepared simultaneously across multiple threads as the next DataCollector is being loaded. Click here for more information.

  • G-Repository Client - In some instances, the IP address of servers are dynamic. In such cases, the G-Repository server will be launched with a different IP address, but the G-Repository Clients were still configured to the previous IP address on which G-Repository server was running. We have added a new command that allows the user to automatically update the client repository configs to the new G-Repository Server URL/IP: 
    • -grcltcsurl or --g-repo-client-change-server-url
    • Example: genrocket -grcltcsurl <URL>

Enhancements
The following enhancements were in this release:
  • G-Repository Help (-grhelp) Command - The formatting has been improved so that the provided details are easier to read at the command line.

  • G-Partition Engine- Added the ability to call the partition engine from an external source (e.g., another instance) as well as from localhost. This can now be done by launching the partition engine on an IP address. 
    • Example: 
      http://<IpOfLocalSystemOrServer>:8181/grRest/partition

  • RESTDirectoryV2Receiver - Added the ability to make a REST API call with this Receiver by dynamically creating the URL. This is helpful when multiple values are stored in a file (e.g., CSV), and an API call needs to be made for each one.

  • Configuration Management - Added a new icon to the Configuration Management tab in the Project Dashboard. This icon can be used to create a new configuration by copying an existing one. Once copied, the user can make any required changes to the new configuration.

Bug Fixes
The following bug fixes were in this release:
  • G-Queries, G-Rules, and G-Cases - Download failing when slash in name. Slashes are no longer allowed when naming these items in the GenRocket web platform.

  • LoremIpsum - LoremIpsumGen reference in any other Generator was causing a Null Pointer exception.

  • G-Repository Client - The G-Repository Client was making a call to GenRocket Cloud even though the G-Repository Server was set up and being used.

  • SWIFT/G-Cases - Disabling a segment for SWIFT in a Test Data Case was causing test data generation to hang.

  • Salesforce Import - During Domain/Attribute creation, duplicate Attribute names were being created while the original name was different. As a result, not all columns were being imported. Versioning has now been added for Attribute names to prevent this issue from occurring during the import.

  • JSONSegmentMergeReceiver - The directory structure was incorrectly created when choosing the 'cross reference' option. An additional directory/file was created. The number of files in the directory also did not match what was set in the directory config.

  • Scenario Execution with G-Case - During execution, an H2 Database was being initialized even when it was not required. This prevented a customer from performing parallel execution of G-Cases because the H2 database would become locked.