About Data Generation Pattern Syntax

This feature is currently available only to customers participating in a private preview. If you'd like to participate to be among the first to try this feature, ask our support or account team for details.

A pattern is used to generate data dynamically by grabbing data from entity fields, using lookups (mapping tables), or using keywords like “appshortname” or “increment” to increment for unique fields.

Below, we define general syntax for patterns you can use to generate data.

Fields and values are NOT case-sensitive.

For information on creating and managing a data generation rule, see Data Generation Rules.

General Syntax

Be sure to wrap every substitution with double curly brackets “{{}}”; otherwise, the literal value will be used to generate the data.

{{fieldName}} => grabs value from that field name
Literal Value => Literal Value

Keywords

{{appshortname}} => Delinea
{{yyyy}} => 2006 //current date year
{{yy}} => 06 //current date year
{{mm}} => 10 //current date month
{{dd}} => 31 //current date day

Field Substitutions

Only the Identity object type is supported at this time, so only identity fields will work. And only Text, LongText fields can be used to generate data.

{{fieldName}} => value for field name
{fieldName[0]}} => value for field name at index 0 (must be an array of string values)

Lookup Substitutions

Lookups have three main parts. First, they are prefixed with the keyword “lookup.” Then, they are followed by the mapping table name (spaces must be used if the mapping table name has spaces) and, finally, the row key.

The row key can be followed by an index for mapping tables that have rows with more than one value per row.

{{lookup.tableName.rowKey}} => The value for the given mapping table at the given row.
{{lookup.tableName.rowKey[2]}} => The value at index 2 for the given mapping table at the given row.

Lookup Reference Substitutions

Lookup references operate the same as lookups in that they can use mapping tables, but instead of providing an explicit row key value, you can use a field on the entity to grab a row key dynamically. They are also prefixed with lookupref instead of lookup.

{{lookupref.tableName.fieldName}} => The value for the given mapping table at the given row. The Row key is generated from the value in fieldName.
{{lookupref.tableName.fieldName[2]}} => The value at index 2 for the given mapping table at the given row.

Modifiers

This section lists the modifiers that you can add to your syntax to generate values.

Character Length

You can specify the maximum number of characters you want to grab from a field or lookup value.

In the event that the value is less than the provided character length, it will grab the entire value.

{{fieldName:3}} => Retrieves only the first 3 characters.
{{lookup.tableName.rowKey:3}} => Retrieves only the first 3 characters.
{{lookup.tableName.fieldName:3}} => Retrieves only the first 3 characters.

Increment

The number provided with the increment substitution will specify the number of places that will be generated. For example, “1” will start at “1” and increment up to “9”, “2” will start at “01” and increment up to “99”, etc.

This will only increment for fields that have the unique property equal to true.

{{increment:3}} => starts at 001 and goes up to 999