Introduction:
With the release of version 1.1 of OpenAmplify's API, we encourage any developers with existing applications to migrate to the new version of the API. Migrating an existing application is simple. To use version 1.1 of the API, point your application at
http://portaltnx.openamplify.com/AmplifyWeb_v11/AmplifyThis
While the new API includes a lot of changes, only a short list of changes are likely to cause hiccups for existing applications.
Possible Hiccups:
<ActionResults>
In version 1.0 the <ActionResults> node is nested inside the <Scores> tag.
In version 1.1 <ActionResults> is nested within <TopActions>
<Temporality> and <TemporalityResult>
For the sake of conformity throughout our returned XML, OpenAmplify has switched the nesting order of <Temporality> and <TemporalityResult>.
In version 1.0 the data for temporality information are found inside <TemporalityResult>, which in turn is nested inside <Temporality> ( Temporality --> TemporalityResult).
In version 1.1, temporality data are inside the <Temporality> tag, which is nested within <TemporalityResult> (TemporalityResult --> Temporality)
Qualify the Root of Your XPath Queries
If you set Analysis to all OpenAmplify will return the new TopicIntention node as well as the Topic node. The newly added TopicIntention node contains duplicates of the Topic nodes augmented with Action nodes. The upshot is that a query for //Topic may return twice as many topics as you expect unless you qualify your roots.
As an example, if you update an xPath query designed to return Topics to read //Topics/Topic or //TopicIntentions/Topic you will get the results you expect
Support and Questions: