June 2024

List now supports function AddRandomIfEmpty which will allow creating random objects to the list. It can be used like below:

lstExistingModelName.AddRandomIfEmpty<>(10, New Namespace.ModelName())
or
lstExistingModelName.AddRandomIfEmpty<>(10, New Namespace.Modelname With

)

Click on the diagram button on the rule set version

And the selected diagram will be displayed

If you wish to search for data with null values simply use the reserved word ‘null’ - the query will switch to using ‘is null’ SQL constructs. The same is true for ‘not null’

Note that the query will change to is null or is not null only, any other data mapping will be replaced, for example Greater than etc.

When you create the search form you can include a new parameter to include the ability to return the columns you used in the search to the summary screen and allocateddata.xlsx. So for example, find accounts where the number_of_sales >= 100 - Would return acct_no=743, number_of_sales=150

There is now an ability to verify - compile and resolve a rule set version from within the data activity.

There is a new option: Run Validate and Preview.

This will in effect compile and resolve the rule set version.

Each of the cells has various statuses - not checked, error, and valid

When you run the preview if there are any errors they will display in the job status:

And you can see the error in the rule set version editor:

If there are no compile errors the preview will display a sample of data in the job status plus create csvs for each table:

The rule set version cell will display:

When selecting sequential in list selector, 3 options:

Start from top (first row)
Randomly select rows
Dynamically offset (Starts from a random row)
-----------------------------------------------------------------------------
Accelerator to Create Parameter from any table within definition and select a column from it.
-----------------------------------------------------------------------------
When creating soft keys, auto populate name.

On foreign key panel on rule set, add buttons to:

Select random value from the generated parent items
Select sequential value from the generated parent items
-----------------------------------------------------------------------
Add to rule set table view warning icon if more than one FK is active
-----------------------------------------------------------------------
Load any tables from selected table in Data Painter

As an alternative to creating a “Process Model” list to drive subset processing you can now create a Subset Rule Set.

 Attach a Definition Version to your Activity and from the Actions dropdown select “Create New Rule Set” and click on the execute button.

 Once a Rule Set has been created you can modify it to select the tables included in the subset and define them as “Driving”, “Subset” or “Reference” tables. 

If you set a table as a Driving table you can then select it and add a driving condition. 

The Foreign Key Rules section of the Rule Set allows you to active or de-activate foreign key relationships from a parent to a child or a child to a parent 

 Once the Subset Rule Set has been created and edited you can create a submit form and run the subset processing from that.

Throughout the data generation where the data painter or column names are displayed, the data type and more details about the column are displayed making it easier to create the data you need. If there has been a deep analysis performed then that can be easily viewed.

The rule defaults allow you to easily make mass edits for data generation and masking. There are a number of standard defaults shipped s standard. You can now copy any of the standard or other groups of default edits, this allows the user to use the prior work and customize it for your own purposes.

The search and reserve now has 4 new operators.

Not Contains
Not Starts With
Ends With
Not Ends With

If you edit the find submit form.

Change the data type to String and switch the UI Type to Range

The Screen will prompt you for a minimum and maximum range

This will convert the SQL query to use a >= and <=

For example: ("order_count" >= 1 and "order_count" <= 3)

When generating or subsetting data, the load order is important to ensure that parent tables get loaded prior to child tables. This avoids having to drop/disable foreign keys. The rule set version will now be created with the load order automatically calculated. You can also disable and enable foreign keys and recalculate the load order from the actions menu in the rule set version.

You can apply defaults to multiple rule set versions in one pass. You can do this for either all of the rule set versions in a rule set OR for all rule set versions being used in a pipeline

A starter set of defaults are now shipped as standard, these contain a series of useful and example types of defaults that can be applied to the generation and masking rule sets.

They are displayed in blue - they cannot be edited but they can be copied.

Te defauls - the ability to mass find and apply changes to the generation, masking and defintion has been significantly improved.

You can now have multiple sets of default rules.

There a number of standard default rules applied.

You can have multiple rule set find and changes.

The search capability has been significantly improved.

The type of attributes and objects has been significantly improved.

There is also the ability to look at the current value and select where that value came from.

This allows for very sophisticated mass changes to be made across multiple test data activities.

Once the find has been run, the old and potential new change will be displayed.

You can selectively filter on these results and choose which cells you wish to apply any changes to.

The ability to declare variable for each Parameter Row Scope has been added