Variable Renaming and Initialization

Some organization might want to rename variables in bulk for all processes upon migration, or create new variables entirely in order to fit a new framework for their organization.

Variable Renaming and Initialization mapping template.pdf

- RPA Framework Mapping.csv
- Mapping Sheet with Example Data.csv - Mapping Sheet with Environment variable.csv
Note:
- Only csv file format is accepted
- Not all columns need to be filled out for each mapping use case

Using Rules Table

Variable based rules cannot be created via the Rules Table. These rules must be created using the CSV and then in some instances they can be modified using the Rules Table.

Using CSV

Export CSV

To start using the CSV Rules sheet, the user must export the Rules table to CSV. To do so, from the Rules Table, click Advanced -> Export Rules to CSV

Because this type of mapping is user driven, the CSV export will not have a row representing these Rule opportunities. The user will have to fill in all necessary rows.

Configure Rules

For Variable Name Conversion, accepted formatting is:

Column A ("ScopeId") = Scope for Rule. Blank implies Instance level
Column G ("SourceActionName") = VARIABLE_CONVERSION
Column L ("TargetActionName")= VARIABLE_CONVERSION
Column N ("SourceParameterName")= Name of variable in source file
Column R ("TargetParameterName")= Desired renaming
Column Y ("IsActive") = TRUE

To Initialize Variables:

All variables initialized in this way will be created in the highest available scope of the process so it can be accessible throughout.

Format for mapping sheet is:

Column A ("ScopeId") = Scope for Rule. Blank implies Instance level
Column G ("SourceActionName") = VARIABLE_INITIALIZATION
Column L ("TargetActionName") = VARIABLE_INITIALIZATION
Column R ("TargetParameterName") = Desired variable name
Column S ("TargetParameterDataType")
- For PAD Exports
  - Leave blank, as PAD auto determines variable type based on context.
- For UiPath Exports, only the following variable types are accepted:
  - String
  - Double
  - Decimal
  - Boolean
  - DateTime
  - DataTable
  - Byte
  - Bitmap
Column X ("DefaultValue")
- For UiPath - Values should be a valid VB expression
Column Y ("IsActive") = TRUE

To Initialize Environment Variables:

Format for mapping sheet is:

Column A ("ScopeId") = Scope for Rule. Blank implies Instance level
Column B ("SourceActionType") = ENVIRONMENT_VARIABLE
Column C ("TargetActionType") = ENVIRONMENT_VARIABLE
Column G ("SourceParameterName") = Name of the variable in the source file
Column X ("DefaultValue") = Desirable Variable Value
Column Y ("IsActive") = Set to TRUE to map the values

To Transform Variables

Fill in the following columns:

Column Q ("SourceParameterValue") = Variable value to transform
Column U ("TargetParameterValue") = Value to change to

Map Variable Enumerations

For variables that take values from an enumerated list, you can define how each valid value in the source RPA tool will convert to a value in the target RPA tool. You do this by providing the list of valid values for the source RPA tool, and the corresponding list of valid values for the target RPA tool (PAD). The conversion will be based on position in the list (e.g. value in 4th position in source list will convert to value in 4th postion in target list). Note that the lists must be of equal length.