TODO, Error, and Robin Mapping

Updated by Luka Koczorowski

If a user finds that they have a common TODO or Error across many exported bots, they can configure a global fix during export to avoid having to repair bots one by one. Also, in certain situations if a user isn't happy with particular output from Blueprint, they can override the exports behaviour.

Using Rules Dashboard

Code replace rules cannot be created using the Rules dashboard they can only be edited. Once a rule is created using the CSV mapping sheet, the original code and substitute code can be modified as seen below:

Using 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.

Fill in the following columns:

  • Column A ("ScopeId") = Scope for Rule. Blank implies Instance level
  • Column B ("SourceActionType") = RUN_ROBINSCRIPT
  • Column C ("TargetActionType") = RUN_ROBINSCRIPT
  • Column H ("SourceActionSelector")  = TODO/ERR/Robin to replace
  • Column M ("TargetActionSelector")  = New Robin code
  • Column Y ("IsActive") = TRUE

Example

Here is a sample export with TODO messages

Using the mapping below

Will result with the following export

How did we do?