Enhancement request: Support for Special Characters in JSON keys/names

Currently, if the key name in a json key/value pair contains a special character (e.g. periods/dots, colons, hyphens) the data pills are broken as a result and the core use case of using Workato to pass data between steps is broken.

We've had to work around this with a custom connector that replaces the special characters in the schema generators JSON and the JSON in the API response.

Business Case: some APIs, especially ones based on standard schemas like SCIM, have special characters in their key names. Having to work around this every time with a custom connector introduces brittleness and some user confusion into the recipe development process.

Example from: https://developer.atlassian.com/cloud/admin/user-provisioning/rest/#api-scim-directory-directoryId-Users-post 

{

  "schemas": [

    "<string>"

  ],

  "userName": "<string>",

  "emails": [

    {

      "value": "<string>",

      "type": "<string>",

      "primary": true

    }

  ],

  "id": "<string>",

  "externalId": "<string>",

  "name": {

    "formatted": "<string>",

    "familyName": "<string>",

    "givenName": "<string>",

    "middleName": "<string>",

    "honorificPrefix": "<string>",

    "honorificSuffix": "<string>"

  },

  "displayName": "<string>",

  "nickName": "<string>",

  "title": "<string>",

  "preferredLanguage": "<string>",

  "department": "<string>",

  "organization": "<string>",

  "timezone": "<string>",

  "phoneNumbers": [

    {

      "value": "<string>",

      "type": "<string>",

      "primary": true

    }

  ],

  "meta": {

    "resourceType": "USER",

    "location": "<string>",

    "lastModified": "<string>",

    "created": "<string>"

  },

  "groups": [

    {

      "type": "<string>",

      "value": "<string>",

      "display": "<string>",

      "$ref": "<string>"

    }

  ],

  "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {

    "organization": "<string>",

    "department": "<string>"

  },

  "urn:scim:schemas:extension:atlassian-external:1.0": {

    "atlassianAccountId": "<string>"

  },

  "active": true

}