Currently for a "rename and move" action, it is not possible to apply an operation on the CollectionPaths field in a user-defined wildcard.
For example, let's say I have this configuration:

and these wildcards:

{
  "1": {
    "default": {
      "field": "title",
      "operations": [
        {
          "function": "replace",
          "regex": "[\\:|\\,|\\.]",
          "replacement": ""
        },
        {
          "function": "replace",
          "regex": "[\\']",
          "replacement": "_"
        }
      ]
    }
  },
  "2": {
    "default": {
      "field": "collectionPaths",
      "operations": [
        {
          "function": "replace",
          "regex": "[\\s]",
          "replacement": "_"
        }
      ]
    }
  }
}

Normally with the wildcard number 2, it is expected that the attached file that is in the collection 3_Resources/Economics Finance Business and Management/Business and Management/Management and Management Techniques/Knowledge Management will be renamed and then moved to the folder<root>/3_Resources/Economics_Finance_Business_and_Management/Business_and_Management/Management_and_Management_Techniques/Knowledge_Management by replacing the spaces by _.

Here, in pictures, the structure of the collections and the expected result:

However, since the function wildcardTable(item) function in wildcards.js expects to work only with fields containing strings and not objects (as is the case with the CollectionPaths field, which is an array), the replace is not a function error occurred. This patch fixes that.