Action Contracts Behaviour

Data Actions
1

Hello everyone, just wanted to ask a very simple question but has been bugging me for quite a while now.

While creating Action Contracts for Data Actions I always set the body to a specific arrangement of fields for easier readability as related fields will be right next to each other. However, after saving and re-loading that Data Action Purecloud somehow jumbles up the body that makes the fields to be all over the place.

Is there a reason why this happens that I'm not aware of? Yes, the Data Action still run fine but it's just a pain to look at the configuration especially with those having lots of fields involved.

2

Can you post an example of a body that gets rearranged after saving?

3

Hi Jason,

It happens on several data actions that we made recently, we would save the body as follows:

 {
  "$schema": "http://json-schema.org/draft-04/schema#",
  "title": "Coles GCR Test - Check Balance Request Schema",
  "description": "Request Schema under testing",
  "type": "object",
  "required": [
    "RequestType",
    "viiUserName",
    "viiPassword",
    "viiTranId",
    "StoreId",
    "CardNumber",
    "PIN"
  ],
  "properties": {
    "RequestType": {
      "type": "string"
    },
    "viiUserName": {
      "type": "string"
    },
    "viiPassword": {
      "type": "string"
    },
    "viiTranId": {
      "type": "string"
    },
    "StoreId": {
      "type": "string"
    },
    "AIIC": {
      "type": "string"
    },
    "CATI": {
      "type": "string"
    },
    "CAIC": {
      "type": "string"
    },
    "CardNumber": {
      "type": "string"
    },
    "PIN": {
      "type": "string"
    }
  }
}

However, upon reloading it would revert to this arrangement:

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "title": "Coles GCR Test - Check Balance Request Schema",
  "description": "Request Schema under testing",
  "type": "object",
  "required": [
    "RequestType",
    "viiUserName",
    "viiPassword",
    "viiTranId",
    "StoreId",
    "CardNumber",
    "PIN"
  ],
  "properties": {
    "CardNumber": {
      "type": "string"
    },
    "StoreId": {
      "type": "string"
    },
    "PIN": {
      "type": "string"
    },
    "CAIC": {
      "type": "string"
    },
    "viiUserName": {
      "type": "string"
    },
    "viiTranId": {
      "type": "string"
    },
    "AIIC": {
      "type": "string"
    },
    "CATI": {
      "type": "string"
    },
    "viiPassword": {
      "type": "string"
    },
    "RequestType": {
      "type": "string"
    }
  }
}
4

Thank you for the example! I reproduced the issue and created an internal ticket of BPIVR-1620 for it. Because priorities can change at any time I can't say if or when this will be fixed.

--Jason

5

No problem Jason, thanks for looking into it! :slight_smile:

6

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.