Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
JSON from Symitar Core with SymConnect

All of our existing extensions have expected and used XML data returned from our Symitar Core using SymConnect. We were curious if returning JSON instead would cause any issues with the Q2 platform's receipt of the data.

For example:

XML:

<MORTGAGE>
  <META>
    <COUNT>6</COUNT>
    <STATUS>COMPLETE</STATUS>
  </META>
  <STAGES>
    <STAGE>
      <LABEL>APPLICATION RECEIVED</LABEL>
      <DATE>02/22/2021</DATE>
      <STATUS>TRUE</STATUS>
      <COMMENT>APPLICATION RECEIVED</COMMENT>
      <ORDER>0</ORDER>
    </STAGE>
    <STAGE>
      <LABEL>APPRAISAL ORDERED</LABEL>
      <DATE>03/24/2021</DATE>
      <STATUS>TRUE</STATUS>
      <COMMENT>APPRAISAL ORDERED LETTER SENT</COMMENT>
      <ORDER>1</ORDER>
    </STAGE>
    <STAGE>
      <LABEL>APPLICATION IN UNDERWRITING</LABEL>
      <DATE>03/24/2021</DATE>
      <STATUS>TRUE</STATUS>
      <COMMENT>APPRAISAL RECEIVED EMAIL SENT</COMMENT>
      <ORDER>2</ORDER>
    </STAGE>
    <STAGE>
      <LABEL>APPLICATION APPROVED/APPLICATION SENT TO CREDIT UNION ATTORNEY</LABEL>
      <DATE>03/24/2021</DATE>
      <STATUS>TRUE</STATUS>
      <COMMENT>TO ATTORNEY EMAIL SENT</COMMENT>
      <ORDER>3</ORDER>
    </STAGE>
    <STAGE>
      <LABEL>APPLICATION NOT CLEARED TO CLOSE. CONTACT YOUR MORTGAGE INTERVIEWER.</LABEL>
      <DATE>--/--/----</DATE>
      <STATUS>FALSE</STATUS>
      <COMMENT></COMMENT>
      <ORDER>4</ORDER>
    </STAGE>
    <STAGE>
      <LABEL>MORTGAGE COMPLETE</LABEL>
      <DATE>02/24/2021</DATE>
      <STATUS>TRUE</STATUS>
      <COMMENT>LOAN DENIED</COMMENT>
      <ORDER>5</ORDER>
    </STAGE>
  </STAGES>
</MORTGAGE>

vs JSON:

{
  "META": {
    "COUNT": 6,
    "STATUS": "COMPLETE"
  },
  "STAGES": [
    {
      "LABEL": "APPLICATION RECEIVED",
      "DATE": "02/22/2021",
      "STATUS": "TRUE",
      "COMMENT": "APPLICATION RECEIVED",
      "ORDER": 0
    },
    {
      "LABEL": "APPRAISAL ORDERED",
      "DATE": "03/24/2021",
      "STATUS": "TRUE",
      "COMMENT": "APPRAISAL ORDERED LETTER SENT",
      "ORDER": 1
    },
    {
      "LABEL": "APPLICATION IN UNDERWRITING",
      "DATE": "03/24/2021",
      "STATUS": "TRUE",
      "COMMENT": "APPRAISAL RECEIVED EMAIL SENT",
      "ORDER": 2
    },
    {
      "LABEL": "APPLICATION APPROVED/APPLICATION SENT TO CREDIT UNION ATTORNEY",
      "DATE": "03/24/2021",
      "STATUS": "TRUE",
      "COMMENT": "TO ATTORNEY EMAIL SENT",
      "ORDER": 3
    },
    {
      "LABEL": "APPLICATION NOT CLEARED TO CLOSE. CONTACT YOUR MORTGAGE INTERVIEWER.",
      "DATE": "--/--/----",
      "STATUS": "FALSE",
      "COMMENT": "",
      "ORDER": 4
    },
    {
      "LABEL": "MORTGAGE COMPLETE",
      "DATE": "02/24/2021",
      "STATUS": "TRUE",
      "COMMENT": "LOAN DENIED",
      "ORDER": 5
    }
  ]
}

Thanks!

Posted 4 years ago
Votes Newest

Answers


Hey Dan, good question!

No issue on the Q2 platform side. The SDK will parse the SymConnect response the same way with the raw JSON within property payload on type SymConnectMessage. Once you get that you can easily json.loads(response.payload) to get it into a working dict.

Posted 4 years ago
Jason Herbert
104 × 1 Administrator
0

Thanks, Jason!

— Dan Collins   4 years ago
137 Views
1 Answer
4 years ago
4 years ago
Tags